mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 19:03:46 +00:00
updates
This commit is contained in:
Siddarth Mandalika
@ -62,7 +62,7 @@ Use the information in the following section for more information:
|
||||
|
||||
[User Experience Walk-through](#bkmk-uewt)
|
||||
|
||||
- Walk-through – It is a step-by-step walk-through of the App-V and UE-V operations and the expectations users should have.
|
||||
- Walk-through – It's a step-by-step walk-through of the App-V and UE-V operations and the expectations users should have.
|
||||
|
||||
- Outcome – It describes the expected results.
|
||||
|
||||
@ -93,7 +93,7 @@ As you review the two scenarios, keep in mind that these scenarios represent the
|
||||
|
||||
- **Performance**: To provide the most optimal user experience, this approach uses the capabilities of a UPM solution and requires extra image preparation and can incur some more image management overhead.
|
||||
|
||||
The following describes many performance improvements in stateful non-persistent deployments. For more information, see [Sequencing Steps to Optimize Packages for Publishing Performance](#sequencing-steps-to-optimize-packages-for-publishing-performance) (in this article).
|
||||
The following section describes many performance improvements in stateful non-persistent deployments. For more information, see [Sequencing Steps to Optimize Packages for Publishing Performance](#sequencing-steps-to-optimize-packages-for-publishing-performance) (in this article).
|
||||
|
||||
- **Storage**: The general expectations of the previous scenario still apply here. However, keep in mind that VM images are typically stored in costly arrays; a slight alteration has been made to the approach. Don't pre-configure user-targeted virtual application packages in the base image.
|
||||
|
||||
@ -177,7 +177,7 @@ For more information, see:
|
||||
In essence all that is required is to enable the UE-V service and download the following Microsoft authored App-V settings template from the [Microsoft User Experience Virtualization (UE-V) template gallery](https://gallery.technet.microsoft.com/Authored-UE-V-Settings-bb442a33). Register the template. For more information about UE-V templates, see [User Experience Virtualization (UE-V) for Windows client overview](/windows/configuration/ue-v/uev-for-windows).
|
||||
|
||||
> [!Note]
|
||||
> Without performing an additional configuration step, User Environment Virtualization (UE-V) will not be able to synchronize the Start menu shortcuts (.lnk files) on the target computer. The .lnk file type is excluded by default.
|
||||
> Without performing an additional configuration step, User Environment Virtualization (UE-V) won't be able to synchronize the Start menu shortcuts (.lnk files) on the target computer. The .lnk file type is excluded by default.
|
||||
|
||||
UE-V will only support removing the .lnk file type from the exclusion list in the RDS and VDI scenarios, where every user’s device will have the same set of applications installed to the same location and every .lnk file is valid for all the users’ devices. For example, UE-V wouldn't currently support the following two scenarios, because the net result will be that the shortcut will be valid on one but not all devices.
|
||||
|
||||
@ -208,13 +208,13 @@ To enable an optimized sign-in experience, for example the App-V approach for th
|
||||
>
|
||||
> App-V is supported when using UPD only when the entire profile is stored on the user profile disk.
|
||||
>
|
||||
> App-V packages are not supported when using UPD with selected folders stored in the user profile disk. The Copy on Write driver does not handle UPD selected folders.
|
||||
> App-V packages are not supported when using UPD with selected folders stored in the user profile disk. The Copy on Write driver doesn't handle UPD selected folders.
|
||||
|
||||
- Capturing changes to the locations, which constitute the user integrations, prior to session sign out.
|
||||
|
||||
With App-V when you add a publishing server (**Add-AppvPublishingServer**) you can configure synchronization, for example refresh during log on and/or after a specified refresh interval. In both cases, a scheduled task is created.
|
||||
With App-V when you add a publishing server (**Add-AppvPublishingServer**) you can configure synchronization, for example refresh during a sign in and/or after a specified refresh interval. In both cases, a scheduled task is created.
|
||||
|
||||
In previous versions of App-V, both scheduled tasks were configured using a VBScript that would initiate the user and global refresh. Starting with Hotfix Package 4 for Application Virtualization 5.0 SP2 the user refresh on log on was initiated by **SyncAppvPublishingServer.exe**. This change was introduced to provide UPM solutions a trigger process. This process delays the publish /refresh to allow the UPM solution to apply the user integrations. It will exit once the publishing/refresh is complete.
|
||||
In previous versions of App-V, both scheduled tasks were configured using a VBScript that would initiate the user and global refresh. Starting with Hotfix Package 4 for Application Virtualization 5.0 SP2, the user refresh on a sign in was initiated by **SyncAppvPublishingServer.exe**. This change was introduced to provide UPM solutions a trigger process. This process delays the publish /refresh to allow the UPM solution to apply the user integrations. It will exit once the publishing/refresh is complete.
|
||||
|
||||
### User Integrations
|
||||
|
||||
@ -253,32 +253,32 @@ This following process is a step-by-step walk-through of the App-V and UPM opera
|
||||
- **Performance**: After implementing this approach in the VDI/RDSH environment, on first login,
|
||||
- (Operation) A user-publishing/refresh is initiated.
|
||||
|
||||
(Expectation) If it's the first time that a user has published virtual applications (for example, non-persistent), this will take the usual duration of a publishing/refresh.
|
||||
(Expectation) If it's the first time that a user has published virtual applications (for example, non-persistent), this operation will take the usual duration of a publishing/refresh.
|
||||
|
||||
- (Operation) After the publishing/refresh, the UPM solution captures the user integrations.
|
||||
|
||||
(Expectation) Depending on how the UPM solution is configured, this may occur as part of the logoff process. This will incur the same/similar overhead as persisting the user state.
|
||||
(Expectation) Depending on how the UPM solution is configured, this capture may occur as part of the sign-out process. This result will incur the same/similar overhead as persisting the user state.
|
||||
|
||||
**On subsequent logins**:
|
||||
|
||||
- (Operation) UPM solution applies the user integrations to the system prior to publishing/refresh.
|
||||
|
||||
(Expectation) There will be shortcuts present on the desktop, or in the start menu, which work immediately. When the publishing/refresh completes (i.e., package entitlements change), some may go away.
|
||||
(Expectation) There will be shortcuts present on the desktop, or in the start menu, which work immediately. When the publishing/refresh completes (that is, package entitlements change), some may go away.
|
||||
|
||||
- (Operation) Publishing/refresh will process un-publish and publish operations for changes in user package entitlements.
|
||||
- (Operation) Publishing/refresh will process unpublish and publish operations for changes in user package entitlements.
|
||||
|
||||
(Expectation) If there are no entitlement changes, publishing will complete in seconds. Otherwise, the publishing/refresh will increase relative to the number and complexity of virtual applications
|
||||
|
||||
The publishing operation (**Publish-AppVClientPackage**) adds entries to the user catalog, maps entitlement to the user, identifies the local store, and finishes by completing any integration steps.
|
||||
|
||||
- (Operation) UPM solution will capture user integrations again at logoff.
|
||||
- (Operation) UPM solution will capture user integrations again at sign off.
|
||||
|
||||
(Expectation) Same as previous.
|
||||
|
||||
**Outcome**:
|
||||
|
||||
- Because the user integrations are entirely preserved, there will be no work for example, integration for the publishing/refresh to complete. All virtual applications will be available within seconds of login.
|
||||
- The publishing/refresh will process changes to the users entitled virtual applications which impacts the experience.
|
||||
- Because the user integrations are entirely preserved, there will be no work for example, integration for the publishing/refresh to complete. All virtual applications will be available within seconds of sign in.
|
||||
- The publishing/refresh will process changes to the users-entitled virtual applications, which impacts the experience.
|
||||
|
||||
- **Storage**: After implementing this approach in the VDI/RDSH environment, on first login
|
||||
|
||||
@ -286,12 +286,12 @@ This following process is a step-by-step walk-through of the App-V and UPM opera
|
||||
|
||||
(Expectation):
|
||||
|
||||
- If this is the first time a user has published virtual applications (for example, non-persistent), this will take the usual duration of a publishing/refresh.
|
||||
- If this instance is the first time a user has published virtual applications (for example, non-persistent), this will take the usual duration of a publishing/refresh.
|
||||
- First and subsequent logins will be impacted by pre-configuring of packages (add/refresh).
|
||||
|
||||
- (Operation) After the publishing/refresh, the UPM solution captures the user integrations.
|
||||
|
||||
(Expectation) Depending on how the UPM solution is configured, this may occur as part of the logoff process. This will incur the same/similar overhead as persisting the user state.
|
||||
(Expectation) Depending on how the UPM solution is configured, this capture may occur as part of the sign-off process. This result will incur the same/similar overhead as persisting the user state.
|
||||
|
||||
**On subsequent logins**:
|
||||
|
||||
@ -299,24 +299,24 @@ This following process is a step-by-step walk-through of the App-V and UPM opera
|
||||
- (Operation) Add/refresh must pre-configure all user targeted applications.
|
||||
|
||||
- (Expectation):
|
||||
- This may increase the time to application availability significantly (on the order of 10’s of seconds).
|
||||
- This may increase the time to application availability significantly (on the order of 10s of seconds).
|
||||
- This will increase the publishing refresh time relative to the number and complexity* of virtual applications.
|
||||
|
||||
- (Operation) Publishing/refresh will process un-publish and publish operations for changes to user package entitlements.
|
||||
- (Operation) Publishing/refresh will process unpublish and publish operations for changes to user package entitlements.
|
||||
|
||||
**Outcome**: Because the add/refresh must re-configure all the virtual applications to the VM, the publishing refresh time on every login will be extended.
|
||||
**Outcome**: Because the add/refresh must reconfigure all the virtual applications to the VM, the publishing refresh time on every login will be extended.
|
||||
|
||||
### <a href="" id="bkmk-plc"></a>Impact to Package Life Cycle
|
||||
|
||||
Upgrading a package is a crucial aspect of the package lifecycle. To help guarantee users have access to the appropriate upgraded (published) or downgraded (un-published) virtual application packages, it is recommended you update the base image to reflect these changes. To understand why review the following section:
|
||||
Upgrading a package is a crucial aspect of the package lifecycle. To help guarantee users have access to the appropriate upgraded (published) or downgraded (unpublished) virtual application packages, it's recommended you update the base image to reflect these changes. To understand why review the following section:
|
||||
|
||||
App-V 5.0 SP2 introduced the concept of pending states. In the past,
|
||||
|
||||
- If an administrator changed entitlements or created a new version of a package (upgraded) and during a publishing/refresh that package was in-use, the un-publish or publish operation, respectively, would fail.
|
||||
- If an administrator changed entitlements or created a new version of a package (upgraded) and during a publishing/refresh that package was in-use, the unpublish or publish operation, respectively, would fail.
|
||||
|
||||
- Now, if a package is in-use the operation will be pended. The un-publish and publish-pend operations will be processed on service restart or if another publish or un-publish command is issued. In the latter case, if the virtual application is in-use otherwise, the virtual application will remain in a pending state. For globally published packages, a restart (or service restart) often needed.
|
||||
- Now, if a package is in use, the operation will be pended. The unpublish and publish-pend operations will be processed on service restart or if another publish or unpublish command is issued. In the latter case, if the virtual application is in-use otherwise, the virtual application will remain in a pending state. For globally published packages, a restart (or service restart) often needed.
|
||||
|
||||
In a non-persistent environment, it is unlikely these pended operations will be processed. The pended operations, for example tasks are captured under **HKEY\_CURRENT\_USER** \\ **Software** \\ **Microsoft** \\ **AppV** \\ **Client** \\ **PendingTasks**. Although this location is persisted by the UPM solution, if it isn't applied to the environment prior to log on, it will not be processed.
|
||||
In a non-persistent environment, it's unlikely these pended operations will be processed. The pended operations, for example tasks are captured under **HKEY\_CURRENT\_USER** \\ **Software** \\ **Microsoft** \\ **AppV** \\ **Client** \\ **PendingTasks**. Although this location is persisted by the UPM solution, if it isn't applied to the environment prior to a sign in, it will not be processed.
|
||||
|
||||
### <a href="" id="bkmk-evdi"></a>Enhancing the VDI Experience through Performance Optimization Tuning
|
||||
|
||||
@ -364,11 +364,11 @@ Several App-V features facilitate new scenarios or enable new customer deploymen
|
||||
|
||||
|Step|Consideration|Benefits|Tradeoffs|
|
||||
|--- |--- |--- |--- |
|
||||
|No Feature Block 1 (FB1, also known as Primary FB)|No FB1 means the application will launch immediately and stream fault (application requires file, DLL and must pull down over the network) during launch. If there are network limitations, FB1 will:<br><li>Reduce the number of stream faults and network bandwidth used when you launch an application for the first time.<li>Delay launch until the entire FB1 has been streamed.|Stream faulting decreases the launch time.|Virtual application packages with FB1 configured will need to be re-sequenced.|
|
||||
|No Feature Block 1 (FB1, also known as Primary FB)|No FB1 means the application will launch immediately and stream fault (application requires file, DLL and must pull down over the network) during launch. If there are network limitations, FB1 will:<br><li>Reduce the number of stream faults and network bandwidth used when you launch an application for the first time.<li>Delay launch until the entire FB1 has been streamed.|Stream faulting decreases the launch time.|Virtual application packages with FB1 configured will need to be resequenced.|
|
||||
|
||||
### Removing FB1
|
||||
|
||||
Removing FB1 does not require the original application installer. After completing the following steps, it is suggested that you revert the computer running the sequencer to a clean snapshot.
|
||||
Removing FB1 doesn't require the original application installer. After completing the following steps, it's suggested that you revert the computer running the sequencer to a clean snapshot.
|
||||
|
||||
**Sequencer UI** - Create a New Virtual Application Package.
|
||||
|
||||
@ -405,7 +405,7 @@ Removing FB1 does not require the original application installer. After completi
|
||||
|
||||
|Step|Considerations|Benefits|Tradeoffs|
|
||||
|--- |--- |--- |--- |
|
||||
|No SXS Install at Publish (Pre-Install SxS assemblies)|Virtual Application packages don't need to be re-sequenced. SxS Assemblies can remain in the virtual application package.|The SxS Assembly dependencies will not install at publishing time.|SxS Assembly dependencies must be pre-installed.|
|
||||
|No SXS Install at Publish (Pre-Install SxS assemblies)|Virtual Application packages don't need to be resequenced. SxS Assemblies can remain in the virtual application package.|The SxS Assembly dependencies won't install at publishing time.|SxS Assembly dependencies must be pre-installed.|
|
||||
|
||||
|
||||
### Creating a new virtual application package on the sequencer
|
||||
@ -414,7 +414,7 @@ If, during sequencer monitoring, an SxS Assembly (such as a VC++ Runtime) is ins
|
||||
|
||||
**Client Side**:
|
||||
|
||||
When publishing a virtual application package, the App-V Client will detect if a required SxS dependency is already installed. If the dependency is unavailable on the computer and it is included in the package, a traditional Windows Installer (.**msi**) installation of the SxS assembly will be initiated. As previously documented, simply install the dependency on the computer running the client to ensure that the Windows Installer (.msi) installation will not occur.
|
||||
When publishing a virtual application package, the App-V Client will detect if a required SxS dependency is already installed. If the dependency is unavailable on the computer and it's included in the package, a traditional Windows Installer (.**msi**) installation of the SxS assembly will be initiated. As previously documented, simply install the dependency on the computer running the client to ensure that the Windows Installer (.msi) installation won't occur.
|
||||
|
||||
|Step|Considerations|Benefits|Tradeoffs|
|
||||
|--- |--- |--- |--- |
|
||||
@ -439,8 +439,8 @@ For documentation on How to Apply a Dynamic Configuration, see:
|
||||
|
||||
|Step|Considerations|Benefits|Tradeoffs|
|
||||
|--- |--- |--- |--- |
|
||||
|Account for Synchronous Script Execution during Package Lifecycle.|If script collateral is embedded in the package, Add cmdlets may be significantly slower.<br>Running of scripts during virtual application launch (StartVirtualEnvironment, StartProcess) and/or Add+Publish will impact the perceived performance during one or more of these lifecycle operations.|Use of Asynchronous (Non-Blocking) Scripts will ensure that the lifecycle operations complete efficiently.|This step requires working knowledge of all virtual application packages with embedded script collateral, which have associated dynamic configurations files and which reference and run scripts synchronously.|
|
||||
|Remove Extraneous Virtual Fonts from Package.|The majority of applications investigated by the App-V product team contained a small number of fonts, typically fewer than 20.|Virtual Fonts impact publishing refresh performance.|Desired fonts will need to be enabled/installed natively. For instructions, see Install or uninstall fonts.|
|
||||
|Account for Synchronous Script Execution during Package Lifecycle.|If script collateral is embedded in the package, Add cmdlets may be slower.<br>Running of scripts during virtual application launch (StartVirtualEnvironment, StartProcess) and/or Add+Publish will impact the perceived performance during one or more of these lifecycle operations.|Use of Asynchronous (Non-Blocking) Scripts will ensure that the lifecycle operations complete efficiently.|This step requires working knowledge of all virtual application packages with embedded script collateral, which have associated dynamic configurations files and which reference and run scripts synchronously.|
|
||||
|Remove Extraneous Virtual Fonts from Package.|Most applications investigated by the App-V product team contained a few fonts, typically fewer than 20.|Virtual Fonts impact publishing refresh performance.|Desired fonts will need to be enabled/installed natively. For instructions, see Install or uninstall fonts.|
|
||||
|
||||
### Determining what virtual fonts exist in the package
|
||||
|
||||
@ -448,7 +448,7 @@ For documentation on How to Apply a Dynamic Configuration, see:
|
||||
|
||||
- Rename Package\_copy.appv to Package\_copy.zip
|
||||
|
||||
- Open AppxManifest.xml and locate the following:
|
||||
- Open AppxManifest.xml and locate the following syntax:
|
||||
|
||||
```xml
|
||||
<appv:Extension Category="AppV.Fonts">
|
||||
@ -458,7 +458,7 @@ For documentation on How to Apply a Dynamic Configuration, see:
|
||||
```
|
||||
|
||||
> [!Note]
|
||||
> If there are fonts marked as **DelayLoad**, those will not impact first launch.
|
||||
> If there are fonts marked as **DelayLoad**, those won't impact first launch.
|
||||
|
||||
### Excluding virtual fonts from the package
|
||||
|
||||
@ -485,9 +485,9 @@ The following terms are used when describing concepts and actions related to App
|
||||
|
||||
- **Re-Integrate** – Applies the user integrations.
|
||||
|
||||
- **Non-Persistent, Pooled** – Creates a computer running a virtual environment each time they log in.
|
||||
- **Non-Persistent, Pooled** – Creates a computer running a virtual environment each time they sign in.
|
||||
|
||||
- **Persistent, Personal** – A computer running a virtual environment that remains the same for every login.
|
||||
- **Persistent, Personal** – A computer running a virtual environment that remains the same for every sign in.
|
||||
|
||||
- **Stateful** - For this document, implies that user integrations are persisted between sessions and a user environment management technology is used in conjunction with non-persistent RDSH or VDI.
|
||||
|
||||
@ -497,13 +497,13 @@ The following terms are used when describing concepts and actions related to App
|
||||
|
||||
- **User Experience** - In the context of App-V, the user experience, quantitatively, is the sum of the following parts:
|
||||
|
||||
- From the point that users initiate a log-in to when they are able to manipulate the desktop.
|
||||
- From the point that users initiate a sign in to when they're able to manipulate the desktop.
|
||||
|
||||
- From the point where the desktop can be interacted with to the point a publishing refresh begins (in Windows PowerShell terms, sync) when using the App-V full server infrastructure. In standalone instances, it is when the **Add-AppVClientPackage** and **Publish-AppVClientPackage** Windows PowerShell commands are initiated.
|
||||
- From the point where the desktop can be interacted with to the point a publishing refresh begins (in Windows PowerShell terms, sync) when using the App-V full server infrastructure. In standalone instances, it's when the **Add-AppVClientPackage** and **Publish-AppVClientPackage** Windows PowerShell commands are initiated.
|
||||
|
||||
- From start to completion of the publishing refresh. In standalone instances, this is the first to last virtual application published.
|
||||
- From start to completion of the publishing refresh. In standalone instances, this refresh is the first to last instance leading to the virtual application being published.
|
||||
|
||||
- From the point where the virtual application is available to launch from a shortcut. Alternatively, it is from the point at which the file type association is registered and will launch a specified virtual application.
|
||||
- From the point where the virtual application is available to launch from a shortcut. Alternatively, it's from the point at which the file type association is registered and will launch a specified virtual application.
|
||||
|
||||
- **User Profile Management** – The controlled and structured approach to managing user components associated with the environment. For example, user profiles, preference and policy management, application control and application deployment. You can use scripting or third-party solutions configure the environment as needed.
|
||||
|
||||
|
||||
@ -33,7 +33,7 @@ To use %AppData% folder redirection, you must:
|
||||
|
||||
* Have an App-V package that has an AppData virtual file system (VFS) folder.
|
||||
* Enable folder redirection and redirect users’ folders to a shared folder, typically a network folder.
|
||||
* Roam both or neither of the following:
|
||||
* Roam both or neither of the following elements:
|
||||
* Files under %appdata%\Microsoft\AppV\Client\Catalog
|
||||
* Registry settings under HKEY_CURRENT_USER\Software\Microsoft\AppV\Client\Packages
|
||||
|
||||
@ -45,7 +45,7 @@ The following scenarios aren't supported by App-V:
|
||||
|
||||
* Configuring %LocalAppData% as a network drive.
|
||||
* Redirecting the Start menu to a single folder for multiple users.
|
||||
* If roaming AppData (%AppData%) is redirected to a network share that is not available, App-V applications will fail to launch, unless the unavailable network share has been enabled for Offline Files.
|
||||
* If roaming AppData (%AppData%) is redirected to a network share that isn't available, App-V applications will fail to launch, unless the unavailable network share has been enabled for Offline Files.
|
||||
|
||||
## How to configure folder redirection for use with App-V
|
||||
|
||||
@ -53,11 +53,11 @@ Folder redirection can be applied to different folders, such as Desktop, My Docu
|
||||
|
||||
## How folder redirection works with App-V
|
||||
|
||||
The following table describes how folder redirection works when %AppData% is redirected to a network and when you have met the requirements listed earlier in this article.
|
||||
The following table describes how folder redirection works when %AppData% is redirected to a network and when you've met the requirements listed earlier in this article.
|
||||
|
||||
|Virtual environment state|Action that occurs|
|
||||
|---|---|
|
||||
|When the virtual environment starts.|The virtual file system (VFS) AppData folder is mapped to the local AppData folder (%LocalAppData%) instead of to the user’s roaming AppData folder (%AppData%).<br>- LocalAppData contains a local cache of the user’s roaming AppData folder for the package in use. The local cache is located under ```%LocalAppData%\Microsoft\AppV\Client\VFS\PackageGUID\AppData```<br>- The latest data from the user’s roaming AppData folder is copied to and replaces the data currently in the local cache.<br>- While the virtual environment is running, data continues to be saved to the local cache. Data is served only out of %LocalAppData% and is not moved or synchronized with %AppData% until the end user shuts down the computer.<br>- Entries to the AppData folder are made using the user context, not the system context.|
|
||||
|When the virtual environment starts.|The virtual file system (VFS) AppData folder is mapped to the local AppData folder (%LocalAppData%) instead of to the user’s roaming AppData folder (%AppData%).<br>- LocalAppData contains a local cache of the user’s roaming AppData folder for the package in use. The local cache is located under ```%LocalAppData%\Microsoft\AppV\Client\VFS\PackageGUID\AppData```<br>- The latest data from the user’s roaming AppData folder is copied to and replaces the data currently in the local cache.<br>- While the virtual environment is running, data continues to be saved to the local cache. Data is served only out of %LocalAppData% and isn't moved or synchronized with %AppData% until the end user shuts down the computer.<br>- Entries to the AppData folder are made using the user context, not the system context.|
|
||||
|When the virtual environment shuts down.|The local cached data in AppData (roaming) is zipped up and copied to the “real” roaming AppData folder in %AppData%. A time stamp that indicates the last known upload is simultaneously saved as a registry key under ```HKCU\Software\Microsoft\AppV\Client\Packages\<PACKAGE_GUID>\AppDataTime```. App-V keeps the three most recent copies of the compressed data under %AppData% for redundancy.|
|
||||
|
||||
|
||||
|
||||
@ -48,7 +48,7 @@ Running App-V Server in Shared Content Store (SCS) mode with clustered file serv
|
||||
To enable SCS mode configurations, follow these steps:
|
||||
|
||||
1. Configure the App-V client to run in SCS mode. For more information, see [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).
|
||||
2. Configure the file server cluster, configured in either the scale out mode (which started with Windows Server 2012) or the earlier clustering mode, with a virtual SAN.
|
||||
2. Configure the file server cluster, configured in either the scale-out mode (which started with Windows Server 2012) or the earlier clustering mode, with a virtual SAN.
|
||||
|
||||
The following steps can be used to validate the configuration:
|
||||
|
||||
@ -63,7 +63,7 @@ Review the following articles to learn more about configuring Windows Server fai
|
||||
|
||||
## Support for Microsoft SQL Server mirroring
|
||||
|
||||
Using Microsoft SQL Server mirroring, where the App-V management server database is mirrored utilizing two SQL Server instances, for App-V management server databases is supported.
|
||||
With the Microsoft SQL Server mirroring being used, where the App-V management server database is mirrored utilizing two SQL Server instances, for App-V management server databases is supported.
|
||||
|
||||
Review the following to learn more about how to configure Microsoft SQL Server mirroring:
|
||||
|
||||
@ -76,7 +76,7 @@ The following steps can be used to validate the configuration:
|
||||
2. Select **Failover** to designate a new master Microsoft SQL Server instance.
|
||||
3. Verify that the App-V management server continues to function as expected after the failover.
|
||||
|
||||
The connection string on the management server can be modified to include ```failover partner = <server2>```. This will only help when the primary on the mirror has failed over to the secondary and the computer running the App-V client is doing a fresh connection (say after reboot).
|
||||
The connection string on the management server can be modified to include ```failover partner = <server2>```. This modification will only help when the primary on the mirror has failed over to the secondary and the computer running the App-V client is doing a fresh connection (say after reboot).
|
||||
|
||||
Use the following steps to modify the connection string to include ```failover partner = <server2>```:
|
||||
|
||||
|
||||
@ -30,7 +30,7 @@ You can use the App-V Sequencer to create plug-in packages for language packs, l
|
||||
For a list of supported Office products, see [Microsoft Office Product IDs that App-V supports](https://support.microsoft.com/help/2842297/product-ids-that-are-supported-by-the-office-deployment-tool-for-click).
|
||||
|
||||
>[!NOTE]
|
||||
>You must use the Office Deployment Tool instead of the App-V Sequencer to create App-V packages for Microsoft 365 Apps for enterprise. App-V does not support package creation for volume-licensed versions of Office Professional Plus or Office Standard. Support for the [Office 2013 version of Office 365 ended in February 2017](https://support.microsoft.com/kb/3199744).
|
||||
>You must use the Office Deployment Tool instead of the App-V Sequencer to create App-V packages for Microsoft 365 Apps for enterprise. App-V doesn't support package creation for volume-licensed versions of Office Professional Plus or Office Standard. Support for the [Office 2013 version of Office 365 ended in February 2017](https://support.microsoft.com/kb/3199744).
|
||||
|
||||
## Using App-V with coexisting versions of Office
|
||||
|
||||
@ -40,7 +40,7 @@ Microsoft’s recommended best practice is to avoid Office coexistence completel
|
||||
|
||||
### Before you implement Office coexistence
|
||||
|
||||
Before implementing Office coexistence, review the information in the following table that corresponds to the newest version of Office that you will use in coexistence. The documentation linked here will guide you in implementing coexistence for Windows Installer-based (MSI) and Click-to-Run installations of Office.
|
||||
Before implementing Office coexistence, review the information in the following table that corresponds to the newest version of Office that you'll use in coexistence. The documentation linked here will guide you in implementing coexistence for Windows Installer-based (MSI) and Click-to-Run installations of Office.
|
||||
|
||||
|Office version|Relevant how-to guides|
|
||||
|---|---|
|
||||
@ -52,10 +52,10 @@ Once you've reviewed the relevant guide, this topic will supplement what you've
|
||||
|
||||
### Supported Office coexistence scenarios
|
||||
|
||||
The following tables summarize supported coexistence scenarios. They are organized according to the version and deployment method you’re starting with and the version and deployment method you are migrating to. Be sure to fully test all coexistence solutions before deploying them to a production audience.
|
||||
The following tables summarize supported coexistence scenarios. They're organized according to the version and deployment method you’re starting with and the version and deployment method you're migrating to. Be sure to fully test all coexistence solutions before deploying them to a production audience.
|
||||
|
||||
>[!NOTE]
|
||||
>Microsoft does not support the use of multiple versions of Office in Windows Server environments that have the Remote Desktop Session Host role service enabled. To run Office coexistence scenarios, you must disable this role service.
|
||||
>Microsoft doesn't support the use of multiple versions of Office in Windows Server environments that have the Remote Desktop Session Host role service enabled. To run Office coexistence scenarios, you must disable this role service.
|
||||
|
||||
### Windows integrations and Office coexistence
|
||||
|
||||
@ -65,10 +65,10 @@ The following table describes the integration level of each version of Office, a
|
||||
|
||||
|Office version|The modes App-V can sequence this version of Office with|
|
||||
|---|---|
|
||||
|Office 2007|Always non-integrated. App-V does not offer any operating system integrations with a virtualized version of Office 2007.|
|
||||
|Office 2007|Always non-integrated. App-V doesn't offer any operating system integrations with a virtualized version of Office 2007.|
|
||||
|Office 2010|Integrated and non-integrated mode.|
|
||||
|Office 2013|Always integrated. Windows operating system integrations cannot be disabled.|
|
||||
|Office 2016|Always integrated. Windows operating system integrations cannot be disabled.|
|
||||
|Office 2013|Always integrated. Windows operating system integrations can't be disabled.|
|
||||
|Office 2016|Always integrated. Windows operating system integrations can't be disabled.|
|
||||
|
||||
Microsoft recommends deploying Office coexistence with only one integrated Office instance. For example, if you’re using App-V to deploy Office 2010 and Office 2013, you should sequence Office 2010 in non-integrated mode. For more information about sequencing Office in non-integration (isolated) mode, see [How to sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0](https://support.microsoft.com/kb/2830069).
|
||||
|
||||
@ -83,12 +83,12 @@ Limitations can occur when you install the following versions of Office on the s
|
||||
* Office 2010 with the Windows Installer-based version
|
||||
* Office 2013 or Office 2016 with App-V
|
||||
|
||||
Publishing Office 2013 or Office 2016 with App-V at the same time as an earlier version of the Windows Installer-based Office 2010 might cause the Windows Installer to start. This is because either the Windows Installer-based or Click-to-Run version of Office 2010 is trying to automatically register itself to the computer.
|
||||
Publishing Office 2013 or Office 2016 with App-V at the same time as an earlier version of the Windows Installer-based Office 2010 might cause the Windows Installer to start. This scenario is because either the Windows Installer-based or Click-to-Run version of Office 2010 is trying to automatically register itself to the computer.
|
||||
|
||||
To bypass the auto-registration operation for native Word 2010, follow these steps:
|
||||
|
||||
1. Exit Word 2010.
|
||||
2. Start the Registry Editor by doing the following:
|
||||
2. Start the Registry Editor by doing the following tasks:
|
||||
|
||||
* In Windows 7k, select **Start**, type **regedit** in the Start Search box, then select the Enter key.
|
||||
|
||||
|
||||
@ -16,13 +16,13 @@ ms.topic: article
|
||||
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
If you are using an electronic software distribution (ESD) system to deploy App-V packages, review the following planning considerations. For information about deploying App-V with Microsoft Endpoint Configuration Manager, see [Introduction to application management in Configuration Manager](/previous-versions/system-center/system-center-2012-R2/gg682125(v=technet.10)#BKMK_Appv).
|
||||
If you're using an electronic software distribution (ESD) system to deploy App-V packages, review the following planning considerations. For information about deploying App-V with Microsoft Endpoint Configuration Manager, see [Introduction to application management in Configuration Manager](/previous-versions/system-center/system-center-2012-R2/gg682125(v=technet.10)#BKMK_Appv).
|
||||
|
||||
Review the following component and architecture requirements options that apply when you use an ESD to deploy App-V packages:
|
||||
|
||||
| Deployment requirement or option | Description |
|
||||
|---|---|
|
||||
| The App-V Management server, Management database, and Publishing server are not required. | These functions are handled by the implemented ESD solution. |
|
||||
| The App-V Management server, Management database, and Publishing server aren't required. | These functions are handled by the implemented ESD solution. |
|
||||
| You can deploy the App-V Reporting server and Reporting database side-by-side with the ESD. | The side-by-side deployment lets you collect data and generate reports.<br/>If you enable the App-V client to send report information without using the App-V Reporting server, the reporting data will be stored in associated .xml files. |
|
||||
|
||||
|
||||
|
||||
@ -20,7 +20,7 @@ There are several different deployment configurations and requirements to consid
|
||||
|
||||
## App-V supported configurations
|
||||
|
||||
[App-V supported configurations](appv-supported-configurations.md) describes the minimum hardware and operating system requirements for each App-V components. For information about software that you must install before you install App-V, see [App-V Prerequisites](appv-prerequisites.md).
|
||||
[App-V supported configurations](appv-supported-configurations.md) describes the minimum hardware and operating system requirements for each App-V component. For information about software that you must install before you install App-V, see [App-V Prerequisites](appv-prerequisites.md).
|
||||
|
||||
## App-V capacity planning
|
||||
|
||||
|
||||
@ -29,8 +29,8 @@ The following list displays the end–to-end high-level workflow for reporting i
|
||||
* SQL Server installed and running with SQL Server Reporting Services (SSRS)
|
||||
|
||||
To confirm SQL Server Reporting Services is running, enter <https://localhost/Reports> in a web browser as administrator on the server that will host App-V Reporting. The SQL Server Reporting Services Home page should appear.
|
||||
2. Install the App-V reporting server and associated database. For more information about installing the reporting server see [How to install the Reporting Server on a standalone computer and connect it to the database](appv-install-the-reporting-server-on-a-standalone-computer.md). Configure the time when the computer running the App-V client should send data to the reporting server.
|
||||
3. If you are not using an electronic software distribution system such as Configuration Manager to view reports then you can define reports in SQL Server Reporting Service. Download predefined appvshort Reports from the Download Center at [Application Virtualization SSRS Reports](https://www.microsoft.com/download/details.aspx?id=42630).
|
||||
2. Install the App-V reporting server and associated database. For more information about installing the reporting server, see [How to install the Reporting Server on a standalone computer and connect it to the database](appv-install-the-reporting-server-on-a-standalone-computer.md). Configure the time when the computer running the App-V client should send data to the reporting server.
|
||||
3. If you aren't using an electronic software distribution system such as Configuration Manager to view reports, then you can define reports in SQL Server Reporting Service. Download predefined appvshort Reports from the Download Center at [Application Virtualization SSRS Reports](https://www.microsoft.com/download/details.aspx?id=42630).
|
||||
|
||||
> [!NOTE]
|
||||
>If you are using the Configuration Manager integration with App-V, most reports are generated from Configuration Manager rather than from App-V.
|
||||
@ -43,13 +43,13 @@ The following list displays the end–to-end high-level workflow for reporting i
|
||||
To immediately send App-V report data, run **Send-AppvClientReport** on the App-V client.
|
||||
|
||||
For more information about configuring reporting on the App-V client, see [About client configuration settings](appv-client-configuration-settings.md). To administer App-V Reporting with Windows PowerShell, see [How to enable reporting on the App-V client by using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md).
|
||||
5. After the reporting server receives the data from the App-V client it sends the data to the reporting database. When the database receives and processes the client data, a successful reply is sent to the reporting server, which then notifies the App-V client.
|
||||
5. After the reporting server receives the data from the App-V client, it sends the data to the reporting database. When the database receives and processes the client data, a successful reply is sent to the reporting server, which then notifies the App-V client.
|
||||
6. When the App-V client receives the success notification, it empties the data cache to conserve space.
|
||||
|
||||
> [!NOTE]
|
||||
>By default, the cache is cleared after the server confirms receipt of data. You can manually configure the client to save the data cache.
|
||||
|
||||
If the App-V client device does not receive a success notification from the server, it retains data in the cache and tries to resend data at the next configured interval. Clients continue to collect data and add it to the cache.
|
||||
If the App-V client device doesn't receive a success notification from the server, it retains data in the cache and tries to resend data at the next configured interval. Clients continue to collect data and add it to the cache.
|
||||
|
||||
### App-V reporting server frequently asked questions
|
||||
|
||||
@ -57,7 +57,7 @@ The following sections provide answers to frequently asked questions about how A
|
||||
|
||||
#### How frequently is reporting information sent to the reporting database?
|
||||
|
||||
Frequency depends on the computer running the App-V client's reporting configuration. You must configure the frequency or interval for sending the reporting data manually, as App-V reporting is not enabled by default.
|
||||
Frequency depends on the computer running the App-V client's reporting configuration. You must configure the frequency or interval for sending the reporting data manually, as App-V reporting isn't enabled by default.
|
||||
|
||||
#### What information is stored in the reporting server database?
|
||||
|
||||
@ -73,10 +73,10 @@ The following information is stored in the reporting database:
|
||||
It depends. Three sets of data can be sent to the reporting server:
|
||||
|
||||
* Operating system and App-V client information, which is about 150 Bytes every time it gets sent to the server.
|
||||
* Published package lists, which are about 7 KB per 30 packages. This is sent only when the package list is updated with a publishing refresh, which is done infrequently; if there is no change, this information is not sent.
|
||||
* Virtual application usage information is about 0.25 KB per event. Opening and closing count as one event if both occur before sending the information. When sending using a scheduled task, only the data since the last successful upload is sent to the server. If sending manually through the Windows PowerShell cmdlet, there is an optional argument called **DeleteOnSuccess** that controls if the data needs to be re-sent the next time around.
|
||||
* Published package lists, which are about 7 KB per 30 packages. This is sent only when the package list is updated with a publishing refresh, which is done infrequently; if there's no change, this information isn't sent.
|
||||
* Virtual application usage information is about 0.25 KB per event. Opening and closing count as one event if both occur before sending the information. When the information is sent through a scheduled task, only the data since the last successful upload is sent to the server. If sending manually through the Windows PowerShell cmdlet, there's an optional argument called **DeleteOnSuccess** that controls if the data needs to be resent the next time around.
|
||||
|
||||
For example, if twenty applications are opened and closed and reporting information is scheduled to be sent daily, the typical daily traffic should be about 0.15 KB + 20 × 0.25 KB, or about 5 KB/user.
|
||||
For example, if 20 applications are opened and closed and reporting information is scheduled to be sent daily, the typical daily traffic should be about 0.15 KB + 20 × 0.25 KB, or about 5 KB/user.
|
||||
|
||||
#### Can I schedule reporting?
|
||||
|
||||
@ -96,7 +96,7 @@ Yes. Besides manually sending reporting using Windows PowerShell cmdlets (**Send
|
||||
|
||||
## App-V Client reporting
|
||||
|
||||
To use App-V reporting you must enable and configure the App-V client. To configure reporting on the client, use the Windows PowerShell cmdlet **Set-AppVClientConfiguration**, or the Group Policy **ADMX Template**. For more information about the Windows PowerShell cmdlets, see [About client configuration settings](appv-client-configuration-settings.md). The following section provides examples of Windows PowerShell commands for configuring App-V client reporting.
|
||||
To use App-V reporting,, you must enable and configure the App-V client. To configure reporting on the client, use the Windows PowerShell cmdlet **Set-AppVClientConfiguration**, or the Group Policy **ADMX Template**. For more information about the Windows PowerShell cmdlets, see [About client configuration settings](appv-client-configuration-settings.md). The following section provides examples of Windows PowerShell commands for configuring App-V client reporting.
|
||||
|
||||
### Configuring App-V client reporting using Windows PowerShell
|
||||
|
||||
@ -177,7 +177,7 @@ Send-AppVClientReport –URL http://MyReportingServer:MyPort/ -DeleteOnSuccess
|
||||
|
||||
If the reporting server has been previously configured, then the **–URL** parameter can be omitted. Alternatively, if the data should be sent to an alternate location, specify a different URL to override the configured **ReportingServerURL** for this data collection.
|
||||
|
||||
The **-DeleteOnSuccess** parameter indicates that if the transfer is successful, then the data cache will be cleared. If this is not specified, then the cache will not be cleared.
|
||||
The **-DeleteOnSuccess** parameter indicates that if the transfer is successful, then the data cache will be cleared. If the transfer-status isn't specified, then the cache won't be cleared.
|
||||
|
||||
### Manual Data Collection
|
||||
|
||||
@ -185,16 +185,16 @@ You can also use the **Send-AppVClientReport** cmdlet to manually collect data.
|
||||
|
||||
|With a reporting server|Without a reporting server|
|
||||
|---|---|
|
||||
|f you have an existing App-V reporting server, create a customized scheduled task or script. Specify that the client sends the data to the specified location at the desired frequency.|If you do not have an existing App-V reporting Server, use the **–URL** parameter to send the data to a specified share. For example: ```Send-AppVClientReport –URL \\Myshare\MyData\ -DeleteOnSuccess``` <br>The previous example will send the reporting data to the ```\\MyShare\MyData\``` location indicated by the **-URL** parameter. After the data has been sent, the cache is cleared.|
|
||||
|f you have an existing App-V reporting server, create a customized scheduled task or script. Specify that the client sends the data to the specified location at the desired frequency.|If you don't have an existing App-V reporting Server, use the **–URL** parameter to send the data to a specified share. For example: ```Send-AppVClientReport –URL \\Myshare\MyData\ -DeleteOnSuccess``` <br>The previous example will send the reporting data to the ```\\MyShare\MyData\``` location indicated by the **-URL** parameter. After the data has been sent, the cache is cleared.|
|
||||
|
||||
>[!NOTE]
|
||||
>If a location other than the Reporting Server is specified, the data is sent in **.xml** format with no additional processing.
|
||||
|
||||
### Creating reports
|
||||
|
||||
To retrieve report information and create reports using App-V you must use one of the following methods:
|
||||
To retrieve report information and create reports using App-V, you must use one of the following methods:
|
||||
|
||||
* Microsoft SQL Server Reporting Services (SSRS)—Microsoft SSRS is available with Microsoft SQL Server. SSRS is not installed when you install the App-V reporting server. It must be deployed separately to generate the associated reports. For more information, see the [What is SQL Server Reporting Services (SSRS)?](/sql/reporting-services/create-deploy-and-manage-mobile-and-paginated-reports) article.
|
||||
* Microsoft SQL Server Reporting Services (SSRS)—Microsoft SSRS is available with Microsoft SQL Server. SSRS isn't installed when you install the App-V reporting server. It must be deployed separately to generate the associated reports. For more information, see the [What is SQL Server Reporting Services (SSRS)?](/sql/reporting-services/create-deploy-and-manage-mobile-and-paginated-reports) article.
|
||||
|
||||
* Scripting—You can generate reports by scripting directly against the App-V reporting database. For example:
|
||||
|
||||
|
||||
@ -22,7 +22,7 @@ ms.author: greglin
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2016
|
||||
|
||||
You can run a locally installed application in a virtual environment, alongside applications that have been virtualized by using Microsoft Application Virtualization (App-V). You might want to do this if you:
|
||||
You can run a locally installed application in a virtual environment, alongside applications that have been virtualized by using Microsoft Application Virtualization (App-V). You might want to do this task if you:
|
||||
|
||||
- Want to install and run an application locally on client computers, but want to virtualize and run specific plug-ins that work with that local application.
|
||||
|
||||
@ -45,7 +45,7 @@ Each method accomplishes essentially the same task, but some methods may be bett
|
||||
|
||||
To add a locally installed application to a package or to a connection group’s virtual environment, you add a subkey to the `RunVirtual` registry key in the Registry Editor, as described in the following sections.
|
||||
|
||||
There is no Group Policy setting available to manage this registry key, so you have to use Microsoft Endpoint Manager or another electronic software distribution (ESD) system, or manually edit the registry.
|
||||
There's no Group Policy setting available to manage this registry key, so you have to use Microsoft Endpoint Manager or another electronic software distribution (ESD) system, or manually edit the registry.
|
||||
|
||||
Starting with App-V 5.0 SP3, when using RunVirtual, you can publish packages globally or to the user.
|
||||
|
||||
@ -63,16 +63,16 @@ Starting with App-V 5.0 SP3, when using RunVirtual, you can publish packages glo
|
||||
For example, create `HKEY_CURRENT_USER \SOFTWARE\Microsoft\AppV\Client\RunVirtual\MyApp.exe`.
|
||||
|
||||
- Connection group can be:
|
||||
- Packages that are published just globally or just to the user
|
||||
- Packages that are published globally or just to the user
|
||||
- Packages that are published globally and to the user
|
||||
|
||||
Use the `HKEY_LOCAL_MACHINE` or `HKEY_CURRENT_USER` key. But, all of the following must be true:
|
||||
Use the `HKEY_LOCAL_MACHINE` or `HKEY_CURRENT_USER` key. But, all of the following conditions must be fulfilled:
|
||||
|
||||
- If you want to include multiple packages in the virtual environment, you must include them in an enabled connection group.
|
||||
- Create only one subkey for one of the packages in the connection group. If, for example, you have one package that is published globally, and another package that is published to the user, you create a subkey for either of these packages, but not both. Although you create a subkey for only one of the packages, all of the packages in the connection group, plus the local application, will be available in the virtual environment.
|
||||
- The key under which you create the subkey must match the publishing method you used for the package.
|
||||
|
||||
For example, if you published the package to the user, you must create the subkey under `HKEY_CURRENT_USER\SOFTWARE\Microsoft\AppV\Client\RunVirtual`. Do not add a key for the same application under both hives.
|
||||
For example, if you published the package to the user, you must create the subkey under `HKEY_CURRENT_USER\SOFTWARE\Microsoft\AppV\Client\RunVirtual`. Don't add a key for the same application under both hives.
|
||||
|
||||
2. Set the new registry subkey’s value to the PackageId and VersionId of the package, separating the values with an underscore.
|
||||
|
||||
@ -80,7 +80,7 @@ Starting with App-V 5.0 SP3, when using RunVirtual, you can publish packages glo
|
||||
|
||||
**Example**: 4c909996-afc9-4352-b606-0b74542a09c1\_be463724-Oct1-48f1-8604-c4bd7ca92fa
|
||||
|
||||
The application in the previous example would produce a registry export file (.reg file) like the following:
|
||||
The application in the previous example would produce a registry export file (.reg file) like the following example:
|
||||
|
||||
```registry
|
||||
Windows Registry Editor Version 5.00
|
||||
|
||||
@ -19,15 +19,15 @@ ms.topic: article
|
||||
This topic contains a brief overview of the accounts and groups, log files, and other security-related considerations for Microsoft Application Virtualization (App-V).
|
||||
|
||||
>[!IMPORTANT]
|
||||
>App-V is not a security product and does not provide any guarantees for a secure environment.
|
||||
>App-V isn't a security product and doesn't provide any guarantees for a secure environment.
|
||||
|
||||
## The PackageStoreAccessControl (PSAC) feature has been deprecated
|
||||
|
||||
Effective as of June, 2014, the PackageStoreAccessControl (PSAC) feature introduced in Microsoft Application Virtualization (App-V) 5.0 Service Pack 2 (SP2) has been deprecated in both single-user and multi-user environments.
|
||||
Effective as of June 2014, the PackageStoreAccessControl (PSAC) feature introduced in Microsoft Application Virtualization (App-V) 5.0 Service Pack 2 (SP2) has been deprecated in both single-user and multi-user environments.
|
||||
|
||||
## General security considerations
|
||||
|
||||
**Understand the security risks.** The most serious risk to App-V is from unauthorized users hijacking an App-V client's functionality, giving the hacker the ability to reconfigure key data on App-V clients. By comparison, short-term loss of App-V functionality from a denial-of-service attack would not be as catastrophic.
|
||||
**Understand the security risks.** The most serious risk to App-V is from unauthorized users hijacking an App-V client's functionality, giving the hacker the ability to reconfigure key data on App-V clients. By comparison, short-term loss of App-V functionality from a denial-of-service attack wouldn't be as catastrophic.
|
||||
|
||||
**Physically secure your computers**. A security strategy that doesn't consider physical security is incomplete. Anyone with physical access to an App-V server could potentially attack the entire client base, so potential physical attacks or thefts should be prevented at all cost. App-V servers should be stored in a physically secure server room with controlled access. Lock the computer with the operating system or a secured screen saver to keep computers secure when the administrators are away.
|
||||
|
||||
@ -50,8 +50,8 @@ No groups are created automatically during App-V setup. You should create the fo
|
||||
|---|---|---|
|
||||
|App-V Management Admin group|Used to manage the App-V management server. This group is created during the App-V Management Server installation.|The management console can't create a new group after installation is complete.|
|
||||
|Database read/write for Management Service account|Provides read/write access to the management database. This account should be created during App-V management database installation.||
|
||||
|App-V Management Service install admin account|Provides public access to schema-version table in management database. This account should be created during App-V management database installation.|This is only required if the management database is being installed separately from the service.|
|
||||
|App-V Reporting Service install admin account|Public access to schema-version table in reporting database. This account should be created during the App-V reporting database installation.|This is only required if reporting database is being installed separately from the service.|
|
||||
|App-V Management Service install admin account|Provides public access to schema-version table in management database. This account should be created during App-V management database installation.|This account is only required if the management database is being installed separately from the service.|
|
||||
|App-V Reporting Service install admin account|Public access to schema-version table in reporting database. This account should be created during the App-V reporting database installation.|This account is only required if reporting database is being installed separately from the service.|
|
||||
|
||||
Consider the following additional information:
|
||||
|
||||
@ -62,9 +62,9 @@ Consider the following additional information:
|
||||
|
||||
### App-V package security
|
||||
|
||||
The following will help you plan how to ensure that virtualized packages are secure.
|
||||
The following information will help you plan how to ensure that virtualized packages are secure.
|
||||
|
||||
* If an application installer applies an access control list (ACL) to a file or directory, then that ACL is not persisted in the package. If the file or directory is modified by a user when the package is deployed, the modified file or directory will either inherit the ACL in the **%userprofile%** or inherit the ACL of the target computer’s directory. The former occurs if the file or directory does not exist in a virtual file system location; the latter occurs if the file or directory exists in a virtual file system location, such as **%windir%**.
|
||||
* If an application installer applies an access control list (ACL) to a file or directory, then that ACL isn't persisted in the package. If the file or directory is modified by a user when the package is deployed, the modified file or directory will either inherit the ACL in the **%userprofile%** or inherit the ACL of the target computer’s directory. The former occurs if the file or directory doesn't exist in a virtual file system location; the latter occurs if the file or directory exists in a virtual file system location, such as **%windir%**.
|
||||
|
||||
## App-V log files
|
||||
|
||||
|
||||
@ -50,7 +50,7 @@ You can install the App-V Management server on a server running Windows Server 2
|
||||
### Management server hardware requirements
|
||||
|
||||
* A 64-bit (x64) processor that runs at 1.4 GHz or faster.
|
||||
* 1 GB RAM (64-bit).
|
||||
* 1-GB RAM (64-bit).
|
||||
* 200 MB of available hard disk space, not including the content directory.
|
||||
|
||||
### Management server database requirements
|
||||
@ -74,10 +74,10 @@ The App-V Publishing server can be installed on a server that runs Windows Serve
|
||||
|
||||
### Publishing server hardware requirements
|
||||
|
||||
App-V adds no additional requirements beyond those of Windows Server.
|
||||
App-V adds requires nothing beyond the requirements of Windows Server.
|
||||
|
||||
* A 64-bit (x64) processor that runs at 1.4 GHz or faster.
|
||||
* 2 GB RAM (64-bit).
|
||||
* 2-GB RAM (64-bit).
|
||||
* 200 MB of available hard disk space, not including the content directory.
|
||||
|
||||
### Reporting server operating system requirements
|
||||
@ -86,10 +86,10 @@ You can install the App-V Reporting server on a server running Windows Server 20
|
||||
|
||||
### Reporting server hardware requirements
|
||||
|
||||
App-V adds no additional requirements beyond those of Windows Server.
|
||||
App-V adds no other requirements beyond those requirements of Windows Server.
|
||||
|
||||
* A 64-bit (x64) processor that runs at 1.4 GHz or faster.
|
||||
* 2 GB RAM (64-bit).
|
||||
* 2-GB RAM (64-bit).
|
||||
* 200 MB of available hard disk space, not including the content directory.
|
||||
|
||||
### Reporting server database requirements
|
||||
|
||||
@ -21,13 +21,13 @@ Use the following procedure to transfer the access and default package configura
|
||||
|
||||
**To transfer access and configurations to another version of a package**
|
||||
|
||||
1. To view the package that you want to configure, open the App-V Management Console. Select the package to which you will transfer the new configuration, right-click the package and select **transfer default configuration from** or **transfer access and configurations from**, depending on the configuration that you want to transfer.
|
||||
1. To view the package that you want to configure, open the App-V Management Console. Select the package to which you'll transfer the new configuration, right-click the package and select **transfer default configuration from** or **transfer access and configurations from**, depending on the configuration that you want to transfer.
|
||||
|
||||
2. To transfer the configuration, in the **Select Previous Version** dialog box, select the package that contains the settings that you want to transfer, and then click **OK**.
|
||||
|
||||
If you select **transfer default configuration from**, then only the underlying dynamic deployment configuration will be transferred.
|
||||
|
||||
If you select **transfer access and configurations from**, then all access permissions, as well as the configuration settings, will be copied.
|
||||
If you select **transfer access and configurations from**, then all access permissions, and the configuration settings, will be copied.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -25,11 +25,11 @@ Users have the ability to control background activity for their device through t
|
||||
|
||||
|
||||
|
||||
The **Battery usage by app** page allows fine-grained tuning of background activity. Users have the ability to set background activity to by **Managed By Windows**, as well as turning it on or off for each app. Only devices with a battery have this page available in the **Settings** app. Here is the set of available controls on desktop:
|
||||
The **Battery usage by app** page allows fine-grained tuning of background activity. Users have the ability to set background activity to by **Managed By Windows**, and turning it on or off for each app. Only devices with a battery have this page available in the **Settings** app. Here's the set of available controls on desktop:
|
||||
|
||||
|
||||
|
||||
Here is the set of available controls for mobile devices:
|
||||
Here's the set of available controls for mobile devices:
|
||||
|
||||
|
||||
|
||||
@ -48,13 +48,13 @@ These policies control the background activity battery settings for Universal Wi
|
||||
|
||||
An app can determine which settings are in place for itself by using [BackgroundExecutionManager.RequestAccessAsync](/uwp/api/Windows.ApplicationModel.Background.BackgroundAccessStatus) before any background activity is attempted, and then examining the returned [BackgroundAccessStatus](/uwp/api/windows.applicationmodel.background.backgroundaccessstatus) enumeration. The values of this enumeration correspond to settings in the **battery usage by App** settings page:
|
||||
|
||||
- **AlwaysAllowed**: Corresponds to **Always Allowed in Background** and **Managed By User**. This enables apps to run as much as possible in the background, including while the device is in battery saver mode.
|
||||
- **AlwaysAllowed**: Corresponds to **Always Allowed in Background** and **Managed By User**. This correspondence enables apps to run as much as possible in the background, including while the device is in battery saver mode.
|
||||
|
||||
- **AllowedSubjectToSystemPolicy**: This is the default value. It corresponds to **Managed by Windows**. This enables apps to run in the background as determined by Windows. If the device is currently in the battery saver state then background activities do not run.
|
||||
- **AllowedSubjectToSystemPolicy**: This value is the default one. It corresponds to **Managed by Windows**. This correspondence enables apps to run in the background as determined by Windows. If the device is currently in the battery saver state, then background activities don't run.
|
||||
|
||||
- **DeniedDueToSystemPolicy**: Corresponds to **Managed by Windows** and indicates that the system has determined that the app cannot currently run in the background.
|
||||
- **DeniedDueToSystemPolicy**: Corresponds to **Managed by Windows** and indicates that the system has determined that the app can't currently run in the background.
|
||||
|
||||
- **DeniedByUser**: Corresponds to **Never Allowed in the Background**. The app cannot run in the background. Either the configuration in the settings app, or enterprise policy, has defined that this app is not allowed to run in the background.
|
||||
- **DeniedByUser**: Corresponds to **Never Allowed in the Background**. The app can't run in the background. Either the configuration in the settings app, or enterprise policy, has defined that this app isn't allowed to run in the background.
|
||||
|
||||
The Universal Windows Platform ensures that consumers will have great battery life and that foreground apps will perform well. Enterprises have the ability to change settings to enable scenarios specific to their business needs. Administrators can use the **Background apps** policies to enable or disable whether a UWP app can run in the background.
|
||||
|
||||
|
||||
@ -53,7 +53,7 @@ You can sideload apps on managed or unmanaged devices.
|
||||
|
||||
Managed devices are typically owned by your organization. They're managed by Group Policy (on-premises), or a Mobile Device Management (MDM) provider, such as Microsoft Intune (cloud). Bring your own devices (BYOD) and personal devices can also be managed by your organization. On managed devices, you can create a policy that turns on sideloading, and then deploy this policy to your Windows devices.
|
||||
|
||||
Unmanaged devices are devices that are not managed by your organization. These devices are typically personal devices owned by users. Users can turn on sideloading using the Settings app.
|
||||
Unmanaged devices are devices that aren't managed by your organization. These devices are typically personal devices owned by users. Users can turn on sideloading using the Settings app.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> To install an app on Windows client, you can:
|
||||
|
||||
@ -16,7 +16,7 @@ manager: dansimp
|
||||
|
||||
> Applies to: Windows 10
|
||||
|
||||
The **Service Host (svchost.exe)** is a shared-service process that serves as a shell for loading services from DLL files. Services are organized into related host groups, and each group runs inside a different instance of the Service Host process. In this way, a problem in one instance does not affect other instances. Service Host groups are determined by combining the services with matching security requirements. For example:
|
||||
The **Service Host (svchost.exe)** is a shared-service process that serves as a shell for loading services from DLL files. Services are organized into related host groups, and each group runs inside a different instance of the Service Host process. In this way, a problem in one instance doesn't affect other instances. Service Host groups are determined by combining the services with matching security requirements. For example:
|
||||
|
||||
* Local Service
|
||||
* Local Service No Network
|
||||
@ -33,7 +33,7 @@ Benefits of this design change include:
|
||||
|
||||
* Increased reliability by insulating critical network services from the failure of another non-network service in the host, and adding the ability to restore networking connectivity seamlessly when networking components crash.
|
||||
* Reduced support costs by eliminating the troubleshooting overhead associated with isolating misbehaving services in the shared host.
|
||||
* Increased security by providing additional inter-service isolation
|
||||
* Increased security by providing more inter-service isolation
|
||||
* Increased scalability by allowing per-service settings and privileges
|
||||
* Improved resource management through per-service CPU, I/O and memory management and increase clear diagnostic data (report CPU, I/O and network usage per service).
|
||||
|
||||
@ -58,24 +58,24 @@ Compare that to the same view of running processes in Windows 10 version 1703:
|
||||
|
||||
|
||||
## Exceptions
|
||||
Some services will continue to be grouped on PCs running with 3.5GB or higher RAM. For example, the Base Filtering Engine (BFE) and the Windows Firewall (Mpssvc) will be grouped together in a single host group, as will the RPC Endpoint Mapper and Remote Procedure Call services.
|
||||
Some services will continue to be grouped on PCs running with 3.5 GB or higher RAM. For example, the Base Filtering Engine (BFE) and the Windows Firewall (Mpssvc) will be grouped together in a single host group, as will the RPC Endpoint Mapper and Remote Procedure Call services.
|
||||
|
||||
If you need to identify services that will continue to be grouped, in addition to seeing them in Task Manager and using command line tools, you can look for the *SvcHostSplitDisable* value in their respective service keys under
|
||||
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.
|
||||
|
||||
The default value of **1** prevents the service from being split.
|
||||
|
||||
For example, this is the registry key configuration for BFE:
|
||||
For example, the registry key configuration for BFE is:
|
||||
|
||||
|
||||
## Memory footprint
|
||||
|
||||
Be aware that separating services increases the total number of SvcHost instances, which increases memory utilization. (Service grouping provided a modest reduction to the overall resource footprint of the services involved.)
|
||||
|
||||
Consider the following:
|
||||
Consider the following example:
|
||||
|
||||
|
||||
|Grouped Services (< 3.5GB) | Split Services (3.5GB+)
|
||||
|Grouped Services (< 3.5 GB) | Split Services (3.5 GB+)
|
||||
|--------------------------------------- | ------------------------------------------ |
|
||||
| | |
|
||||
|
||||
|
||||
Reference in New Issue
Block a user