diff --git a/mdop/medv-v1/TOC.md b/mdop/medv-v1/TOC.md new file mode 100644 index 0000000000..9e402cf4f8 --- /dev/null +++ b/mdop/medv-v1/TOC.md @@ -0,0 +1,87 @@ +# [Microsoft Enterprise Desktop Virtualization 1](microsoft-enterprise-desktop-virtualization-planning-deployment-and-operations-guide-medvv2.md) +## [About This Guide[MEDV]](about-this-guidemedv.md) +## [Getting Started with MED-V](getting-started-with-med-v.md) +### [Overview of MED-V](overview-of-med-v.md) +### [High-Level Architecture[MEDV]](high-level-architecturemedv.md) +### [Key Scenarios for Using MED-V](key-scenarios-for-using-med-v.md) +### [About MED-V 1.0](about-med-v-10.md) +#### [MED-V 1.0 Supported Configurations[MEDV 1.0]](med-v-10-supported-configurationsmedv-10.md) +#### [MED-V 1.0 Installation Checklist](med-v-10-installation-checklist.md) +#### [MED-V 1.0 Release Notes[MEDV 1.0]](med-v-10-release-notesmedv-10.md) +### [About MED-V 1.0 SP1](about-med-v-10-sp1.md) +#### [MED-V 1.0 SP1 Supported Configurations[MEDV 1.0 SP1]](med-v-10-sp1-supported-configurationsmedv-10-sp1.md) +#### [MED-V 1.0 SP1 Upgrade Checklist[MEDV 1.0 SP1]](med-v-10-sp1-upgrade-checklistmedv-10-sp1.md) +#### [MED-V 1.0 SP1 and SP2 Release Notes[MEDV 1.0 SP1]](med-v-10-sp1-and-sp2-release-notesmedv-10-sp1.md) +## [MED-V Infrastructure Planning and Design](med-v-infrastructure-planning-and-design.md) +### [Define the Project Scope](define-the-project-scope.md) +### [Identify the Number of MED-V Instances](identify-the-number-of-med-v-instances.md) +### [Design the MED-V Server Infrastructure](design-the-med-v-server-infrastructure.md) +### [Design the MED-V Image Repositories](design-the-med-v-image-repositories.md) +## [MED-V Deployment and Configuration](med-v-deployment-and-configuration.md) +### [MED-V Installation Prerequisites](med-v-installation-prerequisites.md) +### [Supported Configurations[MEDV orientation]](supported-configurationsmedv-orientation.md) +#### [MED-V 1.0 Supported Configurations[MEDV 1.0]](med-v-10-supported-configurationsmedv-10.md) +#### [MED-V 1.0 SP1 Supported Configurations[MEDV 1.0 SP1]](med-v-10-sp1-supported-configurationsmedv-10-sp1.md) +### [Installation and Upgrade Checklists](installation-and-upgrade-checklists.md) +#### [MED-V 1.0 Installation Checklist](med-v-10-installation-checklist.md) +#### [MED-V 1.0 SP1 Upgrade Checklist[MEDV 1.0 SP1]](med-v-10-sp1-upgrade-checklistmedv-10-sp1.md) +### [Installing and Configuring MED-V Components](installing-and-configuring-med-v-components.md) +#### [How to Install and Configure the MED-V Server Component](how-to-install-and-configure-the-med-v-server-component.md) +#### [How to Configure the Image Web Distribution Server](how-to-configure-the-image-web-distribution-server.md) +#### [How to Install MED-V Client and MED-V Management Console](how-to-install-med-v-client-and-med-v-management-console.md) +#### [How to Uninstall MED-V Components[MEDVv2]](how-to-uninstall-med-v-componentsmedvv2.md) +### [Creating a Virtual PC Image for MED-V](creating-a-virtual-pc-image-for-med-v.md) +### [Creating a MED-V Workspace[MEDV 1.0 SP1]](creating-a-med-v-workspacemedv-10-sp1.md) +### [Configuring MED-V Workspace Policies](configuring-med-v-workspace-policies.md) +#### [How to Apply General Settings to a MED-V Workspace](how-to-apply-general-settings-to-a-med-v-workspace.md) +#### [How to Apply Virtual Machine Settings to a MED-V Workspace](how-to-apply-virtual-machine-settings-to-a-med-v-workspace.md) +#### [How to Configure a Domain User or Group[MEDVv2]](how-to-configure-a-domain-user-or-groupmedvv2.md) +#### [How to Configure Published Applications[MEDVv2]](how-to-configure-published-applicationsmedvv2.md) +#### [How to Configure Web Settings for a MED-V Workspace](how-to-configure-web-settings-for-a-med-v-workspace.md) +#### [How to Configure the Virtual Machine Setup for a MED-V Workspace](how-to-configure-the-virtual-machine-setup-for-a-med-v-workspace.md) +##### [How to Configure the Virtual Machine Setup for a MED-V Workspace[MEDVv2]](how-to-configure-the-virtual-machine-setup-for-a-med-v-workspacemedvv2.md) +##### [How to Configure VM Computer Name Pattern Properties[MEDVv2]](how-to-configure-vm-computer-name-pattern-propertiesmedvv2.md) +##### [Examples of Virtual Machine Configurations[v2]](examples-of-virtual-machine-configurationsv2.md) +#### [How to Apply Network Settings to a MED-V Workspace](how-to-apply-network-settings-to-a-med-v-workspace.md) +#### [How to Apply Performance Settings to a MED-V Workspace](how-to-apply-performance-settings-to-a-med-v-workspace.md) +#### [How to Import and Export a Policy](how-to-import-and-export-a-policy.md) +### [Configuring MED-V for Remote Networks](configuring-med-v-for-remote-networks.md) +### [Configuring MED-V Server for Cluster Mode](configuring-med-v-server-for-cluster-mode.md) +## [MED-V Operations](med-v-operations.md) +### [Using the MED-V Management Console User Interface](using-the-med-v-management-console-user-interface.md) +### [Creating a MED-V Image](creating-a-med-v-image.md) +#### [How to Create and Test a MED-V Image](how-to-create-and-test-a-med-v-image.md) +#### [How to Pack a MED-V Image](how-to-pack-a-med-v-image.md) +#### [How to Upload a MED-V Image to the Server](how-to-upload-a-med-v-image-to-the-server.md) +#### [How to Localize a MED-V Image](how-to-localize-a-med-v-image.md) +#### [How to Update a MED-V Image](how-to-update-a-med-v-image.md) +#### [How to Delete a MED-V Image](how-to-delete-a-med-v-image.md) +### [Deploying a MED-V Workspace Using an Enterprise Software Distribution System](deploying-a-med-v-workspace-using-an-enterprise-software-distribution-system.md) +#### [How to Install MED-V Client[ESDS]](how-to-install-med-v-clientesds.md) +#### [How to Deploy a Workspace Image[ESDS]](how-to-deploy-a-workspace-imageesds.md) +### [Deploying a MED-V Workspace Using a Deployment Package](deploying-a-med-v-workspace-using-a-deployment-package.md) +#### [How to Configure a Deployment Package](how-to-configure-a-deployment-package.md) +#### [How to Install MED-V Client[deployment package]](how-to-install-med-v-clientdeployment-package.md) +#### [How to Deploy a Workspace Image[deployment package]](how-to-deploy-a-workspace-imagedeployment-package.md) +### [Updating a MED-V Workspace Image](updating-a-med-v-workspace-image.md) +### [MED-V Client Operations](med-v-client-operations.md) +#### [How to Start and Exit the MED-V Client](how-to-start-and-exit-the-med-v-client.md) +#### [How to Start, Stop, and Restart a MED-V Workspace](how-to-start-stop-and-restart-a-med-v-workspace.md) +#### [How to View MED-V Settings and General Information](how-to-view-med-v-settings-and-general-information.md) +#### [How to Lock and Unlock a Workspace](how-to-lock-and-unlock-a-workspace.md) +#### [MED-V Client Tools[v2]](med-v-client-toolsv2.md) +## [Troubleshooting MED-V](troubleshooting-med-v.md) +## [Technical Reference[MEDV 1.0 SP1]](technical-referencemedv-10-sp1.md) +### [MED-V Reporting](med-v-reporting.md) +#### [How to Generate Reports [MEDVv2]](how-to-generate-reports-medvv2.md) +#### [How to Work with Reports](how-to-work-with-reports.md) +### [MED-V Trim Transfer Technology [MEDVv2]](med-v-trim-transfer-technology-medvv2.md) +### [How to Back Up and Restore a MED-V Server](how-to-back-up-and-restore-a-med-v-server.md) +### [How to Share Folders Between the Host and the MED-V Workspace](how-to-share-folders-between-the-host-and-the-med-v-workspace.md) +### [How to Set MED-V Workspace Deletion Options](how-to-set-med-v-workspace-deletion-options.md) +### [How to Set Advanced File Transfer Options](how-to-set-advanced-file-transfer-options.md) +### [How to Edit a Published Application with Advanced Settings](how-to-edit-a-published-application-with-advanced-settings.md) +### [How to Set Up Script Actions](how-to-set-up-script-actions.md) +### [Client Installation Command Line Reference](client-installation-command-line-reference.md) +### [How to Configure Image Pre-staging](how-to-configure-image-pre-staging.md) + diff --git a/mdop/medv-v1/about-med-v-20.md b/mdop/medv-v1/about-med-v-20.md new file mode 100644 index 0000000000..46d295b60c --- /dev/null +++ b/mdop/medv-v1/about-med-v-20.md @@ -0,0 +1,37 @@ +--- +title: About MED-V 2.0 +description: About MED-V 2.0 +ms.assetid: 7ec53f2c-db6e-4a6b-a069-99d0c25cd101 +author: MaggiePucciEvans +--- + +# About MED-V 2.0 + + +## In This Section + + +This section provides information related specifically to MED-V 2.0 and includes the following topics: + +[What's New in MED-V 2.0](whats-new-in-med-v-20.md) +Describes system requirements and new and changed features in MED-V 2.0. + +[MED-V 2.0 Supported Configurations](med-v-20-supported-configurations.md) +Describes the supported configurations for MED-V 2.0. + +[MED-V 2.0 Release Notes](med-v-20-release-notes.md) +Provides a list of known issues with MED-V 2.0. + +## Related topics + + +[Getting Started with MED-V](getting-started-with-med-vmedv2.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/authentication-of-med-v-end-users.md b/mdop/medv-v1/authentication-of-med-v-end-users.md new file mode 100644 index 0000000000..ea5f477e8b --- /dev/null +++ b/mdop/medv-v1/authentication-of-med-v-end-users.md @@ -0,0 +1,128 @@ +--- +title: Authentication of MED-V End Users +description: Authentication of MED-V End Users +ms.assetid: aaf96eb6-91d1-4f4d-9854-5fc73c7ae7ab +author: MaggiePucciEvans +--- + +# Authentication of MED-V End Users + + +The authentication of Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 end users is a very important security issue. In this context, authentication refers to verifying the identity of the MED-V end user. + +The following section provides information and guidance about end-user authentication in MED-V. + +## User Authentication in MED-V + + +Authentication in MED-V generally occurs at two levels: when a user first accesses MED-V and every time that they change their password. + +Depending on how you have configured MED-V settings for authentication, the end user is typically prompted at some point to enter their password, either the first time MED-V is started or the first time that they try to open a published application. + +There are several aspects of end-user authentication that you can control, including the following: + +Whether the credentials the end user enters are stored in Credential Manager + +In what manner the end user is presented with the option of entering and saving their password + +Depending on your company’s preferred process for managing end-user authentication, you can specify whether credential caching occurs for a particular MED-V workspace. Caching the credentials of an end user is helpful because they are only prompted one time for their password. If the end user is not allowed to save their password or they decide not to, every time that they start a new MED-V session, they must enter it again. For example, if MED-V is configured to start when the end user logs on to the host but Authentication is disabled, the end user is only prompted one time during logon. In this case, credentials are valid until the end user logs off from the host. + +If it is necessary, you can use Credential Manager to remove any stored end-user credentials. + +By default, credential storing is disabled, but you can change this setting through one of the following methods: + +**While you are creating the MED-V workspace package**. For more information, see [Create a MED-V Workspace Package](create-a-med-v-workspace-package.md). + +**After you have deployed the MED-V workspace**. Edit the MED-V cmdlet parameter UxCredentialCacheEnabled to set the Terminal Services registry key. For more information, see Windows PowerShell Help. + +After MED-V workspace deployment, you can set your preference for end-user authentication by modifying the Terminal Services policy named DisablePasswordSaving. DisablePasswordSaving controls whether the password saving check box appears on the RDP client dialog window and whether the MED-V credential prompt is displayed. + +Following is the policy path for the Terminal Services policy named DisablePasswordSaving. + +**Regedit:** + +HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Virtual Machine\\Policies\\DisablePasswordSaving + +**Note**   +The changes that you make to DisablePasswordSaving only affect the RDP prompt to a virtual machine. + +  + +The following table lists the different ways you can configure your settings for credential storing and the effects of the different configurations: + + +++++ + + + + + + + + + + + + + + + + + + + + + + + + +
ValueConfigurationResult

DisablePasswordSaving

Disabled

The MED-V prompt is presented and a check box to accept is available and cleared. If the end user selects the check box, credentials are cached for subsequent use. The end user also has the benefit of only being prompted when the password expires.

+

If the end user does not select the check box, the Remote Desktop Connection (RDC) Client prompt is presented instead of the MED-V prompt, and the check box to accept is cleared. If the end user selects the check box, the RDC Client credential is stored for later use.

+
+Important   +

RDC does not validate credentials when the end user enters them. If the end user caches the credentials through the RDC prompt, there is a risk that incorrect credentials might be stored. In this case, the incorrect credentials must be deleted in the Windows Credential Manager.

+
+
+  +

DisablePasswordSaving

Enabled

+Note   +

This configuration is more secure because it does not allow end user credentials to be cached.

+
+
+  +
+ +  + +By default, the MED-V installation sets a registry key in the guest to suppress the "password about to expire" prompt. The end user is only prompted for a password change on the host. Credentials that are updated on the host are passed to the guest. + +**Caution**   +If you use Group Policy in your environment, know that it can override the registry key causing the password prompts from the guest to reappear. + +  + +### Security Concerns with Authentication + +Even though caching the end user’s credentials provides the best user experience, you must be aware of the risks involved. + +When credential caching is enabled, the end user’s domain credential is stored in a reversible format within the Windows Credential Manager. As a result, an attacker could write a tool that runs as either a system level process or an end user process and that retrieves the end user's credentials. You can only lessen this risk by setting DisablePasswordSaving to **Enabled**. + +This same concern exists when MED-V authentication is disabled but the Terminal Services policy setting is enabled. + +## Related topics + + +[Security Best Practices for MED-V Operations](security-best-practices-for-med-v-operations.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/command-line-options-for-med-v-installation-files.md b/mdop/medv-v1/command-line-options-for-med-v-installation-files.md new file mode 100644 index 0000000000..c3c474ac32 --- /dev/null +++ b/mdop/medv-v1/command-line-options-for-med-v-installation-files.md @@ -0,0 +1,118 @@ +--- +title: Command-Line Options for MED-V Installation Files +description: Command-Line Options for MED-V Installation Files +ms.assetid: 7b8cd3e4-1d09-44a0-b690-f85b0d0a6b02 +author: MaggiePucciEvans +--- + +# Command-Line Options for MED-V Installation Files + + +When you install or uninstall Microsoft Enterprise Desktop Virtualization (MED-V) 2.0, you have the option of running the installation files at the command prompt. This section describes different options that you can specify when you install or uninstall MED-V at the command prompt. + +### Command-Line Arguments + +You can use the following command-line arguments together with their respective MED-V installation files. + + ++++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Installation FileArgumentAccepted ValuesTypeDescriptionDefault

Host Agent

MEDVDIR

<install path>

Installation

Change installed directory

Installation goes to Program Files\Microsoft Enterprise Desktop Virtualization.

MED-V Workspace Packager

MEDVDIR

<install path>

Installation

Change installed directory

Installation goes to Program Files\Microsoft Enterprise Desktop Virtualization.

MED-V workspace

INSTALLDIR

<install path>

Installation

Change installed directory

Installation goes to ProgramData\Microsoft\Medv\Workspace.

MED-V workspace

OVERWRITE VHD

0 or 1

Installation

Fail installation if VHD exists(0) or overwrite existing VHD(1).

Overwrite does not occur and installation fails if a virtual hard disk (VHD) already exists.

MED-V workspace

SUPPRESSMEDVLAUNCH

0 or 1

Installation

Start(0) or do not start(1) MED-V after MED-V workspace is installed.

If the MED-V workspace was installed with the user interface (UI), a check box on the Finish page controls whether to start MED-V.

MED-V workspace

DELETEDIFFDISKS

0 or 1

Uninstallation

Keep(0) or delete(1) VHDs created by MED-V

No VHDs are deleted.

+ +  + +### Examples of Command-Line Arguments + +The following example installs the MED-V workspace created by the MED-V workspace Packager. The installation file creates a log file in the Temp directory and runs the installation file in quiet mode, but does not start the MED-V Host Agent on completion. The installation file overwrites any VHD left behind by a previous installation that has the same name. + +``` syntax +setup.exe /l* %temp%\medv-workspace-install.log /qn SUPPRESSMEDVLAUNCH=1 OVERWRITEVHD=1 +``` + +The following example uninstalls the MED-V workspace that was previously installed. The installation file creates a log file in the Temp directory and runs the installation file in quiet mode. The installation file deletes any remaining virtual hard disk files from the file system. + +``` syntax +%ProgramData%\Microsoft\Medv\Workspace\uninstall.exe /l* %temp%\medv-workspace-uninstall.log /qn DELETEDIFFDISKS=1 +``` + +## Related topics + + +[Deploy the MED-V Components](deploy-the-med-v-components.md) + +[Technical Reference for MED-V](technical-reference-for-med-v.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/compacting-the-med-v-virtual-hard-disk.md b/mdop/medv-v1/compacting-the-med-v-virtual-hard-disk.md new file mode 100644 index 0000000000..95c7f36ff0 --- /dev/null +++ b/mdop/medv-v1/compacting-the-med-v-virtual-hard-disk.md @@ -0,0 +1,114 @@ +--- +title: Compacting the MED-V Virtual Hard Disk +description: Compacting the MED-V Virtual Hard Disk +ms.assetid: 5e6122d1-9847-4b33-adab-594919eec3c5 +author: MaggiePucciEvans +--- + +# Compacting the MED-V Virtual Hard Disk + + +Although it is optional, you can compact the virtual hard disk (VHD) to reclaim empty disk space and reduce the size of the VHD before you configure the Windows Virtual PC image. + +**Important**   +Before you proceed, create a backup copy of your Windows XP image. + +  + +**Preparing the Virtual Hard Disk** + +1. Open your Windows XP image. + + Click **Start**, click **All Programs**, click **Windows Virtual PC**, click **Windows Virtual PC**, then double-click your Windows XP image. + +2. Clear the DLL cache. + + 1. At a command prompt in the virtual machine, type **sfc /cachesize=1**. + + 2. Restart the virtual machine. + + 3. At a command prompt in the virtual machine, type **sfc /purgecache**. + +3. Delete unnecessary files, such as uninstallers, temp files, log files, page files, shared folders, and so on. + +4. Turn off System Restore. You can also specify this step in your Sysprep.inf file. + + 1. In **Control Panel**, double-click **System**, and then select the **System Restore** tab. + + 2. Select **Turn off System Restore**, and then click **OK**. + +5. Set maximum event log sizes and clear all events. + + 1. Open the event viewer. + + Click **Start**, click **Control Panel**, double-click **Administrative Tools**, then double-click **Event Viewer**. + + 2. Right-click **Application**, and click **Properties**. + + 3. In the **Log Size** area, set **Maximum Log Size** to 512KB and then select **Overwrite events as needed**. + + 4. Click **Clear Log**. In the **Event Viewer** dialog box that appears, click **No**. + + 5. In the **Properties** window, click **OK**. + + 6. Repeat steps a through e for the **Security** and **System** logs. + +6. Run the Disk Cleanup Tool. + + Click **Start**, click **All Programs**, click **Accessories**, click **System Tools**, and then click **Disk Cleanup**. + +7. Configure your page file as needed for your applications. + + 1. In **Control Panel**, double-click **System**, and then select the **Advanced** tab. + + 2. In the **Performance** area, click **Settings**. + + 3. In the **Virtual Memory** area, click **Change**. + + 4. Configure your page file settings. + +8. Shut down the Windows XP image. + +**Defragmenting and Pre-compacting the Virtual Hard Disk** + +1. In **Control Panel** on the host computer that is running Windows 7, click **Administrative Tools**, double-click **Computer Management**, then click **Disk Management**. + +2. By using the Disk Management Console, attach (mount) the virtual hard disk and then defragment the disk. + +3. By using an ISO extraction tool, extract the precompact.iso located in the \\Program Files\\Windows Virtual PC\\Integration Components folder. + +4. Use the precompact.exe program to compress the Windows XP virtual hard disk. + +5. By using the Disk Management Console, detach the virtual hard disk. + +**Compacting the Virtual Hard Disk** + +1. Open Windows Virtual PC. + + Click **Start**, click **All Programs**, click **Windows Virtual PC**, then click **Windows Virtual PC**. + +2. Right-click your Windows XP image and select **Settings**. + +3. Click **Hard Disk** for the one that corresponds to your Windows XP image, and then click **Modify**. + +4. Click **Compact virtual hard disk**. + +5. Click **Compact** and then click **OK**. + +Create a backup copy of your compacted virtual hard disk. + +## Related topics + + +[Configuring a Windows Virtual PC Image for MED-V](configuring-a-windows-virtual-pc-image-for-med-v.md) + +[Technical Reference for MED-V](technical-reference-for-med-v.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/configure-environment-prerequisites.md b/mdop/medv-v1/configure-environment-prerequisites.md new file mode 100644 index 0000000000..e5e3762560 --- /dev/null +++ b/mdop/medv-v1/configure-environment-prerequisites.md @@ -0,0 +1,55 @@ +--- +title: Configure Environment Prerequisites +description: Configure Environment Prerequisites +ms.assetid: 7379e8e5-1cb2-4b8e-8acc-5c04e26f8c91 +author: MaggiePucciEvans +--- + +# Configure Environment Prerequisites + + +Before you can deploy and run Microsoft Enterprise Desktop Virtualization (MED-V) 2.0, you must ensure that your environment meets the following minimum prerequisites. + +**Windows 7** + +The MED-V Host Agent and the MED-V Workspace Packager are only supported in Windows 7 or newer. + +**Windows XP SP3** + +The MED-V Guest Agent is only supported in Windows XP SP3. + +**.NET Framework 3.5 SP1** + +The MED-V Host and Guest agents and the MED-V Workspace Packager require the Microsoft .NET Framework 3.5 SP1. + +**Important**   +You must also install the update [KB959209](http://go.microsoft.com/fwlink/?LinkId=204950) (http://go.microsoft.com/fwlink/?LinkId=204950), which addresses several known application compatibility issues. + +  + +**Note**   +You must manually install the .NET Framework 3.5 SP1 and the update KB959209 into the Windows Virtual PC image that you prepare for use with MED-V. However, by default, the Microsoft .NET Framework 3.5 SP1 and the update are included when you install Windows 7 on the host computer. + +  + +**An Active Directory Infrastructure** + +Group Policy provides the centralized management and configuration of operating systems, applications, and users' settings in an Active Directory environment. + +## Related topics + + +[Configure Installation Prerequisites](configure-installation-prerequisites.md) + +[High-Level Architecture](high-level-architecturemedv2.md) + +[MED-V 2.0 Supported Configurations](med-v-20-supported-configurations.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/configure-installation-prerequisites.md b/mdop/medv-v1/configure-installation-prerequisites.md new file mode 100644 index 0000000000..aa6066bb0b --- /dev/null +++ b/mdop/medv-v1/configure-installation-prerequisites.md @@ -0,0 +1,94 @@ +--- +title: Configure Installation Prerequisites +description: Configure Installation Prerequisites +ms.assetid: ff9cf28a-3eac-4b6c-8ce9-bfc202f57947 +author: MaggiePucciEvans +--- + +# Configure Installation Prerequisites + + +The following instructions are prerequisites for installing and using Microsoft Enterprise Desktop Virtualization (MED-V) 2.0: + +[Windows Virtual PC](#bkmk-howtoinstallandconfiguremicrosoftvirtualpc7) + +[Windows Virtual PC Update](#bkmk-howtoinstallandconfiguremicrosoftvirtualpc7update) + +[Antivirus/Backup Software Configuration](#bkmk-antivirusbackupsoftwareconfiguration) + +## How to Install and Configure Windows Virtual PC + + +**Important**   +If a version of Virtual PC for Windows already exists on the host computer, you must uninstall it before you install Windows Virtual PC. + +  + +**To install Windows Virtual PC** + +1. Download [Windows Virtual PC](http://go.microsoft.com/fwlink/?LinkId=195918) from the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=195918). + +2. Run the installation file on the host computer, and follow the steps in the wizard. + +**Important**   +Windows Virtual PC includes the Integration Components package, which provides features that improve the interaction between the virtual environment and the physical computer. For example, it lets your mouse move between the host and the guest computers. MED-V requires the installation of the Integration Components package. + +  + +## How to Install and Configure the Windows Virtual PC Update + + +The Microsoft update associated with article KB977206 enables Windows XP Mode for computers without hardware-assisted virtualization (HAV) technology. We recommended that you install this update because some integration features might not work correctly if the Integration Components package in the guest operating system do not match the version of Windows Virtual PC that is installed on the host computer. + +**Important**   +You do not have to install this update when you are installing MED-V on host computers that are running Windows 7 with Service Pack 1. + +  + +**Tip**   +In addition to the update listed here, we recommend that you review all available Windows Virtual PC updates and apply those updates that are appropriate or necessary for your environment. + +  + +**To install the Windows Virtual PC Update** + +1. Download the required Windows Virtual PC update from the Microsoft Download Center. + + [32-bit Update](http://go.microsoft.com/fwlink/?LinkId=195919) (http://go.microsoft.com/fwlink/?LinkId=195919). + + [64-bit Update](http://go.microsoft.com/fwlink/?LinkId=195920) (http://go.microsoft.com/fwlink/?LinkId=195920). + +2. Run the installation file on the host computer in elevated mode, and follow the steps in the wizard. + + For more information about the hotfix package for Windows Virtual PC, see [article 977206](http://go.microsoft.com/fwlink/?LinkId=195921) (http://go.microsoft.com/fwlink/?LinkId=195921). + +## How to Configure Antivirus/Backup Software + + +To prevent antivirus activity from affecting the performance of the virtual desktop, we recommend, where you can, to exclude the following virtual machine file types from any antivirus or backup process that is running on the host computer: + +- \*.VMC + +- \*.VUD + +- \*.VSV + +- \*.VHD + +## Related topics + + +[Configure Environment Prerequisites](configure-environment-prerequisites.md) + +[High-Level Architecture](high-level-architecturemedv2.md) + +[MED-V 2.0 Supported Configurations](med-v-20-supported-configurations.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/configuring-a-windows-virtual-pc-image-for-med-v.md b/mdop/medv-v1/configuring-a-windows-virtual-pc-image-for-med-v.md new file mode 100644 index 0000000000..47ecf62eb2 --- /dev/null +++ b/mdop/medv-v1/configuring-a-windows-virtual-pc-image-for-med-v.md @@ -0,0 +1,207 @@ +--- +title: Configuring a Windows Virtual PC Image for MED-V +description: Configuring a Windows Virtual PC Image for MED-V +ms.assetid: d87a0df8-9e08-4d1e-bfb0-9dc3cebf0d28 +author: MaggiePucciEvans +--- + +# Configuring a Windows Virtual PC Image for MED-V + + +After you have installed everything that you want to include in your MED-V image, you can configure the image for use in Microsoft Enterprise Desktop Virtualization (MED-V) 2.0. The topics in this section provide guidance for configuring your MED-V image to run first time setup before you create your MED-V workspace package. + +First time setup prepares the MED-V workspace for an end user. The process creates a virtual machine from the image packaged in the MED-V workspace and then runs Windows Mini-Setup on the virtual machine. This includes the running of both custom setup scripts and the first time setup completion application, FtsCompletion.exe. + +Follow these steps to configure your MED-V image for running first time setup: + +1. As an option, you can compact the virtual hard disk (VHD) to reclaim empty disk space and reduce the size of the VHD before you continue with configuring the Windows Virtual PC image. For more information, see [Compacting the MED-V Virtual Hard Disk](compacting-the-med-v-virtual-hard-disk.md). + +2. Customize the virtual machine setup process. + +3. Seal the MED-V image by using Sysprep. + + **Customizing the Virtual Machine Setup Process** + +1. As part of preparing your image for use with MED-V, you can configure various settings on the virtual machine, such as specifying the settings for running Windows Update. Specify all the necessary virtual machine settings before you create the MED-V workspace package. + +2. Before you create the MED-V workspace package, we recommend that you disable restore points on the virtual machine to prevent the differencing disk from growing unbounded. For more information, see [How to turn off and turn on System Restore in Windows XP](http://go.microsoft.com/fwlink/?LinkId=195927) (http://go.microsoft.com/fwlink/?LinkId=195927). + + **Note**   + You can set up your Sysprep.inf file to disable restore points when first time setup is run. For an example of setting this GuiRunOnce key, see the sample Sysprep.inf file later in this section. + +   + +3. Configure the setup process to run Mini-Setup instead of the default Windows Welcome. You must either run the Sysprep tool by using the **-mini** switch, or select the **MiniSetup** check box in the graphical user interface. For more information, see [How to Seal the Image with Sysprep](#bkmk-seal). + + **Calling the First time setup Completion File** + + 1. An executable called FtsCompletion.exe is included as part of the installation of the MED-V Guest Agent. By default, it is located in the system drive of your MED-V image under **Program Files – Microsoft Enterprise Desktop Virtualization**. + + **Important**   + As the final step in the first time setup process, you must run this executable program. The user for whom the executable program is being called must be a member of the guest’s local administrator group. + +   + + 2. You can decide how you want to call this executable program, for example, through a script that is deployed with the MED-V workspace. You can call this executable as the last line of your Sysprep.inf file. For an example of how to call this executable program in your Sysprep.inf file, see the sample file later in this section. + +After you have completed customization of your MED-V image, you are ready to seal the image by using Sysprep. + +**Sealing the MED-V Image by Using Sysprep** + +1. The System Preparation tool (Sysprep) is a technology that you can use to perform image-based installations throughout the network with minimal intervention by an administrator or IT-Professional. + +2. In a MED-V environment, you can use Sysprep to assign unique security IDs (SID) and other settings to each MED-V workspace the first time that they are started. + + **Note**   + For more information about how to use Sysprep, see [Sysprep Technical Reference](http://go.microsoft.com/fwlink/?LinkId=195930) (http://go.microsoft.com/fwlink/?LinkId=195930). + +   + + **Caution**   + When you use non-ASCII characters in the Sysprep.inf file, you must save the file by using the encoding appropriate for the characters entered. Windows XP expects the Sysprep.inf file to be encoded by using the code page for the language that you are targeting. + + You must also make sure that the System Locale of the computers to which the MED-V workspace is deployed is set to handle the language specific characters that might be present in the Sysprep.inf file. To change the settings for the System Locale, follow these steps: + + 1. To open Region and Language, click **Start**, click **Control Panel**, and then click **Region and Language**. + + 2. Click the **Administrative** tab, and then click **Change System Locale** under **Language for non-Unicode programs**. + + If you are prompted for an administrator password or confirmation, type the administrator password or provide confirmation. + + 3. Select your preferred language and then click **OK**. + +   + + **To configure Sysprep on the MED-V Guest Computer** + + 1. Create a folder named *Sysprep* in the root of the MED-V image system drive. + + 2. Download the deploy.cab file. For more information, see [Windows XP Service Pack 3 Deployment Tools](http://go.microsoft.com/fwlink/?LinkId=195928) From the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=195928). + + 3. From the deploy.cab file, copy or extract the Setupmgr.exe, Sysprep.exe, and Setupcl.exe files to the Sysprep folder. + + 4. In the Sysprep folder, run **Setup Manager** (Setupmgr.exe) to create a Sysprep.inf answer file. + + Or, you can create this file manually or use your company’s existing file. For more information, see [How to use the Sysprep tool to automate successful deployment of Windows XP](http://go.microsoft.com/fwlink/?LinkId=195929) (http://go.microsoft.com/fwlink/?LinkId=195929). + + 5. Follow the **Setup Manager** wizard. + + **Important**   + You must configure the MED-V guest to join a domain that lets users log on by using the credentials that they use to log on to the MED-V host. + +   + + **Caution**   + When you configure a proxy account for joining virtual machines to the domain, know that it is possible for an end user to obtain the proxy account credentials. Take all the necessary security precautions to minimize risk, such as limiting account user rights. For more information about security concerns when you configure a Windows Virtual PC image for MED-V, see [Security Best Practices for MED-V Operations](security-best-practices-for-med-v-operations.md). + +   + + If end users must provide information during the first time setup process based on the parameters specified in the Sysprep.inf file, you must also specify that first time setup is run in **Attended** mode when you are creating your MED-V workspace package. If no information will be required from the end user, you can specify that first time setup is run in **Unattended** mode when you are creating your MED-V workspace package. For more information, see [Create a MED-V Workspace Package](create-a-med-v-workspace-package.md). + + Although you can specify any settings that you prefer, a MED-V best practice is that you create the Sysprep.inf file so that first time setup can be run in **Unattended** mode. This requires that you provide all of the required settings information as you continue through the **Setup Manager** wizard. + + **Caution**   + If you have set a local policy or registry entry to include a service level agreement (SLA) in your image (VHD), you must specify that first time setup is run in **Attended** mode or first time setup will fail. Or, a MED-V best practice is to enforce the SLA through Group Policy later so that the SLA is displayed to the end user after first time setup is finished. + +   + + **Note**   + You can configure the MED-V workspace to set certain Sysprep.inf settings based on the configuration of the host and the identity of the end user. For more information, see [Create a MED-V Workspace Package](create-a-med-v-workspace-package.md). + +   + + 6. Seal the MED-V image. + + **Important**   + We recommend that you make a backup copy of the MED-V image before sealing it. + +   + + After you have completed all the steps in the **Setup Manager** wizard, you are ready to run Sysprep to seal the MED-V image. + + **To run Sysprep** + + 1. Run the System Preparation Tool (Sysprep.exe) from the *Sysprep* folder that you created when you configured Sysprep in the MED-V virtual machine. + + 2. In the warning message box that appears, click **OK**. + + 3. In the **Options** dialog box, select the **Don't reset grace period for activation** and **Use Mini-Setup** check boxes. Also, make sure that the **Shutdown mode** box is set to **Shut down**. + + 4. Click **Reseal**. This removes identity information and clears event logs to prepare for first time setup. + + 5. If you are not satisfied with the information listed in the confirmation message box that appears, click **Cancel** and then change the selections. + + 6. Click **OK** to complete the system preparation process. + + After you have run Sysprep on your MED-V image, the virtual machine shuts down and is ready for use in creating a MED-V workspace. + +## Example + + +Here is an example of a Sysprep.inf file. + +``` syntax +;SetupMgrTag +[GuiUnattended] + EncryptedAdminPassword=NO + TimeZone=10 + OEMDuplicatorstring="MED_V v2 Host" + AdminPassword="administrator" + AutoLogon=Yes + AutoLogonCount=1 + OEMSkipRegional=1 + OemSkipWelcome=1 + +[UserData] + ProductKey= + FullName="MED-V User" + OrgName="Contoso" + ComputerName=* + +[Identification] + JoinDomain=domain.corp.contoso.com + DomainAdmin=UserName + DomainAdminPassword=Password + +[Networking] + InstallDefaultComponents=Yes + +[Branding] + BrandIEUsingUnattended=Yes + +[Proxy] + Proxy_Enable=0 + Use_Same_Proxy=0 + +[Unattended] + InstallFilesPath=C:\sysprep\i386 + TargetPath=\WINDOWS + UpdateServerProfileDirectory=1 + OemSkipEula=Yes + +[RegionalSettings] + LanguageGroup=1 + Language=00000409 + +[GuiRunOnce] +    Command0="wmic /namespace:\\root\default path SystemRestore call Disable %SystemDrive%\" +    Command1="c:\Program Files\Microsoft Enterprise Desktop Virtualization\FtsCompletion.exe" + +[sysprepcleanup] +``` + +## Related topics + + +[Create a MED-V Workspace Package](create-a-med-v-workspace-package.md) + +[Prepare a MED-V Image](prepare-a-med-v-image.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/configuring-advanced-settings-by-using-windows-powershell.md b/mdop/medv-v1/configuring-advanced-settings-by-using-windows-powershell.md new file mode 100644 index 0000000000..7bbbe02c89 --- /dev/null +++ b/mdop/medv-v1/configuring-advanced-settings-by-using-windows-powershell.md @@ -0,0 +1,103 @@ +--- +title: Configuring Advanced Settings by Using Windows PowerShell +description: Configuring Advanced Settings by Using Windows PowerShell +ms.assetid: 437a31cc-2a11-456f-b448-b0b869fb53f7 +author: MaggiePucciEvans +--- + +# Configuring Advanced Settings by Using Windows PowerShell + + +The MED-V workspace package that you create includes a Windows PowerShell script (.ps1) file that you can edit before you test and deploy your MED-V workspace package. This section provides information and guidance to help you manage MED-V configuration settings by using Windows PowerShell before you deploy the MED-V workspaces. + +## Using Windows PowerShell Cmdlets in MED-V + + +The following Windows PowerShell cmdlets are available in Microsoft Enterprise Desktop Virtualization (MED-V) 2.0: + +**New-MedvConfiguration** + +**Export-MedvConfiguration** + +**New-MedvWorkspace** + +**Export-MedvWorkspace** + +To access Windows PowerShell cmdlets for MED-V, open Windows PowerShell and type the following command to import the MED-V modules. + +``` syntax +Import-Module microsoft.medv +``` + +After the modules are imported, you can access inline help for the cmdlets by using the standard Windows PowerShell Help commands, **man** or **get-help**. For example, to access a description of the **New-MedvConfiguration** cmdlet including a complete list of available parameters, type the following command. + +``` syntax +get-help New-MedvConfiguration +``` + +You can also view help for specific parameters. For example, to view help for the parameter VmMemory, type the following: + +``` syntax +get-help New-MedvConfiguration -parameter VmMemory +``` + +To view a list of all MED-V configuration settings and their defaults, type the following command. + +``` syntax +New-MedvConfiguration -ForceDefaults +``` + +To view a list of all MED-V configuration settings and their current values, type the following command. + +``` syntax +gwmi -Class "Setting” -Namespace "root/microsoft/medv” +``` + +## Creating a MED-V Workspace with Custom Settings + + +After you successfully create a MED-V workspace package by using the MED-V Workspace Packager, a Windows PowerShell script is generated in the folder you specified for saving your packager files. The contents of this script show some of the available MED-V configuration settings that you can edit. + +Following these steps, you can customize the script and then run it in Windows PowerShell to create a MED-V workspace with the new settings. + +**Important**   +Run Windows PowerShell with administrative credentials, and ensure that the Windows PowerShell execution policy allows the running of scripts. + +1. Edit the Windows PowerShell script that was generated by the MED-V Workspace Packager, or author a new script with the configuration settings that you want. + +2. Run Windows PowerShell with administrative credentials and at the command prompt, type the following command. + + ``` syntax + & “.\.ps1” + ``` + + This command runs the Windows PowerShell script and runs the **New-MedvWorkspace** cmdlet to generate a new MED-V workspace package. The new packager files are saved in the folder that you originally specified for storing your MED-V Workspace Packager files. For additional help about this cmdlet, see the Windows PowerShell Help. + +  + +## Exporting a MED-V Configuration to a Registry File + + +You can update MED-V configuration settings after the MED-V workspace is installed. Use the **New-MedvConfiguration** cmdlet to specify the parameters that you want to change. For example, to create a registry file that changes the virtual machine memory setting, type the following commands. + +``` syntax +New-MedvConfiguration -VmMemory 1024 | Export-MedvConfiguration -Path c:\medvConfiguration\myConfig.reg +``` + +You can import the resultant registry file from the host computer to a MED-V workspace to apply the new configuration settings. + +## Related topics + + +[Managing MED-V Workspace Configuration Settings](managing-med-v-workspace-configuration-settings.md) + +[Test And Deploy the MED-V Workspace Package](test-and-deploy-the-med-v-workspace-package.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/create-a-med-v-workspace-package.md b/mdop/medv-v1/create-a-med-v-workspace-package.md new file mode 100644 index 0000000000..a72b95c1a0 --- /dev/null +++ b/mdop/medv-v1/create-a-med-v-workspace-package.md @@ -0,0 +1,433 @@ +--- +title: Create a MED-V Workspace Package +description: Create a MED-V Workspace Package +ms.assetid: 3f75fe73-41ac-4389-ae21-5efb2d437f4d +author: MaggiePucciEvans +--- + +# Create a MED-V Workspace Package + + +A MED-V workspace is the Windows XP desktop environment where end users interact with the virtual machine provided by MED-V. The administrator creates and customizes the MED-V workspace. The workspace consists of an image and the Group Policy that defines the rules and functionality of the MED-V workspace. + +You can create multiple MED-V workspaces, each customized with its own configuration, settings, and rules. A user, group, or multiple users or groups can be associated with each MED-V workspace. The customization makes that MED-V workspace available only for that user or group. + +Use the **MED-V Workspace Packager** to create MED-V workspaces. The **MED-V Workspace Packager** is divided into two main sections: + +- A main panel that includes three buttons that you use to create and manage MED-V workspaces. The **Create a MED-V Workspace Package** button opens the **Create MED-V Workspace Package Wizard** that you use to create your MED-V workspaces. + +- A **Help Center** on the right-hand side of the window that provides information and guidance to help you create, test, and manage your MED-V workspaces. + +**Important**   +Before you can use the **MED-V Workspace Packager**, you must first make sure that the Windows PowerShell execution policy is set to Unrestricted. + +`Set-ExecutionPolicy Unrestricted` + +In addition, the SAN policy for the computer on which the **MED-V Workspace Packager** is run must be set to “Online All”. To check the setting of the SAN policy, run the following commands at a command prompt with administrative credentials: + +`diskpart.exe` + +`DISKPART> san` + +`DISKPART> exit` + +If it is necessary, change the SAN policy to "Online All" by typing the following commands at the command prompt with administrative credentials: + +`diskpart.exe` + +`DISKPART> san policy=onlineall` + +`DISKPART> exit` + +  + +**Important**   +If automatic disk encryption software is installed on the computer that you use to mount the virtual hard disk and build the MED-V workspace package, you must disable the software before you start. Otherwise, you cannot use the MED-V workspace on any other computer. + +  + +The information we provide here can help you create your MED-V workspace deployment package. + +## Prerequisites + + +Before you start to build your MED-V workspace deployment package, verify that you have access to the following items: + +- **A prepared Windows XP image** + + For more information about how to create a Windows XP image for use with MED-V, see [Prepare a MED-V Image](prepare-a-med-v-image.md). + +- **A text file or list that contains URL redirection information** + + Your URL redirection text file or list contains those URLs that you want redirected from the host computer to Internet Explorer in the MED-V workspace. When you are using the packaging wizard to create your MED-V workspace, you import, type, or copy and paste this redirection information as one of the steps in the package creation process. + + **Note**   + URL redirection in MED-V only supports the protocols HTTP and HTTPS. MED-V does not provide support for FTP or any other protocols. + +   + + Enter each web address on a single line, for example: + + http://www.contoso.com/webapps/webapp1 + + http://www.contoso.com/webapps/webapp2 + + http://\*.contoso.com + + http://www.contoso.com/webapps/\* + + **Important**   + If you import a text file that includes a URL that uses special characters (such as ~ ! @ \# and so on), make sure that you specify UTF-8 encoding when you save the text file. Special characters do not import correctly into the MED-V Workspace Packager if the text file was saved using the default ANSI encoding. + +   + +## Packaging a MED-V Workspace for a Language Other than the Language of the MED-V Workspace Packager Computer + + +By default, the MED-V workspace supports characters in both the language of the computer and in English. To create a MED-V workspace for a language other than the one installed on the computer, specify **-loc \[locale\]** in the PowerShell script (.ps1) after the MED-V workspace name. + +To create a MED-V workspace package in a language other than the default language of the MED-V Workspace Packager computer, generate a script in the default language by running the MED-V Workspace Packager and then modifying the output script as required for your locale. The script is located in the MED-V workspace output directory that was specified during packaging. The names of the locale settings are on the .WXL files in the following directory: + +C:\\Program Files\\Microsoft Enterprise Desktop Virtualization\\WindowsPowerShell\\Modules\\Microsoft.Medv.Administration.Commands.WorkspacePackager\\locale + +## Creating a MED-V Workspace Package + + +To create a MED-V workspace package, follow these steps: + +**** + +1. To open the **MED-V Workspace Packager**, click **Start**, click **All Programs**, click **Microsoft Enterprise Desktop Virtualization**, and then click **MED-V Workspace Packager**. + +2. On the **MED-V Workspace Packager** main panel, click **Create a MED-V Workspace Package**. + + The MED-V **Create MED-V Workspace Package Wizard** appears. The wizard consists of the following pages: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Package Information

