deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-16 19:03:46 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Fixing broken bookmarks

Browse Source
This commit is contained in:
LizRoss
2016-11-01 13:17:42 -07:00
parent 466887ca18
commit ea0a02fe9f
4 changed files with 4 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
mdop/medv-v2/how-to-test-application-publishing.md
View File

@ -15,7 +15,7 @@ ms.prod: w7
After your test of first time setup finishes, you can verify that the application publishing functionality is working as expected by performing the following tasks.
**To test application publishing**
<a href="" id="bkmk-apppub"></a>**To test application publishing**
1. Verify that the applications that you specified for publishing are visible.
@ -34,8 +34,6 @@ After your test of first time setup finishes, you can verify that the applicatio
**Important**  
Because Windows Virtual PC does not support creating a share from a folder that is already shared, redirection does not occur for any documents that open from a shared folder, such as a My Documents folder that is located on the network. For more information, see [Operations Troubleshooting](operations-troubleshooting-medv2.md).
 
After you have verified that published applications are installed and functioning correctly, you can test whether applications can be added or removed from the MED-V workspace.
**To test that an application can be added or removed**
@ -51,15 +49,12 @@ After you have verified that published applications are installed and functionin
**Note**  
If you encounter any problems when verifying your application publication settings, see [Operations Troubleshooting](operations-troubleshooting-medv2.md).
 
After you have completed testing application publishing, you can test other MED-V workspace configurations to verify that they function as intended.
After you have completed testing your MED-V workspace package and have verified that it is functioning as intended, you can deploy the MED-V workspace to your enterprise.
## Related topics
[How to Test URL Redirection](how-to-test-url-redirection.md)
[How to Verify First Time Setup Settings](how-to-verify-first-time-setup-settings.md)

9
mdop/medv-v2/how-to-test-url-redirection.md
View File

@ -18,9 +18,7 @@ After your test of first time setup finishes, you can verify that the URL redire
**Important**  
The MED-V Host Agent must be running for URL redirection to function correctly.
 
**To test URL Redirection**
<a href="" id="bkmk-urlredir"></a>**To test URL Redirection**
1. Open an Internet Explorer browser in the host computer and enter a URL that you specified for redirection.
@ -45,20 +43,15 @@ The MED-V Host Agent must be running for URL redirection to function correctly.
**Note**  
It can take several seconds for the URL redirection changes to take place.
 
**Note**  
If you encounter any problems when verifying your URL redirection settings, see [Operations Troubleshooting](operations-troubleshooting-medv2.md).
 
After you have completed testing URL redirection in your MED-V workspace, you can test other configurations to verify that they function as intended.
After you have completed testing your MED-V workspace package and have verified that it is functioning as intended, you can deploy the MED-V workspace to your enterprise.
## Related topics
[How to Test Application Publishing](how-to-test-application-publishing.md)
[How to Verify First Time Setup Settings](how-to-verify-first-time-setup-settings.md)

7
windows/manage/uev-configuring-uev-with-system-center-configuration-manager.md
View File

@ -18,7 +18,6 @@ After you deploy User Experience Virtualization (UE-V) and its required features
## UE-V Configuration Pack supported features
The UE-V Configuration Pack includes tools to:
- Create or update UE-V settings location template distribution baselines
@ -103,10 +102,9 @@ It might be necessary to change the PowerShell execution policy to allow these s
1. Select **Administration &gt; Client Settings &gt; Properties**
2. In the **User Agent** tab, set the **PowerShell Execution Policy** to **Bypass**
 
**Create the first UE-V policy configuration item**
<a href="" id="bkmk-create"></a>**Create the first UE-V policy configuration item**
1. Copy the default settings configuration file from the UE-V Config Pack installation directory to a location visible to your ConfigMgr Admin Console:
@ -173,8 +171,7 @@ It might be necessary to change the PowerShell execution policy to allow these s
3. Reimport the CAB file. The version in ConfigMgr will be updated.
## Generate a UE-V Template Baseline
<a href="" id="bkmk-create2"></a>## Generate a UE-V Template Baseline
UE-V templates are distributed using a baseline containing multiple configuration items. Each configuration item contains the discovery and remediation scripts needed to install one UE-V template. The actual UE-V template is embedded within the remediation script for distribution using standard Configuration Item functionality.

2
windows/manage/uev-prepare-for-deployment.md
View File

@ -25,8 +25,6 @@ Whether you want to synchronize settings for only default Windows applications o
- [Define a settings storage location](uev-deploy-required-features.md#ssl)
- [Decide how to manage UE-V configurations](#config)
- [Enable the UE-V service](uev-deploy-required-features.md#enable-the-ue-v-service) on user computers
If you want to use UE-V to synchronize user-defined settings for custom applications (third-party or line-of-business), you’ll need to install and configure these optional additional UE-V features: