From fd605f6974233e4ef93cc96bfd8e4ca10ed78765 Mon Sep 17 00:00:00 2001 From: JanKeller1 Date: Mon, 22 Aug 2016 10:21:24 -0700 Subject: [PATCH] Scrubbed some more links --- windows/manage/appv-client-configuration-settings.md | 2 +- .../appv-deploying-microsoft-office-2010-wth-appv.md | 4 ++-- ...appv-deploying-microsoft-office-2013-with-appv.md | 4 ++-- ...appv-migrating-to-appv-from-a-previous-version.md | 2 +- windows/manage/appv-reporting.md | 2 +- windows/manage/appv-technical-reference.md | 12 +++--------- 6 files changed, 10 insertions(+), 16 deletions(-) diff --git a/windows/manage/appv-client-configuration-settings.md b/windows/manage/appv-client-configuration-settings.md index db1627343f..7fe953302b 100644 --- a/windows/manage/appv-client-configuration-settings.md +++ b/windows/manage/appv-client-configuration-settings.md @@ -48,7 +48,7 @@ The following table provides information about App-V client configuration settin | **RoamingRegistryExclusions**
String | Specifies the registry paths that do not roam with a user profile. Example usage: /ROAMINGREGISTRYEXCLUSIONS=software\\classes;software\\clients | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written (same as Not Configured) | | **IntegrationRootUser**
String | Specifies the location to create symbolic links associated with the current version of a per-user published package. all virtual application extensions, for example shortcuts and file type associations, will point to this path. If you do not specify a path, symbolic links will not be used when you publish the package. For example: %localappdata%\\Microsoft\\AppV\\Client\\Integration. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written (same as Not Configured) | | **IntegrationRootGlobal**
String | Specifies the location to create symbolic links associated with the current version of a globally published package. all virtual application extensions, for example shortcuts and file type associations, will point to this path. If you do not specify a path, symbolic links will not be used when you publish the package. For example: %allusersprofile%\\Microsoft\\AppV\\Client\\Integration | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written (same as Not Configured) | -| **VirtualizableExtensions**
String | A comma -delineated list of file name extensions that can be used to determine if a locally installed application can be run in the virtual environment. When shortcuts, FTAs, and other extension points are created during publishing, App-V will compare the file name extension to the list if the application that is associated with the extension point is locally installed. If the extension is located, the **RunVirtual** command line parameter will be added, and the application will run virtually. For more information about the **RunVirtual** parameter, see [Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications](https://microsoft.sharepoint.com/teams/osg_core_dcp/cpub/partner/Shared%20Documents/APPV&UEV-for-Windows-RS1/App-V/App-V%20updated%20topics%20from%20JAN%20-%20PM%20reviews/appv-running-locally-installed-applications-inside-a-virtual-environment.md). | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written | +| **VirtualizableExtensions**
String | A comma -delineated list of file name extensions that can be used to determine if a locally installed application can be run in the virtual environment. When shortcuts, FTAs, and other extension points are created during publishing, App-V will compare the file name extension to the list if the application that is associated with the extension point is locally installed. If the extension is located, the **RunVirtual** command line parameter will be added, and the application will run virtually. For more information about the **RunVirtual** parameter, see [Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications](appv-running-locally-installed-applications-inside-a-virtual-environment.md). | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written | | **ReportingEnabled**
True (enabled); False (Disabled state) | Enables the client to return information to a reporting server. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | False | | **ReportingServerURL**
String | Specifies the location on the reporting server where client information is saved. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written (same as Not Configured) | | **ReportingDataCacheLimit**
Integer \[0-1024\] | Specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The size applies to the cache in memory. When the limit is reached, the log file will roll over. Set between 0 and 1024. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written (same as Not Configured) | diff --git a/windows/manage/appv-deploying-microsoft-office-2010-wth-appv.md b/windows/manage/appv-deploying-microsoft-office-2010-wth-appv.md index 53acc5a3c3..dcf42974b4 100644 --- a/windows/manage/appv-deploying-microsoft-office-2010-wth-appv.md +++ b/windows/manage/appv-deploying-microsoft-office-2010-wth-appv.md @@ -282,10 +282,10 @@ The following table provides a full list of supported integration points for Off **Connection Groups** -[Deploying Connection Groups in Microsoft App-V v5](https://blogs.technet.microsoft.com/appv/2012/11/06/deploying-connection-groups-in-microsoft-app-v-v5/) - [Managing Connection Groups](appv-managing-connection-groups.md) +[Connection groups on the App-V team blog](https://blogs.technet.microsoft.com/gladiatormsft/tag/connection-groups/) + **Dynamic Configuration** [About App-V Dynamic Configuration](appv-dynamic-configuration.md) diff --git a/windows/manage/appv-deploying-microsoft-office-2013-with-appv.md b/windows/manage/appv-deploying-microsoft-office-2013-with-appv.md index b826ee3db2..90cdcd48d7 100644 --- a/windows/manage/appv-deploying-microsoft-office-2013-with-appv.md +++ b/windows/manage/appv-deploying-microsoft-office-2013-with-appv.md @@ -767,10 +767,10 @@ This section describes the requirements and options for deploying Visio 2013 and **Connection Groups** -[Deploying Connection Groups in Microsoft App-V v5](https://blogs.technet.microsoft.com/appv/2012/11/06/deploying-connection-groups-in-microsoft-app-v-v5/) - [Managing Connection Groups](appv-managing-connection-groups.md) +[Connection groups on the App-V team blog](https://blogs.technet.microsoft.com/gladiatormsft/tag/connection-groups/) + **Dynamic Configuration** [About App-V Dynamic Configuration](appv-dynamic-configuration.md) diff --git a/windows/manage/appv-migrating-to-appv-from-a-previous-version.md b/windows/manage/appv-migrating-to-appv-from-a-previous-version.md index a6f1b76219..4c4578b787 100644 --- a/windows/manage/appv-migrating-to-appv-from-a-previous-version.md +++ b/windows/manage/appv-migrating-to-appv-from-a-previous-version.md @@ -255,4 +255,4 @@ Add or vote on suggestions on the [Application Virtualization feedback site](htt - [Operations for App-V](appv-operations.md) -- [A simplified Microsoft App-V Management Server upgrade procedure](http://go.microsoft.com/fwlink/p/?LinkId=786330) +- [A simplified Microsoft App-V 5.1 Management Server upgrade procedure](https://blogs.technet.microsoft.com/appv/2015/09/23/a-simplified-microsoft-app-v-5-1-management-server-upgrade-procedure/) diff --git a/windows/manage/appv-reporting.md b/windows/manage/appv-reporting.md index f5547a3821..0aced8808d 100644 --- a/windows/manage/appv-reporting.md +++ b/windows/manage/appv-reporting.md @@ -292,7 +292,7 @@ To retrieve report information and create reports using App-V you must use one o **spProcessClientReport** is scheduled to run at midnight or 12:00 AM. - To run the Microsoft SQL Server Scheduled Stored procedure, the Microsoft SQL Server Agent must be running. You should ensure that the Microsoft SQL Server Agent is set to **AutoStart**. For more information see [Autostart SQL Server Agent (SQL Server Management Studio)](http://go.microsoft.com/fwlink/?LinkId=287045). + To run the Microsoft SQL Server Scheduled Stored procedure, the Microsoft SQL Server Agent must be running. You should ensure that the Microsoft SQL Server Agent is set to **AutoStart**. For more information see [Autostart SQL Server Agent (SQL Server Management Studio)](https://technet.microsoft.com/library/ms178130). The stored procedure is also created when using the App-V database scripts. diff --git a/windows/manage/appv-technical-reference.md b/windows/manage/appv-technical-reference.md index 77a442d258..692da1bf49 100644 --- a/windows/manage/appv-technical-reference.md +++ b/windows/manage/appv-technical-reference.md @@ -42,14 +42,8 @@ Add or vote on suggestions on the [Application Virtualization feedback site](htt ## Related topics +[How to Deploy the App-V Databases by Using SQL Scripts](appv-deploy-appv-databases-with-sql-scripts.md) -[Creating App-V 4.5 Databases Using SQL Scripting](https://technet.microsoft.com/en-us/itpro/mdop/solutions/creating-app-v-45-databases-using-sql-scripting) - -  - -  - - - - +[Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md) +[Windows PowerShell reference for App-V](https://technet.microsoft.com/en-us/library/dn903534.aspx)