Specify a name for the MED-V workspace and select a folder where the MED-V workspace package files are saved.

Select Windows XP Image

Specify your prepared Windows XP Virtual PC image.

First Time Setup

Specify the setup process that MED-V follows during first time setup.

MED-V Messages

Specify the messages and optional URL for Help information that the end user sees during first time setup.

Naming Computers

Specify how the MED-V virtual machine is named.

Copy Settings from Host

Specify how the settings for the MED-V workspace are defined.

Startup and Networking

Specify the settings for starting the MED-V workspace, networking, and user credentials.

Web Redirection

Specify a text file or a list of the URLs you want redirected to Internet Explorer in the MED-V workspace.

Summary

Verify your MED-V workspace settings and start to build your MED-V workspace deployment package.

+ +   + +3. On the **Package Information** page, enter a name for the MED-V workspace and select a folder where the MED-V workspace package files are saved. + + **Warning**   + You must name the MED-V workspace and specify a folder to continue. + +   + + After you have finished, click **Next**. + +4. On the **Select Windows XP Image** page, specify the location of your prepared MED-V Windows XP Virtual PC image (.vhd file). + + **Warning**   + You must specify a Windows XP VHD image to continue. + +   + + After you have finished, click **Next**. + +5. On the **First Time Setup** page, select whether you want first time setup to run while attended or unattended and whether you want the MED-V workspace used separately or used by all end users on a shared computer. + + If you select **Unattended setup, without any notification**, the end user is not informed before first time setup is run and the virtual machine is not shown to the end user during first time setup. In addition, the **MED-V Messages** page of the wizard is hidden because no messages are required if first time setup runs in a completely unattended mode. + + If you select **Unattended setup, but notify end users before first time setup begins**, the end user is informed before first time setup is run. However, the virtual machine is not shown to the end user during first time setup. + + Select **Attended setup** if the end user must enter information during first time setup. + + The default behavior is **Unattended setup, but notify end users before first time setup begins**. + + **Caution**   + If you created the Sysprep.inf file so that Mini-Setup requires user input to complete, you must select **Attended setup** or problems might occur during first time setup. + +   + + You can also specify how a MED-V workspace is used on computers that are shared by multiple end users. You can decide that you want to create a unique MED-V workspace for each end user or that you want the MED-V workspace made available to all end users who share the computer. The default is that the MED-V workspace is unique for each end user. + + **Important**   + We recommend that you disable the fast user switching feature in Windows if you configure the MED-V workspace to be accessed by all users on a shared computer. Problems can occur if an end user logs on by using the fast user switching feature in Windows when another user is still logged on. + +   + + **Tip**   + When you create a name mask for the MED-V workspace on the **Naming Computers** page, make sure that each virtual machine on a shared computer has a unique computer name. + +   + + You can also specify whether the MED-V workspace is added to the Administrators group or administrator credentials are managed outside MED-V. By default, the MED-V workspace is not automatically added to the Administrators group. + + After you have finished, click **Next**. + +6. On the **MED-V Messages** page, specify the following messages that the end user sees during first time setup: + + - The message that the end user sees when first time setup starts. + + - The message that the end user sees if first time setup fails or an error occurs. + + **Note**   + The **MED-V Messages** page of the wizard is hidden if you selected **Unattended setup, without any notification** on the **First Time Setup** page. + +   + + You can also specify an optional URL location for help information that is provided to the end user when first time setup is running. + + For example, the URL can point to an internal IT webpage with answers to questions such as "How long will this take and how will I know when it has completed?" or "What do you do if you get an error message?" + + **Note**   + If you specify a URL, a link is shown during first time setup that points the end user to this help information. If you do not specify a URL, no link is provided. + +   + + After you have finished, click **Next**. + +7. On the **Naming Computers** page, you can specify whether computer naming is managed by MED-V or by a system management tool, such as Sysprep. The default is that computer naming is managed by a system management tool. + + If you specify that computer naming is managed by MED-V, select a predefined computer naming convention (mask) from the drop-down list. A preview of a sample computer name appears that is based on the computer that you are using to build the MED-V workspace package. + + If you select one of the custom naming conventions, the fields you can specify are limited to the following characters: + + - The prefix and suffix fields are limited to the characters A-Z, a-z, 0-9, and the special characters ! @ \# $ % ^ & ( ) - \_ ' { } . and ~. + + - The hostname and username fields are limited to the digits 0 through 9. + + **Important**   + Computer names must be unique and are limited to a maximum of 15 characters. When you decide on your computer naming method, consider end users who have multiple computers or that share a computer, and avoid using computer name masks that could cause a collision on the network. + +   + + **Caution**   + The computer name settings that you specify on this page override those specified in the Sysprep.inf answer file. + +   + + After you have finished, click **Next**. + +8. On the **Copy Settings from Host** page, you can select the following settings to specify how the MED-V workspace is configured: + + **Caution**   + The settings that you specify on this page that are copied from the host computer to the MED-V workspace override those specified in the Sysprep.inf answer file. + +   + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Copy regional settings

Select this check box to copy the regional settings from the host computer to the MED-V workspace.

If you select this check box, the following settings are set in the Sysprep.inf file:

+ 
[RegionalSettings]
+    Language
+    SystemLocale
+    UserLocale
+    UserLocale_DefaultUser
+    InputLocale
+    InputLocale_DefaultUser
+

Copy user settings

Select this check box to copy certain user settings, such as user name and company name, from the host to the MED-V workspace.

If you select this check box, the following settings are set in the Sysprep.inf file:

+ 
[UserData]
+    OrgName
+    FullName
+
+ Note   +

Personal settings, such as Internet browsing history, are not copied over to the MED-V workspace.

+
+
+   +

Copy domain name

Select this check box to let the guest join the same domain as the host.

+ Important   +

The MED-V guest must be configured to join a domain that lets users log on by using the credentials that they use to log on to the MED-V host.

+
+
+   +

Copy domain organizational unit

Select this check box to copy the domain organizational unit from the host computer to the MED-V workspace. This check box is only enabled if you select to copy the domain name from the host computer.

+ +   + + After you have finished, click **Next**. + +9. On the **Startup and Networking** page, you can change the default behavior for the following settings: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Start MED-V workspace

Choose whether to start the MED-V workspace at user logon, at first use, or to let the end user decide when the MED-V workspace starts.

The MED-V workspace starts in one of two ways: either when the end user logs on or when they first start an action that requires MED-V, such as opening a published application or entering a URL that requires redirection.

+

You can either define this setting for the end user or let the end user control how MED-V starts.

+
+ Note   +

If you specify that the end user decides, the default behavior they experience is that the MED-V workspace starts when they log on. They can change the default by right-clicking the MED-V icon in the notification area and selecting MED-V User Settings. If you define this setting for the end user, they cannot change how MED-V starts.

+
+
+   +

Networking

Select Shared or Bridged for your networking setting. The default is Shared.

Shared - The MED-V workspace uses Network Address Translation (NAT) to share the host's IP for outgoing traffic.

+

Bridged - The MED-V workspace has its own network address, typically obtained through DHCP.

Store credentials

Choose whether you want to store the end user credentials.

The default behavior is that credential storing is disabled so that the end user must be authenticated every time that they log on.

+
+ Important   +

Even though caching the end user’s credentials provides the best user experience, you should be aware of the risks involved.

+

The end user’s domain credential is stored in a reversible format in the Windows Credential Manager. As a result, an attacker could write a program that retrieves the password and could gain access to the user’s credentials. You can only lessen this risk by disabling the storing of end-user credentials.

+
+
+   +
+ +   + + After you have finished, click **Next**. + +10. On the **Web Redirection** page, you can enter, paste, or import a list of the URLs that are redirected to Internet Explorer in the MED-V workspace. For more information about how to configure your URL redirection information, see [Prerequisites](#bkmk-prereq). + + You can also specify how Internet Explorer in the MED-V workspace is configured for end users. By default, the Internet zone security level is set to High. Also, certain default browsing capabilities, such as the address bar, are removed. This default configuration of Internet Explorer in the MED-V workspace provides a more secure browsing environment for end users. + + **Caution**   + By changing the default settings, you can customize Internet Explorer in the MED-V workspace. However, realize that if you change the default settings so as to make them less secure, you can expose your organization to those security risks that are present in older versions of Internet Explorer. For more information, see [Security Best Practices for MED-V Operations](security-best-practices-for-med-v-operations.md). + +   + + After you have finished, click **Next**. + +11. On the **Summary** page, you can review the packaging settings for this MED-V workspace. If you want to change any settings, click the **Previous** button to return to the relevant page. After you have finished reviewing the settings, click **Create**. + + The **Completion** page of the **Create MED-V Workspace Package Wizard** opens to show the progress of the package creation. + + **Note**   + The MED-V workspace package creation process might take several minutes to complete, depending on the size of the VHD specified. + +   + + If the MED-V workspace package is created successfully, the **Completion** page displays a list of the files that you created and their respective locations. The following is a list of the files that are created and their descriptions: + + - **setup.exe**—an installation program that you deploy and run on end-user computers to install the MED-V workspaces. + + - **<*workspace\_name*>.msi**—an installer file that you deploy to the end-user computers. The setup.exe file will run this file to install the MED-V workspaces. + + - **<*vhd\_name*>.medv**—a compressed VHD file that you deploy to the end-user computers. The setup.exe file uses it when it installs the MED-V workspaces. + + - **<*workspace\_name*>.reg**—the configuration settings that are installed when the setup.exe, <*workspace\_name*>.msi, and <*vhd\_name*>.medv files are deployed and setup.exe is run. + + - **<*workspace\_name*>.ps1**—a Windows PowerShell script that you can use to rebuild the registry file and re-build the MED-V workspace package. + + **Important**   + Before deployment, you can edit configuration settings by updating the .ps1 file that has your preferred method of script editing, such as Windows PowerShell. After you change the .ps1 file, use that file to rebuild the MED-V workspace package that you deploy to your enterprise. For more information, see [Configuring Advanced Settings by Using Windows PowerShell](configuring-advanced-settings-by-using-windows-powershell.md). + + However, after the MED-V workspace is deployed, you must edit configuration settings through the registry. For a list and description of the configuration settings, see [Managing MED-V Workspace Configuration Settings](managing-med-v-workspace-configuration-settings.md). + +   + +12. Click **Close** to close the packaging wizard and return to the **MED-V Workspace Packager**. + +Your MED-V workspace package is now ready for testing before deployment. + +## Related topics + + +[Configuring Advanced Settings by Using Windows PowerShell](configuring-advanced-settings-by-using-windows-powershell.md) + +[Testing the MED-V Workspace Package](testing-the-med-v-workspace-package.md) + +[Prepare a MED-V Image](prepare-a-med-v-image.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/creating-a-windows-virtual-pc-image-for-med-v.md b/mdop/medv-v1/creating-a-windows-virtual-pc-image-for-med-v.md new file mode 100644 index 0000000000..22ce77f181 --- /dev/null +++ b/mdop/medv-v1/creating-a-windows-virtual-pc-image-for-med-v.md @@ -0,0 +1,150 @@ +--- +title: Creating a Windows Virtual PC Image for MED-V +description: Creating a Windows Virtual PC Image for MED-V +ms.assetid: fd7c0b1a-0769-4e7b-ad1a-dad19cca081f +author: MaggiePucciEvans +--- + +# Creating a Windows Virtual PC Image for MED-V + + +Before you can deliver a MED-V workspace to users, you have to first prepare a virtual hard disk that you use to build the MED-V workspace installer package for Microsoft Enterprise Desktop Virtualization (MED-V) 2.0. To prepare the necessary virtual hard disk, you must create a Windows Virtual PC image that contains the required operating system, updates, and software to let you later deploy applications and URL redirection information to users. This section provides guidance about how to create the virtual hard disk. + +To create a virtual image for MED-V, you must follow these steps. + +1. [Create a Windows Virtual PC image](#bkmk-creatingavirtualmachinebyusingmicrosoftvirtualpc) + +2. [Install Windows XP on the image](#bkmk-installingwindowsxpontovpc) + +3. [Install the .NET Framework on the image](#bkmk-installingnet) + +4. [Apply updates to the image](#bkmk-applypatchestovpc) + +5. [Install Integration Components](#bkmk-installintegration) + +## Creating a Windows Virtual PC Image + + +To create a Windows Virtual PC image, see the Windows Virtual PC documentation: + +- [Windows Virtual PC Home Page](http://go.microsoft.com/fwlink/?LinkId=148103) (http://go.microsoft.com/fwlink/?LinkId=148103). + +- [Windows Virtual PC Help](http://go.microsoft.com/fwlink/?LinkId=182378) (http://go.microsoft.com/fwlink/?LinkId=182378). + +Alternately, if you already have a Windows Imaging (WIM) file that you want to use as the basis for your virtual image, you can convert it to a VHD that you use to build the MED-V workspace. For more information about how to convert a WIM to a virtual hard disk, see [Native VHD Support in Windows 7](http://go.microsoft.com/fwlink/?LinkId=195922) (http://go.microsoft.com/fwlink/?LinkId=195922). + +**Important**   +MED-V only supports one virtual hard disk per virtual machine and only one partition on each virtual disk. + +  + +After you have created your virtual hard disk, install Windows XP on the image. + +## Installing Windows XP on a Windows Virtual PC Image + + +MED-V requires that Windows XP SP3 is installed on the Windows Virtual PC image before you build the MED-V workspace. + +For more information about how to install Windows XP, see [Create a virtual machine and install a guest operating system](http://go.microsoft.com/fwlink/?LinkId=182379) (http://go.microsoft.com/fwlink/?LinkId=182379). + +## Installing the .NET Framework 3.5 SP1 on a Windows Virtual PC Image + + +You must manually install the .NET Framework 3.5 SP1 and the update KB959209 into the Windows Virtual PC image that you prepare for use with MED-V. The update [KB959209](http://go.microsoft.com/fwlink/?LinkId=204950) (http://go.microsoft.com/fwlink/?LinkId=204950) addresses several known application compatibility issues. + +## Applying Updates to the Windows Virtual PC Image + + +After you have installed Windows XP on your virtual machine, install any required Windows XP updates on the image, such as SP3. You can also install certain optional updates for better performance. + +**Important**   +MED-V requires that Windows XP SP3 be running on the guest operating system. + +  + +**Warning**   +When you install updates to Windows XP, make sure that you remain on the version of Internet Explorer in the guest that you intend to use in the MED-V workspace. For example, if you intend to run Internet Explorer 6 in the MED-V workspace, make sure that any updates that you install now do not include Internet Explorer 7 or Internet Explorer 8. In addition, we recommend that you configure the registry to prevent automatic updates from upgrading Internet Explorer. + +  + +### Installing an Optional Performance Update + +Although it is optional, we recommend that you install the following update for [hotfix KB972435](http://go.microsoft.com/fwlink/?LinkId=201077) (http://go.microsoft.com/fwlink/?LinkId=201077). This update increases the performance of shared folders in a Terminal Services session: + +**Note**   +The update is publically available. However, you might be prompted to accept an agreement for Microsoft Services. Follow the prompts on the successive webpages to retrieve this hotfix. + +  + +### Configuring a Group Policy Performance Update + +By default, Group Policy is downloaded to a computer one byte at a time. This causes delays while MED-V is being joined to the domain. To increase the performance of Group Policy, set the following registry key value to the registry: + +Registry subkey: HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon + +Entry: BufferPolicyReads + +Type: DWORD + +Value: 1 + +## Installing Integration Components + + +Windows Virtual PC includes the Integration Components package. This provides features that improve the interaction between the virtual environment and the physical computer. For example, the Integration Components package lets your mouse move between the host and the guest computers. + +**Important**   +MED-V requires the installation of the Integration Components package. + +  + +When you configure the virtual image to work with MED-V, you must manually install the Integration Components package on the guest operating system to make the integration features that are available. + +For more information about how to install and use the Integration Components package, see the following: + +- [Install or Upgrade the Integration Components Package](http://go.microsoft.com/fwlink/?LinkId=195923) (http://go.microsoft.com/fwlink/?LinkId=195923). + +- [About Integration Features](http://go.microsoft.com/fwlink/?LinkId=195924) (http://go.microsoft.com/fwlink/?LinkId=195924). + +### Installing RemoteApp Update + +After you install the Integration Components package, you are prompted to install the following update: "Update for Windows XP SP3 to enable RemoteApp." This is a required component for MED-V. + +**Important**   +If you are not prompted to install the RemoteApp update, you must download and install it manually. For more information and instructions about how to download this update, see [Update for Windows XP SP3 to enable RemoteApp](http://go.microsoft.com/fwlink/?LinkId=195925) (http://go.microsoft.com/fwlink/?LinkId=195925). + +  + +### Enabling Remote Desktop + +By default, Remote Desktop is enabled after you install the Integration Components package. For MED-V to be operational, ensure that Remote Desktop is enabled, and do not distribute any Group Policy that disables it. + +For information about how to enable Remote Desktop, see [Enable or disable Remote Desktop](http://go.microsoft.com/fwlink/?LinkId=201162) (http://go.microsoft.com/fwlink/?LinkId=201162). + +## Customizing Internet Explorer by Using the Internet Explorer Administration Kit + + +If you want, you can use the Internet Explorer Administration Kit to customize Internet Explorer on the guest operating system. For more information, see the [Internet Explorer 6 Administration Kit and Deployment Guide](http://go.microsoft.com/fwlink/?LinkId=200007) (http:// go.microsoft.com/fwlink/?LinkId=200007). + +**Warning**   +You should consider security concerns associated with customizing Internet Explorer in the MED-V workspace. For more information, see [Security Best Practices for MED-V Operations](security-best-practices-for-med-v-operations.md). + +  + +After your virtual hard disk is installed with an up-to-date guest operating system, you can install applications on the image. + +## Related topics + + +[Installing Applications on a Windows Virtual PC Image](installing-applications-on-a-windows-virtual-pc-image.md) + +[Configuring a Windows Virtual PC Image for MED-V](configuring-a-windows-virtual-pc-image-for-med-v.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/define-and-plan-your-med-v-deployment.md b/mdop/medv-v1/define-and-plan-your-med-v-deployment.md new file mode 100644 index 0000000000..c7b6df8f2a --- /dev/null +++ b/mdop/medv-v1/define-and-plan-your-med-v-deployment.md @@ -0,0 +1,36 @@ +--- +title: Define and Plan your MED-V Deployment +description: Define and Plan your MED-V Deployment +ms.assetid: a90945cc-dc37-4548-963d-e0c6f8ba0467 +author: MaggiePucciEvans +--- + +# Define and Plan your MED-V Deployment + + +Use the information in this section when you plan your Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 project. + +## In This Section + + +[Determining How MED-V Will Be Deployed](determining-how-med-v-will-be-deployed.md) +Provides information to help you determine how to deploy MED-V throughout your enterprise. + +[Identifying the Number and Types of MED-V Workspaces](identifying-the-number-and-types-of-med-v-workspaces.md) +Provides information to help you identify the computers in your enterprise that require MED-V and to calculate the disk space necessary for a MED-V deployment. + +## Related topics + + +[End-to-End Planning Scenario for MED-V 2.0](end-to-end-planning-scenario-for-med-v-20.md) + +[Planning for MED-V](planning-for-med-v.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/deploy-the-med-v-components.md b/mdop/medv-v1/deploy-the-med-v-components.md new file mode 100644 index 0000000000..e6f9d3f99c --- /dev/null +++ b/mdop/medv-v1/deploy-the-med-v-components.md @@ -0,0 +1,42 @@ +--- +title: Deploy the MED-V Components +description: Deploy the MED-V Components +ms.assetid: fc2c5ef2-9c71-412a-8f6c-93df248f77d6 +author: MaggiePucciEvans +--- + +# Deploy the MED-V Components + + +This section provides information about how to deploy the Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 components and how to uninstall the components. + +## In This Section + + +[How to Install the MED-V Workspace Packager](how-to-install-the-med-v-workspace-packager.md) +Describes how to install the MED-V Workspace Packager, which you use to create MED-V workspaces. + +[How to Deploy the MED-V Components Through an Electronic Software Distribution System](how-to-deploy-the-med-v-components-through-an-electronic-software-distribution-system.md) +Describes how to manually install the MED-V components by using an electronic software distribution (ESD) system. + +[How to Manually Install the MED-V Host Agent](how-to-manually-install-the-med-v-host-agent.md) +Describes how to install the MED-V Host Agent. + +[How to Uninstall the MED-V Components](how-to-uninstall-the-med-v-components.md) +Describes how to uninstall the MED-V components. + +## Related topics + + +[MED-V 2.0 Deployment Overview](med-v-20-deployment-overview.md) + +[Prepare the Deployment Environment for MED-V](prepare-the-deployment-environment-for-med-v.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/deploying-the-med-v-workspace-package.md b/mdop/medv-v1/deploying-the-med-v-workspace-package.md new file mode 100644 index 0000000000..84f381313b --- /dev/null +++ b/mdop/medv-v1/deploying-the-med-v-workspace-package.md @@ -0,0 +1,42 @@ +--- +title: Deploying the MED-V Workspace Package +description: Deploying the MED-V Workspace Package +ms.assetid: f314425a-d60f-4b8d-b71f-d13d1da9297f +author: MaggiePucciEvans +--- + +# Deploying the MED-V Workspace Package + + +After you have tested your Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 installer package, you can deploy it throughout your enterprise by using your company’s preferred method of provisioning software and other applications. + +**Note**   +When you are ready to deploy, we recommend that you install the MED-V workspace by running the setup.exe executable program that is included in your MED-V workspace installer package. + +  + +**Warning**   +Before you can install the MED-V workspace, you must first install the MED-V Host Agent. + +  + +## In This Section + + +[How to Deploy a MED-V Workspace Through an Electronic Software Distribution System](how-to-deploy-a-med-v-workspace-through-an-electronic-software-distribution-system.md) +Provides information about how to deploy MED-V workspaces by using an ESD system. + +[How to Deploy a MED-V Workspace in a Windows 7 Image](how-to-deploy-a-med-v-workspace-in-a-windows-7-image.md) +Provides information about how to deploy a MED-V workspace in a Windows 7 image. + +[How to Deploy a MED-V Workspace Manually](how-to-deploy-a-med-v-workspace-manually.md) +Provides information about how to manually deploy a MED-V workspace. + +  + +  + + + + + diff --git a/mdop/medv-v1/deployment-of-med-v.md b/mdop/medv-v1/deployment-of-med-v.md new file mode 100644 index 0000000000..b3c6e39d1e --- /dev/null +++ b/mdop/medv-v1/deployment-of-med-v.md @@ -0,0 +1,43 @@ +--- +title: Deployment of MED-V +description: Deployment of MED-V +ms.assetid: 52ea8ae4-ec2e-4cb8-ab38-e6400f47d3ba +author: MaggiePucciEvans +--- + +# Deployment of MED-V + + +The topics in this section help you prepare your environment for deploying Microsoft Enterprise Desktop Virtualization (MED-V) 2.0. + +## In This Section + + +[End-to-End Deployment Scenario for MED-V 2.0](end-to-end-deployment-scenario-for-med-v-20.md) +Describes an end-to-end deployment scenario for MED-V 2.0. + +[MED-V 2.0 Supported Configurations](med-v-20-supported-configurations.md) +Describes the supported configurations for MED-V 2.0. + +[MED-V 2.0 Deployment Overview](med-v-20-deployment-overview.md) +Describes the requirements for deploying MED-V 2.0. + +[Prepare the Deployment Environment for MED-V](prepare-the-deployment-environment-for-med-v.md) +Provides procedures for configuring the MED-V 2.0 environment and installation prerequisites. + +[Deploy the MED-V Components](deploy-the-med-v-components.md) +Describes how to install the MED-V Host Agent, the MED-V Workspace Packager, and other components required to run MED-V 2.0. + +## Related topics + + +[Microsoft Enterprise Desktop Virtualization 2.0](index.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/deployment-troubleshooting.md b/mdop/medv-v1/deployment-troubleshooting.md new file mode 100644 index 0000000000..550be696c8 --- /dev/null +++ b/mdop/medv-v1/deployment-troubleshooting.md @@ -0,0 +1,58 @@ +--- +title: Deployment Troubleshooting +description: Deployment Troubleshooting +ms.assetid: 9ee980f2-4e77-4020-9f0e-8c2ffdc390ad +author: MaggiePucciEvans +--- + +# Deployment Troubleshooting + + +This topic includes information to help you troubleshoot deployment issues in Microsoft Enterprise Desktop Virtualization (MED-V) 2.0. + +## Troubleshooting Issues in MED-V Deployment + + +The following issue might occur when you deploy MED-V. The solution helps troubleshoot this issue. + +**Problems Occur if Installing MED-V for Current User Only.** MED-V only supports the installation of the MED-V Workspace Packager, the MED-V Host Agent, and the MED-V workspace for all users. Installing for the current user only causes failures in the installation of the components and in the setup of the MED-V workspace. + +**Solution** + +Never use the option **ALLUSERS=””** when installing the MED-V components. + +**MED-V Requires Exclusive Use of the Virtualization Stack.** Only one virtualization stack can be run at a time on a computer. Windows Virtual PC must use the virtual stack, and MED-V depends on Windows Virtual PC. Therefore, if you try to deploy or use MED-V when other applications are running that use the virtual stack, MED-V cannot run or be successfully installed. + +**Solution** + +Close any application that is running that uses the virtualization stack before you install or run MED-V. + +**Shortcuts Remain after Uninstall.** By default, when you uninstall MED-V, shortcuts in the end user’s **Start** menu are removed. However, in certain situations, such as for end users who are running roaming profiles, shortcuts to MED-V published applications remain in the end user’s **Start** menu. + +**Solution** + +To manually delete the remaining shortcuts on the **Start** menu, right-click the shortcuts, and then click **Remove**. + +**Disable Logon Message Group Policy Setting in the MED-V Workspace.** If the Windows XP logon message is enabled in the MED-V workspace, the end user must log on every time they want to open a MED-V virtual application. This creates a poor user experience. + +**Solution** + +Disable the following Group Policy settings in the MED-V virtual machine: + +**Interactive logon: Message text for users attempting to log on** + +**Interactive logon: Message title for users attempting to log on** + +## Related topics + + +[Operations Troubleshooting](operations-troubleshooting-medv2.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/detecting-network-changes-that-affect-med-v.md b/mdop/medv-v1/detecting-network-changes-that-affect-med-v.md new file mode 100644 index 0000000000..26668e4245 --- /dev/null +++ b/mdop/medv-v1/detecting-network-changes-that-affect-med-v.md @@ -0,0 +1,87 @@ +--- +title: Detecting Network Changes that Affect MED-V +description: Detecting Network Changes that Affect MED-V +ms.assetid: fd29b95a-cda2-464d-b86d-50b6bd64b4ca +author: MaggiePucciEvans +--- + +# Detecting Network Changes that Affect MED-V + + +The Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 solution lets you configure your environment to detect certain network changes that might occur after MED-V workspaces are deployed and that can affect MED-V. + +The feature includes a component running in the guest operating system that is notified of network configuration changes on the host computer. It allows a non-Microsoft ESD or other application that is running in the guest to resolve to the same network endpoints that the host ESD or application resolves to. + +**Note**   +This feature is only available if the virtual machine is configured for network address translation (NAT) mode. If the virtual machine is configured for BRIDGED mode, no change indications are generated. + +  + +This section provides information and instruction to assist you in monitoring those network changes that can affect MED-V. + +## To detect network changes for MED-V + + +After you have deployed your MED-V workspaces, you can monitor changes to certain network configurations by preforming the following tasks: + +1. Create a Managed Object Format (MOF) file that will look for the network configuration changes that you want to monitor. The following code shows an example of the MOF file that you can create. + + ``` syntax +#pragma namespace ("\\\\.\\root\\ccm\\NetworkConfig") + + class CCM_IPConfig + { + [NotNull: ToInstance ToSubClass] uint32 AddressFamily; // AF_INET, AF_INET6 + [Key, NotNull: ToInstance ToSubClass] string IPAddress; // IPv4 or IPv6 address + [NotNull: ToInstance ToSubClass] string SubnetMask; // IPv4 subnet mask + }; + + class CCM_NetworkAdapter + { + [Key, NotNull: ToInstance ToSubClass] string Name; + [NotNull: ToInstance ToSubClass] uint32 DHCPEnabled = 0; + [NotNull: ToInstance ToSubClass] uint32 Quarantined = 0; // To check if it is quarantined. + CCM_IPConfig IPConfigInfo[]; + }; + + [singleton] + class CCM_NetworkAdapters + { + [NotNull: ToInstance ToSubClass] String ProviderName; // MED-V or other provider + CCM_NetworkAdapter AdaptersInfo[]; + }; + ``` + +2. Compile the MOF file. + +3. Install the MOF file in the guest. + +After you have installed the MOF file, you can create an event subscription that subscribes to Windows Management Instrumentation (WMI) creation, modification, or deletion events for the **CCM\_NetworkAdapters** class. This detects the following changes to the host: + +Are there any configuration changes to the network, such as changes to the IP address or network adapter? + +Is the network available or unavailable? + +Was the network setup changed from BRIDGED mode to NAT mode? + +Was the network setup changed from NAT mode to BRIDGED mode? + +A MED-V component on the host monitors the network for these changes and then signals the guest of the change. A component in the guest creates a WMI instance to monitor the MED-V workspace for these changes. + +The event subscription you created provides notification through the WMI system when one or more of these network changes – creation, modification, or deletion – occurs. + +## Related topics + + +[Monitor MED-V Workspaces](monitor-med-v-workspaces.md) + +[Manage MED-V Workspace Settings](manage-med-v-workspace-settings.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/determining-how-med-v-will-be-deployed.md b/mdop/medv-v1/determining-how-med-v-will-be-deployed.md new file mode 100644 index 0000000000..a8387afe2c --- /dev/null +++ b/mdop/medv-v1/determining-how-med-v-will-be-deployed.md @@ -0,0 +1,41 @@ +--- +title: Determining How MED-V Will Be Deployed +description: Determining How MED-V Will Be Deployed +ms.assetid: addbfef6-799e-4fe7-87d2-7e096a5ef5a5 +author: MaggiePucciEvans +--- + +# Determining How MED-V Will Be Deployed + + +You can determine how you might deploy MED-V throughout your enterprise by evaluating your existing infrastructure, a review of which you can take advantage of for your deployment. + +## Determine How You Will Deploy MED-V + + +Because MED-V is a desktop-based solution, it works with your existing infrastructure. For example, if you currently deploy applications to physical computers by using an electronic software distribution system, you can also use your electronic software distribution system to deploy to MED-V workspaces. + +If you are currently using an electronic software distribution solution, you can use that to distribute MED-V workspaces and their dependent applications. You can also use this solution for distribution of subsequent applications after MED-V is deployed. For more information about deploying MED-V with an ESD, see [How to Deploy a MED-V Workspace Through an Electronic Software Distribution System](how-to-deploy-a-med-v-workspace-through-an-electronic-software-distribution-system.md). + +**Note**   +Whichever electronic software distribution solution that you use, you must be familiar with the requirements of your particular solution. If you are using System Center Configuration Manager 2007 R2 or a later version, see the [Configuration Manager Documentation Library](http://go.microsoft.com/fwlink/?LinkId=66999) in the Microsoft Technical Library (http://go.microsoft.com/fwlink/?LinkId=66999). + +  + +You might prefer to install MED-V in a Windows 7 image. Then, after you deploy the Windows 7 images throughout your enterprise, MED-V is ready to be installed when an end user needs it. For more information, see [How to Deploy a MED-V Workspace in a Windows 7 Image](how-to-deploy-a-med-v-workspace-in-a-windows-7-image.md). + +## Related topics + + +[Define and Plan your MED-V Deployment](define-and-plan-your-med-v-deployment.md) + +[Planning for MED-V](planning-for-med-v.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/end-to-end-deployment-scenario-for-med-v-20.md b/mdop/medv-v1/end-to-end-deployment-scenario-for-med-v-20.md new file mode 100644 index 0000000000..3ec00e93ff --- /dev/null +++ b/mdop/medv-v1/end-to-end-deployment-scenario-for-med-v-20.md @@ -0,0 +1,50 @@ +--- +title: End-to-End Deployment Scenario for MED-V 2.0 +description: End-to-End Deployment Scenario for MED-V 2.0 +ms.assetid: 91bb5a9a-5fb1-4743-8494-9d4dee2ec222 +author: MaggiePucciEvans +--- + +# End-to-End Deployment Scenario for MED-V 2.0 + + +This sample scenario for Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 helps you deploy the MED-V components in your enterprise by using multiple scenarios end-to-end. You can think of this sample scenario as a case study that helps put the individual scenarios and procedures in context. + +This section provides basic information and directions for deploying MED-V components as an end-to-end solution in your enterprise. + +## MED-V Deployment Step-by-step Scenario + + +The topics in this step-by-step scenario include the following: + +- [MED-V 2.0 Supported Configurations](med-v-20-supported-configurations.md) discusses the requirements that you must have to install and run Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 in your environment. This topic specifies the operating system requirements, configuration requirements, and MED-V workspace requirements. This topic also includes localization information about the languages that MED-V 2.0 supports. + +- [MED-V 2.0 Deployment Overview](med-v-20-deployment-overview.md) discusses general information and instructions to help you install and deploy MED-V throughout your enterprise. The MED-V components are client-based and are delivered and managed by using your existing enterprise infrastructure and processes. This topic provides an overview of the MED-V solution that includes information about the MED-V installation files and the MED-V components that you deploy. This topic also provides a high-level overview of the MED-V installation and deployment process. + +- [Prepare the Deployment Environment for MED-V](prepare-the-deployment-environment-for-med-v.md) discusses how to prepare your environment for a MED-V 2.0 deployment. This section describes the prerequisites that are required for the MED-V environment, such as Microsoft Windows 7 and an Active Directory infrastructure in which you use Group Policy to provide centralized management and configuration of operating systems, applications, and users' settings. This section also describes the prerequisites that you must have for installing and deploying MED-V 2.0 throughout your enterprise, such as Windows Virtual PC and the required Windows Virtual PC update. + +- [Deploy the MED-V Components](deploy-the-med-v-components.md) discusses the different ways you can install all of the necessary installation files and MED-V components throughout your enterprise. To install and deploy MED-V, you typically follow these steps: + + 1. Install the **MED-V Workspace Packager** on the administrator computer that you will use to build the MED-V workspace packages. For more information, see [How to Install the MED-V Workspace Packager](how-to-install-the-med-v-workspace-packager.md). + + 2. Create and test your MED-V workspace packages. For more information, see [Create a MED-V Workspace Package](create-a-med-v-workspace-package.md) and [Testing the MED-V Workspace Package](testing-the-med-v-workspace-package.md). + + 3. Deploy MED-V throughout your enterprise by using your company’s existing method for deploying applications. For more information, see [Deploying the MED-V Workspace Package](deploying-the-med-v-workspace-package.md). + +## Related topics + + +[Deployment of MED-V](deployment-of-med-v.md) + +[End-to-End Planning Scenario for MED-V 2.0](end-to-end-planning-scenario-for-med-v-20.md) + +[End-to-End Operations Scenario for MED-V 2.0](end-to-end-operations-scenario-for-med-v-20.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/end-to-end-operations-scenario-for-med-v-20.md b/mdop/medv-v1/end-to-end-operations-scenario-for-med-v-20.md new file mode 100644 index 0000000000..9cd66d9e3b --- /dev/null +++ b/mdop/medv-v1/end-to-end-operations-scenario-for-med-v-20.md @@ -0,0 +1,64 @@ +--- +title: End-to-End Operations Scenario for MED-V 2.0 +description: End-to-End Operations Scenario for MED-V 2.0 +ms.assetid: 1d87f5f3-9fc5-4731-8bd1-c155714f34ee +author: MaggiePucciEvans +--- + +# End-to-End Operations Scenario for MED-V 2.0 + + +This sample scenario for Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 helps you deploy and manage MED-V by using multiple scenarios end-to-end. You can think of this sample scenario as a case study that helps put the individual scenarios and procedures in context. + +This section provides basic information and directions for creating, deploying, and managing MED-V workspaces as an end-to-end solution in your enterprise. + +## MED-V Operations Step-by-step Scenario + + +The step-by-step procedures that you follow in a MED-V operations scenario include the following: + +- [Creating a Windows Virtual PC Image for MED-V](creating-a-windows-virtual-pc-image-for-med-v.md#bkmk-creatingavirtualmachinebyusingmicrosoftvirtualpc) reviews how to create and configure a Windows Virtual PC image for MED-V. Before you can deliver a MED-V workspace to users, you must first prepare a virtual hard disk (VHD) that you use to build the MED-V workspace installer package for MED-V. + +- [Creating a Windows Virtual PC Image for MED-V](creating-a-windows-virtual-pc-image-for-med-v.md#bkmk-installingwindowsxpontovpc) reviews how to install the Windows XP SP3 operating system on your Windows Virtual PC image. MED-V requires that Windows XP SP3 is installed on the Windows Virtual PC image before you build the MED-V workspace. + +- [Creating a Windows Virtual PC Image for MED-V](creating-a-windows-virtual-pc-image-for-med-v.md#bkmk-installingnet) reviews how to manually install the .NET Framework 3.5 SP1 and the update KB959209 into the Windows Virtual PC image that you prepare for use with MED-V. MED-V requires the .NET Framework 3.5 SP1, and the update [KB959209](http://go.microsoft.com/fwlink/?LinkId=204950) (http://go.microsoft.com/fwlink/?LinkId=204950) addresses several known application compatibility issues. + +- [Creating a Windows Virtual PC Image for MED-V](creating-a-windows-virtual-pc-image-for-med-v.md#bkmk-applypatchestovpc) reviews how to update your Windows XP image with the latest software updates and other hotfixes necessary or important for running MED-V. + +- [Creating a Windows Virtual PC Image for MED-V](creating-a-windows-virtual-pc-image-for-med-v.md#bkmk-installintegration) reviews how to install the integration components package in your Windows XP image. These provide features that improve the interaction between the virtual environment and the physical computer. + +- [Installing Applications on a Windows Virtual PC Image](installing-applications-on-a-windows-virtual-pc-image.md) reviews how you can install certain kinds of software on your Windows XP image that are helpful when you are running MED-V, such as an electronic software distribution system and antivirus software. + +- [Configuring a Windows Virtual PC Image for MED-V](configuring-a-windows-virtual-pc-image-for-med-v.md) discusses how to configure the image by using Sysprep to make sure that it is ready for use with MED-V. The prepared MED-V image is then used to create your MED-V workspace package. + +- [Create a MED-V Workspace Package](create-a-med-v-workspace-package.md) reviews how to build the MED-V workspace package that you deploy throughout your enterprise. You deploy the MED-V workspace package to install the MED-V workspace on end-user computers. A MED-V workspace is the Windows XP desktop environment from which end users interact with the virtual machine provided by MED-V. + +- [Testing the MED-V Workspace Package](testing-the-med-v-workspace-package.md) discusses how to create a test environment in which you can test the functionality of the MED-V workspace package, such as first time setup settings and application publishing. After you have completed testing your MED-V workspace package and have verified that it is functioning as intended, you can deploy it throughout your enterprise. + +- [Deploying the MED-V Workspace Package](deploying-the-med-v-workspace-package.md) discusses how to deploy the MED-V workspace either by using an electronic software distribution system or in a Windows 7 image. Or if you prefer, this section also shows you how you can deploy the MED-V workspace manually. + +- [Monitor MED-V Workspaces](monitor-med-v-workspaces.md) reviews how to monitor the deployment of MED-V workspaces to determine whether first time setup completed successfully. Monitoring the success of first time setup is important because MED-V is not in a usable state until first time setup has completed successfully. This section also shows you can set up your environment to detect those network changes that can affect MED-V. + +- [Manage MED-V Workspace Applications](manage-med-v-workspace-applications.md) reviews how to install and remove or publish and unpublish applications on a deployed MED-V workspace. This section also shows how to manually update software in a MED-V workspace and how to manage automatic updates. The MED-V workspace is a virtual machine that contains a separate operating system whose automatic software update process must be managed exactly like the physical computers in your enterprise. + +- [Manage MED-V URL Redirection](manage-med-v-url-redirection.md) reviews how to add and remove web address redirection settings on the deployed MED-V workspace. You can add or remove URL redirection information through the registry or by rebuilding the MED-V workspace. You can also use the wizard on the MED-V Workspace Packager to manage web address redirection. + +- [Manage MED-V Workspace Settings](manage-med-v-workspace-settings.md) reviews how to view and edit MED-V configuration settings by using the MED-V Workspace Packager. This section lists all the configurable MED-V registry keys and includes the type, default, and description of each. This section also includes information about how to manage printers in MED-V workspaces. In MED-V 2.0, printer redirection gives users a consistent printing experience between the MED-V virtual machine and the host computer. + +## Related topics + + +[Operations for MED-V](operations-for-med-v.md) + +[End-to-End Planning Scenario for MED-V 2.0](end-to-end-planning-scenario-for-med-v-20.md) + +[End-to-End Deployment Scenario for MED-V 2.0](end-to-end-deployment-scenario-for-med-v-20.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/end-to-end-planning-scenario-for-med-v-20.md b/mdop/medv-v1/end-to-end-planning-scenario-for-med-v-20.md new file mode 100644 index 0000000000..80543c2172 --- /dev/null +++ b/mdop/medv-v1/end-to-end-planning-scenario-for-med-v-20.md @@ -0,0 +1,42 @@ +--- +title: End-to-End Planning Scenario for MED-V 2.0 +description: End-to-End Planning Scenario for MED-V 2.0 +ms.assetid: e7833883-be93-4b42-9fa3-5c4d9a919058 +author: MaggiePucciEvans +--- + +# End-to-End Planning Scenario for MED-V 2.0 + + +This sample scenario for Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 helps you achieve your goal of planning your MED-V deployment by using multiple scenarios end-to-end. You can think of this sample scenario as a case study that helps put the individual scenarios and procedures in context. + +This section provides basic information and directions for planning you MED-V deployment as an end-to-end solution in your enterprise. + +## MED-V Planning Step-by-Step Scenario + + +The topics in this step-by-step scenario include the following: + +- [High-Level Architecture](high-level-architecturemedv2.md) discusses the high-level system architecture and component design of MED-V 2.0. MED-V enhances Windows Virtual PC to run two operating systems on one device, adding virtual image delivery, Group Policy-based provisioning, and centralized management. By using MED-V, you can easily configure, deploy, and manage corporate Windows Virtual PC images on any Windows-based desktop running Windows 7 Professional, Enterprise, or Windows 7 Ultimate. + +- [Define and Plan your MED-V Deployment](define-and-plan-your-med-v-deployment.md) discusses the considerations for planning your MED-V 2.0 deployment. This topic provides direction about identifying the systems in your enterprise that receive MED-V and calculating disk space requirements. This topic also helps evaluate your existing infrastructure and determines how it can be used for MED-V deployment. + +- [MED-V 2.0 Best Practices](med-v-20-best-practices.md) discusses the recommended best practices for planning, installing, deploying, and managing MED-V 2.0 in your environment. These best practices include recommendations that produce faster run times, better operability during first time setup, increased performance, and better virtual machine management. + +## Related topics + + +[Planning for MED-V](planning-for-med-v.md) + +[End-to-End Deployment Scenario for MED-V 2.0](end-to-end-deployment-scenario-for-med-v-20.md) + +[End-to-End Operations Scenario for MED-V 2.0](end-to-end-operations-scenario-for-med-v-20.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/example-med-v-checklists.md b/mdop/medv-v1/example-med-v-checklists.md new file mode 100644 index 0000000000..e2adf2ab5c --- /dev/null +++ b/mdop/medv-v1/example-med-v-checklists.md @@ -0,0 +1,43 @@ +--- +title: Example MED-V Checklists +description: Example MED-V Checklists +ms.assetid: cf9c33e8-1b7a-4306-92f6-edbb70ab23b5 +author: MaggiePucciEvans +--- + +# Example MED-V Checklists + + +This section provides example checklists that you can reference when you plan your MED-V project, prepare your environment, and deploy the MED-V components and MED-V workspaces throughout your enterprise. + +## In this Section + + +[Example MED-V Environment Planning Checklist](example-med-v-environment-planning-checklist.md) +Describes the tasks to be completed when planning your MED-V environment. + +[Example MED-V Project Planning Checklist](example-med-v-project-planning-checklist.md) +Describes the tasks to be completed when planning your MED-V project. + +[Example MED-V System Installation Checklist](example-med-v-system-installation-checklist.md) +Provides a list of all the steps required for installing MED-V 2.0. + +[Example MED-V Image Preparation Checklist](example-med-v-image-preparation-checklist.md) +Describes the tasks to be completed when you prepare your MED-V image for deployment. + +[Example MED-V Workspace Deployment Checklist](example-med-v-workspace-deployment-checklist.md) +Describes the tasks to be completed when you deploy your MED-V workspace. + +## Related topics + + +[Technical Reference for MED-V](technical-reference-for-med-v.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/example-med-v-environment-planning-checklist.md b/mdop/medv-v1/example-med-v-environment-planning-checklist.md new file mode 100644 index 0000000000..ab76d560ff --- /dev/null +++ b/mdop/medv-v1/example-med-v-environment-planning-checklist.md @@ -0,0 +1,53 @@ +--- +title: Example MED-V Environment Planning Checklist +description: Example MED-V Environment Planning Checklist +ms.assetid: 877d1660-abef-4e81-ab3a-a8a3ec181d26 +author: MaggiePucciEvans +--- + +# Example MED-V Environment Planning Checklist + + +The following checklist provides a high-level list of items to consider and outlines the steps that you should take when planning your Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 environment. + + ++++ + + + + + + + + + + + + + + + + + + + + + + + + +
StepReference

Review the components of a MED-V deployment.

[High-Level Architecture](high-level-architecturemedv2.md)

Ensure that your computing environment meets the supported configurations required for installing MED-V 2.0.

[MED-V 2.0 Supported Configurations](med-v-20-supported-configurations.md)

Determine how you want to design your MED-V deployment.

[Define and Plan your MED-V Deployment](define-and-plan-your-med-v-deployment.md)

Review the list of best practices for ensuring that your MED-V deployment environment is more secure.

[Security and Protection for MED-V](security-and-protection-for-med-v.md)

+ +  + +  + +  + + + + + diff --git a/mdop/medv-v1/example-med-v-image-preparation-checklist.md b/mdop/medv-v1/example-med-v-image-preparation-checklist.md new file mode 100644 index 0000000000..35ef08fc19 --- /dev/null +++ b/mdop/medv-v1/example-med-v-image-preparation-checklist.md @@ -0,0 +1,49 @@ +--- +title: Example MED-V Image Preparation Checklist +description: Example MED-V Image Preparation Checklist +ms.assetid: d69f252f-624b-439e-814b-b68cdaf7d582 +author: MaggiePucciEvans +--- + +# Example MED-V Image Preparation Checklist + + +The following checklist provides a high-level list of items to consider and outlines the steps to take when you prepare your MED-V image for deployment. + + ++++ + + + + + + + + + + + + + + + + + + + + +
StepReference

Create a virtual machine that is running Windows XP SP3 with updates and additions.

[Creating a Windows Virtual PC Image for MED-V](creating-a-windows-virtual-pc-image-for-med-v.md)

Install any predeployment software that you want on the MED-V image.

[Installing Applications on a Windows Virtual PC Image](installing-applications-on-a-windows-virtual-pc-image.md)

Package the MED-V image by using Sysprep.

[Configuring a Windows Virtual PC Image for MED-V](configuring-a-windows-virtual-pc-image-for-med-v.md)

+ +  + +  + +  + + + + + diff --git a/mdop/medv-v1/example-med-v-project-planning-checklist.md b/mdop/medv-v1/example-med-v-project-planning-checklist.md new file mode 100644 index 0000000000..4647f4b0de --- /dev/null +++ b/mdop/medv-v1/example-med-v-project-planning-checklist.md @@ -0,0 +1,53 @@ +--- +title: Example MED-V Project Planning Checklist +description: Example MED-V Project Planning Checklist +ms.assetid: 2b599bcb-1808-43ba-a689-1642bda24511 +author: MaggiePucciEvans +--- + +# Example MED-V Project Planning Checklist + + +The following checklist provides a high-level list of items to consider and outlines the steps that you can take when planning your Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 project. + + ++++ + + + + + + + + + + + + + + + + + + + + + + + + +
StepReference

Determine how you can use MED-V to help solve your application compatibility issues.

[Planning for Application Operating System Compatibility](planning-for-application-operating-system-compatibility.md)

Plan an end-to-end deployment scenario for your organization.

[End-to-End Planning Scenario for MED-V 2.0](end-to-end-planning-scenario-for-med-v-20.md)

Define the project scope by defining the end users and determining the MED-V images to be managed.

[Define and Plan your MED-V Deployment](define-and-plan-your-med-v-deployment.md)

Review the list of best practices for ensuring that your MED-V deployment is more secure.

[Security and Protection for MED-V](security-and-protection-for-med-v.md)

+ +  + +  + +  + + + + + diff --git a/mdop/medv-v1/example-med-v-system-installation-checklist.md b/mdop/medv-v1/example-med-v-system-installation-checklist.md new file mode 100644 index 0000000000..3f633e1f33 --- /dev/null +++ b/mdop/medv-v1/example-med-v-system-installation-checklist.md @@ -0,0 +1,53 @@ +--- +title: Example MED-V System Installation Checklist +description: Example MED-V System Installation Checklist +ms.assetid: 9e5673ba-dee4-4680-9c57-a149beab14d3 +author: MaggiePucciEvans +--- + +# Example MED-V System Installation Checklist + + +The following checklist provides a high-level list of items to consider and outlines the steps to take when you install Microsoft Enterprise Desktop Virtualization (MED-V) 2.0. + + ++++ + + + + + + + + + + + + + + + + + + + + + + + + +
StepReference

Ensure that your computing environment meets the supported configurations that are required for installing MED-V 2.0.

[MED-V 2.0 Supported Configurations](med-v-20-supported-configurations.md)

Plan and design the MED-V deployment.

[Planning for MED-V](planning-for-med-v.md)

Verify that the required installation prerequisites are configured.

[Configure Installation Prerequisites](configure-installation-prerequisites.md)

Install the MED-V Host Agent and MED-V Workspace Packager.

[Deploy the MED-V Components](deploy-the-med-v-components.md)

+ +  + +  + +  + + + + + diff --git a/mdop/medv-v1/example-med-v-workspace-deployment-checklist.md b/mdop/medv-v1/example-med-v-workspace-deployment-checklist.md new file mode 100644 index 0000000000..3d6ccacce7 --- /dev/null +++ b/mdop/medv-v1/example-med-v-workspace-deployment-checklist.md @@ -0,0 +1,53 @@ +--- +title: Example MED-V Workspace Deployment Checklist +description: Example MED-V Workspace Deployment Checklist +ms.assetid: d8857883-9b2d-40ac-9136-59e4e20e02fe +author: MaggiePucciEvans +--- + +# Example MED-V Workspace Deployment Checklist + + +The following checklist provides a high-level list of items to consider and outlines the steps that you should take when you deploy your MED-V workspace. + + ++++ + + + + + + + + + + + + + + + + + + + + + + + + +
StepReference

Prepare the MED-V image for deployment.

[Prepare a MED-V Image](prepare-a-med-v-image.md)

Create the MED-V workspace deployment package.

[Create a MED-V Workspace Package](create-a-med-v-workspace-package.md)

Test the MED-V workspace installer package.

[Testing the MED-V Workspace Package](testing-the-med-v-workspace-package.md)

Deploy the MED-V workspace installer package.

[Deploying the MED-V Workspace Package](deploying-the-med-v-workspace-package.md)

+ +  + +  + +  + + + + + diff --git a/mdop/medv-v1/getting-started-with-med-vmedv2.md b/mdop/medv-v1/getting-started-with-med-vmedv2.md new file mode 100644 index 0000000000..9ed056d7a4 --- /dev/null +++ b/mdop/medv-v1/getting-started-with-med-vmedv2.md @@ -0,0 +1,40 @@ +--- +title: Getting Started with MED-V +description: Getting Started with MED-V +ms.assetid: 283734d7-231c-45b6-92c9-c95a46ec3628 +author: MaggiePucciEvans +--- + +# Getting Started with MED-V + + +This section provides general information for administrators who are evaluating and using Microsoft Enterprise Desktop Virtualization (MED-V) 2.0. + +## In This Section + + +[Overview of MED-V](overview-of-med-vmedv2.md) +Provides general information about the MED-V solution to your application compatibility issues. + +[Planning for Application Operating System Compatibility](planning-for-application-operating-system-compatibility.md) +Provides planning guidance for evaluating MED-V to help solve application operating system compatibility issues. + +[High-Level Architecture](high-level-architecturemedv2.md) +Describes the components of a MED-V deployment. + +[About MED-V 2.0](about-med-v-20.md) +Provides information specifically related to MED-V including what’s new in MED-V 2.0 and MED-V 2.0 supported configurations. + +## Related topics + + +[Microsoft Enterprise Desktop Virtualization 2.0](index.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/high-level-architecturemedv2.md b/mdop/medv-v1/high-level-architecturemedv2.md new file mode 100644 index 0000000000..2d890e9884 --- /dev/null +++ b/mdop/medv-v1/high-level-architecturemedv2.md @@ -0,0 +1,72 @@ +--- +title: High-Level Architecture +description: High-Level Architecture +ms.assetid: a00edb9f-207b-4f32-9e8f-522ea2739d2f +author: MaggiePucciEvans +--- + +# High-Level Architecture + + +This section describes the high-level system architecture and component design of Microsoft Enterprise Desktop Virtualization (MED-V) 2.0. + +## System Architecture + + +MED-V enhances Windows Virtual PC to run two operating systems on one device, adding virtual image delivery, Group Policy-based provisioning, and centralized management. By using MED-V, you can easily configure, deploy, and manage corporate Windows Virtual PC images on any Windows-based desktop running Windows 7 Professional, Enterprise, or Windows 7 Ultimate. The MED-V solution includes the following components: + + **MED-V Host** +A Windows 7 environment that includes a MED-V Host Agent, an electronic software distribution (ESD) system, a registry management system, and a MED-V guest. The MED-V host interacts with the MED-V guest so that certain setup functions and system information can be processed. + + **MED-V Host Agent** +The MED-V software contained in the MED-V host that provides a channel to communicate with the MED-V guest. It also provides functionality such as first time setup and application publishing. + +**Note**   +After MED-V and its required components are installed MED-V must be configured. The configuration of MED-V is referred to as first time setup. + +  + +**ESD System** +Your existing software distribution method that lets you deploy and install the MED-V workspace package files that MED-V creates. + +**Registry Management System** +Your existing method of managing Group Policy settings and preferences. + +**Windows Virtual PC Image** +An administrator-defined virtual machine that contains the following components: + +**Corporate Operating System** +Your standard corporate operating system. + +**Management and Security Tools** +Your standard management and security tools, such as virus protection. + + **MED-V Guest** +A Windows XP SP3 environment, as part of a Windows Virtual PC running on Windows 7 that contains the following components: + + **MED-V Guest Agent** +The MED-V software contained in the MED-V guest that provides a channel to communicate with the MED-V host. It also supports the MED-V Host Agent with functions like performing first time setup. + +**Note**   +The MED-V Guest Agent is installed automatically during first time setup. + +  + +**ESD Client** +An optional part of your ESD system that installs software packages and reports status to the ESD system. + +## Related topics + + +[Planning for Application Operating System Compatibility](planning-for-application-operating-system-compatibility.md) + +[Prepare the Deployment Environment for MED-V](prepare-the-deployment-environment-for-med-v.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/how-to-add-or-remove-url-redirection-information-in-a-deployed-med-v-workspace.md b/mdop/medv-v1/how-to-add-or-remove-url-redirection-information-in-a-deployed-med-v-workspace.md new file mode 100644 index 0000000000..af2eccc248 --- /dev/null +++ b/mdop/medv-v1/how-to-add-or-remove-url-redirection-information-in-a-deployed-med-v-workspace.md @@ -0,0 +1,67 @@ +--- +title: How to Add or Remove URL Redirection Information in a Deployed MED-V Workspace +description: How to Add or Remove URL Redirection Information in a Deployed MED-V Workspace +ms.assetid: bf55848d-bf77-452e-aaa5-4dd4868ff5bd +author: MaggiePucciEvans +--- + +# How to Add or Remove URL Redirection Information in a Deployed MED-V Workspace + + +To edit URL redirection information in a deployed MED-V workspace, we recommend that you update the system registry by using Group Policy. Although we do not recommend it, you can also rebuild and redeploy the MED-V workspace with the updated URL redirection information. + +The registry key is usually located at: + +Computer\\HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\MEDV\\v2\\UserExperience + +The following multi-string value must be present: `RedirectUrls` + +The value data for `RedirectUrls` is a list of all of the URLs that you specified for redirection when you built the MED-V workspace package by using the **MED-V Workspace Packager**. For more information, see [Create a MED-V Workspace Package](create-a-med-v-workspace-package.md). + +You can add and remove URL redirection information by performing one of the following tasks: + +- [Edit the URL Redirection Registry Key and Deploy Using Group Policy](#bkmk-editreg) + +- [Edit the URL Redirection Text File and Rebuild the MED-V Workspace](#bkmk-edittext) + +**To update URL Redirection information by using Group Policy** + +1. Edit the registry key multi-string value that is named `RedirectUrls`. This value is typically located at: + + Computer\\HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\MEDV\\v2\\UserExperience + + If you are adding URLs to the registry key, enter them one per line, as was required when you built the MED-V workspace package. For more information, see [Create a MED-V Workspace Package](create-a-med-v-workspace-package.md). + +2. Deploy the updated registry key by using Group Policy. For more information about how to use Group Policy, see [Group Policy Software Installation](http://go.microsoft.com/fwlink/?LinkId=195931) (http://go.microsoft.com/fwlink/?LinkId=195931). + +**Note**   +This method of editing URL redirection information is a MED-V best practice. + +  + +**To rebuild the MED-V workspace by using an updated URL text file** + +- Another method of adding and removing URLs from the redirection list is to update the URL redirection text file and then use it to build a new MED-V workspace. You can then redeploy the MED-V workspace as before, by using your standard process of deployment, such as an ESD system. + + **Important**   + We do not recommend this method of editing URL redirection information. In addition, any time that you redeploy the MED-V workspace back out to your enterprise, first time setup must run again, and any data saved in the virtual machine is lost. + +   + +## Related topics + + +[How to Test URL Redirection](how-to-test-url-redirection.md) + +[Managing Applications Deployed to MED-V Workspaces](managing-applications-deployed-to-med-v-workspaces.md) + +[Create a MED-V Workspace Package](create-a-med-v-workspace-package.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/how-to-create-a-test-environment.md b/mdop/medv-v1/how-to-create-a-test-environment.md new file mode 100644 index 0000000000..1088e353e5 --- /dev/null +++ b/mdop/medv-v1/how-to-create-a-test-environment.md @@ -0,0 +1,85 @@ +--- +title: How to Create a Test Environment +description: How to Create a Test Environment +ms.assetid: a0db2299-16f3-4516-8769-7d55ca4a1e98 +author: MaggiePucciEvans +--- + +# How to Create a Test Environment + + +The following are some steps and instructions to help you create a test environment that you can use to test your MED-V workspace package locally before deploying it throughout your enterprise. This section provides guidance about how to create a test environment, either manually or by using an electronic software distribution system. + +**To create a test environment by using an ESD** + +1. Use your company’s method of deploying software throughout the enterprise to deploy the following necessary components to a test computer. Install them in the following order: + + - **Windows Virtual PC** – if not already installed. For more information, see [Configure Installation Prerequisites](configure-installation-prerequisites.md). + + - **Windows Virtual PC Additions and Updates**– if not already installed. For more information, see [Configure Installation Prerequisites](configure-installation-prerequisites.md). + + - **MED-V Host Agent Installation File** – installs the Host Agent (MED-V\_HostAgent\_Setup installation file). For more information, see [How to Manually Install the MED-V Host Agent](how-to-manually-install-the-med-v-host-agent.md). + + - **MED-V Workspace Installer, VHD, and Setup Executable** – created in the **MED-V Workspace Packager**. For more information, see [Create a MED-V Workspace Package](create-a-med-v-workspace-package.md). + + **Important**   + The VHD and Setup executable program must be in the same folder as the MED-V workspace installer. Then, install the MED-V workspace installer by running setup.exe. + +   + +2. After all of the components are installed on the test computer, run the MED-V Host Agent to start first time setup. + + Click **Start**, click **All Programs**, click **Microsoft Enterprise Desktop Virtualization**, and then click **MED-V Host Agent**. + + **Note**   + If you cannot physically run the MED-V Host Agent on the test computer, first time setup starts automatically the next time that the computer restarts. + +   + +First time setup starts and can take ten minutes or more to finish. + +For information about testing your configuration settings when first time setup is running, see [How to Verify First Time Setup Settings](how-to-verify-first-time-setup-settings.md). + +**To create a test environment manually** + +1. Install the MED-V Host Agent in a local test environment that includes MED-V prerequisites, such as Windows Virtual PC with additions and updates. For information, see [How to Manually Install the MED-V Host Agent](how-to-manually-install-the-med-v-host-agent.md). + +2. Copy the MED-V workspace files to your test environment. The MED-V workspace files are located in the destination folder that you specified in the **MED-V Workspace Packager**. + + **Important**   + The VHD and Setup executable program must be in the same folder on your test environment as the MED-V workspace installer. + +   + +3. Install the MED-V workspace by running setup.exe. + +4. Start first time setup by running the MED-V Host Agent. + + Click **Start**, click **All Programs**, click **Microsoft Enterprise Desktop Virtualization**, and then click **MED-V Host Agent**. + +First time setup starts and might take several minutes to complete, depending on the size of the VHD specified. + +You are now ready to test the different settings for configuration, application publishing, and URL redirection that you specified for your MED-V workspace. + +**Note**   +By default, MED-V overrides the screen lock policy in the guest. However, this does not pose a security problem because the host computer still honors the screen lock policy. + +  + +## Related topics + + +[How to Verify First Time Setup Settings](how-to-verify-first-time-setup-settings.md) + +[How to Test Application Publishing](how-to-test-application-publishing.md) + +[How to Test URL Redirection](how-to-test-url-redirection.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/how-to-deploy-a-med-v-workspace-in-a-windows-7-image.md b/mdop/medv-v1/how-to-deploy-a-med-v-workspace-in-a-windows-7-image.md new file mode 100644 index 0000000000..e535850389 --- /dev/null +++ b/mdop/medv-v1/how-to-deploy-a-med-v-workspace-in-a-windows-7-image.md @@ -0,0 +1,57 @@ +--- +title: How to Deploy a MED-V Workspace in a Windows 7 Image +description: How to Deploy a MED-V Workspace in a Windows 7 Image +ms.assetid: a83aba4e-8681-4906-9872-f431c0bb15f9 +author: MaggiePucciEvans +--- + +# How to Deploy a MED-V Workspace in a Windows 7 Image + + +You can install all the MED-V components into a Windows 7 image that you distribute throughout your enterprise just as you would any new installation of Windows 7. The end user then finishes the installation of the MED-V workspace by clicking a **Start** menu shortcut that you configure to start MED-V. First time setup starts and the end user follows the instructions to complete the configuration. + +The following section provides information and instructions to help you deploy the MED-V workspace throughout your enterprise by using a Windows 7 image. + +**To deploy a MED-V workspace in a Windows 7 image** + +1. Create a standard image of Windows 7. For more information, see [Building a Standard Image of Windows 7: Step-by-Step Guide](http://go.microsoft.com/fwlink/?LinkId=204843) (http://go.microsoft.com/fwlink/?LinkId=204843). + +2. In the Windows 7 image, install Windows Virtual PC and the Windows Virtual PC updates. For more information, see [Configure Installation Prerequisites](configure-installation-prerequisites.md). + +3. Install the MED-V Host Agent by using the MED-V\_HostAgent\_Setup installation file. For more information, see [How to Manually Install the MED-V Host Agent](how-to-manually-install-the-med-v-host-agent.md). + + **Warning**   + Internet Explorer must be closed before you install the MED-V Host Agent, otherwise conflicts can occur later with URL redirection. You can also do this by specifying a computer restart during a distribution. + +   + +4. Copy the MED-V workspace package files to the Windows 7 image. The MED-V workspace package files are the MED-V workspace installer, .medv file, and setup.exe file that you created by using the **MED-V Workspace Packager**. + + **Important**   + The .medv and setup.exe file must be in the same folder as the MED-V workspace installer. Then, install the MED-V workspace by running setup.exe. + +   + +5. Configure a shortcut on the **Start** menu to open the MED-V workspace package installation. + + Create a **Start** menu shortcut to the setup.exe file that lets the end user start a MED-V installation as required. + +6. By using your company’s standard image deployment process, distribute the Windows 7 image to computers in your enterprise that require MED-V. + +When the end user has to access an application published in the MED-V workspace, they can click the **Start** menu shortcut to install the MED-V workspace. This automatically starts first time setup and completes the configuration of MED-V. After first time setup is complete, the end user can access the MED-V applications on the **Start** menu. + +## Related topics + + +[MED-V 2.0 Deployment Overview](med-v-20-deployment-overview.md) + +[How to Deploy a MED-V Workspace Through an Electronic Software Distribution System](how-to-deploy-a-med-v-workspace-through-an-electronic-software-distribution-system.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/how-to-deploy-a-med-v-workspace-manually.md b/mdop/medv-v1/how-to-deploy-a-med-v-workspace-manually.md new file mode 100644 index 0000000000..2aeb1a745f --- /dev/null +++ b/mdop/medv-v1/how-to-deploy-a-med-v-workspace-manually.md @@ -0,0 +1,74 @@ +--- +title: How to Deploy a MED-V Workspace Manually +description: How to Deploy a MED-V Workspace Manually +ms.assetid: 94bfb209-2230-49b6-bb40-9c6ab088dbf4 +author: MaggiePucciEvans +--- + +# How to Deploy a MED-V Workspace Manually + + +In some instances, you might want to deploy your MED-V workspace manually, for example, if your company does not use an electronic software distribution system to deploy applications. + +This section provides instruction about how to manually deploy a MED-V workspace. + +**To deploy a MED-V workspace manually** + +1. Copy all prerequisite applications and the MED-V workspace package files to a shared drive or to a DVD. The following is a list of the required applications and files. + + - **Windows Virtual PC**. For more information, see [Configure Installation Prerequisites](configure-installation-prerequisites.md). + + - **Windows Virtual PC Additions and Updates**. For more information, see [Configure Installation Prerequisites](configure-installation-prerequisites.md). + + - **MED-V Host Agent Installation File** – installs the Host Agent (MED-V\_HostAgent\_Setup installation file). + + **Warning**   + Close Internet Explorer before you install the MED-V Host Agent, otherwise conflicts can occur later with URL redirection. You can also do this by specifying a computer restart during a distribution. + +   + + - **MED-V Workspace Installer, VHD, and Setup Executable** – created with the **MED-V Workspace Packager**. For more information, see [Create a MED-V Workspace Package](create-a-med-v-workspace-package.md). + + **Important**   + The compressed VHD file (.medv) and the Setup executable program (setup.exe) must be in the same folder as the MED-V workspace installer. + +   + +2. Install the following in the order listed. The end user can perform this task manually or you can create a script to install the following: + + - Windows Virtual PC and the Windows Virtual PC additions and updates. A computer restart is required. + + - The MED-V Host Agent. + + **Note**   + If it is running, Internet Explorer must be restarted before the installation of the MED-V Host Agent can finish. + +   + + - The MED-V workspace package. + + Install the MED-V workspace by running the setup.exe program that is included in the MED-V workspace package files. + +3. Complete first time setup. + + After the MED-V workspace is installed, you have the option of starting MED-V. This starts the MED-V Host Agent. You can either start MED-V at that time, or start the MED-V Host Agent later to complete first time setup. + + To start the MED-V Host Agent, click **Start**, click **All Programs**, click **Microsoft Enterprise Desktop Virtualization**, and then click **MED-V Host Agent**. + +## Related topics + + +[How to Deploy a MED-V Workspace Through an Electronic Software Distribution System](how-to-deploy-a-med-v-workspace-through-an-electronic-software-distribution-system.md) + +[How to Deploy a MED-V Workspace in a Windows 7 Image](how-to-deploy-a-med-v-workspace-in-a-windows-7-image.md) + +[Deploying the MED-V Workspace Package](deploying-the-med-v-workspace-package.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/how-to-deploy-a-med-v-workspace-through-an-electronic-software-distribution-system.md b/mdop/medv-v1/how-to-deploy-a-med-v-workspace-through-an-electronic-software-distribution-system.md new file mode 100644 index 0000000000..d999e4b091 --- /dev/null +++ b/mdop/medv-v1/how-to-deploy-a-med-v-workspace-through-an-electronic-software-distribution-system.md @@ -0,0 +1,179 @@ +--- +title: How to Deploy a MED-V Workspace Through an Electronic Software Distribution System +description: How to Deploy a MED-V Workspace Through an Electronic Software Distribution System +ms.assetid: b5134c35-e1de-470c-93f8-ead6218d9dce +author: MaggiePucciEvans +--- + +# How to Deploy a MED-V Workspace Through an Electronic Software Distribution System + + +An electronic software distribution system is designed to efficiently move software to many different computers over slow or fast network connections. The following section provides information and instructions to help you deploy your MED-V workspace throughout your enterprise by using a software distribution system. + +**Note**   +Whichever software distribution solution that you use, you must be familiar with the requirements of your particular solution. If you are using System Center Configuration Manager 2007 R2 or a later version, see the [Configuration Manager Documentation Library](http://go.microsoft.com/fwlink/?LinkId=66999) in the Microsoft Technical Library (http://go.microsoft.com/fwlink/?LinkId=66999). + +  + +**Important**   +If you are using System Center Configuration Manager 2007 SP2 and your MED-V workspaces are configured to operate in **NAT** mode, the virtual machines are classified as Internet-based clients and cannot find the closest distribution points from which to download content. + +The [hotfix to improve the functionality for VMs that are managed by MED-V](http://go.microsoft.com/fwlink/?LinkId=201088) (http://go.microsoft.com/fwlink/?LinkId=201088) adds new functionality to virtual machines that are managed by MED-V and that are configured to operate in **NAT** mode. The new functionality lets virtual machines access the closest distribution points. Therefore, the administrator can manage the virtual machine and the host computer in the same manner. This hotfix must be installed first on the site server and then on the client. + +The update is publically available. However, you might be prompted to accept an agreement for Microsoft Services. Follow the prompts on the successive webpages to retrieve this hotfix. + +  + +You can also deploy the MED-V components together by using a batch file, but this requires a restart after the installation of Windows Virtual PC. To bypass this requirement, you can specify a single restart after all of the components are installed. The single restart also automatically starts MED-V because the MED-V workspace installation places an entry in the RUNKEY. + +**To deploy a MED-V workspace by using a software distribution system** + +1. Define a group of computers and users in the electronic software distribution system as the target set of computers/users. + +2. Create packages for each Microsoft installation file that needs to be distributed. The following are the required files and the order in which they must be installed: + + 1. **Windows Virtual PC** – if not already installed (a computer restart is required). For more information, see [Configure Installation Prerequisites](configure-installation-prerequisites.md). + + 2. **Windows Virtual PC Additions and Updates** – if not already installed. For more information, see [Configure Installation Prerequisites](configure-installation-prerequisites.md). + + 3. **MED-V Host Agent Installation File** – installs the Host Agent (MED-V\_HostAgent\_Setup installation file). For more information, see [How to Manually Install the MED-V Host Agent](how-to-manually-install-the-med-v-host-agent.md). + + **Warning**   + Close Internet Explorer before you install the MED-V Host Agent, otherwise conflicts can occur later with URL redirection. You can also do this by specifying a computer restart during a distribution. + +   + + 4. **MED-V Workspace Installer, VHD, and Setup Executable** – created in the **MED-V Workspace Packager**. For more information, see [Create a MED-V Workspace Package](create-a-med-v-workspace-package.md). + + **Important**   + The compressed virtual hard disk file (.medv) and the Setup executable program (setup.exe) must be in the same folder as the MED-V workspace installer. Then, install the MED-V workspace installer by running setup.exe. + +   + + **Tip**   + Because problems can occur when you install MED-V from a network location, we recommend that you copy the MED-V workspace setup files locally and then run setup.exe. + +   + +3. Configure the packages to run in silent mode (no user interaction is required). + + Running in silent mode eliminates the prompt to close Internet Explorer if it is running and the prompt to start the MED-V Host Agent. Both actions are performed when the computer is restarted. + + **Note**   + Installation of Windows Virtual PC requires you to restart the computer. You can create a single installation process and install all the components at the same time if you suppress the restart and ignore the prerequisites necessary for MED-V to install. You can also do this by using command-line arguments. For an example of these arguments, see [How to Deploy the MED-V Components Through an Electronic Software Distribution System](how-to-deploy-the-med-v-components-through-an-electronic-software-distribution-system.md#bkmk-batch). MED-V automatically starts when the computer is restarted. + +   + +4. Install MED-V and its components before installing Windows Virtual PC. See the example batch file later in this topic. + + **Important**   + Select the **IGNORE\_PREREQUISITES** option as shown in the example batch file so that the MED-V components can be installed prior to the required VPC components. Install the MED-V components in this order to allow for the single restart. + +   + +5. Identify any other requirements necessary for the installation and for your software distribution system, such as target platforms and the free disk space. + +6. Assign the packages to the target set of computers/users. + + As computers are running, the software distribution system client recognizes that new packages are available and begins to install the packages per the definition and requirements. The installations should run sequentially in silent. We recommend that this is performed as a single process that does not require a restart until all the packages are installed. + +7. After the installations are complete, restart the updated computers. + + Depending on the software distribution system, you can schedule a restart of the computer or the end users can restart the computers manually during their regular work. After the computer is restarted, MED-V automatically starts after an end user logs on. When MED-V starts for the first time, it runs first time setup. + +First time setup starts and might take several minutes to finish, depending on the size of the virtual hard disk that you specified and the number of policies applied to the MED-V workspace on startup. The end user can track the progress by watching the MED-V icon in the notification area. For more information about first time setup, see [MED-V 2.0 Deployment Overview](med-v-20-deployment-overview.md). + +**To install the MED-V workspace by using a batch file** + +1. Run the installation at a command prompt with administrative credentials. + +2. Deploy each component to a single directory. If run from a network share, a longer time is required to decompress the .medv file. + +3. As a best practice, specify that Windows Virtual PC and the Windows Virtual PC hotfix are installed after the MED-V Host Agent and the MED-V workspace package files. This means that Windows Update will not cause any interference with the installation process by requiring a restart. + +4. Restart the computer after the batch file is finished. + +After the restart, the user is prompted to run first time setup and complete the configuration of MED-V. + +The following example, with the specified arguments, shows how to install 64-bit MED-V components in a single process: + + ++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ArgumentDescription

/norestart

Prevents the installation of Windows Virtual PC and the Windows Virtual PC update from restarting the host computer.

/quiet

Installs the MED-V components in quiet mode without user interaction.

/qn

Installs the MED-V components without a user interface.

IGNORE_PREREQUISITES

Installs without checking for Windows Virtual PC.

+
+Note   +

Only specify this argument if you are installing Windows Virtual PC as part of this installation.

+
+
+  +

OVERWRITEVHD

Forces the installation of the MED-V workspace and prevents any prompts that it might generate.

+ +  + +## Example + + +``` syntax +:: Install MED-V and the Pre-requisites + +:: Install the MED-V Host Agent: install in quiet mode, ignore that Windows Virtual PC is not installed completely, and log results +start /WAIT .\MED-V_HostAgent_Setup.exe /qn IGNORE_PREREQUISITES=1 /l* %TEMP%\MEDVhost.log + +:: Install the MED-V Workspace: install in quiet mode, Overwrite the VHD if it already exists, and log results +start /WAIT .\setup.exe /qn OVERWRITEVHD=1 /l* %TEMP%\MEDVworkspace.log + +:: Install Windows Virtual PC: install in quiet mode and do not reboot +start /WAIT wusa.exe Windows6.1-KB958559-x64.msu /norestart /quiet + +:: Install Windows Virtual PC patch to support non-HAV: install in quiet mode and do not reboot +wusa.exe Windows6.1-KB977206-x64.msu /norestart /quiet + +:: After successful installation of the above components, a reboot of the host computer is required to complete installation. +``` + +## Related topics + + +[MED-V 2.0 Deployment Overview](med-v-20-deployment-overview.md) + +[How to Deploy a MED-V Workspace in a Windows 7 Image](how-to-deploy-a-med-v-workspace-in-a-windows-7-image.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/how-to-deploy-the-med-v-components-through-an-electronic-software-distribution-system.md b/mdop/medv-v1/how-to-deploy-the-med-v-components-through-an-electronic-software-distribution-system.md new file mode 100644 index 0000000000..a6c99a60bf --- /dev/null +++ b/mdop/medv-v1/how-to-deploy-the-med-v-components-through-an-electronic-software-distribution-system.md @@ -0,0 +1,182 @@ +--- +title: How to Deploy the MED-V Components Through an Electronic Software Distribution System +description: How to Deploy the MED-V Components Through an Electronic Software Distribution System +ms.assetid: 8a800bdf-6fa4-47b4-b417-df053289d4e8 +author: MaggiePucciEvans +--- + +# How to Deploy the MED-V Components Through an Electronic Software Distribution System + + +An electronic software distribution system can help you efficiently move software to many computers over slow or fast network connections. The following section provides information and instructions to help you deploy the Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 components throughout your enterprise by using a software distribution system. + +**Note**   +Whichever software distribution solution that you use, you must be familiar with the requirements of your particular solution. If you are using System Center Configuration Manager 2007 R2 or a later version, see the [Configuration Manager Documentation Library](http://go.microsoft.com/fwlink/?LinkId=66999) in the Microsoft Technical Library (http://go.microsoft.com/fwlink/?LinkId=66999). + +  + +**Important**   +If you are using System Center Configuration Manager 2007 SP2 and your MED-V workspaces are configured to operate in **NAT** mode, the virtual machines are classified as Internet-based clients and cannot find the closest distribution points from which to download content. + +The [hotfix to improve the functionality for VMs that are managed by MED-V](http://go.microsoft.com/fwlink/?LinkId=201088) (http://go.microsoft.com/fwlink/?LinkId=201088) adds new functionality to virtual machines that are managed by MED-V and that are configured to operate in **NAT** mode. The new functionality lets virtual machines access the closest distribution points. Therefore, the administrator can manage the virtual machine and the host computer in the same manner. This hotfix must be installed first on the site server and then on the client. + +The update is publically available. However, you might be prompted to accept an agreement for Microsoft Services. Follow the prompts on the successive webpages to retrieve this hotfix. + +  + +**Note**   +You must install the MED-V workspace packager and build your MED-V workspaces before you can deploy the MED-V components through your software distribution system. For more information about how to prepare an image and to build your MED-V workspaces, see [Operations for MED-V](operations-for-med-v.md). + +  + +**To deploy the MED-V components by using a software distribution system** + +1. Define a group of computers and users in the electronic software distribution system as the target set of computers/users. + +2. Create packages for each Microsoft installation file that needs to be distributed. The following are the required files and the order in which they must be installed: + + 1. **Windows Virtual PC** – if not already installed (a computer restart is required). For more information, see [Configure Installation Prerequisites](configure-installation-prerequisites.md). + + 2. **Windows Virtual PC Additions and Updates** – if not already installed. For more information, see [Configure Installation Prerequisites](configure-installation-prerequisites.md). + + 3. **MED-V Host Agent Installation File** – installs the Host Agent (MED-V\_HostAgent\_Setup installation file). For more information, see [How to Manually Install the MED-V Host Agent](how-to-manually-install-the-med-v-host-agent.md). + + **Warning**   + Close Internet Explorer before you install the MED-V Host Agent, otherwise conflicts can occur later with URL redirection. You can also do this by specifying a computer restart during a distribution. + +   + + 4. **MED-V Workspace Installer, VHD, and Setup Executable** – created in the **MED-V Workspace Packager**. For more information, see [Create a MED-V Workspace Package](create-a-med-v-workspace-package.md). + + **Important**   + The compressed virtual hard disk file (.medv) and the Setup executable program (setup.exe) must be in the same folder as the MED-V workspace installer. Then, install the MED-V workspace installer by running setup.exe. + +   + + **Tip**   + Because problems that can occur when you install MED-V from a network location, we recommend that you copy the MED-V workspace setup files locally and then run setup.exe. + +   + +3. Configure the packages to run in silent mode (no user interaction is required). + + Running in silent mode eliminates the prompt to close Internet Explorer if it is running and the prompt to start the MED-V Host Agent. Both actions are performed when the computer is restarted. + + **Note**   + Installation of Windows Virtual PC requires you to restart the computer. You can create a single installation process and install all the components at the same time if you suppress the restart and ignore the prerequisites necessary for MED-V to install. You can also do this by using command-line arguments. For an example of these arguments, see [To install the MED-V components by using a batch file](#bkmk-batch). MED-V automatically starts when the computer is restarted. + +   + +4. Install MED-V and its components before installing Windows Virtual PC. See the example batch file later in this topic. + + **Important**   + Select the **IGNORE\_PREREQUISITES** option as shown in the example batch file so that the MED-V components can be installed prior to the required VPC components. Install the MED-V components in this order to allow for the single restart. + +   + +5. Identify any other requirements necessary for the installation and for your software distribution system, such as target platforms and the free disk space. + +6. Assign the packages to the target set of computers/users. + + As computers are running, the software distribution system client recognizes that new packages are available and begins to install the packages per the definition and requirements. The installations should run sequentially in silent mode. We recommend that this is performed as a single process that does not require a restart until all the packages are installed. + +7. After the installations are complete, restart the updated computers. + + Depending on the software distribution system, you can schedule a restart of the computer or the end users can restart the computers manually during their regular work. After the computer is restarted, MED-V automatically starts after an end user logs on. When MED-V starts for the first time, it runs first time setup. + +First time setup starts and might take several minutes to finish, depending on the size of the virtual hard disk that you specified and the number of policies applied to the MED-V workspace on startup. The end user can track the progress by watching the MED-V icon in the notification area. For more information about first time setup, see [MED-V 2.0 Deployment Overview](med-v-20-deployment-overview.md). + +**To install the MED-V components by using a batch file** + +1. Run the installation at a command prompt with administrative credentials. + +2. Deploy each component to a single directory. If run from a network share, a longer time is required to decompress the .medv file. + +3. As a best practice, specify that Windows Virtual PC and the Windows Virtual PC hotfix are installed after the MED-V Host Agent and the MED-V workspace package files. This means that Windows Update will not cause any interference with the installation process by requiring a restart. + +4. Restart the computer after the batch file is finished. + +After the restart, the user is prompted to run first time setup and complete the configuration of MED-V. + +The following example, with the specified arguments, shows how to install 64-bit MED-V components in a single process: + + ++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ArgumentDescription

/norestart

Prevents the installation of Windows Virtual PC and the Windows Virtual PC update from restarting the host computer.

/quiet

Installs the MED-V components in quiet mode without user interaction.

/qn

Installs the MED-V components without a user interface.

IGNORE_PREREQUISITES

Installs without checking for Windows Virtual PC.

+
+Note   +

Only specify this argument if you are installing Windows Virtual PC as part of this installation.

+
+
+  +

OVERWRITEVHD

Forces the installation of the MED-V workspace and prevents any prompts that it might generate.

+ +  + +## Example + + +``` syntax +:: Install MED-V and the Pre-requisites + +:: Install the MED-V Host Agent: install in quiet mode, ignore that Windows Virtual PC is not installed completely, and log results +start /WAIT .\MED-V_HostAgent_Setup.exe /qn IGNORE_PREREQUISITES=1 /l* %TEMP%\MEDVhost.log + +:: Install the MED-V Workspace: install in quiet mode, Overwrite the VHD if it already exists, and log results +start /WAIT .\setup.exe /qn OVERWRITEVHD=1 /l* %TEMP%\MEDVworkspace.log + +:: Install Windows Virtual PC: install in quiet mode and do not reboot +start /WAIT wusa.exe Windows6.1-KB958559-x64.msu /norestart /quiet + +:: Install Windows Virtual PC patch to support non-HAV: install in quiet mode and do not reboot +wusa.exe Windows6.1-KB977206-x64.msu /norestart /quiet + +:: After successful installation of the above components, a reboot of the host computer is required to complete installation. +``` + +## Related topics + + +[MED-V 2.0 Deployment Overview](med-v-20-deployment-overview.md) + +[Deploy the MED-V Components](deploy-the-med-v-components.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/how-to-install-the-med-v-workspace-packager.md b/mdop/medv-v1/how-to-install-the-med-v-workspace-packager.md new file mode 100644 index 0000000000..9ba434e06e --- /dev/null +++ b/mdop/medv-v1/how-to-install-the-med-v-workspace-packager.md @@ -0,0 +1,70 @@ +--- +title: How to Install the MED-V Workspace Packager +description: How to Install the MED-V Workspace Packager +ms.assetid: 627478e9-6798-4b32-9a50-7a1b72bea295 +author: MaggiePucciEvans +--- + +# How to Install the MED-V Workspace Packager + + +Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 includes a **MED-V Workspace Packager**, which the desktop administrator uses to create the MED-V workspace deployment packages that are distributed to the end users. The packager provides step-by-step guidance on how to create MED-V workspaces and contains wizards that help in the process. + +**Important**   +Before you start to run the wizards, make sure that you have a prepared VHD ready to install. For more information, see [Prepare a MED-V Image](prepare-a-med-v-image.md). + +  + +This section provides step-by-step instructions for installing or repairing the **MED-V Workspace Packager**. + +**To install the MED-V Workspace Packager** + +1. Locate the MED-V installation files that you received as part of your software download. + +2. Double-click the MED-V\_WorkspacePackager\_Setup installation file. + + The **Microsoft Enterprise Desktop Virtualization (MED-V) Workspace Packager Setup** wizard opens. Click **Next** to continue. + +3. Accept the Microsoft Software License Terms, and then click **Next**. + +4. Select the destination folder for installing the MED-V Workspace Packager, and then click **Next**. + +5. To begin the installation, click **Install**. + +6. After the installation is completed successfully, click **Finish** to close the wizard. + + To verify that the installation of the packager was successful, click **Start**, click **All Programs**, click **Microsoft Enterprise Desktop Virtualization**, and then click **MED-V Workspace Packager.** + + For information about how to use the **MED-V Workspace Packager**, see [Create a MED-V Workspace Package](create-a-med-v-workspace-package.md). + +If the packager does not open as expected, you can try to repair the installation. + +**To repair the MED-V Workspace Packager installation** + +1. Double-click the MED-V\_WorkspacePackager\_Setup installation file. + + The **Microsoft Enterprise Desktop Virtualization (MED-V) Workspace Packager Setup** wizard opens. Click **Next** to continue. + +2. To repair errors that might have occurred in the installation, click **Repair**. + +3. To begin the repair process, click **Repair** again. + +4. After the repair is completed successfully, click **Finish** to close the wizard. + + To verify that the repair of the packager was successful, click **Start**, click **All Programs**, click **Microsoft Enterprise Desktop Virtualization**, and then click **MED-V Workspace Packager.** + +## Related topics + + +[How to Manually Install the MED-V Host Agent](how-to-manually-install-the-med-v-host-agent.md) + +[How to Uninstall the MED-V Components](how-to-uninstall-the-med-v-components.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/how-to-manage-url-redirection-by-using-the-med-v-workspace-packager.md b/mdop/medv-v1/how-to-manage-url-redirection-by-using-the-med-v-workspace-packager.md new file mode 100644 index 0000000000..96f4670227 --- /dev/null +++ b/mdop/medv-v1/how-to-manage-url-redirection-by-using-the-med-v-workspace-packager.md @@ -0,0 +1,59 @@ +--- +title: How to Manage URL Redirection by Using the MED-V Workspace Packager +description: How to Manage URL Redirection by Using the MED-V Workspace Packager +ms.assetid: 1a8d25af-479f-42d3-bf5f-c7fd974bbf8c +author: MaggiePucciEvans +--- + +# How to Manage URL Redirection by Using the MED-V Workspace Packager + + +You can use the MED-V Workspace Packager to manage URL redirection in the MED-V workspace. + +**To manage web address redirection in a MED-V workspace** + +1. To open the **MED-V Workspace Packager**, click **Start**, click **All Programs**, click **Microsoft Enterprise Desktop Virtualization**, and then click **MED-V Workspace Packager**. + +2. On the **MED-V Workspace Packager** main panel, click **Manage Web Redirection**. + +3. In the **Manage Web Redirection** window, you can type, paste, or import a list of the URLs that are redirected to Internet Explorer in the MED-V workspace. + + **Note**   + URL redirection in MED-V only supports the protocols HTTP and HTTPS. MED-V does not provide support for FTP or any other protocols. + +   + + Enter each web address on a single line, for example: + + http://www.contoso.com/webapps/webapp1 + + http://www.contoso.com/webapps/webapp2 + + http://\*.contoso.com + + http://www.contoso.com/webapps/\* + + **Important**   + If you import a text file that includes a URL that uses special characters (such as ~ ! @ \# and so on), make sure that you specify UTF-8 encoding when you save the text file. Special characters do not import correctly into the MED-V Workspace Packager if the text file was saved using the default ANSI encoding. + +   + +4. Click **Save as…** to save the updated URL redirection files in the specified folder. MED-V creates a registry file that contains the updated URL redirection information. Deploy the updated registry key by using Group Policy. For more information about how to use Group Policy, see [Group Policy Software Installation](http://go.microsoft.com/fwlink/?LinkId=195931) (http://go.microsoft.com/fwlink/?LinkId=195931). + + MED-V also creates a Windows PowerShell script in the specified folder that you can use to re-create the updated MED-V workspace package. + +## Related topics + + +[How to Add or Remove URL Redirection Information in a Deployed MED-V Workspace](how-to-add-or-remove-url-redirection-information-in-a-deployed-med-v-workspace.md) + +[Manage MED-V URL Redirection](manage-med-v-url-redirection.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/how-to-manually-install-the-med-v-host-agent.md b/mdop/medv-v1/how-to-manually-install-the-med-v-host-agent.md new file mode 100644 index 0000000000..6332393925 --- /dev/null +++ b/mdop/medv-v1/how-to-manually-install-the-med-v-host-agent.md @@ -0,0 +1,64 @@ +--- +title: How to Manually Install the MED-V Host Agent +description: How to Manually Install the MED-V Host Agent +ms.assetid: 4becc90b-6481-4e1f-a4d3-aec74c8821ec +author: MaggiePucciEvans +--- + +# How to Manually Install the MED-V Host Agent + + +There are two separate but related components to the Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 solution: the MED-V Host Agent and Guest Agent. The Host Agent resides on the host computer (a user’s computer that is running Windows 7) and provides a channel to communicate with the MED-V guest (the MED-V virtual machine running in the host computer). It also provides certain MED-V related functionality, such as application publishing. + +Typically, you deploy and install the MED-V Host Agent by using your company’s preferred method of provisioning software. However, before deploying MED-V across your enterprise, you might prefer to install the Host Agent locally for testing. This section provides step-by-step instructions for manually installing the MED-V Host Agent. + +**Note**   +The MED-V Guest Agent is installed automatically during first time setup. + +  + +**Important**   +Close Internet Explorer before you install the MED-V Host Agent, otherwise conflicts can occur later with URL redirection. You can also do this by specifying a computer restart during a distribution. + +  + +**To install the MED-V Host Agent** + +1. Locate the MED-V installation files that you received as part of your software download. + +2. Double-click the MED-V\_HostAgent\_Setup installation file. + + The **Microsoft Enterprise Desktop Virtualization (MED-V) Host Agent Setup** wizard opens. Click **Next** to continue. + +3. Accept the Microsoft Software License Terms, and then click **Next**. + +4. Select the destination folder for installing the MED-V Host Agent. Click **Next**. + +5. To begin the Host Agent installation, click **Install**. + +6. After the installation is completed successfully, click **Finish** to close the wizard. + + To verify that the installation of the Host Agent was successful, click **Start**, click **All Programs**, click **Microsoft Enterprise Desktop Virtualization**, and then click **MED-V Host Agent**. + +**Note**   +Until a MED-V workspace is installed, the MED-V Host Agent can be started and runs, but provides no functionality. + +  + +## Related topics + + +[How to Deploy the MED-V Components Through an Electronic Software Distribution System](how-to-deploy-the-med-v-components-through-an-electronic-software-distribution-system.md) + +[How to Install the MED-V Workspace Packager](how-to-install-the-med-v-workspace-packager.md) + +[How to Uninstall the MED-V Components](how-to-uninstall-the-med-v-components.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/how-to-publish-and-unpublish-an-application-on-the-med-v-workspace.md b/mdop/medv-v1/how-to-publish-and-unpublish-an-application-on-the-med-v-workspace.md new file mode 100644 index 0000000000..9f312168e2 --- /dev/null +++ b/mdop/medv-v1/how-to-publish-and-unpublish-an-application-on-the-med-v-workspace.md @@ -0,0 +1,102 @@ +--- +title: How to Publish and Unpublish an Application on the MED-V Workspace +description: How to Publish and Unpublish an Application on the MED-V Workspace +ms.assetid: fd5a62e9-0577-44d2-ae17-61c0aef78ce8 +author: MaggiePucciEvans +--- + +# How to Publish and Unpublish an Application on the MED-V Workspace + + +Even though an application is installed in a MED-V workspace, you might also have to publish the application before it becomes available to the end user. By default, most applications are published at the time that they are installed and shortcuts are created and enabled. + +In some cases, you might want to install applications on the MED-V workspace without making them available to the end user, for example, virus-scanning software. Similarly, there are occasions in which you want to publish an application that is installed on the MED-V workspace that was previously unavailable to the end user. For example, you might have to publish an installed application if the installation did not automatically create a shortcut on the **Start** menu. + +**Important**   +If you publish an application that does not support UNC paths, we recommend that you map the application to a drive. + +  + +You can publish or unpublish applications to a deployed MED-V workspace by performing one of the following tasks: + +**To publish or unpublish an installed application** + +1. To publish an application on a deployed MED-V workspace, copy a shortcut for that application to the following folder on the virtual machine: + + C:\\Documents and Settings\\All Users\\Start Menu + + If it is necessary, use Group Policy or an ESD system to deploy a script that copies the shortcut for that application to the All Users\\Start Menu folder. + +2. To unpublish an application on a deployed MED-V workspace, delete the shortcut for that application from the following folder on the virtual machine: + + C:\\Documents and Settings\\All Users\\Start Menu + + If it is necessary, use Group Policy or an ESD system to deploy a script that deletes the shortcut for that application from the All Users\\Start Menu folder. + + **Note**   + Frequently, the shortcut is automatically deleted from the host computer **Start** menu when you uninstall the application. However, in some cases, such as for a MED-V workspace that is configured for all users of a shared computer, you might have to manually delete the shortcut on the **Start** menu after the application is uninstalled. The end-user can do this by right-clicking the shortcut and selecting **Delete**. + +   + +To test that the application was published or unpublished, verify on the MED-V workspace whether the corresponding shortcut is available or not. + +**Note**   +Applications that are included in Windows XP SP3 and are located in the virtual machine Start Menu folder are not automatically published to the host. They are controlled by registry settings that block automatic publishing. For more information, see [Windows Virtual PC Application Exclude List](windows-virtual-pc-application-exclude-list.md). + +  + +**To publish Control Panel items** + +1. Create a shortcut on the virtual machine where the target is the name of the item, such as C:\\WINDOWS\\system32\\appwiz.cpl. + + The shortcut must be either created in or moved to the "%ALLUSERSPROFILE%\\Start Menu\\" folder or one of its subfolders. + + The item will be published to the host computer in the corresponding location in the host Start Menu folder. + +2. Start the shortcut for the item in the host. + +**Caution**   +When you create the shortcut, do not specify %SystemRoot%\\control.exe. This application will not be published because it is contained in the registry settings that block automatic publishing. + +  + +**How MED-V handles automatic application publishing** + +1. During application publishing, MED-V copies the shortcuts from the guest virtual machine to the host computer by trying to match the folder hierarchy that exists in the guest. By doing this, MED-V copies shortcuts from the guest to the host by following these steps: + + 1. MED-V tries to locate a folder under Start Menu\\Programs in the host computer that is named the same as the folder in the guest where the shortcut resides. + + 2. If there is no matching folder, MED-V then tries to locate a folder in the host Start Menu folder that is named the same as the folder in the guest where the shortcut resides. + + 3. If there is no matching folder, MED-V copies the shortcut to the default folder on the host, the Start Menu\\Programs folder. + +2. Example of application publishing process: + + 1. If an application shortcut is published to the Start Menu\\Programs\\AppShortcuts folder in the guest, then MED-V looks in the host computer for a Start Menu\\Programs\\ AppShortcuts folder and if found, copies the shortcut to that folder. + + 2. If the folder is not found, then MED-V looks in the host computer for a Start Menu\\AppShortcuts folder and if found, copies the shortcut to that folder. + + 3. If the folder is not found, then MED-V copies the shortcut to the Start Menu\\Programs folder. + +**Note**   +A folder must already exist in the host computer Start Menu folder for MED-V to copy the shortcut there. MED-V does not create the folder if it does not already exist. + +  + +## Related topics + + +[Installing and Removing an Application on the MED-V Workspace](installing-and-removing-an-application-on-the-med-v-workspace.md) + +[Managing Software Updates for MED-V Workspaces](managing-software-updates-for-med-v-workspaces.md) + +[Windows Virtual PC Application Exclude List](windows-virtual-pc-application-exclude-list.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/how-to-test-application-publishing.md b/mdop/medv-v1/how-to-test-application-publishing.md new file mode 100644 index 0000000000..9251deb8c2 --- /dev/null +++ b/mdop/medv-v1/how-to-test-application-publishing.md @@ -0,0 +1,71 @@ +--- +title: How to Test Application Publishing +description: How to Test Application Publishing +ms.assetid: 17ba2e12-50a0-4f41-8300-f61f09db9f6c +author: MaggiePucciEvans +--- + +# How to Test Application Publishing + + +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** + +1. Verify that the applications that you specified for publishing are visible. + + Click **Start** and then click **All Programs** and search for the specified applications. + + In some cases, you might have the same application installed two times, one time on the host computer and one time on the guest. If a published application that has the same name is published to the same location on the host **Start** menu, it is distinguished from the host application shortcut by adding the virtual machine name to the shortcut name. For example, for a virtual machine named “MEDVHost1”, a host application might be "Notepad" and a published application might be "Notepad (MEDVHost1)". + +2. Verify that the applications function as intended. + + On the host computer, start the applications that you published and verify that they open in Windows XP SP3 on the guest. The application must appear in a Windows XP-style window on the host computer desktop. + +3. If applicable, verify that document redirection functions as intended. + + If a published application on the guest has to open a folder on the host system drive, ensure that it can open the specified folder. + + **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** + +1. Add or remove an application from the MED-V workspace. + + For information about how to add and remove applications from a MED-V workspace, see [Managing Applications Deployed to MED-V Workspaces](managing-applications-deployed-to-med-v-workspaces.md). + +2. If you added an application, repeat the steps in [To Test Application Publishing](#bkmk-apppub) to verify that the new application functions as intended. + +3. If you removed an application, click **Start** and then click **All Programs** and verify that any applications that you removed are no longer listed. + +**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) + +[Deploying the MED-V Workspace Package](deploying-the-med-v-workspace-package.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/how-to-test-url-redirection.md b/mdop/medv-v1/how-to-test-url-redirection.md new file mode 100644 index 0000000000..ddf6d181fb --- /dev/null +++ b/mdop/medv-v1/how-to-test-url-redirection.md @@ -0,0 +1,70 @@ +--- +title: How to Test URL Redirection +description: How to Test URL Redirection +ms.assetid: 38d80088-da1d-4098-b27e-76f9e78f81dc +author: MaggiePucciEvans +--- + +# How to Test URL Redirection + + +After your test of first time setup finishes, you can verify that the URL redirection functionality is working as expected by performing the following tasks. + +**Important**   +The MED-V Host Agent must be running for URL redirection to function correctly. + +  + +**To test URL Redirection** + +1. Open an Internet Explorer browser in the host computer and enter a URL that you specified for redirection. + +2. Verify that the webpage is opened in Internet Explorer on the guest virtual machine. + +3. Repeat this process for each URL that you want to test. + +**To test that a URL can be added or removed** + +1. Add or remove a URL from the MED-V workspace. + + For information about how to add and remove URLs for redirection on a MED-V workspace, see [Manage MED-V URL Redirection](manage-med-v-url-redirection.md). + +2. If you added a URL to the redirection list, repeat the steps in [To Test URL Redirection](#bkmk-urlredir) to verify that the new URL redirects as intended. + +3. If you removed a URL from the redirection list, verify that it is removed by following these steps: + + 1. Open an Internet Explorer browser in the host computer and enter the URL that you removed from the redirection list. + + 2. Verify that the webpage is opened in Internet Explorer on the host computer instead of on the guest virtual machine. + + **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) + +[Deploying the MED-V Workspace Package](deploying-the-med-v-workspace-package.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/how-to-uninstall-the-med-v-components.md b/mdop/medv-v1/how-to-uninstall-the-med-v-components.md new file mode 100644 index 0000000000..2a5709d3e5 --- /dev/null +++ b/mdop/medv-v1/how-to-uninstall-the-med-v-components.md @@ -0,0 +1,87 @@ +--- +title: How to Uninstall the MED-V Components +description: How to Uninstall the MED-V Components +ms.assetid: c121dd27-6b2f-4d41-a21a-c6e8608c5c41 +author: MaggiePucciEvans +--- + +# How to Uninstall the MED-V Components + + +Under certain circumstances, you might want to uninstall all or part of the Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 components from your enterprise. For example, you have resolved all application operating system compatibility issues, or you want to deploy a different MED-V workspace in your enterprise. + +Typically, you can configure your electronic software distribution (ESD) system to uninstall the MED-V components by using a Windows-based Installer. Alternately, you can uninstall all or some MED-V components manually. + +**Important**   +Before you can uninstall the MED-V Host Agent, you must first uninstall any installed MED-V workspace. + +  + +Use the following procedures to uninstall the MED-V components from your enterprise. + +**To uninstall MED-V using an electronic software distribution System** + +1. Use your ESD system to distribute a script that invokes the uninstall.exe executable program for every MED-V workspace that you want to uninstall. The file is located at C:\\ProgramData\\Microsoft\\Medv\\Workspace. You can set a flag to run the uninstall executable program silently so that end users are unaware of the uninstallation. + +2. Create a package to distribute the MED-V Host Agent installation file to each computer on which a MED-V workspace was uninstalled. Configure the package to run the uninstallation in silent mode. + +The ESD client recognizes when the new packages are available and starts to uninstall the packages per the definition and requirements. + +**To manually uninstall a MED-V workspace** + +1. On the host computer, click **Start**, click **Control Panel**, and then click **Programs and Features**. + +2. In the **Programs and Features** window, select the MED-V workspace that you want to remove, and then click **Uninstall**. (The MED-V workspace is named "MED-V Workspace - <*workspace\_name*>"). The <*workspace\_name*> **Setup Wizard** opens. + +3. On the **Setup Wizard**, click **Next**, and then click **Remove**. + +4. If you prefer, select the check box to delete the master VHD disk and differencing disks created by MED-V. This is not required, but frees disk space after the uninstallation finishes. + +5. Click **Remove**. + + **Note**   + If MED-V is currently running, a dialog box appears and prompts you whether you want to shut it down. Click **Yes** to continue with the uninstallation. Click **No** to cancel the uninstallation. + +   + +Alternately, you can remove a MED-V workspace by running the `uninstall.exe` file, typically located at C:\\ProgramData\\Microsoft\\Medv\\Workspace. + +**To manually uninstall the MED-V Host Agent** + +1. On the Windows 7 host computer, click **Start**, click **Control Panel**, and then click **Programs and Features**. + +2. In the **Programs and Features** window, select **MED-V Host Agent**, and then click **Uninstall**. + + The Windows Installer removes the MED-V Host Agent. + + **Note**   + If you try to uninstall the MED-V Host Agent before you uninstall the MED-V workspace, a dialog box appears that states that you must first uninstall the MED-V workspace. Click **OK** to continue. + +   + +**To manually uninstall the MED-V Workspace Packager** + +1. On the host computer, click **Start**, click **Control Panel**, and then click **Programs and Features**. + +2. In the **Programs and Features** window, select **MED-V Workspace Packager**, and then click **Uninstall**. + + The Windows Installer removes the MED-V Workspace Packager. + + **Note**   + You can uninstall the MED-V Workspace Packager at any time without affecting any deployed MED-V workspaces. + +   + +## Related topics + + +[Deploy the MED-V Components](deploy-the-med-v-components.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/how-to-verify-first-time-setup-settings.md b/mdop/medv-v1/how-to-verify-first-time-setup-settings.md new file mode 100644 index 0000000000..ace2ebf580 --- /dev/null +++ b/mdop/medv-v1/how-to-verify-first-time-setup-settings.md @@ -0,0 +1,102 @@ +--- +title: How to Verify First Time Setup Settings +description: How to Verify First Time Setup Settings +ms.assetid: e8a07d4c-5786-4455-ac43-2deac4042efd +author: MaggiePucciEvans +--- + +# How to Verify First Time Setup Settings + + +While your test of first time setup is running or after it finishes, you can verify the settings that you configured in your MED-V workspace by performing the following tasks. + +**Note**   +For information about how to monitor the successful completion of first time setup throughout your enterprise after deployment, see [Monitoring MED-V Workspace Deployments](monitoring-med-v-workspace-deployments.md). + +  + +**To verify settings during first time setup** + +1. While first time setup is running, verify the following: + + If you specified **Unattended** mode, verify that the virtual machine does not appear when first time setup is running. + + If you specified attended mode, verify that the virtual machine appears and that all fields that require user input are displayed. + +2. You can also monitor the complete first time setup process by viewing the virtual machine when first time setup is running. To do this, follow these steps: + + 1. Open the Windows Virtual PC Console. + + Click **Start**, click **All Programs**, click **Windows Virtual PC**, and then click **Windows Virtual PC**. + + 2. Start MED-V if it is not already running. + + If not already present, in a short time, a virtual machine with the name of the deployed MED-V workspace appears in the list of virtual machines. + + 3. Double-click the MED-V virtual machine to open it. + + You can observe the MED-V virtual machine when it is being set up, and you can troubleshoot the Mini-Setup procedure. Verify the information in the different screens as they go by, such as configuring networking settings, computer domain join information, configuring of the Guest Agent, set up of personal settings, and shutdown. + + 4. The virtual machine closes automatically when first time setup finishes. + + **Note**   + You can close the virtual machine window at any time and first time setup continues. + +   + +**To verify settings after first time setup finishes** + +1. Ensure that first time setup finished successfully. + +2. Verify that the MED-V workspace is set up correctly. + + 1. Open the Windows Virtual PC Console. + + Click **Start**, click **All Programs**, click **Windows Virtual PC**, and then click **Windows Virtual PC**. + + 2. Double-click your installed MED-V workspace. + + If the MED-V workspace is already running a virtual application, you might be prompted to close the application before you can open the virtual machine. + + 3. In the MED-V workspace, right-click **My Computer**, and then click **Properties**. + + 4. Verify that the MED-V workspace joined the correct domain. If applicable to your organization, test domain joining by specifying two different domains to verify that the guest domain is overridden by the host domain. + + 5. Verify that the MED-V workspace joined the domain organizational unit that you specified. + + 6. If you specified the computer name mask, verify that the new computer name matches what was specified. + +3. Verify that the locale settings that you specified are correct. + + 1. In the MED-V workspace, click **Start** and then click **Control Panel**. + + 2. Verify your specified configuration settings, for example, **Date and Time** and **Regional and Language**. + +**Note**   +If you encounter any problems when verifying your first time setup settings, see [Operations Troubleshooting](operations-troubleshooting-medv2.md). + +  + +After you have verified that your first time setup settings are correct, you can test other MED-V workspace configurations to verify that they function as intended, such as application publishing and URL redirection. + +After you have completed all testing of 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 Test URL Redirection](how-to-test-url-redirection.md) + +[Deploying the MED-V Workspace Package](deploying-the-med-v-workspace-package.md) + +[Manage MED-V Workspace Settings](manage-med-v-workspace-settings.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/identifying-the-number-and-types-of-med-v-workspaces.md b/mdop/medv-v1/identifying-the-number-and-types-of-med-v-workspaces.md new file mode 100644 index 0000000000..d61c3205ec --- /dev/null +++ b/mdop/medv-v1/identifying-the-number-and-types-of-med-v-workspaces.md @@ -0,0 +1,114 @@ +--- +title: Identifying the Number and Types of MED-V Workspaces +description: Identifying the Number and Types of MED-V Workspaces +ms.assetid: 11642253-6b1f-4c4a-a11e-48d8a360e1ea +author: MaggiePucciEvans +--- + +# Identifying the Number and Types of MED-V Workspaces + + +MED-V creates a virtual environment for running applications that require Windows XP or that require a version of Internet Explorer that differs from the version on the host computer. This virtual environment is known as a MED-V workspace. + +Depending on the application compatibility requirements faced by your organization as you migrate to Windows 7, only certain users or departments might require MED-V workspaces. As you plan your deployment, you have to determine the number of MED-V workspaces required in your enterprise. You also have to define the requirements of each MED-V workspace. + +## Identify the Number and Types of MED-V Workspaces + + +Identify the computers and groups in your enterprise for which you will be creating MED-V workspaces. Typically, these are the users who require access to those applications that cannot be migrated to Windows 7. Identify those applications that cannot be migrated and the users who require a MED-V workspace to run these applications. + +You might also have intranet addresses that have not yet been optimized for Windows 7. The MED-V workspace provides an Internet Explorer browser through which end users can better access those web addresses that are not yet ready for the migration to Windows 7. As you are preparing and planning your MED-V deployment, you will have to identify and compile a list of the URL addresses to redirect from Internet Explorer on the host computer to Internet Explorer in the MED-V workspace. + +Finally, you have to evaluate your disk space requirements. Most MED-V workspaces are 2 gigabytes (GB) or larger. The available disk space on a system can be consumed quickly, depending on the number of users and the configuration of MED-V. Also, your company’s preferred method of distribution can require additional space. Generally, you should free a minimum of 10 GB of disk space for a MED-V workspace, but this varies greatly, depending on the size of the image. + +### Calculate the Disk Space Requirements for MED-V Workspaces + +A MED-V workspace requires memory and disk space from the host computer on which it is installed. At a minimum, 2 GB of disk space are required on the host. Disk space is variable and depends on the number of applications and the data in a user’s MED-V workspace. + +We recommend a minimum of 10 GB of disk space for MED-V. This amount allows for a basic Windows XP workspace and some basic installed applications and web redirection. It also provides available space for the host swap drive. In a basic configuration, MED-V and a single deployed MED-V workspace consume as much as 6 to 8 GB. If you include lots of applications on the MED-V workspace or have more than one user per computer, then you can use the following calculation to more accurately determine the disk space your MED-V workspace requires: + +*Base VHD + (User per computer x (Difference Disk + Saved State))* + +To calculate the required disk space, determine the following: + +- **Size of the base VHD** – the virtual hard disk that was used to create the MED-V workspace. + + **Important**   + Do not use the .medv file size for your calculation because the .medv file is compressed. + +   + +- **Users per computer** – MED-V creates a MED-V workspace for each user on a computer; the MED-V workspace consumes disk space as each user logs on and the MED-V workspace is created. + +- **Size of the differencing disk** – used to track the difference from the base VHD. This size varies as you add applications and software updates to the virtual hard disk. A differencing disk is created for each MED-V user when they start MED-V for the first time. + +- **Size of the Saved State file** – used to maintain state in the virtual machine. Typically, this is just a bit larger than the allocated RAM for the virtual machine. For example, 1 GB of RAM allocated creates a file about 1,081,000 KB. + +The following example shows a calculation based on three users of a MED-V workspace that has a 2.6 GB virtual hard disk: + +*2.6gb + (3 x (1.5gb + 1gb)) = 10.1gb* + +**Note**   +A MED-V best practice is to calculate the required space by using a lab deployment to validate the requirements. + +  + +### Locate the Files to Determine File Size + +The following locations contain the files for the computer and user settings: + + +++++ + + + + + + + + + + + + + + + + + + + + + + + + +
TypeLocationFiles

Base VHD

%ProgramData%\Microsoft\Medv\Workspace

InternalName.vhd - Where InternalName is the name of the virtual hard disk that you selected in the MED-V Workspace Packager.

Differencing Disk

%LocalAppData%\Microsoft\MEDV\v2\Virtual Machines

WorkspaceName.vhd

Saved State File

%LocalAppData%\Microsoft\MEDV\v2\Virtual Machines

WorkspaceName.vsv

+ +  + +### Calculate the Disk Space Requirements for Shared MED-V Workspaces + +If you are calculating for a shared MED-V workspace deployment on a single computer, then the number of users per computer in your calculation is always “1” because MED-V only configures a single differencing disk for all users. + +You can find the differencing disk and the saved state file for shared MED-V workspaces in %ProgramData%\\Microsoft\\Medv\\AllUsers. + +## Related topics + + +[Define and Plan your MED-V Deployment](define-and-plan-your-med-v-deployment.md) + +[Planning for MED-V](planning-for-med-v.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/images/506f54d0-38fa-446a-8070-17ae26da5355.gif b/mdop/medv-v1/images/506f54d0-38fa-446a-8070-17ae26da5355.gif new file mode 100644 index 0000000000..751dd1cdd0 Binary files /dev/null and b/mdop/medv-v1/images/506f54d0-38fa-446a-8070-17ae26da5355.gif differ diff --git a/mdop/medv-v1/images/medv-logon.gif b/mdop/medv-v1/images/medv-logon.gif new file mode 100644 index 0000000000..bcc102a289 Binary files /dev/null and b/mdop/medv-v1/images/medv-logon.gif differ diff --git a/mdop/medv-v1/images/medv-ui-console-general.gif b/mdop/medv-v1/images/medv-ui-console-general.gif new file mode 100644 index 0000000000..128e43aea0 Binary files /dev/null and b/mdop/medv-v1/images/medv-ui-console-general.gif differ diff --git a/mdop/medv-v1/images/medv.gif b/mdop/medv-v1/images/medv.gif new file mode 100644 index 0000000000..29b45a998f Binary files /dev/null and b/mdop/medv-v1/images/medv.gif differ diff --git a/mdop/medv-v1/index.md b/mdop/medv-v1/index.md new file mode 100644 index 0000000000..20881f1f96 --- /dev/null +++ b/mdop/medv-v1/index.md @@ -0,0 +1,50 @@ +--- +title: Microsoft Enterprise Desktop Virtualization 2.0 +description: Microsoft Enterprise Desktop Virtualization 2.0 +ms.assetid: 84109be0-4613-42e9-85fc-fcda8de6e4c4 +author: MaggiePucciEvans +--- + +# Microsoft Enterprise Desktop Virtualization 2.0 + + +![med-v logotype](images/med-v2logo.gif) + +Welcome to Microsoft Enterprise Desktop Virtualization (MED-V) 2.0. MED-V 2.0 uses Windows Virtual PC to provide an enterprise solution for desktop virtualization. By using MED-V, you can easily create, deliver, and manage corporate Windows Virtual PC images on any Windows-based desktop running Windows 7 Professional, Enterprise, or Windows 7 Ultimate. + +MED-V is an integral component of the Microsoft Desktop Optimization Pack, a dynamic solution available to Software Assurance customers, which helps reduce software installation costs, enables delivery of applications as services, and helps manage and control enterprise desktop environments. + +For more information about how to perform MED-V tasks, use the following sections. + +## In This Section + + +[Getting Started with MED-V](getting-started-with-med-vmedv2.md) + +[Planning for MED-V](planning-for-med-v.md) + +[Deployment of MED-V](deployment-of-med-v.md) + +[Operations for MED-V](operations-for-med-v.md) + +[Troubleshooting MED-V](troubleshooting-med-vmedv2.md) + +[Security and Protection for MED-V](security-and-protection-for-med-v.md) + +[Technical Reference for MED-V](technical-reference-for-med-v.md) + +## Reference + + +For more information about MED-V, see + +[Microsoft Windows Enterprise: Improving Virtual PCs with MED-V](http://go.microsoft.com/fwlink/?LinkId=195917) (http://go.microsoft.com/fwlink/?LinkId=195917). + +  + +  + + + + + diff --git a/mdop/medv-v1/installing-and-removing-an-application-on-the-med-v-workspace.md b/mdop/medv-v1/installing-and-removing-an-application-on-the-med-v-workspace.md new file mode 100644 index 0000000000..015cee3947 --- /dev/null +++ b/mdop/medv-v1/installing-and-removing-an-application-on-the-med-v-workspace.md @@ -0,0 +1,96 @@ +--- +title: Installing and Removing an Application on the MED-V Workspace +description: Installing and Removing an Application on the MED-V Workspace +ms.assetid: 24f32720-51ab-4385-adfe-4f5a65e45fdf +author: MaggiePucciEvans +--- + +# Installing and Removing an Application on the MED-V Workspace + + +Applications that are incompatible with the host operating system can be run in the MED-V workspace and opened in the MED-V workspace in the same manner in which they are opened from the host computer, on the **Start** menu or by using a localhost shortcut. + +After you have deployed a MED-V workspace, you have several different options available to you for installing and removing applications in the MED-V workspace. These options include the following: + +- [Using Group Policy](#bkmk-grouppolicy) + +- [Using an Electronic Software Distribution System](#bkmk-esd) + +- [Using Application Virtualization (APP-V)](#bkmk-appv) + +- [Updating the Core Image](#bkmk-coreimage) + +**Important**   +To make sure that an installed application is automatically published to the host, install the application on the virtual machine for **All Users**. For more information about application publishing, see [How to Publish and Unpublish an Application on the MED-V Workspace](how-to-publish-and-unpublish-an-application-on-the-med-v-workspace.md). + +  + +**Tip**   +MED-V does not support guest-to-host redirection for content handling, such as double-clicking a Microsoft Word document in Internet Explorer in the MED-V workspace. Therefore, the required applications, such as Microsoft Word, must be installed in MED-V workspace to provide the default content handling functionality that an end user might expect. + +  + +## Adding and Removing Applications by Using Group Policy + + +You can use Group Policy and Group Policy objects to assign or publish applications to all or some MED-V workspaces in your enterprise. For assigned applications, when an end user logs on to their computer, the application appears on the **Start** menu. When they select the new application for the first time, the application installs and is ready for use. For published applications, the application does not appear on the **Start** menu. It is only available for the end user to install by using **Add or Remove Programs** in **Control Panel** or by opening a file that is associated with the application. + +You can also use Group Policy and Group Policy objects in the same manner to remove applications from the MED-V workspace. + +For more information about how to add and remove applications by using Group Policy, see [Group Policy Software Installation](http://go.microsoft.com/fwlink/?LinkId=195931) (http://go.microsoft.com/fwlink/?LinkId=195931). + +## Adding and Removing Applications by Using an ESD System + + +An electronic software distribution (ESD) system is designed to efficiently deploy software and other information to many different computers over network connections. If your organization uses an ESD system to deploy software, you can use it to add and remove applications on MED-V workspaces just as you add and remove applications on physical computers. + +## Adding and Removing Applications by Using APP-V + + +Microsoft Application Virtualization (App-V) provides the administrative capability to make applications available to end-user computers without having to install the applications directly on those computers. You might want to use MED-V and App-V together if, for example, your organization has applications that you sequenced with App-V in Windows XP, and re-sequencing them would delay your migration to Windows 7. + +You can use MED-V together with App-V to add and remove virtual applications on a deployed MED-V workspace. To manage applications in this manner, you must first install the App-V agent on the MED-V guest operating system. You can then use App-V in the MED-V workspace to add and remove the virtual applications. + +For information about how to install and use App-V, see [Application Virtualization](http://go.microsoft.com/fwlink/?LinkId=122939) (http://go.microsoft.com/fwlink/?LinkId=122939). + +**Important**   +App-V applications that you publish to the MED-V workspace have file-type associations that cannot redirect from the host computer to the guest virtual machine. However, the end user can still access these file types by clicking **File**, and then by clicking **Open** on the published App-V application. + +To force redirection of those file-type associations, query App-V for mapped file type associations by typing the following at a command prompt in the guest virtual machine: **sftmime /QUERY OBJ:TYPE**. Then, map those file type associations in the host computer. + +  + +## Adding and Removing Applications on the Core Image + + +Although not considered a MED-V best practice, you can add and remove applications directly on the core image. After you have added or removed an application, you can redeploy the MED-V workspace back out to your enterprise just as you deployed it originally. + +For more information about how to add or remove applications on the core image, see [Installing Applications on a Windows Virtual PC Image](installing-applications-on-a-windows-virtual-pc-image.md). + +**Important**   +We do not recommend this method of managing applications. If you add or remove applications on the core image and redeploy the MED-V workspace back out to your enterprise, first time setup must run again, and any data saved on the virtual machine is lost. + +  + +**Note**   +Even though an application is installed into a MED-V workspace, you might also have to publish the application before it becomes available to the end user. For example, you might have to publish an installed application if the installation did not automatically create a shortcut on the **Start** menu. Likewise, to unpublish an application, you might have to manually remove a shortcut from the **Start** menu. + +By default, most applications are published at the time that they are installed, when shortcuts are automatically created and enabled. + +  + +## Related topics + + +[How to Test Application Publishing](how-to-test-application-publishing.md) + +[How to Publish and Unpublish an Application on the MED-V Workspace](how-to-publish-and-unpublish-an-application-on-the-med-v-workspace.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/installing-applications-on-a-windows-virtual-pc-image.md b/mdop/medv-v1/installing-applications-on-a-windows-virtual-pc-image.md new file mode 100644 index 0000000000..c25af833db --- /dev/null +++ b/mdop/medv-v1/installing-applications-on-a-windows-virtual-pc-image.md @@ -0,0 +1,61 @@ +--- +title: Installing Applications on a Windows Virtual PC Image +description: Installing Applications on a Windows Virtual PC Image +ms.assetid: 32651eff-e3c6-4ef4-947d-2beddc695eac +author: MaggiePucciEvans +--- + +# Installing Applications on a Windows Virtual PC Image + + +After you have created a Windows Virtual PC image for use with Microsoft Enterprise Desktop Virtualization (MED-V) 2.0, you can install other components that are helpful when running MED-V, such as an electronic software distribution (ESD) system and antivirus software. + +The following section provides information to help you install software on the MED-V image. + +**Caution**   +For ease of MED-V workspace management after deployment, we recommend that you limit the number of components that you install on the MED-V image to those components that are required or that are helpful when using MED-V. For example, although they are not required to run MED-V, you can install an ESD system to use later for installing applications to a MED-V workspace and antivirus software for security on the image. + +  + +**Installing Software on a MED-V Image** + +1. If it is not currently running, open your MED-V virtual machine. + + 1. Click **Start**, click **All Programs**, click **Windows Virtual PC** and then click **Windows Virtual PC**. + + 2. Double-click your MED-V virtual machine. + +2. From inside the virtual machine operating system, locate the installation files for the software that you want to install. + +3. Follow the installation instructions that are provided by the software vendor. + + **Note**   + After installation is complete, you might have to close and then restart the virtual machine. + +   + +Repeat these steps for any software or application that you want to install on the MED-V image. We recommend that you limit the number of applications that you preinstall on the image. The recommended process for installing applications and other software on the image is to preinstall an ESD system now and to use it later to deploy software to the image. Alternately, you can also use Group Policy or App-V to add or remove applications on a MED-V workspace. For more information, see [Managing Applications Deployed to MED-V Workspaces](managing-applications-deployed-to-med-v-workspaces.md). + +For more information about how to install software on a virtual image, see the following articles: + +- [Publish and Use Virtual Applications](http://go.microsoft.com/fwlink/?LinkId=195926) (http://go.microsoft.com/fwlink/?LinkId=195926). + +- [Windows Virtual PC Help](http://go.microsoft.com/fwlink/?LinkId=182378) (http://go.microsoft.com/fwlink/?LinkId=182378). + +After you have installed all of the software that you want on the MED-V image, your image is ready to be packaged. + +## Related topics + + +[Configuring a Windows Virtual PC Image for MED-V](configuring-a-windows-virtual-pc-image-for-med-v.md) + +[Prepare a MED-V Image](prepare-a-med-v-image.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/manage-med-v-url-redirection.md b/mdop/medv-v1/manage-med-v-url-redirection.md new file mode 100644 index 0000000000..7ad7846794 --- /dev/null +++ b/mdop/medv-v1/manage-med-v-url-redirection.md @@ -0,0 +1,40 @@ +--- +title: Manage MED-V URL Redirection +description: Manage MED-V URL Redirection +ms.assetid: 274161c0-b54a-4364-bb63-89996afccd04 +author: MaggiePucciEvans +--- + +# Manage MED-V URL Redirection + + +After you deploy your MED-V workspace, you can select from different methods to add or remove URL redirection information in the MED-V workspaces. + +Included in this section are both information and instructions to help you manage URL redirection information on assigned MED-V workspaces. + +## In This Section + + +[How to Add or Remove URL Redirection Information in a Deployed MED-V Workspace](how-to-add-or-remove-url-redirection-information-in-a-deployed-med-v-workspace.md) +Provides assistance in adding and removing URL redirection information on MED-V workspaces. + +[How to Manage URL Redirection by Using the MED-V Workspace Packager](how-to-manage-url-redirection-by-using-the-med-v-workspace-packager.md) +Provides assistance in managing URL redirection information through the MED-V Workspace Packager. + +## Related topics + + +[How to Test URL Redirection](how-to-test-url-redirection.md) + +[Create a MED-V Workspace Package](create-a-med-v-workspace-package.md) + +[Manage MED-V Workspace Applications](manage-med-v-workspace-applications.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/manage-med-v-workspace-applications.md b/mdop/medv-v1/manage-med-v-workspace-applications.md new file mode 100644 index 0000000000..5f9e674e5c --- /dev/null +++ b/mdop/medv-v1/manage-med-v-workspace-applications.md @@ -0,0 +1,37 @@ +--- +title: Manage MED-V Workspace Applications +description: Manage MED-V Workspace Applications +ms.assetid: f58c7504-a77a-41a8-ac38-7e618da131fb +author: MaggiePucciEvans +--- + +# Manage MED-V Workspace Applications + + +This section provides information about how to manage MED-V workspace applications. + +## In This Section + + +[Managing Applications Deployed to MED-V Workspaces](managing-applications-deployed-to-med-v-workspaces.md) +Describes how to install and remove applications on the VHD and how to publish existing applications. + +[Managing Software Updates for MED-V Workspaces](managing-software-updates-for-med-v-workspaces.md) +Describes how to manage software updates for MED-V workspaces. + +[Managing Automatic Updates for MED-V Workspaces](managing-automatic-updates-for-med-v-workspaces.md) +Describes how to manage automatic software updates for MED-V workspaces. + +## Related topics + + +[Manage MED-V Workspace Settings](manage-med-v-workspace-settings.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/manage-med-v-workspace-settings.md b/mdop/medv-v1/manage-med-v-workspace-settings.md new file mode 100644 index 0000000000..84fa7458f8 --- /dev/null +++ b/mdop/medv-v1/manage-med-v-workspace-settings.md @@ -0,0 +1,42 @@ +--- +title: Manage MED-V Workspace Settings +description: Manage MED-V Workspace Settings +ms.assetid: 35ebd16e-31c7-4996-81be-af1d56346803 +author: MaggiePucciEvans +--- + +# Manage MED-V Workspace Settings + + +The information provided here can help administrators manage MED-V workspace settings. + +## In This Section + + +[Managing MED-V Workspace Settings by Using the MED-V Workspace Packager](managing-med-v-workspace-settings-by-using-the-med-v-workspace-packager.md) +Describes how to use the MED-V Workspace Packager to manage certain MED-V workspace settings. + +[Managing MED-V Workspace Settings by Using a WMI](managing-med-v-workspace-settings-by-using-a-wmi.md) +Describes how to use Windows Management Instrumentation to manage MED-V workspace settings. + +[Managing MED-V Workspace Configuration Settings](managing-med-v-workspace-configuration-settings.md) +Describes how to manage MED-V workspace configuration settings. + +[Managing Printers on a MED-V Workspace](managing-printers-on-a-med-v-workspace.md) +Describes how MED-V manages printer redirection in a MED-V workspace. + +## Related topics + + +[Monitor MED-V Workspaces](monitor-med-v-workspaces.md) + +[Operations for MED-V](operations-for-med-v.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/managing-applications-deployed-to-med-v-workspaces.md b/mdop/medv-v1/managing-applications-deployed-to-med-v-workspaces.md new file mode 100644 index 0000000000..235baa817b --- /dev/null +++ b/mdop/medv-v1/managing-applications-deployed-to-med-v-workspaces.md @@ -0,0 +1,36 @@ +--- +title: Managing Applications Deployed to MED-V Workspaces +description: Managing Applications Deployed to MED-V Workspaces +ms.assetid: 9a9bcdf5-0aa7-42a3-b6f0-6065adb01bcb +author: MaggiePucciEvans +--- + +# Managing Applications Deployed to MED-V Workspaces + + +After you deploy your MED-V workspace, you have several different methods to select from to install, remove, publish, and unpublish applications on the MED-V workspaces. + +This section provides information and instructions to help you manage applications after you have deployed the MED-V workspace. + +## In This Section + + +[Installing and Removing an Application on the MED-V Workspace](installing-and-removing-an-application-on-the-med-v-workspace.md) +Provides assistance in installing and removing applications on MED-V workspaces. + +[How to Publish and Unpublish an Application on the MED-V Workspace](how-to-publish-and-unpublish-an-application-on-the-med-v-workspace.md) +Provides assistance in publishing and unpublishing applications on MED-V workspaces. + +## Related topics + + +[How to Test Application Publishing](how-to-test-application-publishing.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/managing-automatic-updates-for-med-v-workspaces.md b/mdop/medv-v1/managing-automatic-updates-for-med-v-workspaces.md new file mode 100644 index 0000000000..0198e1125b --- /dev/null +++ b/mdop/medv-v1/managing-automatic-updates-for-med-v-workspaces.md @@ -0,0 +1,98 @@ +--- +title: Managing Automatic Updates for MED-V Workspaces +description: Managing Automatic Updates for MED-V Workspaces +ms.assetid: 306f28a2-d653-480d-b737-4b8b3132de5d +author: MaggiePucciEvans +--- + +# Managing Automatic Updates for MED-V Workspaces + + +The MED-V workspace is a virtual machine that contains a separate operating system, whose automatic software update process must be managed just like the physical computers in your enterprise. Because the guest operating system is not always necessarily running when the host operating system is running, you must ensure that the MED-V virtual machine is configured in such a way that software updates can be applied to the guest operating system as required. The Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 solution provides the functionality that lets you determine how automatic software updates are processed in a MED-V workspace. + +## Managing MED-V Workspace Wake-Up Policy + + +The MED-V workspace wake-up policy guarantees that the MED-V virtual machine is made available for updates for the time that you specify in your MED-V configuration settings. This applies to both updates that are published from Microsoft through Windows Update and updates deployed and controlled by non-Microsoft solutions, such as antivirus applications. + +**Important**   +The MED-V workspace wake-up policy is optimized for the Microsoft Update infrastructure. If you are using Microsoft System Center Configuration Manager to deploy non-Microsoft updates, we recommend that you also use the System Center Updates Publisher, which takes advantage of the same infrastructure as Microsoft Update and therefore benefits from the MED-V workspace wake-up policy. For more information, see [System Center Updates Publisher](http://go.microsoft.com/fwlink/?LinkId=200035) (http://go.microsoft.com/fwlink/?LinkId=200035). + +  + +When you created your MED-V workspace package, you configured when and how it starts, either when the end user logs on (**Fast Start**) or when the end user first opens a published application (**Normal Start**). Or you set the option to let the end user control this setting. + +Either way, whenever the **Fast Start** option is selected, the virtual machine continues to run as long as the MED-V host is logged on as User. In this configuration, because MED-V is active when the host is active, automatic updates are applied without requiring any extra processing from MED-V. + +However, for those cases in which **Fast Start** is not specified or the virtual machine hibernates or stops, MED-V guarantees through its MED-V workspace wake-up policy that the guest operating system is being regularly updated even when MED-V is not used regularly. MED-V performs this function by regularly waking up the virtual machine based on the configuration settings that you specify. This enables the automatic update clients in the virtual machine to execute based on their configurations. After the time period defined by the MED-V configuration setting elapses, MED-V returns the virtual machine to its previous state. + +**Note**   +If the end user opens a published application during the update period, the required updates are applied, but MED-V is not automatically hibernated or shut down after the update period ends. Instead, MED-V continues running. + +  + +The MED-V workspace wake-up policy includes three main components: + +**Guest Update Manager** + +Residing on the MED-V host, this stand-alone executable program is responsible for waking up the virtual machine according to a predefined, configurable schedule. Specify the configuration settings to indicate at what time the update manager should wake up the virtual machine every day, and how long the virtual machine should be kept awake (in minutes) to allow for updates to be applied. After the number of minutes specified has been reached, the guest update manager puts the virtual machine into hibernation, prepared for the next use. You can schedule the execution of this executable program through the Windows Task Manager. + +**Guest Restart Management Service** + +Residing on the MED-V host, this service has three primary responsibilities. Along with the Guest Update Manager, it manages the restart of the virtual machine at user logon, if it is required. It detects when virtual machine restarts are required caused by updates being installed. And it ensures that the task for the Guest Update Manager is always scheduled according to configuration. + +**Guest Update Service** + +Residing on the MED-V virtual machine, this Windows service has the responsibility of monitoring when installed updates require a restart. After the service becomes aware of the need for a restart, it notifies the guest restart management service on the host. + +### Configuration Settings for MED-V Workspace Wake-Up Policy + +You control when and for how long the virtual machine awakens to receive automatic updates by defining the following two configuration values in the registry. Both of these values are located under the HKLM\\Software\\Microsoft\\MEDV\\v2\\VM key. + +**GuestUpdateTime** – Configures the hour and minute each day when MED-V must wake up the virtual machine for updating, based on the 24-hour clock standard. Specify the time in the format HH:MM. The default value is 00:00 (midnight). + +**GuestUpdateDuration** – Configures the number of minutes that MED-V must keep the virtual machine awake for updating, starting at the time specified in the GuestUpdateTime configuration setting. The default value is 240 (4 hours). Setting this value to zero (0) disables the MED-V workspace wake-up policy. + +For more information about how to define your MED-V configuration values, see [Managing MED-V Workspace Configuration Settings](managing-med-v-workspace-configuration-settings.md). + +**Note**   +A MED-V best practice is to set your wake up interval to match the time when MED-V virtual machines are planned to be updated regularly. In addition, we recommend that you configure these settings to resemble the host computer’s behavior. + +  + +### Reboot Notification Using your ESD System + +You can configure your ESD system to notify MED-V whenever a restart is required for the MED-V workspace after automatic updates have been applied. When you apply automatic updates through your ESD system that you know require a restart, you should write a script to signal the following global event on the MED-V workspace: + +**Important**   +You must open the event with Modify Only rights and then signal it. If you do not open it with the correct permissions, it does not work. + +  + +``` syntax +/// +/// The guest is required to be restarted due to an ESD update. +/// +public const string MedvGuestRebootRequiredEventName = @"Global\MedvGuestRebootRequiredEvent"; +using (EventWaitHandle notificationEvent = +EventWaitHandle.OpenExisting(eventName, EventWaitHandleRights.Modify)) +{ +notificationEvent.Set(); +} +``` + +When you signal this event, MED-V captures it and informs the virtual machine that a restart is required. + +## Related topics + + +[Managing Software Updates for MED-V Workspaces](managing-software-updates-for-med-v-workspaces.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/managing-med-v-workspace-configuration-settings.md b/mdop/medv-v1/managing-med-v-workspace-configuration-settings.md new file mode 100644 index 0000000000..f647be46ae --- /dev/null +++ b/mdop/medv-v1/managing-med-v-workspace-configuration-settings.md @@ -0,0 +1,774 @@ +--- +title: Managing MED-V Workspace Configuration Settings +description: Managing MED-V Workspace Configuration Settings +ms.assetid: 517d04de-c31f-4b50-b2b3-5f8c312ed37b +author: MaggiePucciEvans +--- + +# Managing MED-V Workspace Configuration Settings + + +Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 stores its configuration settings in the registry. The information we include here about the registry may help you better manage your MED-V services. + +MED-V uses the following search path when looking for the resultant settings values: + +MED-V first looks in the machine policy. + +If the value is not found, MED-V looks in the user policy. + +If the value is not found, MED-V looks in the HKEY\_LOCAL\_MACHINE\\System hive. + +If the value is not found, MED-V looks in the HKEY\_CURRENT USER registry hive. + +If the value is still not found, MED-V uses the default. + +A general best practice is to set the value in the HKEY\_LOCAL\_MACHINE\\System hive or in the machine policy. But if you want the end user to be able to configure a particular setting, then you should leave it out. + +**Note**   +Before you deploy your MED-V workspaces, you can use a script editor to change the Windows PowerShell script (.ps1 file) that the MED-V workspace packager created. For more information, see [Configuring Advanced Settings by Using Windows PowerShell](configuring-advanced-settings-by-using-windows-powershell.md). + +After you have deployed your MED-V workspaces, you can change certain MED-V configuration settings by editing the registry entries. + +  + +This section lists all the configurable MED-V registry keys and explains their uses. + +## Diagnostics Key + + +The following table provides information about the registry values associated with the HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Medv\\v2\\Diagnostics key. + + ++++++ + + + + + + + + + + + + + + + + +
Name Type Data/Default Description 

EventLogLevel 

DWORD 

Default=3

The type of information that is logged in the event log. Levels include the following: 0 (None), 1 (Error), 2 (Warning), 3 (Information), 4 (Debug).

+ +  + +## Fts Key + + +The following table provides information about the registry values associated with the HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Medv\\v2\\Fts key. + + ++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeData/DefaultDescription

AddUserToAdminGroupEnabled 

DWORD

Default=0

Configures whether first time setup automatically adds the end user to the administrator's group. 0 = false; 1 = true.

0 = false: First time setup does not automatically add the end user to the administrator's group.

1 = true: First time setup automatically adds the end user to the administrator's group.

ComputerNameMask 

SZ

MEDV* 

The computer name mask that is used to create the guest virtual machine's computer name.

The mask can contain a %username% tag to insert the username as part of the computer name. Likewise, the %hostname% tag inserts the name of the host computer.

+

Every "#" character in the mask is replaced by a random digit. An asterisk (*) character at the end of the mask is replaced by random alphanumeric characters.

+

A specific number of characters from %hostname% and %username% can be captured by using square brackets. For example, "%username%[3]" would use the first three characters of the username.

DeleteVMStateTimeout

DWORD

Default=90

The time-out value, in seconds, when first time setup tries to delete the virtual machine. Range = 0 to 2147483647.

DetachVfdTimeout

DWORD

Default=120

The time-out value, in seconds, when first time setup tries to detach the virtual floppy disk from the virtual machine. Range = 0 to 2147483647.

DialogUrl 

SZ

Customizable URL that links to internal webpage and is displayed by first time setup dialog messages. 

ExplorerTimeout

DWORD

Default=900

The time-out value, in seconds, that first time setup waits for Windows Explorer. Range = 0 to 2147483647.

FailureDialogMsg 

MULTI_SZ

Message is found in resource file 

Customizable message that is displayed to the end user when first time setup cannot be completed.

GiveUserGroupRightsMaxRetryCount 

DWORD 

Default=3

The maximum number of times that MED-V tries to give an end user group rights. Exceeding the specified retry value without being able to successfully give an end user group rights most likely causes a virtual machine preparation failure that is then subject to the MaxRetryCount value. Range = 0 to 2147483647.

GiveUserGroupRightsTimeout 

DWORD

Default=300

The time-out value, in seconds, when giving a user group rights. Range = 0 to 2147483647.

LogFilePaths 

MULTI_SZ

A list of the log file paths that MED-V collects during first time setup. 

MaxPostponeTime 

DWORD

Default=120

The maximum number of hours that first time setup can be postponed by the end user. Range = 0 to 2147483647.

MaxRetryCount 

DWORD

Default=3

The maximum number of times that MED-V tries to prepare a virtual machine if each attempt ends in a failure other than a software error. When virtual machine preparation fails and the number of first time setup retries is exceeded, then MED-V informs the end user about the failure and does not give the option to retry. The count is re-set every time that MED-V is started. Range = 0 to 2147483647.

Mode 

SZ

Default=Unattended

Configures how first time setup interacts with the user. Possible values are as follows:

Attended. The end user must enter information during first time setup.

+
+Note   +

If you created the Sysprep.inf file so that Mini-Setup requires user input to complete, then you must select Attended mode or problems might occur during first time setup.

+
+
+  +

Unattended. The virtual machine is not shown to the end user during first time setup, but the end user is prompted before first time setup starts.

Silent. The virtual machine is not shown to the end user at all during first time setup.

NonInteractiveRetryTimeoutInc 

DWORD

Default=15

The time-out value, in minutes, that first time setup must be completed in first time setup interactive mode when re-attempting setup. Range = 0 to 2147483647.

NonInteractiveTimeout 

DWORD

Default=45

The time-out value, in minutes, that first time setup must be completed in first time setup interactive mode. Range = 0 to 2147483647.

PostponeUtcDateTimeLimit 

SZ

The date and time, in UTC DateTime format, that first time setup can be postponed. Enter in the format "yyyy-MM-dd hh:mm" with hours specified by using the 24-hour clock standard.

RetryDialogMsg 

MULTI_SZ

Message is found in resource file 

Customizable message that is displayed to the end user when first time setup must re-attempt setup.

SetComputerNameEnabled 

DWORD

Default=0

Configures whether the ComputerName entry under the [UserData] section of the Sysprep.inf file in the guest should be updated according to the specified ComputerNameMask.   0 = false; 1 = true.

0 = false: The ComputerName entry in the Sysprep.inf file is not updated according to the ComputerNameMask.

1 = true: The ComputerName entry in the Sysprep.inf file is updated according to the ComputerNameMask.

SetJoinDomainEnabled 

DWORD

Default=0

Configures whether the JoinDomain setting under the [Identification] section of the Sysprep.inf file in the guest should be updated to match the settings on the host.  0 = false; 1 = true.

0 = false: The JoinDomain setting in the Sysprep.inf file is not updated to match the settings on the host.

1 = true: The JoinDomain setting in the Sysprep.inf file is updated to match the settings on the host.

SetMachineObjectOUEnabled 

DWORD

Default=0

Configures whether the MachineObjectOU setting under the [Identification] section of the Sysprep.inf file in the guest is updated to match the host.  0 = false; 1 = true.

0 = false: The MachineObjectOU setting in the Sysprep.inf file is not updated to match the settings on the host.

1 = true: The MachineObjectOU setting in the Sysprep.inf file is updated to match the settings on the host.

SetRegionalSettingsEnabled 

DWORD

Default=0

Configures whether the settings under the [RegionalSettings] section of the Sysprep.inf file in the guest are updated to match the host.  0 = false; 1 = true.

+
+Note   +

By default, the setting for TimeZone in the guest is always synchronized with the TimeZone setting in the host.

+
+
+  +

0 = false: The settings under the [RegionalSettings] section of the Sysprep.inf file in the guest are not updated to match the host.

1 = true: The settings under the [RegionalSettings] section of the Sysprep.inf file in the guest are updated to match the host.

SetUserDataEnabled 

DWORD

Default=0

Configures whether the FullName and the OrgName settings under the [UserData] section of the Sysprep.inf file in the guest are updated to match the settings on the host.  0 = false; 1 = true.

0 = false: The FullName and OrgName settings in the Sysprep.inf file are not updated to match the settings on the host.

1 = true: The FullName and OrgName settings in the Sysprep.inf file are updated to match the settings on the host.

StartDialogMsg 

MULTI_SZ

Message is found in resource file 

Customizable message that is displayed to the end user when first time setup is ready to start. 

TaskCancelTimeout

DWORD

Default=30

The time-out value, in seconds, that first time setup waits for a response from the virtual machine for a Cancel operation. Range = 0 to 2147483647.

TaskVMTurnOffTimeout

DWORD

Default=60

The time-out value, in seconds, that first time setup waits for the virtual machine to shut down. Range = 0 to 2147483647.

UpgradeTimeout

DWORD

Default=600

The time, in seconds, before an attempted upgrade of the MED-V Guest Agent software times out. Range = 0 to 2147483647.

+ +  + +## UserExperience Key + + +The following table provides information about the registry values associated with the HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Medv\\v2\\UserExperience key and the HKEY\_CURRENT\_USER\\Software\\Microsoft\\Medv\\v2\\UserExperience key. + + ++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeData/DefaultDescription

AppPublishingEnabled 

DWORD

Default=1

Configures whether application publication from the guest to the host is enabled.  0 = false; 1 = true.

0 = false: Disables application publishing from the guest to the host.

1 = true: Enables application publishing from the guest to the host.

AudioSharingEnabled 

DWORD

Default=1

Configures whether the sharing of the audio I/O device between the guest and the host is enabled.  0 = false; 1 = true.

0 = false: Disables the sharing of the audio I/O device between the guest and the host.

1 = true: Enables the sharing of the audio I/O device between the guest and the host.

ClipboardSharingEnabled 

DWORD

Default=1

Configures whether the sharing of the Clipboard between the guest and the host is enabled.  0 = false; 1 = true.

0 = false: Disables the sharing of the Clipboard between the guest and the host.

1 = true: Enables the sharing of the Clipboard between the guest and the host.

DialogTimeout

DWORD

Default=300

The time, in seconds, before the first time setup Start Dialog times out. Range = 0 to 2147483647.

HideVmTimeout

DWORD

Default=30

The time-out value, in minutes, that the full-screen virtual machine window is hidden from the end user during a long logon attempt.

LogonStartEnabled 

DWORD

Default=1

Configures whether the guest should be started when the end user logs on to the desktop or when the first guest application is started.  0 = false; 1 = true.

0 = false: The guest is started when the first guest application is started.

1 = true: The guest is started when the end user logs on to the desktop.

PrinterSharingEnabled 

DWORD

Default=1

Configures whether the sharing of printers between the guest and the host is enabled.  0 = false; 1 = true.

0 = false: Disables the sharing of printers between the guest and the host.

1 = true: Enables the sharing of printers between the guest and the host.

RebootAbsoluteDelayTimeout 

DWORD

Default=1440

The time-out value, in minutes, that first time setup waits for a restart. Range = 0 to 2147483647.

RedirectUrls 

MULTI_SZ

Specified URL list

Specifies a list of URLs to be redirected from the host to the guest. 

SmartCardLogonEnabled

DWORD

Default=0

Configures whether smart cards can be used to authenticate users to MED-V. 0 = false; 1 = true.

0 = false: Does not let Smart Cards authenticate end users to MED-V.

1 = true: Lets Smart Cards authenticate end users to MED-V.

+
+Important   +

If SmartCardLogonEnabled and CredentialCacheEnabled are both enabled, SmartCardLogonEnabled overrides CredentialCacheEnabled.

+
+
+  +

SmartCardSharingEnabled 

DWORD

Default=1

Configures whether the sharing of Smart Cards between the guest and the host is enabled.  0 = false; 1 = true.

0 = false: Disables the sharing of Smart Cards between the guest and the host.

1 = true: Enables the sharing of Smart Cards between the guest and the host.

USBDeviceSharingEnabled 

DWORD

Default=1

Configures whether the sharing of USB devices between the guest and the host is enabled.  0 = false; 1 = true.

0 = false: Disables the sharing of USB devices between the guest and the host.

1 = true: Enables the sharing of USB devices between the guest and the host.

+ +  + +## VM Key + + +The following table provides information about the registry values associated with the HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Medv\\v2\\VM key and the HKEY\_CURRENT\_USER\\Software\\Microsoft\\Medv\\v2\\VM key. + + ++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeData/DefaultDescription

CloseAction 

SZ

Default=HIBERNATE

The action that the virtual machine performs after the last application that is running is closed. This setting is ignored if the LogonStartEnabled value is enabled. Possible options are as follows:

HIBERNATE . This option releases all physical resources that the virtual machine is using, such as memory and CPU, and saves the state of all running applications and operations.

SHUTDOWN . This option shuts down the guest operating system safely and then releases all physical resources that the virtual machine is using, such as memory and CPU.

TURN-OFF. This option can cause data loss because it is the same as turning off the power button or pulling out the power cord on a physical computer. Use this option only if you cannot use one of the other two options.

GuestMemFromHostMem 

MULTI_SZ

378, 512, 1024, 1536, 2048 

A list of memory (MB) values for the guest. This value is used to determine how much RAM is available to the guest. Combined with HostMemToGuestMem, a lookup table is created to determine how much RAM to allocate on the guest virtual machine. Possible values can be from 128 to 3712.

GuestUpdateDuration 

DWORD

Default=240

The number of minutes that MED-V should keep the guest awake for automatic updating, starting at the time specified in the GuestUpdateTime value. Range = 0 to 1440. Setting this value to zero (0) disables the guest patching functionality.

+

For more information about guest patching for automatic updating, see [Managing Automatic Updates for MED-V Workspaces](managing-automatic-updates-for-med-v-workspaces.md).

GuestUpdateTime 

SZ

Default=00:00

The hour and minute each day when MED-V should wake up the guest for automatic updating, by using the 24-hour clock standard. Specify the time in the format HH:MM  

+

For more information about guest patching for automatic updating, see [Managing Automatic Updates for MED-V Workspaces](managing-automatic-updates-for-med-v-workspaces.md).

HostMemToGuestMem 

MULTI_SZ

1024, 2048, 4096, 8192, 16384 

A list of memory (MB) values for the guest, determined by the RAM available on the host. Combined with GuestMemFromHostMem, a lookup table is created to determine how much RAM to allocate on the guest virtual machine. Possible values can be from 1024 to 16384.

HostMemToGuestMemCalcEnabled

DWORD

Default=1

Configures whether the memory allocated for the guest is calculated from the memory present on the host.  0 = false; 1 = true.

0 = false: The memory allocated for the guest is not calculated from the memory present on the host.

1 = true: The memory allocated for the guest is calculated from the memory present on the host.

Memory 

DWORD

Default=512

The RAM (MB) that should be allocated for the guest virtual machine. This setting is ignored if the HostMemToGuestMemEnabled setting is enabled. Range=128 to 2048.

MultiUserEnabled 

DWORD

Default=0

Configures whether multiple users share the same MED-V workspace.  0 = false; 1 = true.

0 = false: Multiple users do not share the same MED-V workspace.

1 = true: Multiple users share the same MED-V workspace.

NetworkingMode 

SZ

Default=NAT

The kind of network connection used on the guest. Possible values are as follows:

Bridged. MED-V has its own network address, typically obtained through DHCP.

NAT. MED-V uses Network Address Translation (NAT) to share the host's IP for outgoing traffic.

TaskTimeout 

DWORD

Default=600

A general time-out value, in seconds, that MED-V waits for a task to be completed, such as restarting and shutting down. Range = 0 to 2147483647.

+ +  + +## Guest Registry Settings + + +This section lists the configurable MED-V guest registry keys and explains their uses. + +### v2 + +The following table provides information about the guest registry value associated with the HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Medv\\v2\\ key. + + ++++++ + + + + + + + + + + + + + + + + + + + + + + +
Name Type Data/Default Description

EnableGPWorkarounds

DWORD 

Default=1 

Configures how MED-V handles the keys BufferPolicyReads and GroupPolicyMinTransferRate.

By default, MED-V sets these keys as follows:

+

BufferPolicyReads=1 and GroupPolicyMinTransferRate=0.

+

Create the EnableGPWorkarounds  key, if it is necessary, and set the key to zero if you do not want MED-V to change the default settings of BufferPolicyReads and GroupPolicyMinTransferRate.

+
+Note   +

If your MED-V workspace is running in NAT mode, EnableGPWorkarounds affects the registry keys BufferPolicyReads and GroupPolicyMinTransferRate. If your MED-V workspace is running in BRIDGED mode, EnableGPWorkarounds only affects the registry key BufferPolicyReads.

+
+
+  +
+

1=true: MED-V sets the keys BufferPolicyReads=1 and GroupPolicyMinTransferRate=0 (if running in NAT mode) or just BufferPolicyReads=1 (if running in BRIDGED mode).

+

0=false: MED-V does not make any changes to the keys BufferPolicyReads and GroupPolicyMinTransferRate.

+ +  + +## Related topics + + +[Manage MED-V Workspace Applications](manage-med-v-workspace-applications.md) + +[Manage MED-V URL Redirection](manage-med-v-url-redirection.md) + +[Manage MED-V Workspace Settings](manage-med-v-workspace-settings.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/managing-med-v-workspace-settings-by-using-a-wmi.md b/mdop/medv-v1/managing-med-v-workspace-settings-by-using-a-wmi.md new file mode 100644 index 0000000000..090de15615 --- /dev/null +++ b/mdop/medv-v1/managing-med-v-workspace-settings-by-using-a-wmi.md @@ -0,0 +1,136 @@ +--- +title: Managing MED-V Workspace Settings by Using a WMI +description: Managing MED-V Workspace Settings by Using a WMI +ms.assetid: 05a665a3-2309-46c1-babb-a3e3bbb0b1f9 +author: MaggiePucciEvans +--- + +# Managing MED-V Workspace Settings by Using a WMI + + +You can use Windows Management Instrumentation (WMI) in Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 to manage your current configuration settings. + +## To manage MED-V workspace settings with a WMI + + +A WMI browsing tool lets you view and edit the settings in a MED-V workspace. The WMI provider is implemented by using the WMI Provider Extension framework from the Microsoft .Net Framework 3.5. + +The WMI provider is implemented in the **root\\microsoft\\medv** namespace and implements the class **Setting**. The class **Setting** contains properties that correspond to the settings in the system registry under the HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Medv registry key. + +**Caution**   +WMI browsing tools can be used to delete or modify classes and instances. Deleting or modifying certain classes and instances can result in the loss of valuable data and cause MED-V to function unpredictably. + +  + +You can use your preferred WMI browsing tool to view and edit MED-V configuration settings by following these steps. + +1. Open your preferred WMI browsing tool with administrator permissions. + +2. Connect to the namespace **root\\microsoft\\medv**. + +3. Enumerate the instances to connect to the running instance. You want to connect to the instance of the class **Setting**. + + An **Object Editor** window opens. The MED-V configuration settings are listed as **Properties**. + +Perform the following steps to edit a MED-V configuration setting in the WMI. + +1. In the list of **Properties** on the **Object Editor** window, double-click the name of the configuration setting you want to edit. For example, to edit MED-V URL redirection information, double-click the property **UxRedirectUrls**. + + A **Property Editor** window opens. + +2. Edit the value to update the configuration information. For example, to edit MED-V URL redirection information, add or remove a web address in the list. + +3. Save the updated property settings. + +After you have finished viewing or editing MED-V configuration settings, close the WMI browsing tool. + +**Important**   +In some cases, a restart of the MED-V workspace is required for changes to MED-V configuration settings to take effect. + +  + +The following code shows the Managed Object Format (MOF) file that defines the **Setting** class. + +``` syntax +[dynamic: ToInstance, provider("TroubleShooting, Version=2.0.392.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"), singleton: DisableOverride ToInstance ToSubClass] +class Setting : ConfigValueProvider +{ +                boolean UxSmartCardLogonEnabled = TRUE; +                [read] string User; +                [implemented] void Clear([in] string propertyName); +}; +``` + +The **Setting** class inherits from the **ConfigValueProvider** class. The following code shows the Managed Object Format (MOF) file that defines the **ConfigValueProvider** class. + +``` syntax +[abstract] +class ConfigValueProvider +{ +                [write] string DiagEventLogLevel; +                [write] boolean FtsAddUserToAdminGroupEnabled; +                [write] string FtsComputerNameMask; +                [write] sint32 FtsDeleteVMStateTimeout; +                [write] sint32 FtsDetachVfdTimeout; +                [write] string FtsDialogUrl; +                [write] sint32 FtsExplorerTimeout; +                [write] string FtsFailureDialogMsg; +                [write] string FtsLogFilePaths[]; +                [write] sint32 FtsMaxPostponeTime; +                [write] sint32 FtsMaxRetryCount; +                [write] string FtsMode; +                [write] sint32 FtsNonInteractiveRetryTimeoutInc; +                [write] sint32 FtsNonInteractiveTimeout; +                [write] string FtsPostponeUtcDateTimeLimit; +                [write] string FtsRetryDialogMsg; +                [write] boolean FtsSetComputerNameEnabled; +                [write] boolean FtsSetJoinDomainEnabled; +                [write] boolean FtsSetMachineObjectOUEnabled; +                [write] boolean FtsSetRegionalSettingsEnabled; +                [write] boolean FtsSetUserDataEnabled; +                [write] string FtsStartDialogMsg; +                [write] sint32 FtsTaskCancelTimeout; +                [write] sint32 FtsTaskVMTurnOffTimeout; +                [write] sint32 FtsUpgradeTimeout; +                [write] boolean UxAppPublishingEnabled; +                [write] boolean UxAudioSharingEnabled; +                [write] boolean UxClipboardSharingEnabled; +                [write] boolean UxCredentialCacheEnabled; +                [write] sint32 UxDialogTimeout; +                [write] sint32 UxHideVmTimeout; +                [write] boolean UxLogonStartEnabled; +                [write] boolean UxPrinterSharingEnabled; +                [write] sint32 UxRebootAbsoluteDelayTimeout; +                [write] string UxRedirectUrls[]; +                [write] boolean UxShowExit; +                [write] boolean UxSmartCardLogonEnabled; +                [write] boolean UxSmartCardSharingEnabled; +                [write] boolean UxUSBDeviceSharingEnabled; +                [write] string VmCloseAction; +                [write] sint32 VmGuestMemFromHostMem[]; +                [write] sint32 VmGuestUpdateDuration; +                [write] string VmGuestUpdateTime; +                [write] sint32 VmHostMemToGuestMem[]; +                [write] boolean VmHostMemToGuestMemCalcEnabled; +                [write] sint32 VmMemory; +                [write] boolean VmMultiUserEnabled; +                [write] string VmNetworkingMode; +                [write] sint32 VmTaskTimeout; +}; +``` + +## Related topics + + +[Managing MED-V Workspace Configuration Settings](managing-med-v-workspace-configuration-settings.md) + +[Manage MED-V Workspace Settings](manage-med-v-workspace-settings.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/managing-med-v-workspace-settings-by-using-the-med-v-workspace-packager.md b/mdop/medv-v1/managing-med-v-workspace-settings-by-using-the-med-v-workspace-packager.md new file mode 100644 index 0000000000..4f01b0b3a4 --- /dev/null +++ b/mdop/medv-v1/managing-med-v-workspace-settings-by-using-the-med-v-workspace-packager.md @@ -0,0 +1,91 @@ +--- +title: Managing MED-V Workspace Settings by Using the MED-V Workspace Packager +description: Managing MED-V Workspace Settings by Using the MED-V Workspace Packager +ms.assetid: e4b2c516-b9f8-44f9-9eae-caac6c2af3e7 +author: MaggiePucciEvans +--- + +# Managing MED-V Workspace Settings by Using the MED-V Workspace Packager + + +You can use the MED-V Workspace Packager to manage certain settings in the MED-V workspace. + +**To manage settings in a MED-V workspace** + +1. To open the **MED-V Workspace Packager**, click **Start**, click **All Programs**, click **Microsoft Enterprise Desktop Virtualization**, and then click **MED-V Workspace Packager**. + +2. On the **MED-V Workspace Packager** main panel, click **Manage Settings**. + +3. In the **Manage Settings** window, you can configure the following MED-V workspace settings: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Start MED-V workspace

Choose whether to start the MED-V workspace at user logon, at first use, or to let the end user decide when the MED-V workspace starts.

The MED-V workspace starts in one of two ways: either when the end user logs on or when they first perform an action that requires MED-V, such as opening a published application or entering a URL that requires redirection.

+

You can either define this setting for the end user or let the end user control how MED-V starts.

+
+ Note   +

If you specify that the end user decides, the default behavior they experience is that the MED-V workspace starts when they log on. They can change the default by right-clicking the MED-V icon in the notification area and selecting MED-V User Settings. If you define this setting for the end user, they cannot change the way in which MED-V starts.

+
+
+   +

Networking

Select Shared or Bridged for your networking setting. The default is Shared.

Shared - The MED-V workspace uses Network Address Translation (NAT) to share the host's IP for outgoing traffic.

+

Bridged - The MED-V workspace has its own network address, typically obtained through DHCP.

Store credentials

Choose whether you want to store the end user credentials.

The default behavior is that credential storing is disabled so that the end user must be authenticated every time that they log on.

+
+ Important   +

Even though caching the end user’s credentials provides the best user experience, you should be aware of the risks involved.

+

The end user’s domain credential is stored in a reversible format in the Windows Credential Manager. An attacker could write a program that retrieves the password and thus gain access to the user’s credentials. You can only lessen this risk by disabling the storing of end user credentials.

+
+
+   +
+ +   + +4. Click **Save as…** to save the updated configuration settings in the specified folder. MED-V creates a registry file that contains the updated settings. Deploy the updated registry file by using Group Policy. For more information about how to use Group Policy, see [Group Policy Software Installation](http://go.microsoft.com/fwlink/?LinkId=195931) (http://go.microsoft.com/fwlink/?LinkId=195931). + + MED-V also creates a Windows PowerShell script in the specified folder that you can use to re-create this updated registry file. + +## Related topics + + +[Managing MED-V Workspace Configuration Settings](managing-med-v-workspace-configuration-settings.md) + +[Manage MED-V Workspace Settings](manage-med-v-workspace-settings.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/managing-printers-on-a-med-v-workspace.md b/mdop/medv-v1/managing-printers-on-a-med-v-workspace.md new file mode 100644 index 0000000000..216089c44a --- /dev/null +++ b/mdop/medv-v1/managing-printers-on-a-med-v-workspace.md @@ -0,0 +1,59 @@ +--- +title: Managing Printers on a MED-V Workspace +description: Managing Printers on a MED-V Workspace +ms.assetid: ba0a65ad-444f-4d18-95eb-8b9fa1a3ffba +author: MaggiePucciEvans +--- + +# Managing Printers on a MED-V Workspace + + +In Microsoft Enterprise Desktop Virtualization (MED-V) 2.0, printer redirection provides end users with a consistent printing experience between the MED-V virtual machine and the host computer. + +This topic provides information about how to manage printing in a MED-V workspace. + +## Managing Printers in MED-V Workspaces + + +In most cases, MED-V handles printer redirection automatically. After first time setup finishes, MED-V identifies all network printers installed on the host, retrieves the corresponding drivers from the network print server, and if found, installs the relevant drivers in the MED-V workspace. After all drivers are found and installed, MED-V reboots the MED-V workspace. Only after the MED-V workspace restarts, the host printers are present and available on the guest, typically in a few minutes. + +**Note**   +If applications are running on the MED-V workspace, the end user is prompted to let the restart continue or postpone it until later. If no applications are running, the restart is automatic and not shown to the end user. + +  + +Every time MED-V is re-started, it checks whether any new printers are installed on the host and, if found, retrieves the corresponding drivers from the network print server and installs them on the guest. MED-V then restarts the MED-V workspace just as when first time setup was completed. + +**Important**   +After the relevant drivers are installed on the guest, the printers only become visible on the guest after the restart occurs. + +  + +If at any time a driver cannot be located or installed, it must be manually installed on the guest for the network printer to be available to the end user. + +The following list offers some additional guidance: + +**MED-V only manages network printers**. Drivers for printers that are installed locally on the host are not automatically installed on the guest. + +**MED-V only installs printer drivers if found on the print server**. If not found, printer drivers must be manually installed. + +**Printers manually installed on the guest are not accessible to the host**. By default, MED-V only supports printer redirection from the guest to the host. + +**Warning**   +If a printer is manually installed on the guest, and the same printer is later installed on the host, the result is that the printer is installed two times in the guest. To avoid this situation, a MED-V best practice is to manage printer redirection in one manner only: either disable redirection and install printers manually on the guest, or enable redirection and do not install printers manually on the guest. + +  + +## Related topics + + +[Manage MED-V Workspace Settings](manage-med-v-workspace-settings.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/managing-software-updates-for-med-v-workspaces.md b/mdop/medv-v1/managing-software-updates-for-med-v-workspaces.md new file mode 100644 index 0000000000..566c2b068e --- /dev/null +++ b/mdop/medv-v1/managing-software-updates-for-med-v-workspaces.md @@ -0,0 +1,57 @@ +--- +title: Managing Software Updates for MED-V Workspaces +description: Managing Software Updates for MED-V Workspaces +ms.assetid: a28d6dcd-cb9f-46ba-8dac-1d990837a3a3 +author: MaggiePucciEvans +--- + +# Managing Software Updates for MED-V Workspaces + + +You have several different options available to you for providing software updates for the applications in the deployed MED-V workspace. + +**Note**   +For information about how to specify the configuration settings that define how MED-V receives automatic updates, see [Managing Automatic Updates for MED-V Workspaces](managing-automatic-updates-for-med-v-workspaces.md). + +  + +**Updating Software in a MED-V Workspace** + +1. **Using an Electronic Software Distribution System** + + If your organization uses an Electronic Software Distribution System (ESD) system to deploy software, you can use it to provide software updates for applications on MED-V workspaces just as you provide updates for applications on physical computers. + +2. **Using Group Policy** + + If your organization deploys software by using Group Policy, you can use it to provide software updates for applications on MED-V workspaces just as you provide updates for applications on physical computers. + +3. **Using Application Virtualization (APP-V)** + + If you use MED-V together with App-V, you can provide software updates to applications in the MED-V workspace by following the steps that are required by App-V for updating software. For more information, see [Application Virtualization](http://go.microsoft.com/fwlink/?LinkId=122939) (http://go.microsoft.com/fwlink/?LinkId=122939). + +4. **Updating Software in the Core Image** + + Although not considered a MED-V best practice, you can install software updates to applications on the core image. After you have installed the updates, you can then redeploy the MED-V workspace back out to your enterprise just as you deployed it originally. + + **Important**   + We do not recommend this method of managing software updates. In addition, if you update software in the core image and redeploy the MED-V workspace back out to your enterprise, first time setup must run again, and any data saved in the virtual machine is lost. + +   + +## Related topics + + +[Managing Automatic Updates for MED-V Workspaces](managing-automatic-updates-for-med-v-workspaces.md) + +[How to Test Application Publishing](how-to-test-application-publishing.md) + +[How to Publish and Unpublish an Application on the MED-V Workspace](how-to-publish-and-unpublish-an-application-on-the-med-v-workspace.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/med-v-2-configuration-cmdlets-stub.md b/mdop/medv-v1/med-v-2-configuration-cmdlets-stub.md new file mode 100644 index 0000000000..3ae51d75e9 --- /dev/null +++ b/mdop/medv-v1/med-v-2-configuration-cmdlets-stub.md @@ -0,0 +1,29 @@ +--- +title: MED-V 2 Configuration Cmdlets +description: MED-V 2 Configuration Cmdlets +ms.assetid: 1e90029c-4acd-4275-9f2a-2cf3358fca82 +author: MaggiePucciEvans +--- + +# MED-V 2 Configuration Cmdlets + + +Insert introduction here. + +## Section Heading + + +Insert section body here. + +### Subsection Heading + +Insert subsection body here. + +  + +  + + + + + diff --git a/mdop/medv-v1/med-v-2-workspace-cmdlets-stub.md b/mdop/medv-v1/med-v-2-workspace-cmdlets-stub.md new file mode 100644 index 0000000000..dd8806b3f6 --- /dev/null +++ b/mdop/medv-v1/med-v-2-workspace-cmdlets-stub.md @@ -0,0 +1,29 @@ +--- +title: MED-V 2 Workspace Cmdlets +description: MED-V 2 Workspace Cmdlets +ms.assetid: 8820156f-8279-4ed0-af88-77fee95c533a +author: MaggiePucciEvans +--- + +# MED-V 2 Workspace Cmdlets + + +Insert introduction here. + +## Section Heading + + +Insert section body here. + +### Subsection Heading + +Insert subsection body here. + +  + +  + + + + + diff --git a/mdop/medv-v1/med-v-20-best-practices.md b/mdop/medv-v1/med-v-20-best-practices.md new file mode 100644 index 0000000000..7c112b3f66 --- /dev/null +++ b/mdop/medv-v1/med-v-20-best-practices.md @@ -0,0 +1,102 @@ +--- +title: MED-V 2.0 Best Practices +description: MED-V 2.0 Best Practices +ms.assetid: 47ba2dd1-6c6e-4d6e-8e18-b42291f8e02a +author: MaggiePucciEvans +--- + +# MED-V 2.0 Best Practices + + +When you are planning, deploying, and managing MED-V in your enterprise, you may find the best practice recommendations to be useful. + +### Configure first time setup to run unattended + +Although you can specify any settings that you prefer, a MED-V best practice is that you create the Sysprep.inf file so that first time setup can be run in **Unattended** mode. This requires you to provide all the required settings information as you continue through the **Setup Manager** wizard. For more information about how to configure the MED-V image, see [Configuring a Windows Virtual PC Image for MED-V](configuring-a-windows-virtual-pc-image-for-med-v.md). + +### Disable restore points on the virtual machine + +Before you create the MED-V workspace package, we recommend that you disable restore points on the virtual machine to prevent the differencing disk from growing unbounded. For more information, see [How to turn off and turn on System Restore in Windows XP](http://go.microsoft.com/fwlink/?LinkId=195927) (http://go.microsoft.com/fwlink/?LinkId=195927). + +### Configure MED-V image to use local profiles + +We recommend that you apply only those policies that make sense in an application compatibility environment for Windows XP. For example, desktop customization policies do not typically have to be applied and should be disabled. For more information about how to allow only local profiles, see [Group Policy Settings for Roaming User Profiles](http://go.microsoft.com/fwlink/?LinkId=205072) (http://go.microsoft.com/fwlink/?LinkId=205072). + +### Configure a Group Policy performance update + +By default, Group Policy is downloaded to a computer one byte at a time. This causes delays when MED-V is being joined to the domain. To increase the performance of Group Policy, we recommend that you set the following registry key value to the registry: + +Registry subkey: HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon + +Entry: BufferPolicyReads + +Type: DWORD + +Value: 1 + +### Distribute legal notice through Group Policy instead of in the MED-V image + +If you want end users to see a service level agreement (SLA) before they access MED-V, we recommend that you enforce the SLA through Group Policy later so that the SLA is displayed to the end user after the first time setup is finished. + +**Caution**   +Even though a best practice is to run first time setup in **Unattended** mode, if you decide to set the local policy or registry entry to include an SLA in your image (virtual hard disk), you must also specify that first time setup is run in **Attended** mode, or first time setup can fail. + +  + +### Compact the virtual hard disk + +We recommend that you compact your virtual hard disk to reclaim empty disk space and reduce the size of the virtual hard disk. For more information about how to compact your virtual hard disk, see [Compacting the MED-V Virtual Hard Disk](compacting-the-med-v-virtual-hard-disk.md). + +### Configure virtual machine to restart on blue screen crash + +We recommend that you configure the MED-V workspace virtual machine to automatically restart when it encounters a blue screen crash. To configure this setting in the guest, set the AutoReboot value in the HKEY\_LOCAL\_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\CrashControl key to “1”. + +You can also configure this setting by clicking **Start**, clicking **Control Panel**, and then clicking **System**. Then, in the **Startup and Recovery** area of the **Advanced** tab, click **Settings**. Select the **Automatically restart** check box and click **OK**. + +### Back up MED-V image before sealing it + +We recommend that you create a backup copy of the MED-V image before you seal it. For more information about sealing your MED-V image, see [Configuring a Windows Virtual PC Image for MED-V](configuring-a-windows-virtual-pc-image-for-med-v.md). + +### Install Windows Virtual PC last when installing from a batch file + +When you install the MED-V components by using a batch file, specify that Windows Virtual PC and the Windows Virtual PC hotfix are installed after the MED-V Host Agent and the MED-V workspace package files. This ensures that Windows Update will not cause any interference with the installation process by requiring a restart. + +### Install MED-V workspace from local folder + +Because of problems that can occur when you install MED-V from a network location, we recommend that you copy the MED-V workspace setup files locally and then run setup.exe. + +### Manage printer redirection in one manner only + +If a printer is manually installed on the MED-V guest virtual machine, and the same printer is later installed on the host computer, the result is that it is installed two times in the guest. To avoid this situation, we recommend as MED-V best practice that you manage printer redirection in one manner only: either disable redirection and install printers manually on the guest, or enable redirection and do not install printers manually on the guest. + +### Configure settings for MED-V guest patching + +You can control when and for how long the MED-V virtual machine awakens to receive automatic updates by defining the relevant configuration values in the registry. A MED-V best practice is to set your wake-up interval to match the time when you have scheduled regular updates for MED-V virtual machines. In addition, we recommend that you configure these settings to resemble the host computer’s behavior. + +For more information about how to configure settings for MED-V guest patching, see [Managing Automatic Updates for MED-V Workspaces](managing-automatic-updates-for-med-v-workspaces.md). + +### Configure antivirus/backup software + +To prevent antivirus activity from affecting the performance of the virtual desktop, we recommend that when you can, you exclude the following virtual machine file types from any antivirus or backup process that is running on the MED-V host computer: + +- \*.VMC + +- \*.VUD + +- \*.VSV + +- \*.VHD + +## Related topics + + +[Security and Protection for MED-V](security-and-protection-for-med-v.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/med-v-20-deployment-overview.md b/mdop/medv-v1/med-v-20-deployment-overview.md new file mode 100644 index 0000000000..7c214a9f36 --- /dev/null +++ b/mdop/medv-v1/med-v-20-deployment-overview.md @@ -0,0 +1,153 @@ +--- +title: MED-V 2.0 Deployment Overview +description: MED-V 2.0 Deployment Overview +ms.assetid: 0b8998ea-c46f-4c81-a304-f380b2ed7cf8 +author: MaggiePucciEvans +--- + +# MED-V 2.0 Deployment Overview + + +This section provides general information and instructions about how to install and deploy Microsoft Enterprise Desktop Virtualization (MED-V) 2.0. + +## Overview + + +MED-V 2.0 is based on an application model, where the same methods that you use to deploy applications can be used to deploy and manage MED-V. A deployed MED-V solution includes two components: the MED-V Host Agent and Guest Agent. The MED-V Host Agent is installed on the Windows 7 desktop and the MED-V Guest Agent is installed on Windows XP inside the MED-V workspace. MED-V also includes a MED-V Workspace Packager that provides the information and tools necessary for creating and configuring MED-V workspaces. + +**Important**   +MED-V only supports the installation of the MED-V Workspace Packager, the MED-V Host Agent, and the MED-V workspace for all users. Installing MED-V for the current user only by selecting **ALLUSERS=””** causes failures in the installation of the components and in the setup of the MED-V workspace. + +  + +### The MED-V Installation Files + +MED-V includes the following installation files, required for running MED-V: + +**The MED-V Host Agent Installation File** + +The Host Agent installation file is named MED-V\_HostAgent\_Setup.exe. This file is distributed and installed on each relevant end-user computer as part of your enterprise-wide deployment of MED-V. + +**The MED-V Workspace Packager Installation File** + +The MED-V Workspace Packager installation file is named MED-V\_WorkspacePackager\_Setup.exe. Use this file to install the MED-V Workspace Packager on a computer where you have administrator rights and permissions. The desktop administrator uses the MED-V Workspace Packager to create and manage MED-V workspaces. + +**Note**   +The MED-V Guest Agent is installed automatically during first time setup. + +  + +### The MED-V Deployment Process + +The following is a high-level overview of the MED-V installation and deployment process: + +1. Install the MED-V Workspace Packager on the computer where you have administrative credentials and that you will be using to build the MED-V workspace packages. For more information, see [How to Install the MED-V Workspace Packager](how-to-install-the-med-v-workspace-packager.md). + +2. Prepare your MED-V image and create your MED-V workspace packages by using the MED-V Workspace Packager. For more information, see [Operations for MED-V](operations-for-med-v.md). + +3. Deploy the required MED-V components throughout your enterprise. The required components of MED-V are Windows Virtual PC, the MED-V Host Agent, and the MED-V workspace. + +**Important**   +Installation of the MED-V components requires administrative credentials. If an end user is installing MED-V, they are prompted to enter administrative credentials. Alternately, administrative credentials can be provided in context if you are installing by using an electronic software distribution (ESD) system. + +  + +### The MED-V Components + +The MED-V components that you deploy throughout your enterprise consist of the following: + +**Windows Virtual PC** + +MED-V functions inside Windows Virtual PC images for its compatibility solution. Windows Virtual PC and the update for Windows 7 (KB977206) are required. For more information, see [Configure Installation Prerequisites](configure-installation-prerequisites.md). + +**The MED-V Host Agent Installation File** + +MED-V\_HostAgent\_Setup.exe. + +**The MED-V Workspace Installation Files** + +The MED-V workspace installation files are created when you build your MED-V workspace package that consists of the following: + +A setup.exe executable program that executes the MED-V workspace installation + +A <MED-V\_workspace\_name>.msi installer + +A <VHD\_filename>.medv file, which is the compressed virtual hard disk + +The files for configuration settings (<workspace\_name>.reg and <workspace\_name>.ps1) + +To deploy MED-V, copy all the required installation files to the host computer or to a share that can be accessed by the host computer. Run the component installation files for Windows Virtual PC, the MED-V Host Agent, and the MED-V workspace. Then start the MED-V Host Agent to complete the first time setup of MED-V. + +You can perform the installation manually. However, we recommend that you use an electronic software distribution method to automate the deployment of the components. For more information, see [How to Deploy a MED-V Workspace Through an Electronic Software Distribution System](how-to-deploy-a-med-v-workspace-through-an-electronic-software-distribution-system.md). + +**Note**   +For information about available command-line arguments to control install options, see [Command-Line Options for MED-V Installation Files](command-line-options-for-med-v-installation-files.md). + +  + +## Deployment Steps + + +When you deploy MED-V throughout your enterprise, there are two main considerations: installation and first time setup. + +### Installation + +1. **Windows Virtual PC** - During installation, MED-V checks for Windows Virtual PC and its required update for Windows 7 (KB977206). For more information, see [Configure Installation Prerequisites](configure-installation-prerequisites.md). + + You can install these as part of the Windows 7 installations before you install MED-V, or you can install them as part of the MED-V distribution. However, MED-V does not include a mechanism for their deployment; they must be deployed by using an electronic software distribution (ESD) system or as part of the Windows 7 image. + + **Important**   + When you install the MED-V components by using a batch file, a best practice is to specify that Windows Virtual PC and the Windows Virtual PC hotfix are installed after the MED-V Host Agent and the MED-V workspace package files. This means that Windows Update will not cause any interference with the installation process by requiring a restart. + +   + + **Note**   + After you install Windows Virtual PC, the computer must be restarted. + +   + +2. **MED-V Host Agent** – Install the MED-V Host Agent on the Windows 7 computer where MED-V will be run. This must be installed before installing the MED-V workspace and checks to make sure that Windows Virtual PC is installed. + +3. **MED-V workspace** – You create the files that are required in this installation by using the MED-V Workspace Packager: the setup.exe, .medv, and .msi files. To install the MED-V workspace, run setup.exe; this triggers the other files as required. The installation places an entry in the registry under the local machine run key to start the MED-V Host Agent, which always runs MED-V when Windows is started. + + **Important**   + The installation of the MED-V workspace can be run interactively by the end user or silently through an electronic software distribution system. Installation of the MED-V workspace requires administrative credentials, so end users must be administrators of their computers to install the MED-V workspace. Alternately, an electronic software distribution system typically runs in the system context and has sufficient permissions. + +   + + **Tip**   + Because of problems that can occur when you install MED-V from a network location, we recommend that you copy the MED-V workspace setup files locally and then run setup.exe. + +   + +### First Time Setup + +After MED-V and its required components are installed, MED-V must be configured. The configuration of MED-V is known as first time setup. By using the **MED-V Workspace Packager**, you can configure first time setup to run silently or interactively. First time setup of MED-V requires end users to enter their password to authenticate to the MED-V workspace, but otherwise can be almost invisible to the user. Notifications are shown in the notification area, such as when first time setup is complete and applications are ready. The following are the actions that occur during first time setup of MED-V: + +1. The virtual hard disk must be configured. Mini-Setup runs and expands the Windows XP image. Typically, this occurs in a hidden window, but MED-V can be configured to display during this configuration. + +2. After Mini-Setup finishes, you can run commands that you must have for additional configuration, such as installing ESD software or other applications, or configuring the image. These can be called in the Sysprep.inf file, but are not required there. For more information, see [Configuring a Windows Virtual PC Image for MED-V](configuring-a-windows-virtual-pc-image-for-med-v.md). + +3. Ftscompletion.exe is run as the last step in configuration. This process completes the MED-V configuration, adds the user to the RDP group to let them access the MED-V workspace, copies logs, signals MED-V that the MED-V workspace is ready, and then restarts the MED-V workspace. This process can also add the user as an administrator of the MED-V workspace if this was configured when the MED-V workspace was created. Ftscompletion.exe is typically called through the Sysprep,inf file but can also be run through another method, such as a script. However, Ftscompletion.exe must be the last action that is performed when the workstation is configured. For more information, see [Configuring a Windows Virtual PC Image for MED-V](configuring-a-windows-virtual-pc-image-for-med-v.md). + +4. After the MED-V workspace is restarted by Ftscompletion.exe, the end user is logged on. If they did not save their password during first time setup, they are prompted for it again. The MED-V workspace is then started and configured for the user. Configuration includes applying Group Policy. + + We recommend that you apply only those policies that make sense in an application compatibility environment for Windows XP. For example, desktop personalization policies do not typically need to be applied and should be disabled. For more information about how to allow only local profiles, see [Group Policy Settings for Roaming User Profiles](http://go.microsoft.com/fwlink/?LinkId=205072) (http://go.microsoft.com/fwlink/?LinkId=205072). + +After first time setup is complete, the end user is notified that the published applications are ready. They are then able to access the applications installed in the MED-V workspace from their **Start** menu. + +## Related topics + + +[Prepare the Deployment Environment for MED-V](prepare-the-deployment-environment-for-med-v.md) + +[Deployment of MED-V](deployment-of-med-v.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/med-v-20-release-notes.md b/mdop/medv-v1/med-v-20-release-notes.md new file mode 100644 index 0000000000..4fe91b7f6b --- /dev/null +++ b/mdop/medv-v1/med-v-20-release-notes.md @@ -0,0 +1,59 @@ +--- +title: MED-V 2.0 Release Notes +description: MED-V 2.0 Release Notes +ms.assetid: b8f7d938-566e-434c-b4b8-28b67cdfd0b1 +author: MaggiePucciEvans +--- + +# MED-V 2.0 Release Notes + + +Updated: March 10, 2011 + +**To search these release notes, press CTRL+F.** + +Read these release notes thoroughly before you install the Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 platform. These release notes contain information that is required to successfully install MED-V 2.0 and contain information that is not available in the product documentation. If there is a difference between these release notes and other MED-V platform documentation, the latest change should be considered authoritative. These release notes supersede the content included with this product. + +## About the Product Documentation + + +Documentation for Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 is distributed with the product and is also located at [Microsoft Enterprise Desktop Virtualization 2.0](http://go.microsoft.com/fwlink/?LinkID=207065) (http://go.microsoft.com/fwlink/?LinkId=207065). + +## Protect Against Security Vulnerabilities and Viruses + + +To help protect against security vulnerabilities and viruses, we recommend that you install the latest available security updates for any new software being installed. For more information, see [Microsoft Security](http://go.microsoft.com/fwlink/?LinkId=3482) (http://go.microsoft.com/fwlink/?LinkId=3482). + +## Known Issues with MED-V 2.0 + + +This section provides the most up-to-date information about issues with the Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 platform. These issues do not appear in the product documentation and in some cases might contradict existing product documentation. When it is possible, these issues will be addressed in later releases. + +**Note**   +There are currently no known issues with MED-V 2.0. + +  + +## Release Notes Copyright Information + + +This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet website references, may change without notice. You bear the risk of using it. + +Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred. + +This document does not provide you with any legal rights to any intellectual property in any Microsoft product. This document is confidential and proprietary to Microsoft. It is disclosed and can be used only pursuant to a nondisclosure agreement. + + + +Microsoft, Active Directory, ActiveSync, MS-DOS, Windows, Windows Server, and Windows Vista are trademarks of the Microsoft group of companies. + +All other trademarks are property of their respective owners. + +  + +  + + + + + diff --git a/mdop/medv-v1/med-v-20-supported-configurations.md b/mdop/medv-v1/med-v-20-supported-configurations.md new file mode 100644 index 0000000000..e4e9e93cf1 --- /dev/null +++ b/mdop/medv-v1/med-v-20-supported-configurations.md @@ -0,0 +1,233 @@ +--- +title: MED-V 2.0 Supported Configurations +description: MED-V 2.0 Supported Configurations +ms.assetid: 88f1d232-aa01-45ab-8da7-d086269250b5 +author: MaggiePucciEvans +--- + +# MED-V 2.0 Supported Configurations + + +Your environment may already meet the configuration requirements provided here so that you can install and run Microsoft Enterprise Desktop Virtualization (MED-V) 2.0. We have included requirements including host operating system, disk space, and MED-V workspace requirements. + +## MED-V 2.0 Host Computer Requirements + + +### MED-V 2.0 Host Operating System Requirements + +The following table lists the operating systems that are supported for MED-V 2.0 installation on the host computer. + + ++++++ + + + + + + + + + + + + + + + + +
Operating SystemEditionService PackSystem Architecture

Windows 7

Professional, Enterprise, or Ultimate

None or SP1

x86 or x64

+ +  + +The following table lists the minimal RAM required for each operating system supported in MED-V 2.0. + + ++++ + + + + + + + + + + + + + + + + +
Operating SystemMinimum Required RAM

Windows 7 x86

2GB

Windows 7 x64

2GB

+ +  + +### Minimum Recommended Disk Space + +We recommend a minimum of 10GB of available storage. However, the disk space that is required varies greatly and depends on the number of applications published in the MED-V workspace. + +### MED-V 2.0 Host Configuration + +**.NET Framework Version** + +The .NET Framework 3.5 SP1 version of the Microsoft .NET Framework is required for MED-V 2.0. However, you can install the .NET Framework 4 or later version if the .NET Framework 3.5 is already installed. + +**Virtualization Engine** + +Windows Virtual PC with the hotfix that is described in Microsoft Knowledge Base article 977206 is supported for MED-V 2.0. + +**Internet Browser** + +Windows Internet Explorer 8 and Windows Internet Explorer 9 are supported for MED-V 2.0. + +**Microsoft Server Environments** + +The MED-V Host Agent and the MED-V Workspace Packager are not supported in any server environment. + +## MED-V 2.0 Workspace Requirements + + +### MED-V 2.0 Workspace Operating System Requirements + +The following table lists the operating systems supported for MED-V 2.0 workspaces. + + ++++++ + + + + + + + + + + + + + + + + +
Operating SystemEditionService PackSystem Architecture

Windows XP

Professional Edition

SP3

x86

+ +  + +### MED-V 2.0 Workspace Configuration + +**.NET Framework Version** + +Only the .NET Framework 3.5 SP1 version of the Microsoft .NET Framework is supported for MED-V 2.0 workspace installation. + +**Internet Browser** + +Windows Internet Explorer 6, Windows Internet Explorer 7, Windows Internet Explorer 8, and Windows Internet Explorer 9 are supported for the MED-V 2.0 workspace installation. + +### MED-V 2.0 Workspace Creation + +The virtual hard disk used to build a MED-V 2.0 workspace package must be created by using Windows Virtual PC. + +## MED-V 2.0 Globalization Information + + +### MED-V 2.0 Host Agent Globalization Information + +The following Windows operating system language versions are supported for the MED-V 2.0 Host Agent: + +- French + +- Italian + +- German + +- Spanish + +- Korean + +- Japanese + +- Brazilian Portuguese + +- Russian + +- Chinese Traditional + +- Chinese Simplified + +- Dutch + +- Swedish + +- Danish + +- Finnish + +- Portuguese + +- Norwegian + +- Polish + +- Turkish + +- Hungarian + +- Czech + +- Greek + +- Slovak + +- Slovenian + +### MED-V 2.0 Workspace Packager Globalization Information + +The following Windows operating system language versions are supported for the MED-V 2.0 Workspace Packager: + +- French + +- Italian + +- German + +- Spanish + +- Korean + +- Japanese + +- Brazilian Portuguese + +- Russian + +- Chinese Traditional + +- Chinese Simplified + +## Related topics + + +[Deployment of MED-V](deployment-of-med-v.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/med-v-event-log-messages.md b/mdop/medv-v1/med-v-event-log-messages.md new file mode 100644 index 0000000000..d748489683 --- /dev/null +++ b/mdop/medv-v1/med-v-event-log-messages.md @@ -0,0 +1,476 @@ +--- +title: MED-V Event Log Messages +description: MED-V Event Log Messages +ms.assetid: 7ba7344d-153b-4cc4-a00a-5d42aee9986b +author: MaggiePucciEvans +--- + +# MED-V Event Log Messages + + +The log files for Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 provide detailed information about how to deploy and manage MED-V in your enterprise and help verify functionality or help troubleshoot issues. + +## Event IDs + + +The following are a list of MED-V event IDs to help troubleshoot issues that you might encounter when you deploy or manage MED-V. + +### Fts + +Shows the event IDs for first time setup. + +### Event ID 3066 + +Start virtual machine operation failed. + +**Description** +A potential problem exists with the virtual hard disk (VHD) that you are using to create a MED-V workspace. + +**Solution** +Verify that you can create a virtual machine with the VHD for MED-V and that it can be started. + +### Event ID 3071 + +Virtual machine preparation failed. + +**Description** +A problem occurred with first time setup that might have been caused by many different issues. These include problems with network connectivity. + +**Solution** +Restart the MED-V Host Agent to rerun first time setup. + +### Event ID 3078 + +Virtual machine preparation failed. + +**Description** +A potential problem exists with the VHD that you are using to create a MED-V workspace. + +**Solution** +Verify that you can create a virtual machine with the VHD for MED-V and that it can be started. + +### Event ID 3079 + +Retrying virtual machine preparation. + +**Description** +MED-V is trying to prepare the virtual machine. + +**Solution** +No action is required. Let first time setup finish. + +### Event ID 3080 + +The client was stopped when preparing the virtual machine. + +**Description** +MED-V stops unexpectedly when it tries to prepare the virtual machine. + +**Solution** +Start the MED-V Host Agent and let first time setup complete + +### Event ID 3084 + +Virtual machine is not valid. First time setup needs to be re-run. + +**Description** +The MED-V Host Agent detected a problem with the virtual machine. + +**Solution** +No action is required. Let first time setup finish. + +### Event ID 3099 + +Call to start virtual machine failed. + +**Description** +A potential problem exists with the VHD you are using to create a MED-V workspace. + +**Solution** +Verify that you can create a virtual machine with the VHD for MED-V and that it can be opened. + +### VM Management + +### Event ID 4022 + +VMManagerException Fatal error while issuing command to VM. + +**Description** +The end user tried to exit MED-V by logging off or by shutting down the MED-V host, and the VMTaskTimeout configuration setting was exceeded. + +**Solution** +Restart MED-V. + +### Event ID 4028 + +VM Operation timed out. + +**Description** +The end user tried to exit MED-V by logging off or by shutting down the host, and the VMTaskTimeout configuration setting was exceeded. + +**Solution** +Restart MED-V. + +### Event ID 4038 + +Vmsal posted an error message to the user. + +**Description** +An error message is displayed to the end user stating that MED-V could not start the virtual application. + +**Solution** +If the error is logged two or more times in a row, stop MED-V and connect to the virtual machine by using Windows Virtual PC console and attempt to start the application in Full Screen. + +### Event ID 4040 + +Recycling Additions because TerminalServices is not initialized in the guest. + +**Description** +MED-V rebooted the virtual machine because Remote Desktop Services was not initialized on the virtual machine. + +**Solution** +If the error is logged two or more times in a row, stop MED-V and connect to the virtual machine by using Windows Virtual PC console. + +### Event ID 4042 + +Failed to recycle additions in the guest. + +**Description** +MED-V failed to recycle virtual machine additions on the virtual machine. + +**Solution** +If the error is logged two or more times in a row, stop MED-V and connect to the virtual machine by using Windows Virtual PC console. + +### Event ID 4043 + +Failed to reset expired password in the virtual machine. + +**Description** +The end user did not reset the password in the virtual machine before it expired. As a result, the user might not be able to access network resources or save work. + +**Solution** +Shut down the MED-V guest and restart it. + +### URL Redirection + +### Event ID 5005 + +Couldn’t get VM name from configuration; can’t launch guest browser. + +**Description** +URL Redirection could not obtain the MED-V workspace name from the configuration. As a result, it cannot inform Windows Virtual PC to open the redirected URL in the MED-V workspace browser. + +**Solution** +Ensure that the MED-V workspace name is set and that it matches a virtual machine name in the C:\\Users\\<*user*>\\Virtual Machines directory. The MED-V workspace name is located at HKLM\\SOFTWARE\\Microsoft\\Medv\\v2\\VM\\Name. + +For example, if the user is "Matt" and the workspace name is "mattsworkspace", the value of HKLM\\SOFTWARE\\Microsoft\\Medv\\v2\\VM\\Name should be "mattsworkspace", and there should be a file that is named C:\\Users\\Matt\\Virtual Machines\\mattsworkspace.vcmx. + +### Event ID 5006 + +Failed to create pipe server. + +**Description** +The URL Redirection service could not create the pipe server to communicate with Internet Explorer. + +**Solution** +Check system event logs for attempts to create a file or resource whose path begins similar to the following: "\\\\.\\pipe\\MEDVUrlRedirectionPipe\_" and ends with the user’s user name and domain name. If this is not present in the event log, restart the computer. + +### ConfigMgr (Guest) + +### Event ID 7001 + +The host network configuration data is not properly formatted. + +**Description** +Either the network configuration received from the host is an incorrectly formatted XML string, or the network information returned from the host cannot be written to an XML document. + +**Solution** +Restart the host computer and the virtual machine. + +### Event ID 7005 + +A change to the host network configuration was detected, but was not able to be applied because the host network configuration data was not properly formatted. + +**Description** +A change to the host network configuration was communicated to the virtual machine, but could not be processed in the virtual machine because of an error. This error could be caused by incorrectly formatted data or the inability to set the information into the Windows Management Instrumentation (WMI) CCMNetworkAdapter instance. + +**Solution** +Restart the host and virtual machine. + +### ConfigMgr (Host) + +### Event ID 8006 + +The virtual machine cannot be found. + +**Description** +Windows Virtual PC 7 cannot locate the virtual machine. The virtual machine might have been deleted, moved, removed, or access was denied. + +**Solution** +Reinstall the virtual machine. + +### Event ID 8008 + +The workstation's network configuration information could not be retrieved. + +**Description** +Network configuration information could not be collected from the MED-V host, most likely because of a system call failure in the .NET Framework. This failure can also occur if the network information returned from the MED-V host cannot be written to an XML document. + +**Solution** +Restart the host workstation. + +### Event ID 8010 + +The network configuration data could not be set in the virtual machine. + +**Description** +The MED-V host network address translation (NAT) could not be communicated to the virtual machine, most likely because the virtual machine is in a bad state or the Windows Virtual PC Additions were not installed or enabled. + +**Solution** +Shut down and restart the virtual machine. In addition, you might have to reinstall the virtual machine. + +### Event ID 8011 + +The network configuration data could not be reset in the virtual machine. + +**Description** +The MED-V host network configuration (BRIDGED) could not be communicated to the virtual machine, most likely because the virtual machine is in a bad state or the Windows Virtual PC Additions were not installed or enabled. + +**Solution** +Shut down and restart the virtual machine. In addition, you might have to reinstall the virtual machine. + +### Printer Redirection + +### Event ID 9001 + +File Permission Error. + +**Description** +The end user is not authorized to access the folder required to open or create the MED-V printer file for reading. + +**Solution** +Verify that the User\\AppData\\ path can be accessed and that the user has permission to read and write to it. For example, if the user is "Matt", the path C:\\Users\\Matt\\AppData\\, and all files therein should have Read and Write permissions. And if it exists, the path C:\\Users\\Matt\\AppData\\Local\\Microsoft\\MEDV\\v2\\ and all files therein should have Read and Write permissions. + +### Event ID 9002 + +File Permission Error. + +**Description** +The end user is not authorized to access the folder required to open or create the MED-V printer file for writing. + +**Solution** +Ensure that the User\\AppData\\ path can be accessed, and that the user has permission to read and write to it. For example, if the user is "Matt", the path C:\\Users\\Matt\\AppData\\ and all files therein should have Read and Write permissions. And if it exists, the path C:\\Users\\Matt\\AppData\\Local\\Microsoft\\MEDV\\v2\\ and all files therein should have Read and Write permissions. + +### Event ID 9004 + +Could not create path for storing MEDV printer files. + +**Description** +The printer redirection service could not access files or create directories required for storing the printer information. + +**Solution** +Verify that the User\\AppData\\ path can be accessed and that the user has permission to read and write to it. For example, if the user is "Matt", the path C:\\Users\\Matt\\AppData\\ and all files therein should have Read and Write permissions. And if it exists, the path C:\\Users\\Matt\\AppData\\Local\\Microsoft\\MEDV\\v2\\ and all files therein should have Read and Write permissions. + +### Event ID 9005 + +Couldn’t get VM name from configuration; cannot launch guest installer. Cannot update MED-V – No host network detected. + +**Description** +The printer redirection service was not able to obtain the MED-V workspace name from the MED-V configuration and cannot inform Windows Virtual PC to start the installer on the MED-V guest. + +**Solution** +Ensure that the MED-V workspace name is set and that it matches a virtual machine name in the C:\\Users\\<*user*>\\Virtual Machines directory. The MED-V workspace name is located at HKLM\\SOFTWARE\\Microsoft\\Medv\\v2\\VM\\Name. + +For example, if the user is "Matt" and the workspace name is "mattsworkspace", the value of HKLM\\SOFTWARE\\Microsoft\\Medv\\v2\\VM\\Name should be "mattsworkspace" and there should be a file that is named C:\\Users\\Matt\\Virtual Machines\\mattsworkspace.vcmx. + +### Application Publishing + +### Event ID 10015 + +A file system error occurred during the reconcile process. The reconcile process will not process the file <*filename*> but will continue to process any other changes. + +**Description** +An unauthorized access or I/O error occurred when a shortcut was being created or deleted. + +**Solution** +Check that the file path can be accessed and that the user has permissions to create or delete the specified file. + +### Event ID 10021 + +Error <*error\_information*> for file operation <*operation\_name*> on file <*filename*>. + +**Description** +An unauthorized access or I/O error occurred when a shortcut was being created or deleted. + +**Solution** +Check that the file path can be accessed and that the user has permissions to create or delete the specified file. + +### Guest Patching + +### Event ID 11001 + +Guest wakeup task usage message. + +**Description** +MedvHost.exe with the /GuestWakeup option was executed incorrectly, or the command is formatted incorrectly. + +**Solution** +Ensure that the command is executed with the following format: + +Medvhost.exe /GuestWakeup /d:< *duration\_in\_minutes*> /v:”< *workspace\_name*>” where + +<*duration\_in\_minutes*> is the number of minutes that the virtual machine should stay awake (default is 240) and + +<*workspace\_name*> is the name of the virtual machine that should be awakened. + +### Event ID 11002 + +Cannot update MED-V – No host network detected. + +**Description** +Guest patching could not finish because no host network connection was detected. + +**Solution** +Connect the MED-V host to an active network connection before you run guest patching. + +### Event ID 11003 + +Cannot update MED-V – Host not running on A/C powerFailed to create pipe server. + +**Description** +Guest patching could not finish because the host appears to be running on battery power instead of from a power cord. + +**Solution** +Connect the host computer to a power cord before you run guest patching. + +### Client UX + +### Event ID 14003 + +The following tray status message was too long and could not be displayed: <*tray\_status\_message*> + +**Description** +MED-V created an unanticipated string that was too long for the tray tooltip or balloon message. As a result, the displayed message was truncated. + +**Solution** +This is a rare error that can occur when MED-V is randomly creating the tooltip text. There is no solution. + +### Event ID 14004 + +MED-V stopped due to an unhandled exception. + +**Description** +An unhandled exception caused MED-V to stop unexpectedly. + +**Solution** +Restart MED-V. + +### Event ID 14005 + +Server attempted to create mutex but it already existed. + +**Description** +A second instance of MedvHost.exe is stuck in memory. + +**Solution** +Open TaskManager and end all MedvHost.exe processes. + +### Event ID 14006 + +Error modifying or deleting registry value <*registry\_value*>. + +**Description** +MED-V is unable to modify the specified entry in the registry. + +**Solution** +Ensure that you install or uninstall MED-V with administrative credentials. + +### Event ID 14007 + +The file specified (<*filename*>) is not valid. + +**Description** +During install or uninstall, a corrupted temp file was passed to MED-V host. + +**Solution** +Delete all files in the Temp folder and reinstall or uninstall MED-V. + +### Event ID 14008 + +File not found: <*filename*>. + +**Description** +During install or uninstall, a path of a required temp file was not found. + +**Solution** +Delete all files in the Temp folder and reinstall or uninstall MED-V. + +### Event ID 14009 + +Unable to read parameter file <*filename*>. + +**Description** +During the install or uninstall process, MED-V was unable to read a temp file. + +**Solution** +Delete all files in the Temp folder and reinstall or uninstall MED-V. In addition, verify that the user has the necessary rights and permissions to the Temp folder. + +### Event ID 14010 + +Error deserializing parameter file <*filename*>. + +**Description** +During the install or uninstall process, MED-V encountered a corrupted temp file. + +**Solution** +Delete all files in the Temp folder and reinstall or uninstall MED-V. In addition, verify that the user has the necessary rights and permissions to the Temp folder. + +### Event ID 14011 + +Unexpected error deserializing parameter file <*filename*>. + +**Description** +During the install or uninstall process, MED-V encountered a corrupted temp file. + +**Solution** +Delete all files in the Temp folder and reinstall or uninstall MED-V. In addition, verify that the user has the necessary rights and permissions to the Temp folder. + +### Event ID 14012 + +Unexpected error when settings rights on folder <*folder\_name*> for user <*username*>. + +**Description** +An error occurs when MED-V is unable to set rights and permissions on certain folders during installation. + +**Solution** +Check the administrator rights to the following folders: + +@"%ProgramData%\\Microsoft\\Medv\\AllUsers" + +@"%ProgramData%\\Microsoft\\Medv\\MedvLock" + +@"%ProgramData%\\Microsoft\\Medv\\Monitoring" + +### Event ID 14013 + +Unexpected error when creating lock file. + +**Description** +An error occurs when MED-V is unable to create a file in the @"%ProgramData%\\Microsoft\\Medv\\MedvLock" folder during installation. + +**Solution** +Check the administrator rights to the MedvLock folder. + +## Related topics + + +[Troubleshooting MED-V](troubleshooting-med-vmedv2.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/monitor-med-v-workspaces.md b/mdop/medv-v1/monitor-med-v-workspaces.md new file mode 100644 index 0000000000..f395ecdc20 --- /dev/null +++ b/mdop/medv-v1/monitor-med-v-workspaces.md @@ -0,0 +1,36 @@ +--- +title: Monitor MED-V Workspaces +description: Monitor MED-V Workspaces +ms.assetid: f514afe2-8add-4105-9520-1a491733fa79 +author: MaggiePucciEvans +--- + +# Monitor MED-V Workspaces + + +This section provides information and contains procedures to help administrators monitor MED-V workspaces. + +## In This Section + + +[Monitoring MED-V Workspace Deployments](monitoring-med-v-workspace-deployments.md) +Describes how to monitor the deployment of MED-V workspaces to determine whether first time setup finished. + +[Detecting Network Changes that Affect MED-V](detecting-network-changes-that-affect-med-v.md) +Describes how to set up your environment to detect those network changes that can affect MED-V. + +## Related topics + + +[Manage MED-V Workspace Settings](manage-med-v-workspace-settings.md) + +[Operations for MED-V](operations-for-med-v.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/monitoring-med-v-workspace-deployments.md b/mdop/medv-v1/monitoring-med-v-workspace-deployments.md new file mode 100644 index 0000000000..3088969eff --- /dev/null +++ b/mdop/medv-v1/monitoring-med-v-workspace-deployments.md @@ -0,0 +1,95 @@ +--- +title: Monitoring MED-V Workspace Deployments +description: Monitoring MED-V Workspace Deployments +ms.assetid: 5de0cb06-b8a9-48a5-b8b3-836954295765 +author: MaggiePucciEvans +--- + +# Monitoring MED-V Workspace Deployments + + +The monitoring feature in Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 lets you run queries on individual MED-V workspaces to determine whether first time setup succeeded throughout your enterprise after the MED-V workspaces are deployed. Monitoring the success of first time setup is important because MED-V is not in a usable state until first time setup has been completed successfully. + +This section provides information and instruction to assist you in monitoring the success or failure of first time setup. + +## To monitor MED-V workspace deployments + + +The monitoring feature consists of a coupled in-process Windows Management Instrumentation (WMI) provider that you can query using WMI Query Language to discover the status of first time setup for all end users on a MED-V workspace. + +The WMI provider is implemented by using the WMI Provider Extension framework from the Microsoft .Net Framework 3.5. The WMI provider executes in the context of LocalService and stores the first time setup state securely under \\ProgramData. + +The WMI provider is implemented in the **root\\microsoft\\medv** namespace and implements the class **FTS\_Status**, which exposes the method **SetFtsState**. MED-V uses **SetFtsState** to set the first time setup state. + +The class contains the following properties. + + ++++ + + + + + + + + + + + + + + + + + + + + + + + + +
PropertyDescription

Machine

Read Only property that contains the name of the guest virtual machine provisioned by first time setup. This key contains the name that the guest would have had on first time setup failure.

StatusCode

Read Only property that contains zero if first time setup succeeded. Any other value returned equals the event ID for the error that is logged.

Time

The UTC time that first time setup completed.

User

The user for which first time setup was run.

+ +  + +The following code shows the Managed Object Format (MOF) file that defines the **FTS\_Status** class. + +``` syntax +[dynamic: ToInstance, provider("MedvWmi, Version=2.0.258.0, Culture=neutral, PublicKeyToken=14986c3f172d1c2c")] +class FTS_Status +{ +[read, key] string User; +[read] string Machine; +[read] sint32 StatusCode; +[read] datetime Time; +[static, implemented] void SetFtsState([in] sint32 statusCode, [in] string machine); +}; +``` + +Because your main concern is most likely those MED-V workspaces for which first time setup was not completed successfully, you can write your query to only return those that failed first time setup, for example: + +``` syntax +Select * from FTS_Status where StatusCode != 0 +``` + +In this case, the monitoring feature returns a list of those MED-V workspaces that failed first time setup, which you can use to take the appropriate actions to resolve the failure. + +## Related topics + + +[Monitor MED-V Workspaces](monitor-med-v-workspaces.md) + +[How to Verify First Time Setup Settings](how-to-verify-first-time-setup-settings.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/operations-for-med-v.md b/mdop/medv-v1/operations-for-med-v.md new file mode 100644 index 0000000000..8d38e3e4ba --- /dev/null +++ b/mdop/medv-v1/operations-for-med-v.md @@ -0,0 +1,52 @@ +--- +title: Operations for MED-V +description: Operations for MED-V +ms.assetid: 8f3f367d-fa9d-4468-814a-f0495adfaea4 +author: MaggiePucciEvans +--- + +# Operations for MED-V + + +The topics in this section provide step-by-step instructions and help you deploy and manage the Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 environment and its components. + +## In This Section + + +[End-to-End Operations Scenario for MED-V 2.0](end-to-end-operations-scenario-for-med-v-20.md) +Describes an end-to-end operations scenario for MED-V 2.0. + +[Prepare a MED-V Image](prepare-a-med-v-image.md) +Describes how to create, install, configure, package, and test a Windows Virtual PC image for MED-V 2.0. + +[Create a MED-V Workspace Package](create-a-med-v-workspace-package.md) +Describes how to use the MED-V Workspace Packager to create or modify a MED-V workspace deployment package. + +[Test And Deploy the MED-V Workspace Package](test-and-deploy-the-med-v-workspace-package.md) +Describes how to test and deploy a MED-V workspace deployment package. + +[Monitor MED-V Workspaces](monitor-med-v-workspaces.md) +Describes how to monitor successful MED-V workspace deployments. + +[Manage MED-V Workspace Applications](manage-med-v-workspace-applications.md) +Describes how to manage the applications that are deployed to a MED-V workspace. + +[Manage MED-V URL Redirection](manage-med-v-url-redirection.md) +Describes how to manage URL redirection in a MED-V workspace. + +[Manage MED-V Workspace Settings](manage-med-v-workspace-settings.md) +Describes how to manage configuration settings and printers in a MED-V workspace. + +## Related topics + + +[Microsoft Enterprise Desktop Virtualization 2.0](index.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/operations-troubleshooting-medv2.md b/mdop/medv-v1/operations-troubleshooting-medv2.md new file mode 100644 index 0000000000..3e5dcc5454 --- /dev/null +++ b/mdop/medv-v1/operations-troubleshooting-medv2.md @@ -0,0 +1,132 @@ +--- +title: Operations Troubleshooting +description: Operations Troubleshooting +ms.assetid: 948d7869-accd-44da-974f-93409234dee7 +author: MaggiePucciEvans +--- + +# Operations Troubleshooting + + +This topic includes information that you can use to help troubleshoot general operational issues in Microsoft Enterprise Desktop Virtualization (MED-V) 2.0. + +## Troubleshooting Issues in MED-V Operations + + +The following are some issues end users might encounter when they run MED-V and solutions to help troubleshoot these issues: + +**Documentation Redirection Fails**. This issue typically occurs when an end user’s My Documents folder points to a network location. Windows does not support creating a share from another shared folder. When a drive or folder is redirected to the guest, RDP\\Windows Virtual PC creates a share for that folder. Therefore, if the My Documents folder on the host is already pointing to a share, RDP\\Windows Virtual PC cannot create a share of a share. + +Another possible cause of this issue is that the credentials that are required to connect to the network resource might differ from the user’s domain credentials. MED-V might be detecting that documents are redirected on the host, send that information to the guest, and then try to reconnect the network resource. If the user’s credentials do not authenticate, MED-V might stop trying to authenticate. + +**Solution** + +Try one of the following to resolve this issue: + +- Set the user’s root directory inside Active Directory. The guest and host should then connect to the same network resource. + +- Instead of redirecting the My Documents folder to a UNC path, map it to a drive letter (on the host, map a drive that points to the network resource). The My Documents folder can then be set to use the drive letter instead of the UNC path. The guest will then redirect to that same mapped drive as expected. + +- Create a startup script in the guest that redirects the My Documents folder to the network resource and provides additional credentials as needed. + +**URL Redirection Fails**. A URL that you have specified for redirection from the host to the guest is not redirecting as intended or is returning an error message that indicates that the website does not exist. + +**Solution** + +This error can occur when there is a misspelling or incorrect use of characters, such as asterisk (\*), in the URL redirection information. Check the registry value for URL redirection and correct any mistakes. + +The registry key is called `RedirectUrls` and is typically located at: + +Computer\\HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\MEDV\\v2\\UserExperience + +**Icon in Taskbar Misleading**. By default, the icon that appears in an end user’s taskbar for published applications and redirected URLs is the icon for Windows Virtual PC. If an end user is not aware of this default behavior, they can become confused when looking at the taskbar to locate their application. + +**Solution** + +The only way to avoid this default behavior is to change the user settings for the taskbar properties as follows: + +1. Right-click the taskbar and then click **Properties**. + +2. In the **Taskbar and Start Menu Properties** dialog box, click the **Taskbar** tab. + +3. In the drop-down bar for the **Taskbar buttons** box, select **Never combine**. + +4. Click **OK**. + +The expected icons for published applications and redirected URLs are displayed. + +**Warning Issued if Second User Attempts Log on or if Virtual Machine is in Use**. A warning message is issued when a second user logs on to a MED-V workspace while a first user is still running MED-V. The warning is also issued if MED-V is started while the virtual machine is being used, for example, if the virtual machine was started through Windows Virtual PC on the **Start** menu. When the end user accepts the warning message, MED-V shuts down. + +**Solution** + +An end user must verify that all other users are logged off MED-V before they try to log on. This ensures that no other instance of MED-V is running and that Windows Virtual PC is not in control of the virtual machine. + +**Beeps Heard During First Time Setup**. Occasionally, beeps are heard while MED-V is running first time setup. This can be confusing to an end user. The beeps are originating from the virtual machine when it performs certain actions, such as shutting down. + +**Solution** + +You can stop the beep service by specifying the "net stop beep" command at the beginning of each virtual machine start sequence. Or you can disable the beep service by specifying the “sc config beep start= disabled" command. You can specify these commands either before you seal the image or as part of Sysprep. + +**Multiple Network Connections Created for MED-V Workspaces in BRIDGED Mode**. If first time setup is creating a MED-V workspace that is configured for NAT mode, it only creates a single network connection in Windows Virtual PC. However, if first time setup is creating a MED-V workspace that is configured for BRIDGED mode, it creates a separate network connection for each network adapter that is installed in the computer, because MED-V cannot determine which network adapter is active. This also ensures that roaming users always have a network adapter available for wired and wireless connections. + +**Solution** + +None. + +**MED-V Application is Unresponsive for Too Long when Closing**. In some instances, a MED-V application stops responding when it is trying to close. + +**Solution** + +You can specify the length of time that MED-V waits to close unresponsive applications by setting the WaitToKillAppTimeout registry key in the guest virtual machine. For more information, see [How To Increase Shutdown Time So That Processes Can Quit Properly in Windows XP](http://go.microsoft.com/fwlink/?LinkId=206819) (http://go.microsoft.com/fwlink/?LinkId=206819). + +**Renaming a Published Application Shortcut in the Guest Virtual Machine does not Change the Published Name in the Host**. When you publish an application by creating a shortcut and then rename the shortcut in the guest virtual machine, the original application name remains in the host **Start** menu. The program continues to run as expected, however the program will always retain the original name. + +**Solution** + +None. This is a known behavior of Windows Virtual PC. + +**Moving a Shortcut in the Guest Virtual Machine does not Update the Location on the Host Computer Start Menu**. MED-V application shortcuts that are published to the host computer **Start** menu are cataloged in the registry. If you move an application shortcut into a subfolder, the registry is not updated to reflect the change. + +**Solution** + +Follow these steps to change the location of a MED-V application shortcut: + +1. When MED-V is running, open up Windows Explorer on the MED-V guest virtual machine. + +2. Browse to the "%ALLUSERSPROFILE%\\Start Menu\\Programs" directory. + +3. Move the application shortcuts out of the startmenu or programs folders. + +4. After about 30 seconds, validate that the shortcuts are removed from the host computer **Start** menu. + +5. Move the application shortcuts back in to the new program folders under the Start Menu\\Programs directory. + +6. After about 30 seconds, validate that the shortcuts are updated in the host computer **Start** Menu. + +**Published Applications can Time Out after Sitting Idle**. In some cases, published applications will time out if they have sat idle for some time. This situation only occurs if IPsec is enabled and the MED-V workspace is configured for NAT mode. This situation does not occur if running in BRIDGED mode. + +**Solution** + +Disable IPsec when you are running the MED-V workspace in NAT mode. + +**Pinning a Published Application to the Taskbar Bypasses MED-V**. If an end user pins a published application to the taskbar and then closes the application, MED-V is bypassed the next time that the application is opened from the taskbar icon. Instead, the application opens directly in a VMSAL window. + +**Solution** + +Do not pin the applications published in MED-V to the taskbar. + +## Related topics + + +[Security Best Practices for MED-V Operations](security-best-practices-for-med-v-operations.md) + +[Deployment Troubleshooting](deployment-troubleshooting.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/overview-of-med-vmedv2.md b/mdop/medv-v1/overview-of-med-vmedv2.md new file mode 100644 index 0000000000..35135e34ba --- /dev/null +++ b/mdop/medv-v1/overview-of-med-vmedv2.md @@ -0,0 +1,38 @@ +--- +title: Overview of MED-V +description: Overview of MED-V +ms.assetid: 393daa9b-2d76-43e1-861a-9d8c00f68cf6 +author: MaggiePucciEvans +--- + +# Overview of MED-V + + +Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 enables the deployment and management of Windows Virtual PC images throughout an enterprise. By providing large-scale deployments of desktops running Windows XP Professional SP3 that are hosted through Windows Virtual PC, MED-V lets businesses upgrade to Windows 7, even though some of their applications might not yet be fully functional or supported. + +This guide helps you understand, deploy, and manage your MED-V environment. By using the information provided in this guide, you can plan for and prepare your MED-V deployment, learn how to monitor and manage MED-V workspaces, and understand how to use MED-V to benefit your IT organization. + +## Key Scenarios for Using MED-V + + +Incompatibility of legacy applications together with new versions of Windows can often delay enterprise upgrades to the latest version of Windows. Testing and migrating applications takes time, and users cannot take advantage of the new capabilities and enhancements offered by the newest operating system. + +By delivering applications in a Windows Virtual PC that is running Windows XP SP3, MED-V removes the barriers to operating system upgrades and lets administrators complete testing and address incompatible applications after the upgrade. + +From the user's perspective, these applications can be accessed from the standard desktop **Start** menu and appear side-by-side with native applications, so there is minimal change to the user experience. + +## Related topics + + +[Planning for Application Operating System Compatibility](planning-for-application-operating-system-compatibility.md) + +[MED-V 2.0 Supported Configurations](med-v-20-supported-configurations.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/planning-for-application-operating-system-compatibility.md b/mdop/medv-v1/planning-for-application-operating-system-compatibility.md new file mode 100644 index 0000000000..d10b79aba5 --- /dev/null +++ b/mdop/medv-v1/planning-for-application-operating-system-compatibility.md @@ -0,0 +1,110 @@ +--- +title: Planning for Application Operating System Compatibility +description: Planning for Application Operating System Compatibility +ms.assetid: cdb0a7f0-9da4-4562-8277-12972eb0fea8 +author: MaggiePucciEvans +--- + +# Planning for Application Operating System Compatibility + + +This topic helps determine how to resolve application operating system compatibility issues, and discusses how Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 works as a solution for your organization. + +This topic discusses the business requirements for MED-V and compares MED-V to Windows XP Mode and Microsoft Application Virtualization (App-V): + +- [Business Requirements for MED-V](#bkmk-whenmedv) + +- [Benefits of MED-V versus Windows XP Mode](#bkmk-medvvsxp) + +- [Benefits of MED-V versus App-V](#bkmk-medvvsappv) + +## Business Requirements for MED-V + + +When your company’s IT department is determining whether to upgrade to Windows 7, it must pay attention to its line-of-business applications and web-based line-of-business applications to make certain that these can run on the new operating system. Often, these applications and URLs were created to work specifically with an older version of Windows or Internet Explorer, and problems can occur when trying to use them in the new operating system. Microsoft offers many different methods for handling the various compatibility issues that can occur when you upgrade, such as the Application Compatibility Toolkit (ACT) and the Windows 7 Program Compatibility Assistant. But even after all applications have been tested for compatibility and fixes have been determined, some applications still do not work correctly on Windows 7 or are too costly to resolve. + +By using MED-V, you can run these legacy applications through a Windows Virtual PC environment that is running Windows XP. Because you no longer have to test and validate these problem applications on the new operating system before upgrading, your migration to Windows 7 is much smoother and quicker. + +### Using MED-V Checklist + +Consider MED-V if any of the following scenarios apply to you: + +- You are a large organization (for example, 500 users and more), have an Enterprise Agreement with Microsoft, and plan to upgrade to Windows 7. + +- You have tested your line-of-business applications and have found some that are incompatible with Windows 7. + +- You have resolved the compatibility issues for some of these problem applications by upgrading the application or by using a Microsoft-provided shim, such as the Application Compatibility Toolkit (ACT), but compatibility issues remain for some applications. + +- You have considered App-V as an option for delivering the incompatible applications and have concluded that even after you implement App-V, you still have application operating system compatibility issues that you must address. + +- You have considered Windows XP Mode as a solution and have determined that it is not an efficient option because: + + - You want to be able to deploy virtual images that contain the problem applications to all end users at the same time, instead of individually, and have the virtual images automatically joined to the domain. + + - You have decided it is much more cost effective to manage these legacy applications (that are delivered virtually) and control the Windows Virtual PC settings from a centralized location instead of on each end user’s desktop. + + - You want to be able to update and support the virtual machines in scale instead of per desktop. + + - You want the ability to redirect URLs that run better on an older version of Internet Explorer to the virtual machines and to easily manage URL redirection later. + +- You have determined that it would be more cost effective and helpful to upgrade to Windows 7 as soon as possible and have decided to postpone resolving your remaining application compatibility issues until a later date, knowing that you have a solution available in MED-V. + +## Benefits of MED-V versus Windows XP Mode + + +Windows Virtual PC for Windows 7 lets you run different versions of an operating system at the same time on a single device and is included in Windows 7 Professional Edition and higher. + +Windows XP Mode functionality takes advantage of Windows Virtual PC by providing a preconfigured Windows XP image that lets you create a virtual Windows XP environment. In this virtual environment, you can manually install applications that are incompatible with Windows 7 and that run seamlessly from your desktop through Windows Virtual PC. + +**By using Windows XP Mode, you can do the following:** + +- Run applications that are compatible with Windows XP inside a virtual machine that runs in Windows Virtual PC. + +- Publish these applications to the host’s desktop or Program menu. + +When you want to deliver these virtual machines on a large scale as part of an enterprise migration to Windows 7, you must be able to deploy the virtual machines quickly, provision, and customize them efficiently, control their settings, and support them easily. + +MED-V builds upon Windows XP Mode to deliver enterprise-wide application compatibility. Whereas Windows XP mode is limited to providing virtual application functionality to individuals and small businesses, MED-V allows for large-scale deployments of preconfigured Windows XP images throughout your corporate network. It gives you an enterprise-ready management solution for the configuration, deployment, and maintenance of these virtual MED-V workspaces. MED-V also gives enterprise administrators a set of policies to control image use. This includes which users will have access to which specific applications within these images. + +**By using MED-V, you can do the following:** + +- Upgrade to your new operating system without having to test and resolve every incompatible application and URL. + +- Deploy virtual Windows XP images that are automatically domain-joined and customized per user. + +- Provision applications and URL redirection information to users. + +- Control the Windows Virtual PC settings. + +- Maintain and support endpoints through monitoring and troubleshooting. + +- Ensure that guest computers are patched, even if in a suspended state. + +- Automate per-user virtual machine creation and sysprep initialization. + +- Easily diagnose issues on the host and guest computers. + +- Seamlessly manage guest computers that are connected through Windows Virtual PC NAT mode. + +## Benefits of MED-V versus App-V + + +MED-V and App-V are two very different technologies that can easily work together to solve your application operating system compatibility issues. By using App-V, you create an individualized package for each application, each of which is then kept separate from the others. Each virtual application can then be immediately delivered to the end user, which is very useful for a Windows 7 deployment strategy. + +MED-V does not handle applications individually. Instead, it creates an additional instance of Windows XP on the same desktop that is running Windows 7. You can install as many applications as necessary into this virtual image and manage the image just as you would any other desktop in your organization. + +In addition, you can use MED-V together with App-V so that virtual applications that are sequenced through App-V are installed, published, and managed by using MED-V. + +## Related topics + + +[Define and Plan your MED-V Deployment](define-and-plan-your-med-v-deployment.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/planning-for-med-v.md b/mdop/medv-v1/planning-for-med-v.md new file mode 100644 index 0000000000..39246010e0 --- /dev/null +++ b/mdop/medv-v1/planning-for-med-v.md @@ -0,0 +1,37 @@ +--- +title: Planning for MED-V +description: Planning for MED-V +ms.assetid: 8124b765-6930-4607-8bd9-93068403c7a2 +author: MaggiePucciEvans +--- + +# Planning for MED-V + + +The topics in this section help you plan and design your Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 deployment. + +## In This Section + + +[End-to-End Planning Scenario for MED-V 2.0](end-to-end-planning-scenario-for-med-v-20.md) +Provides planning guidance for end-to-end deployment scenarios. + +[Define and Plan your MED-V Deployment](define-and-plan-your-med-v-deployment.md) +Describes how to define the project scope by defining the end users, determining the MED-V images to be managed, and determining the organization’s service level expectations. + +[MED-V 2.0 Best Practices](med-v-20-best-practices.md) +Provides guidance for planning your deployment following MED-V 2.0 best practices. + +## Related topics + + +[Microsoft Enterprise Desktop Virtualization 2.0](index.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/prepare-a-med-v-image.md b/mdop/medv-v1/prepare-a-med-v-image.md new file mode 100644 index 0000000000..75c84ae39d --- /dev/null +++ b/mdop/medv-v1/prepare-a-med-v-image.md @@ -0,0 +1,39 @@ +--- +title: Prepare a MED-V Image +description: Prepare a MED-V Image +ms.assetid: 1bc757e5-8aef-4163-8542-1bdccc028961 +author: MaggiePucciEvans +--- + +# Prepare a MED-V Image + + +To deploy a Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 image to multiple computers, you must first prepare the image for deployment. + +This section provides information about the steps that are required to prepare a MED-V image for deployment. + +## In This Section + + +[Creating a Windows Virtual PC Image for MED-V](creating-a-windows-virtual-pc-image-for-med-v.md) +Describes how to create and configure a Windows Virtual PC image for MED-V. This includes installing Windows XP on the image with the required updates and integration components. + +[Installing Applications on a Windows Virtual PC Image](installing-applications-on-a-windows-virtual-pc-image.md) +Describes the process of installing applications on your MED-V image. + +[Configuring a Windows Virtual PC Image for MED-V](configuring-a-windows-virtual-pc-image-for-med-v.md) +Describes how to configure and package a Windows Virtual PC image for MED-V by using Sysprep. + +## Related topics + + +[Operations for MED-V](operations-for-med-v.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/prepare-the-deployment-environment-for-med-v.md b/mdop/medv-v1/prepare-the-deployment-environment-for-med-v.md new file mode 100644 index 0000000000..fe926b5346 --- /dev/null +++ b/mdop/medv-v1/prepare-the-deployment-environment-for-med-v.md @@ -0,0 +1,36 @@ +--- +title: Prepare the Deployment Environment for MED-V +description: Prepare the Deployment Environment for MED-V +ms.assetid: d15ea370-7fdb-4852-a1ba-730ec7568e3e +author: MaggiePucciEvans +--- + +# Prepare the Deployment Environment for MED-V + + +This section provides information about preparing your Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 deployment environment. + +## In This Section + + +[Configure Environment Prerequisites](configure-environment-prerequisites.md) +Describes the prerequisites that are required as part of the MED-V 2.0 environment. + +[Configure Installation Prerequisites](configure-installation-prerequisites.md) +Describes the prerequisites that are required before you install MED-V 2.0. + +## Related topics + + +[Example MED-V System Installation Checklist](example-med-v-system-installation-checklist.md) + +[Deploy the MED-V Components](deploy-the-med-v-components.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/restarting-and-resetting-a-med-v-workspace.md b/mdop/medv-v1/restarting-and-resetting-a-med-v-workspace.md new file mode 100644 index 0000000000..9a68f55c22 --- /dev/null +++ b/mdop/medv-v1/restarting-and-resetting-a-med-v-workspace.md @@ -0,0 +1,50 @@ +--- +title: Restarting and Resetting a MED-V Workspace +description: Restarting and Resetting a MED-V Workspace +ms.assetid: a959cdb3-a727-47c7-967e-e58f224e74de +author: MaggiePucciEvans +--- + +# Restarting and Resetting a MED-V Workspace + + +During troubleshooting, you may sometimes find it necessary to restart or reset the MED-V workspace. Restarting the MED-V workspace is basically the same as restarting a physical computer. Resetting the MED-V workspace reruns first time setup and deletes all data that is stored in the virtual machine. Because all stored data is deleted, you typically should only reset the MED-V workspace to resolve the most serious troubleshooting issues, or to restore a previously working MED-V workspace back to a working state. + +For information about how to open the MED-V Administration Toolkit, see [Troubleshooting MED-V by Using the Administration Toolkit](troubleshooting-med-v-by-using-the-administration-toolkit.md). + +**Restarting a MED-V Workspace** + +1. On the **MED-V Administration Toolkit** window, click **Restart MED-V Workspace**. A dialog window opens in which you must confirm that you want to restart the MED-V workspace. + +2. Click **Restart**. + + Any published applications that are running or redirected web sites that are open will be closed when the MED-V workspace restarts. + +**Resetting a MED-V Workspace** + +1. On the **MED-V Administration Toolkit** window, click **Reset MED-V Workspace**. A dialog window opens in which you must confirm that you want to reset the MED-V workspace. + + **Warning**   + Resetting the MED-V workspace causes first time setup to run again, and thus reloads the original virtual hard disk. All data that is stored in the MED-V workspace since first time setup was originally run will be deleted. + +   + +2. Click **Reset**. + + Any published applications that are running or redirected web sites that are open will be closed when the MED-V workspace resets. + +## Related topics + + +[Viewing and Configuring MED-V Logs](viewing-and-configuring-med-v-logs.md) + +[Viewing MED-V Workspace Configurations](viewing-med-v-workspace-configurations.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/security-and-protection-for-med-v.md b/mdop/medv-v1/security-and-protection-for-med-v.md new file mode 100644 index 0000000000..edb9a7939d --- /dev/null +++ b/mdop/medv-v1/security-and-protection-for-med-v.md @@ -0,0 +1,34 @@ +--- +title: Security and Protection for MED-V +description: Security and Protection for MED-V +ms.assetid: 5db66d56-eb65-4bff-a9e4-3d52de4256bd +author: MaggiePucciEvans +--- + +# Security and Protection for MED-V + + +The following section contains best practices that we recommend for running Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 in a secure configuration. + +## In This Section + + +[Security Best Practices for MED-V Operations](security-best-practices-for-med-v-operations.md) +Describes best practices to follow to help maintain security when preparing, building, testing, deploying, and managing MED-V workspaces. + +[Authentication of MED-V End Users](authentication-of-med-v-end-users.md) +Describes best practices to follow to help maintain security when verifying the identity of MED-V end users. + +## Related topics + + +[Microsoft Enterprise Desktop Virtualization 2.0](index.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/security-best-practices-for-med-v-operations.md b/mdop/medv-v1/security-best-practices-for-med-v-operations.md new file mode 100644 index 0000000000..545d74720a --- /dev/null +++ b/mdop/medv-v1/security-best-practices-for-med-v-operations.md @@ -0,0 +1,51 @@ +--- +title: Security Best Practices for MED-V Operations +description: Security Best Practices for MED-V Operations +ms.assetid: 231e2b9a-8b49-42fe-93b5-2ef12fe17bac +author: MaggiePucciEvans +--- + +# Security Best Practices for MED-V Operations + + +As an authorized administrator, you are responsible to protect the information of the users and maintain security of your organization during and after the deployment of MED-V workspaces. In particular, consider the following issues. + +**Customizing Internet Explorer in the MED-V workspace**. Earlier versions of the Windows operating system and of Internet Explorer are not as secure as current versions. Therefore, Internet Explorer in the MED-V workspace is configured to prevent browsing and other activities that can pose security risks. In addition, the Internet security zone setting for Internet Explorer in the MED-V workspace is set to the highest level. By default, both of these configurations are set in the MED-V Workspace Packager when you create your MED-V workspace package. + +By using Internet Explorer Administration Kit (IEAK) or by changing the defaults in the MED-V Workspace Packager, you can customize Internet Explorer in the MED-V workspace. However, realize that if you customize Internet Explorer in the MED-V workspace in such a way as to make it less secure, you can expose your organization to those security risks that are present in older versions of Internet Explorer. + +From a security perspective, best practices for managing Internet Explorer in the MED-V workspace are as follows: + +- When creating your MED-V workspace package, leave the defaults set so that Internet Explorer in the MED-V workspace is configured to prevent browsing and other activities that can pose security risks. + +- When creating your MED-V workspace package, leave the defaults set so that the security setting for the Internet security zone remains at the highest level. + +- Configure your enterprise proxy or Internet Explorer Content Advisor to block domains that are outside your company’s intranet. + +**Configuring a MED-V workspace for all users on a shared computer.** When configuring a MED-V workspace so that it can be accessed by all users on a shared computer, realize that the guest virtual machine (VHD) is put in a location that gives Read and Write access to all users on that system. + +**Configuring a proxy account for domain joining.** When configuring a proxy account for joining virtual machines to the domain, you must know that it is possible for an end user to obtain the proxy account credentials. Thus, necessary precautions must be taken, such as limiting account user rights, to prevent an end user from using the credentials for causing harm. + +**Sysprep Configuration.** Although the Sysprep.inf file is encrypted by default, its contents can be decrypted and read by any determined end user who can successfully log on to the virtual machine. This raises security concerns because the Sysprep.inf file can contain credentials in addition to a Windows product key. + +You can lessen this risk by setting up a limited account for joining virtual machines to the domain and specifying the credentials for that account when configuring Sysprep. Alternately, you can also configure Sysprep and first time setup to run in **Attended** mode and require end users to provide their credentials for joining the virtual machine to the domain. + +A MED-V best practice is to specify that FtsCompletion.exe is run under an account that gives the end user rights to connect to the guest through the Remote Desktop Connection (RDC) Client. + +**End-user authentication.** Enabling the caching of end-user credentials provides the best user experience of MED-V, but creates the potential that someone could gain access to the end user’s credentials. The only way to lessen this risk is by specifying on the **MED-V Workspace Packager** that end-user credentials are not stored. For more information about authentication of end users, see [Authentication of MED-V End Users](authentication-of-med-v-end-users.md). + +## Related topics + + +[Operations Troubleshooting](operations-troubleshooting-medv2.md) + +[Microsoft Enterprise Desktop Virtualization 2.0](index.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/technical-reference-for-med-v.md b/mdop/medv-v1/technical-reference-for-med-v.md new file mode 100644 index 0000000000..8cea19ac36 --- /dev/null +++ b/mdop/medv-v1/technical-reference-for-med-v.md @@ -0,0 +1,54 @@ +--- +title: Technical Reference for MED-V +description: Technical Reference for MED-V +ms.assetid: 52aa15ae-6ca8-4494-8660-313c7b723406 +author: MaggiePucciEvans +--- + +# Technical Reference for MED-V + + +The technical reference information we provide here includes example checklists for planning, deployment, and operations for Microsoft Enterprise Desktop Virtualization (MED-V) 2.0. + +## In This Section + + +[Command-Line Options for MED-V Installation Files](command-line-options-for-med-v-installation-files.md) +Provides a list and description of the options that you can specify when you install or uninstall MED-V at the command prompt. + +[Compacting the MED-V Virtual Hard Disk](compacting-the-med-v-virtual-hard-disk.md) +Describes the steps to follow to compact your virtual hard disk before you configure your Windows XP image for use with MED-V. + +[MED-V Event Log Messages](med-v-event-log-messages.md) +Describes how to use the event logs in MED-V to troubleshoot deployment and operations issues. + +[Updating MED-V 2.0](updating-med-v-20.md) +Provides information about how to upgrade your MED-V installation. + +[Windows Virtual PC Application Exclude List](windows-virtual-pc-application-exclude-list.md) +Describes how to specify certain installed applications that you do not want published to the host computer. + +[MED-V 2 Configuration Cmdlets](http://go.microsoft.com/fwlink/?LinkId=213301) +Provides information about cmdlets you can use to perform various MED-V configuration tasks from the command line. + +[MED-V 2 Workspace Cmdlets](http://go.microsoft.com/fwlink/?LinkId=213302) +Provides information about cmdlets you can use to perform various MED-V workspace configuration tasks from the command line. + +[Example MED-V Checklists](example-med-v-checklists.md) +Provides several checklist examples that you can reference when planning, deploying, or managing MED-V. + +## Related topics + + +[Microsoft Enterprise Desktop Virtualization 2.0](index.md) + +[Security and Protection for MED-V](security-and-protection-for-med-v.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/test-and-deploy-the-med-v-workspace-package.md b/mdop/medv-v1/test-and-deploy-the-med-v-workspace-package.md new file mode 100644 index 0000000000..0f7121bc91 --- /dev/null +++ b/mdop/medv-v1/test-and-deploy-the-med-v-workspace-package.md @@ -0,0 +1,29 @@ +--- +title: Test And Deploy the MED-V Workspace Package +description: Test And Deploy the MED-V Workspace Package +ms.assetid: 0238dea7-a08c-4859-b8b1-2b52bc63fda6 +author: MaggiePucciEvans +--- + +# Test And Deploy the MED-V Workspace Package + + +This section provides information and instructions for testing and deploying your Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 image. + +## In This Section + + +[Testing the MED-V Workspace Package](testing-the-med-v-workspace-package.md) +Provides instructions and guidance for testing the MED-V workspace installer package. + +[Deploying the MED-V Workspace Package](deploying-the-med-v-workspace-package.md) +Provides general information about how to deploy MED-V workspaces. + +  + +  + + + + + diff --git a/mdop/medv-v1/testing-the-med-v-workspace-package.md b/mdop/medv-v1/testing-the-med-v-workspace-package.md new file mode 100644 index 0000000000..14335ff638 --- /dev/null +++ b/mdop/medv-v1/testing-the-med-v-workspace-package.md @@ -0,0 +1,35 @@ +--- +title: Testing the MED-V Workspace Package +description: Testing the MED-V Workspace Package +ms.assetid: 83edcb6e-9615-4d18-96b8-f085a647294e +author: MaggiePucciEvans +--- + +# Testing the MED-V Workspace Package + + +After you have created your MED-V workspace deployment package, you can test the package locally before deploying it throughout your enterprise. The topics in this section provide some steps and instructions to help you test your MED-V workspace deployment package. + +## In This Section + + +[How to Create a Test Environment](how-to-create-a-test-environment.md) +Provides information about how to create a test environment, either manually or by using an electronic software distribution (ESD) system. + +[How to Verify First Time Setup Settings](how-to-verify-first-time-setup-settings.md) +Provides information and guidance for testing your first time setup settings. + +[How to Test URL Redirection](how-to-test-url-redirection.md) +Provides information and guidance for testing your URL redirection settings. + +[How to Test Application Publishing](how-to-test-application-publishing.md) +Provides information and guidance for testing application publishing. + +  + +  + + + + + diff --git a/mdop/medv-v1/troubleshooting-med-v-by-using-the-administration-toolkit.md b/mdop/medv-v1/troubleshooting-med-v-by-using-the-administration-toolkit.md new file mode 100644 index 0000000000..b1a02ecaa7 --- /dev/null +++ b/mdop/medv-v1/troubleshooting-med-v-by-using-the-administration-toolkit.md @@ -0,0 +1,52 @@ +--- +title: Troubleshooting MED-V by Using the Administration Toolkit +description: Troubleshooting MED-V by Using the Administration Toolkit +ms.assetid: 6c096a1c-b9ce-4ec7-8dfd-5286e3b9a617 +author: MaggiePucciEvans +--- + +# Troubleshooting MED-V by Using the Administration Toolkit + + +Use the MED-V Administration Toolkit to troubleshoot certain problems in a MED-V workspace. The MED-V Administration Toolkit lets you access and configure event logs, restart or reset the MED-V workspace, and view the published applications and redirected web addresses in the MED-V workspace. You can also use the MED-V Administration Toolkit to open the MED-V workspace virtual machine in full-screen mode. + +## To Open the MED-V Administration Toolkit + + +Perform the following steps to open the MED-V Administration Toolkit: + +1. On the host computer that contains the MED-V workspace you are troubleshooting, open a Command Prompt window. + +2. Browse to %systemdrive%\\Program Files\\Microsoft Enterprise Desktop Virtualization. + +3. At the command prompt, type **MedvHost /toolkit**. + +After the MED-V Administration Toolkit opens, you can use the toolkit to help resolve issues in the MED-V workspace found during troubleshooting. + +## In this Section + + +[Viewing and Configuring MED-V Logs](viewing-and-configuring-med-v-logs.md) +Describes how to use the MED-V Administration Toolkit to collect and manage MED-V event logs in the host computer and the guest virtual machine. + +[Restarting and Resetting a MED-V Workspace](restarting-and-resetting-a-med-v-workspace.md) +Describes how to restart and reset MED-V workspaces by using the MED-V Administration Toolkit. + +[Viewing MED-V Workspace Configurations](viewing-med-v-workspace-configurations.md) +Describes how to use the MED-V Administration Toolkit to view the published applications and redirected web addresses in a MED-V workspace and how to open the MED-V workspace virtual machine in full-screen mode. + +## Related topics + + +[MED-V Event Log Messages](med-v-event-log-messages.md) + +[Troubleshooting MED-V](troubleshooting-med-vmedv2.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/troubleshooting-med-vmedv2.md b/mdop/medv-v1/troubleshooting-med-vmedv2.md new file mode 100644 index 0000000000..c7d2499973 --- /dev/null +++ b/mdop/medv-v1/troubleshooting-med-vmedv2.md @@ -0,0 +1,37 @@ +--- +title: Troubleshooting MED-V +description: Troubleshooting MED-V +ms.assetid: 4502d62b-a7db-4f83-81e2-23fd8b0820e1 +author: MaggiePucciEvans +--- + +# Troubleshooting MED-V + + +You can use the information provided here to help you troubleshoot issues in Microsoft Enterprise Desktop Virtualization (MED-V) 2.0. + +## In This Section + + +[Deployment Troubleshooting](deployment-troubleshooting.md) +Describes how to troubleshoot deployment issues in your MED-V environment. + +[Operations Troubleshooting](operations-troubleshooting-medv2.md) +Describes how to troubleshoot common issues that can occur during the operation of MED-V. + +[Troubleshooting MED-V by Using the Administration Toolkit](troubleshooting-med-v-by-using-the-administration-toolkit.md) +Describes how to access and use the MED-V Administration Toolkit to troubleshoot deployment and operations issues. + +## Related topics + + +[Microsoft Enterprise Desktop Virtualization 2.0](index.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/updating-med-v-20.md b/mdop/medv-v1/updating-med-v-20.md new file mode 100644 index 0000000000..68b43ac2fc --- /dev/null +++ b/mdop/medv-v1/updating-med-v-20.md @@ -0,0 +1,32 @@ +--- +title: Updating MED-V 2.0 +description: Updating MED-V 2.0 +ms.assetid: beea2f54-42d7-4a17-98e0-d243a8562265 +author: MaggiePucciEvans +--- + +# Updating MED-V 2.0 + + +Help secure your system by applying the appropriate security updates for Microsoft Enterprise Desktop Virtualization (MED-V) 2.0. + +## Updating MED-V + + +You can update MED-V interactively, by the end user, or silently by using an electronic software distribution system. Installation of the MED-V Host Agent upgrades the MED-V Host Agent and then updates the MED-V workspace if required. The MED-V Host Agent and Guest Agent keep in sync. If applications are running from the MED-V workspace while the MED-V Host Agent is being updated, a restart of the host computer is required to complete the update. If no applications are running, MED-V is restarted automatically and the upgrade is completed without a restart of the host computer. + +If you are updating MED-V by using an electronic software distribution system, you can control the restart behavior. To do this, suppress the restart by typing **REBOOT=”ReallySuppress”** at the command prompt when installing MED-V\_HostAgent\_Setup.exe. Then, configure the electronic software distribution system to capture the 3010 return code (which signals that a restart is required) and perform the set restart behavior. + +## Related topics + + +[Technical Reference for MED-V](technical-reference-for-med-v.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/viewing-and-configuring-med-v-logs.md b/mdop/medv-v1/viewing-and-configuring-med-v-logs.md new file mode 100644 index 0000000000..42c574c4cb --- /dev/null +++ b/mdop/medv-v1/viewing-and-configuring-med-v-logs.md @@ -0,0 +1,61 @@ +--- +title: Viewing and Configuring MED-V Logs +description: Viewing and Configuring MED-V Logs +ms.assetid: a15537ce-981d-4f55-9c3c-e7fbf94b8fe5 +author: MaggiePucciEvans +--- + +# Viewing and Configuring MED-V Logs + + +When you are troubleshooting MED-V issues and problems, you may find it helpful or necessary to access the MED-V event logs. You can open Event Viewer for the host computer and the guest virtual machine by using the MED-V Administration Toolkit. You can also use the MED-V Administration Toolkit to set the logging level at which the MED-V event logs report MED-V events. + +For information about how to open the MED-V Administration Toolkit, see [Troubleshooting MED-V by Using the Administration Toolkit](troubleshooting-med-v-by-using-the-administration-toolkit.md). + +## Viewing MED-V Event Logs + + +On the **MED-V Administration Toolkit** window, click **Host Events** to open the event viewer for the host computer. Or, click **Guest Events** to open Event Viewer for the guest virtual machine. + +Event Viewer opens and displays the corresponding event logs that you can use to troubleshoot the issues that you might encounter when you deploy or manage MED-V. By default, only errors and warnings are displayed. For more information about specific event IDs and messages, see [MED-V Event Log Messages](med-v-event-log-messages.md). + +**Note**   +End users can only save event log files in the guest if they have administrative permissions. + +  + +### To manually open the Event Viewer in the host computer + +1. Click **Start**, click **Control Panel**, and then click **Administrative Tools**. + +2. Double-click **Event Viewer**, and then click **Applications and Services Logs**. + +3. Double-click **MEDV**. + +## Configuring MED-V Event Logs + + +You can specify the MED-V event logging level by selecting the corresponding option button on the MED-V Administration Toolkit. You can decide whether event logging includes errors only, errors and warnings, or errors, warnings and informational messages. The event logging level specified is set for both the host computer and the guest virtual machine. + +You can also specify the event logging level by editing the EventLogLevel registry value. For more information, see [Managing MED-V Workspace Configuration Settings](managing-med-v-workspace-configuration-settings.md). + +**Note**   +The level you specify on the **MED-V Administration Toolkit** window applies to future MED-V event logging. If you set the level to capture all errors, warnings, and informational messages, then the event logs fill more quickly and older events are removed. + +  + +## Related topics + + +[Restarting and Resetting a MED-V Workspace](restarting-and-resetting-a-med-v-workspace.md) + +[Viewing MED-V Workspace Configurations](viewing-med-v-workspace-configurations.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/viewing-med-v-workspace-configurations.md b/mdop/medv-v1/viewing-med-v-workspace-configurations.md new file mode 100644 index 0000000000..cc13b8a31f --- /dev/null +++ b/mdop/medv-v1/viewing-med-v-workspace-configurations.md @@ -0,0 +1,54 @@ +--- +title: Viewing MED-V Workspace Configurations +description: Viewing MED-V Workspace Configurations +ms.assetid: 5de6cf04-6beb-4ac9-ad52-26ac8c0c8ce6 +author: MaggiePucciEvans +--- + +# Viewing MED-V Workspace Configurations + + +When you are troubleshooting MED-V issues and problems, you can use the MED-V Administration Toolkit to view the published applications and redirected web addresses in the MED-V workspace. You can also use the MED-V Administration Toolkit to open the MED-V workspace in full-screen mode. + +For information about how to open the MED-V Administration Toolkit, see [Troubleshooting MED-V by Using the Administration Toolkit](troubleshooting-med-v-by-using-the-administration-toolkit.md). + +## Viewing MED-V Published Applications + + +On the **MED-V Administration Toolkit** window, click **View Published Applications**. + +The **MED-V Workspace Published Applications** window opens and displays a list of the applications that were published in the MED-V workspace. You can use this information to troubleshoot certain issues, such as determining whether an application was published as expected. + +For information about how to publish applications to the MED-V workspace, see [How to Publish and Unpublish an Application on the MED-V Workspace](how-to-publish-and-unpublish-an-application-on-the-med-v-workspace.md). + +## Viewing MED-V Redirected Web Addresses + + +On the **MED-V Administration Toolkit** window, click **View Redirected Web Addresses**. + +The **Web Addresses Redirected to the MED-V Workspace** window opens and displays a list of the redirected web addresses specified for the MED-V workspace. You can use this information to troubleshoot certain issues, such as determining whether a web address was specified correctly for redirection. + +For information about how to manage web addresses redirection in the MED-V workspace, see [How to Add or Remove URL Redirection Information in a Deployed MED-V Workspace](how-to-add-or-remove-url-redirection-information-in-a-deployed-med-v-workspace.md). + +## Opening the MED-V Workspace Virtual Machine + + +On the **MED-V Administration Toolkit** window, click **View MED-V Workspace Full Screen**. + +MED-V closes if it was running, and the MED-V workspace virtual machine opens in full-screen mode. You can use this full-screen window to easily access all the components of the virtual machine that might be helpful in troubleshooting, such as its hard disk and settings files. + +## Related topics + + +[Viewing and Configuring MED-V Logs](viewing-and-configuring-med-v-logs.md) + +[Restarting and Resetting a MED-V Workspace](restarting-and-resetting-a-med-v-workspace.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/whats-new-in-med-v-20.md b/mdop/medv-v1/whats-new-in-med-v-20.md new file mode 100644 index 0000000000..439342f3ec --- /dev/null +++ b/mdop/medv-v1/whats-new-in-med-v-20.md @@ -0,0 +1,87 @@ +--- +title: What's New in MED-V 2.0 +description: What's New in MED-V 2.0 +ms.assetid: 53b10bff-2b6f-463b-bdc2-5edc56526792 +author: MaggiePucciEvans +--- + +# What's New in MED-V 2.0 + + +Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 has evolved the application compatibility support for Windows 7 and removed functionality that is not required for this scenario. For example, features such as encryption of the MED-V workspace, the centralized MED-V server, and MED-V workspace trim transfer have been removed. + +## Changes in Standard Functionality + + +This section discusses the key areas where MED-V 2.0 functionality has changed. + +### MED-V Workspace Creation + +The virtual hard disk used for the MED-V workspace is now created in Windows Virtual PC. The methods that are used to create the MED-V workspace include installing Windows XP SP3, updating the operating system, and preparing it to be managed through software management infrastructure. + +The offline management and trim transfer functionality were removed, in addition to the proprietary MED-V workspace encryption and compression functionality. When you create a MED-V workspace, an administrator should prepare and configure appropriate applications and management tools in the image instead of using the virtual machine preparation tool that is provided in MED-V 1.0. + +Running Sysprep on the MED-V image is now required and validated during the packaging of the MED-V workspace. The MED-V Workspace Packager provides a graphical user interface (GUI) that guides the administrator through the packaging process. The console from MED-V 1.0 was removed together with the functionality of managing images, managing MED-V workspace profiles, and the requirement to stage and encrypt MED-V workspaces. + +### MED-V Workspace Deployment + +To deploy a MED-V workspace, an administrator is now able to take advantage of their electronic software distribution tools. The client-pull method available in MED-V 1.0 was removed and the MED-V workspace is now delivered by using methods outside MED-V. Administrators can treat MED-V workspaces as they would any other application package and can schedule deployments and installations of MED-V by using their existing tools and processes. MED-V installations can be deployed silently and can easily be managed inside an existing software distribution infrastructure. + +### MED-V Workspace Management + +The MED-V workspace in MED-V 2.0 is based on a Windows Virtual PC virtual hard disk. MED-V has extended the capabilities that Windows Virtual PC provides by improving the seamless experience without requiring encryption or special tools to access the MED-V workspace. + +After MED-V is deployed to a workstation, the MED-V workspace can be opened in full-screen mode by using Windows Virtual PC. This new functionality removed the requirement for policies that set a preference for seamless or full-screen modes and also removed the need to force full-screen for diagnostics and troubleshooting. + +Publishing applications to the MED-V workspace is no longer performed with profiles and by manually entering the path to applications. Instead, it occurs automatically as applications are installed on the guest. The central image repository that included versions of the images that were delivered through trim transfer is removed. Instead, MED-V enables administrators to manage the MED-V workspace as they would a physical computer, by letting applications and updates be distributed without the complexity of a dedicated MED-V infrastructure. + +## Changes in MED-V Features + + +Several key areas of MED-V 2.0 reflect improvements or additions to the following features. + +### MED-V Workspace Creation + +MED-V workspaces must be created by using Windows Virtual PC. Existing Virtual PC 2007 images must be migrated. The virtual machine Prep tool is not included in MED-V 2.0 and administrators should configure, update, and optimize their images according to the MED-V 2.0 Help file. Running Sysprep on the MED-V image is a required step and must be performed before packaging. + +### MED-V Workspace Packaging + +Windows PowerShell is the foundation of the MED-V Workspace Packager. This functionality replaces some former console abilities and functionality that managed centralized functions of MED-V. The MED-V Workspace Packager merely packages the virtual hard disk with the appropriate settings and image so that it can be easily deployed by administrators. Advanced features are provided by using Windows PowerShell. + +### MED-V Workspace Distribution + +Dedicated server infrastructure is no longer required for MED-V 2.0 and the client pull method to deploy MED-V workspaces was removed. MED-V workspaces are now deployed using your electronic software distribution infrastructure and can be stored on common shares that are used for other installation packages. + +### First Time Setup + +The first time setup process is now integrated with the standard imaging convention of Sysprep. The MED-V workspace first time setup process can dynamically apply settings specified in the MED-V Workspace Packager to the image as it begins Mini-Setup. The scripting tool in the console was removed and the first time setup process is now based on options that are configured in the MED-V Workspace Packager by the administrator. + +### Application Publishing + +Administrators can install applications on the MED-V image either before packaging, after the MED-V workspace is deployed, or by using a combination of both. MED-V no longer examines MED-V workspace policy to publish applications, but instead refers to what is actually installed on the guest. As applications are installed on the guest, they are automatically detected and published to the host **Start** menu and are ready to be started by the end user. + +### URL Redirection + +MED-V 2.0 provides seamless host-to-guest web address redirection based on the policies configured and managed by the administrator. After a URL is redirected to the guest browser, the default experience is to attempt to limit the user to that redirected site. This minimizes the browsing activities that a user can perform that are not intended by the administrator. Guest-to-host browser redirection was removed. + +### Troubleshooting + +MED-V now takes advantage of standard host-based processes for troubleshooting. Because the MED-V workspace is no longer encrypted, it can be opened in full-screen mode within the Windows Virtual PC console, where it can be viewed and worked with as a standard workstation. In addition, the logs are no longer encrypted locally and logged centrally. MED-V now makes extensive use of the local event logs, and the logging level of the output, from informational to debug levels, can be easily configured. Finally, a troubleshooting toolkit is now provided so administrators and helpdesk personnel can have a graphical, aggregated view of all the troubleshooting options, and they can effortlessly select the activities that most suit their needs. + +MED-V is no longer run as a system service. Instead, it is run as user-owned processes, and it only runs when a user is logged on. Functionality that was formerly provided by the system-owned service is now provided in the user-side processes. + +## Related topics + + +[Deployment of MED-V](deployment-of-med-v.md) + +[Operations for MED-V](operations-for-med-v.md) + +  + +  + + + + + diff --git a/mdop/medv-v1/windows-virtual-pc-application-exclude-list.md b/mdop/medv-v1/windows-virtual-pc-application-exclude-list.md new file mode 100644 index 0000000000..1e281ccc81 --- /dev/null +++ b/mdop/medv-v1/windows-virtual-pc-application-exclude-list.md @@ -0,0 +1,67 @@ +--- +title: Windows Virtual PC Application Exclude List +description: Windows Virtual PC Application Exclude List +ms.assetid: 7715f198-f5ed-421e-8740-0cec2ca4ece3 +author: MaggiePucciEvans +--- + +# Windows Virtual PC Application Exclude List + + +In some instances, you might not want applications that are installed in the MED-V workspace to be published to the host computer **Start** menu. You can unpublish these applications by following the instructions at [How to Publish and Unpublish an Application on the MED-V Workspace](how-to-publish-and-unpublish-an-application-on-the-med-v-workspace.md). However, if the program ever automatically updates, it might also be automatically republished. This causes you to have to unpublish the application again. + +Windows Virtual PC includes a feature known as the "Exclude List" that lets you specify certain installed applications that you do not want published to the host **Start** menu. The "Exclude List" is located in the guest registry in the HLKM\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Virtual Machine\\VPCVAppExcludeList key and lists those applications that are not published to the host **Start** menu. You can think of the “Exclude List” as permanently unpublishing the specified applications because any automatic updates to the applications that are listed will not cause them to be automatically republished. + +## Managing Applications by Using the Exclude List in Windows Virtual PC + + +**** + +1. Open the MED-V workspace in full screen. + + For information about opening the MED-V workspace in full-screen mode by using the MED-V Administration Toolkit, see [Viewing MED-V Workspace Configurations](viewing-med-v-workspace-configurations.md#bkmk-fullscreen). Or you can manually open it in full screen by clicking **Start**, click **All Programs**, click **Windows Virtual PC**, click **Windows Virtual PC**, and then double-click the MED-V workspace. + +2. In the MED-V workspace Windows Virtual PC window, open Registry Editor. + + Click **Start**, click **Run**, and then type regedit. Then click **OK**. + +3. In Registry Editor, locate the HKLM\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Virtual Machine\\VPCVAppExcludeList registry key. + +4. Create a new registry value for the installed application that you do not want published to the host computer **Start** menu. For example, if you want to unpublish the automatically published program Microsoft Silverlight, follow these steps: + + 1. With the VPCVAppExcludeList registry key highlighted, click **Edit**, click **New**, and then click **String Value**. + + 2. Enter the name for the new registry value. For example, for Microsoft Silverlight, you might enter sllauncher.exe. + + 3. Double-click the new registry value and enter the value data. + + The value data is the full path for the command that you want to unpublish. You can find the full path by right-clicking on the shortcut on the **Start** menu for the application that you do not want published and then clicking **Properties**. The full path is listed in the **Shortcut** tab under **Target**. + + For example, for the program Microsoft Silverlight, the full path might be "C:\\Program Files\\Microsoft Silverlight\\4.0.50917.0\\Silverlight.Configuration.exe." + + **Important**   + If applicable, remove the quotation marks from the full path when you enter it into the value data field. + +   + +5. Close Registry Editor and restart the MED-V workspace virtual machine. + + The application is still installed in the MED-V workspace but is now removed from the host computer **Start** menu. + +You can also republish an excluded application to the host **Start** menu by deleting the corresponding value from the VPCVAppExcludeList key. For example, to republish Microsoft Silverlight, right-click the registry value sllauncher.exe and select **Delete**. + +## Related topics + + +[Technical Reference for MED-V](technical-reference-for-med-v.md) + +[How to Publish and Unpublish an Application on the MED-V Workspace](how-to-publish-and-unpublish-an-application-on-the-med-v-workspace.md) + +  + +  + + + + +