mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 10:53:43 +00:00
New build 4/13/16
This commit is contained in:
Brian Lich
39
mdop/medv-v1/about-med-v-10-sp1.md
Normal file
39
mdop/medv-v1/about-med-v-10-sp1.md
Normal file
@ -0,0 +1,39 @@
|
|||||||
|
---
|
||||||
|
title: About MED-V 1.0 SP1
|
||||||
|
description: About MED-V 1.0 SP1
|
||||||
|
ms.assetid: 4c16e935-46c4-49c3-9e53-c60404d5da0c
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# About MED-V 1.0 SP1
|
||||||
|
|
||||||
|
|
||||||
|
Microsoft Enterprise Desktop Virtualization (MED-V) 1.0 Service Pack 1 (SP1) provides support for Windows 7 and Windows Server 2008 R2.
|
||||||
|
|
||||||
|
The topics in this section provide information relating specifically to MED-V 1.0 SP1.
|
||||||
|
|
||||||
|
## In This Section
|
||||||
|
|
||||||
|
|
||||||
|
<a href="" id="med-v-1-0-sp1-supported-configurations"></a>[MED-V 1.0 SP1 Supported Configurations](med-v-10-sp1-supported-configurationsmedv-10-sp1.md)
|
||||||
|
Delineates the supported configurations for MED-V 1.0 SP1.
|
||||||
|
|
||||||
|
<a href="" id="med-v-1-0-sp1-upgrade-checklist"></a>[MED-V 1.0 SP1 Upgrade Checklist](med-v-10-sp1-upgrade-checklistmedv-10-sp1.md)
|
||||||
|
Provides a step-by-step procedure for upgrading from MED-V 1.0 to MED-V 1.0 SP1.
|
||||||
|
|
||||||
|
<a href="" id="med-v-1-0-sp1-and-sp2-release-notes"></a>[MED-V 1.0 SP1 and SP2 Release Notes](med-v-10-sp1-and-sp2-release-notesmedv-10-sp1.md)
|
||||||
|
Provides known issues specific to MED-V 1.0 SP1.
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[MED-V 1.0 Release Notes](med-v-10-release-notesmedv-10.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
37
mdop/medv-v1/about-med-v-10.md
Normal file
37
mdop/medv-v1/about-med-v-10.md
Normal file
@ -0,0 +1,37 @@
|
|||||||
|
---
|
||||||
|
title: About MED-V 1.0
|
||||||
|
description: About MED-V 1.0
|
||||||
|
ms.assetid: 89651022-a2ba-4d8a-a3ff-68539ea7a235
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# About MED-V 1.0
|
||||||
|
|
||||||
|
|
||||||
|
## In This Section
|
||||||
|
|
||||||
|
|
||||||
|
This section provides information related specifically to MED-V 1.0 and includes the following topics:
|
||||||
|
|
||||||
|
<a href="" id="med-v-1-0-supported-configurations"></a>[MED-V 1.0 Supported Configurations](med-v-10-supported-configurationsmedv-10.md)
|
||||||
|
Delineates the supported configurations for MED-V 1.0.
|
||||||
|
|
||||||
|
<a href="" id="med-v-1-0-installation-checklist"></a>[MED-V 1.0 Installation Checklist](med-v-10-installation-checklist.md)
|
||||||
|
Provides a list of all the steps required for installing MED-V 1.0.
|
||||||
|
|
||||||
|
<a href="" id="med-v-1-0-release-notes"></a>[MED-V 1.0 Release Notes](med-v-10-release-notesmedv-10.md)
|
||||||
|
Provides a list of known issues with MED-V.
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[MED-V 1.0 SP1 and SP2 Release Notes](med-v-10-sp1-and-sp2-release-notesmedv-10-sp1.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,37 +0,0 @@
|
|||||||
---
|
|
||||||
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:
|
|
||||||
|
|
||||||
<a href="" id="what-s-new-in-med-v-2-0"></a>[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.
|
|
||||||
|
|
||||||
<a href="" id="med-v-2-0-supported-configurations"></a>[MED-V 2.0 Supported Configurations](med-v-20-supported-configurations.md)
|
|
||||||
Describes the supported configurations for MED-V 2.0.
|
|
||||||
|
|
||||||
<a href="" id="med-v-2-0-release-notes"></a>[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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
32
mdop/medv-v1/about-this-guidemedv.md
Normal file
32
mdop/medv-v1/about-this-guidemedv.md
Normal file
@ -0,0 +1,32 @@
|
|||||||
|
---
|
||||||
|
title: About This Guide
|
||||||
|
description: About This Guide
|
||||||
|
ms.assetid: 17d8f150-226e-45f8-87e3-f425a77243e4
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# About This Guide
|
||||||
|
|
||||||
|
|
||||||
|
This Planning, Deployment, and Operations guide for Microsoft Enterprise Desktop Virtualization (MED-V) provides background information about MED-V, installing MED-V, and how it works and explains how to correctly use the product. The guide includes the following:
|
||||||
|
|
||||||
|
- System requirements and supported platforms
|
||||||
|
|
||||||
|
- Environmental prerequisites and considerations
|
||||||
|
|
||||||
|
- Step-by-step instructions for installing MED-V server, management, and client
|
||||||
|
|
||||||
|
- Step-by-step instructions for configuring MED-V image, workspace, and policy
|
||||||
|
|
||||||
|
- Step-by-step instructions for deploying a MED-V workspace
|
||||||
|
|
||||||
|
- MED-V client operations
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,128 +0,0 @@
|
|||||||
---
|
|
||||||
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:
|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="33%" />
|
|
||||||
<col width="33%" />
|
|
||||||
<col width="33%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Value</th>
|
|
||||||
<th align="left">Configuration</th>
|
|
||||||
<th align="left">Result</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>DisablePasswordSaving</p></td>
|
|
||||||
<td align="left"><p><strong>Disabled</strong></p></td>
|
|
||||||
<td align="left"><p>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.</p>
|
|
||||||
<p></p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p></p></td>
|
|
||||||
<td align="left"><p></p></td>
|
|
||||||
<td align="left"><p>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.</p>
|
|
||||||
<div class="alert">
|
|
||||||
<strong>Important</strong>
|
|
||||||
<p>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.</p>
|
|
||||||
</div>
|
|
||||||
<div>
|
|
||||||
|
|
||||||
</div></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>DisablePasswordSaving</p></td>
|
|
||||||
<td align="left"><p><strong>Enabled</strong></p></td>
|
|
||||||
<td align="left"><div class="alert">
|
|
||||||
<strong>Note</strong>
|
|
||||||
<p>This configuration is more secure because it does not allow end user credentials to be cached.</p>
|
|
||||||
</div>
|
|
||||||
<div>
|
|
||||||
|
|
||||||
</div></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
122
mdop/medv-v1/client-installation-command-line-reference.md
Normal file
122
mdop/medv-v1/client-installation-command-line-reference.md
Normal file
@ -0,0 +1,122 @@
|
|||||||
|
---
|
||||||
|
title: Client Installation Command Line Reference
|
||||||
|
description: Client Installation Command Line Reference
|
||||||
|
ms.assetid: 122a593d-3314-4e9b-858a-08a25ed00c32
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# Client Installation Command Line Reference
|
||||||
|
|
||||||
|
|
||||||
|
**To install MED-V from the command line**
|
||||||
|
|
||||||
|
1. From the command line, run the MED-V .msi package followed by any of the optional parameters described in the following table.
|
||||||
|
|
||||||
|
2. The MED-V .msi package is called *MED-V\_x.msi*, where *x* is the version number.
|
||||||
|
|
||||||
|
For example, *MED-V\_1.0.65.msi*.
|
||||||
|
|
||||||
|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="33%" />
|
||||||
|
<col width="33%" />
|
||||||
|
<col width="33%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead>
|
||||||
|
<tr class="header">
|
||||||
|
<th align="left">Parameter</th>
|
||||||
|
<th align="left">Value</th>
|
||||||
|
<th align="left">Description</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>/quiet</p></td>
|
||||||
|
<td align="left"><p></p></td>
|
||||||
|
<td align="left"><p>Silent installation</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>/log <full path to log file></p></td>
|
||||||
|
<td align="left"><p>The full path to the log file.</p></td>
|
||||||
|
<td align="left"><p></p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>INSTALLDIR</p></td>
|
||||||
|
<td align="left"><p>The full path to the installation directory.</p></td>
|
||||||
|
<td align="left"><p></p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>VMSFOLDER</p></td>
|
||||||
|
<td align="left"><p>The full path to the virtual machine folder.</p></td>
|
||||||
|
<td align="left"><p></p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>INSTALL_ADMIN_TOOLS</p></td>
|
||||||
|
<td align="left"><p><strong>1,0</strong></p>
|
||||||
|
<p>Default: <strong>0</strong></p></td>
|
||||||
|
<td align="left"><p>Installs MED-V administration tools.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>START_AUTOMATICALLY</p></td>
|
||||||
|
<td align="left"><p><strong>1,0</strong></p>
|
||||||
|
<p>Default: <strong>0</strong></p></td>
|
||||||
|
<td align="left"><p>Automatically starts MED-V client every time the user logs on to Windows.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>SERVER_ADDRESS</p></td>
|
||||||
|
<td align="left"><p>host name or IP</p></td>
|
||||||
|
<td align="left"><p></p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>SERVER_PORT</p></td>
|
||||||
|
<td align="left"><p>port</p></td>
|
||||||
|
<td align="left"><p></p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>SERVER_SSL</p></td>
|
||||||
|
<td align="left"><p><strong>1,0</strong></p>
|
||||||
|
<p>for <strong>https</strong> or <strong>http</strong></p></td>
|
||||||
|
<td align="left"><p></p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>START_MEDV</p></td>
|
||||||
|
<td align="left"><p><strong>1,0</strong></p>
|
||||||
|
<p>Default: <strong>1</strong></p></td>
|
||||||
|
<td align="left"><p>Starts MED-V at the completion of the MED-V installation.</p>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>It is recommended to set START_MEDV=0 in case MED-V is installed by the system.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>DESKTOP_SHORTCUT</p></td>
|
||||||
|
<td align="left"><p><strong>1,0</strong></p>
|
||||||
|
<p>Default: <strong>1</strong></p></td>
|
||||||
|
<td align="left"><p>Creates a shortcut on the desktop, which starts MED-V client.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>MINIMAL_RAM_REQUIRED</p></td>
|
||||||
|
<td align="left"><p>RAM in MB</p></td>
|
||||||
|
<td align="left"><p>When installing MED-V, checks whether the computer has the minimum amount of RAM specified. If not, installation is aborted.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>SKIP_OS_CHECK</p></td>
|
||||||
|
<td align="left"><p><strong>1,0</strong></p></td>
|
||||||
|
<td align="left"><p>Omits the operating system validation.</p></td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,118 +0,0 @@
|
|||||||
---
|
|
||||||
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.
|
|
||||||
|
|
||||||
<table style="width:100%;">
|
|
||||||
<colgroup>
|
|
||||||
<col width="16%" />
|
|
||||||
<col width="16%" />
|
|
||||||
<col width="16%" />
|
|
||||||
<col width="16%" />
|
|
||||||
<col width="16%" />
|
|
||||||
<col width="16%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Installation File</th>
|
|
||||||
<th align="left">Argument</th>
|
|
||||||
<th align="left">Accepted Values</th>
|
|
||||||
<th align="left">Type</th>
|
|
||||||
<th align="left">Description</th>
|
|
||||||
<th align="left">Default</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Host Agent</p></td>
|
|
||||||
<td align="left"><p>MEDVDIR</p></td>
|
|
||||||
<td align="left"><p><install path></p></td>
|
|
||||||
<td align="left"><p>Installation</p></td>
|
|
||||||
<td align="left"><p>Change installed directory</p></td>
|
|
||||||
<td align="left"><p>Installation goes to Program Files\Microsoft Enterprise Desktop Virtualization.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>MED-V Workspace Packager</p></td>
|
|
||||||
<td align="left"><p>MEDVDIR</p></td>
|
|
||||||
<td align="left"><p><install path></p></td>
|
|
||||||
<td align="left"><p>Installation</p></td>
|
|
||||||
<td align="left"><p>Change installed directory</p></td>
|
|
||||||
<td align="left"><p>Installation goes to Program Files\Microsoft Enterprise Desktop Virtualization.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>MED-V workspace</p></td>
|
|
||||||
<td align="left"><p>INSTALLDIR</p></td>
|
|
||||||
<td align="left"><p><install path></p></td>
|
|
||||||
<td align="left"><p>Installation</p></td>
|
|
||||||
<td align="left"><p>Change installed directory</p></td>
|
|
||||||
<td align="left"><p>Installation goes to ProgramData\Microsoft\Medv\Workspace.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>MED-V workspace</p></td>
|
|
||||||
<td align="left"><p>OVERWRITE VHD</p></td>
|
|
||||||
<td align="left"><p>0 or 1</p></td>
|
|
||||||
<td align="left"><p>Installation</p></td>
|
|
||||||
<td align="left"><p>Fail installation if VHD exists(0) or overwrite existing VHD(1).</p></td>
|
|
||||||
<td align="left"><p>Overwrite does not occur and installation fails if a virtual hard disk (VHD) already exists.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>MED-V workspace</p></td>
|
|
||||||
<td align="left"><p>SUPPRESSMEDVLAUNCH</p></td>
|
|
||||||
<td align="left"><p>0 or 1</p></td>
|
|
||||||
<td align="left"><p>Installation</p></td>
|
|
||||||
<td align="left"><p>Start(0) or do not start(1) MED-V after MED-V workspace is installed.</p></td>
|
|
||||||
<td align="left"><p>If the MED-V workspace was installed with the user interface (UI), a check box on the <strong>Finish</strong> page controls whether to start MED-V.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>MED-V workspace</p></td>
|
|
||||||
<td align="left"><p>DELETEDIFFDISKS</p></td>
|
|
||||||
<td align="left"><p>0 or 1</p></td>
|
|
||||||
<td align="left"><p>Uninstallation</p></td>
|
|
||||||
<td align="left"><p>Keep(0) or delete(1) VHDs created by MED-V</p></td>
|
|
||||||
<td align="left"><p>No VHDs are deleted.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### 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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,114 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,55 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,94 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
## <a href="" id="bkmk-howtoinstallandconfiguremicrosoftvirtualpc7"></a>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.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## <a href="" id="bkmk-howtoinstallandconfiguremicrosoftvirtualpc7update"></a>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).
|
|
||||||
|
|
||||||
## <a href="" id="bkmk-antivirusbackupsoftwareconfiguration"></a>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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,207 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,103 +0,0 @@
|
|||||||
---
|
|
||||||
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
|
|
||||||
& “.\<workspacename>.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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
73
mdop/medv-v1/configuring-med-v-for-remote-networks.md
Normal file
73
mdop/medv-v1/configuring-med-v-for-remote-networks.md
Normal file
@ -0,0 +1,73 @@
|
|||||||
|
---
|
||||||
|
title: Configuring MED-V for Remote Networks
|
||||||
|
description: Configuring MED-V for Remote Networks
|
||||||
|
ms.assetid: 4d2f0081-622f-4a6f-8d73-f8c2108036e0
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# Configuring MED-V for Remote Networks
|
||||||
|
|
||||||
|
|
||||||
|
You can configure MED-V to work from inside a network, remotely, or both from inside the network and remotely.
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-howtoconfiguremedvtoworkfrominsideanetworkorremotely"></a>
|
||||||
|
|
||||||
|
|
||||||
|
**To configure MED-V to work from inside a network**
|
||||||
|
|
||||||
|
- Configure a MED-V server and image distribution inside the network.
|
||||||
|
|
||||||
|
**To configure MED-V to work remotely**
|
||||||
|
|
||||||
|
1. Configure a MED-V server and an image distribution server that are accessible from the Internet.
|
||||||
|
|
||||||
|
2. If needed, configure a perimeter network (also called a DMZ) reverse proxy.
|
||||||
|
|
||||||
|
3. Set the authentication method, in the *ClientSettings.xml* file, which can be found in the **Servers\\Configuration Server\\** folder.
|
||||||
|
|
||||||
|
**To configure MED-V to work both from inside a network and remotely**
|
||||||
|
|
||||||
|
1. Configure a MED-V server and image distribution server inside the network.
|
||||||
|
|
||||||
|
2. Ensure that the servers are accessible from the Internet.
|
||||||
|
|
||||||
|
3. Configure the DNS resolution so that when the client attempts to connect to a server, it automatically connects to the correct server (within the network or over the Internet) based on the client location.
|
||||||
|
|
||||||
|
4. If needed, configure a perimeter network reverse proxy.
|
||||||
|
|
||||||
|
5. Set the authentication method, in the *ClientSettings.xml* file, which can be found in the **Servers\\Configuration Server\\** folder.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
When applying new settings, the service must be restarted.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- You can change the IIS authentication scheme to one of the following: BASIC, DIGEST, NTLM, or NEGOTIATE. The default is NEGOTIATE and uses the following entry:
|
||||||
|
|
||||||
|
``` syntax
|
||||||
|
<ImageDistribution>
|
||||||
|
<!-- The authentication used for image download. Basic and digest authentication should be used only under SSL.-->
|
||||||
|
<!-- The line below can be one of the following: -->
|
||||||
|
<!--BG_AUTH_SCHEME>BG_AUTH_SCHEME_BASIC</BG_AUTH_SCHEME-->
|
||||||
|
<!--BG_AUTH_SCHEME>BG_AUTH_SCHEME_DIGEST</BG_AUTH_SCHEME-->
|
||||||
|
<!--BG_AUTH_SCHEME>BG_AUTH_SCHEME_NTLM</BG_AUTH_SCHEME-->
|
||||||
|
<!--BG_AUTH_SCHEME>BG_AUTH_SCHEME_NEGOTIATE</BG_AUTH_SCHEME-->
|
||||||
|
<Authentication type="Kidaro.Foundation.Bits.BG_AUTH_SCHEME">
|
||||||
|
<BG_AUTH_SCHEME>BG_AUTH_SCHEME_NEGOTIATE</BG_AUTH_SCHEME>
|
||||||
|
</Authentication>
|
||||||
|
</ImageDistribution>
|
||||||
|
```
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[MED-V Infrastructure Planning and Design](med-v-infrastructure-planning-and-design.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
53
mdop/medv-v1/configuring-med-v-server-for-cluster-mode.md
Normal file
53
mdop/medv-v1/configuring-med-v-server-for-cluster-mode.md
Normal file
@ -0,0 +1,53 @@
|
|||||||
|
---
|
||||||
|
title: Configuring MED-V Server for Cluster Mode
|
||||||
|
description: Configuring MED-V Server for Cluster Mode
|
||||||
|
ms.assetid: 41f0b2a3-4ce9-48e1-a6fb-4c13c4228515
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# Configuring MED-V Server for Cluster Mode
|
||||||
|
|
||||||
|
|
||||||
|
You can configure the MED-V server in cluster mode. In cluster mode, two servers are used and all files identified as mutual to both servers are placed on a file system. The server accesses the files from the file system rather than storing the files locally.
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-howtoconfigurethemedvserverinclustermode"></a>
|
||||||
|
|
||||||
|
|
||||||
|
**To configure the MED-V server in cluster mode**
|
||||||
|
|
||||||
|
1. Install and configure MED-V on one of the servers.
|
||||||
|
|
||||||
|
2. Create a shared network in a central location where all of the servers can access it.
|
||||||
|
|
||||||
|
3. Copy the contents of the *<InstallDir>/Servers/ConfigurationServer* folder to the shared network.
|
||||||
|
|
||||||
|
4. Install MED-V server on all designated servers.
|
||||||
|
|
||||||
|
5. On the shared network, assign full access to all MED-V server system accounts.
|
||||||
|
|
||||||
|
6. On each server, do the following:
|
||||||
|
|
||||||
|
1. In the *<InstallDir>/Servers/ServerConfiguration.xml* file, set the value of *<StorePath>* to the shared network path.
|
||||||
|
|
||||||
|
2. Copy the *<InstsallDir>/Servers/KeyPair.xml* file from the original server to all MED-V servers.
|
||||||
|
|
||||||
|
3. Restart the MED-V service.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
If all servers have the same local settings (such as listening ports, IIS server, management permissions, report database, and so on), the *<InstallDir>/Servers/ServerSettings.xml* can be shared by all servers as well.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[MED-V Infrastructure Planning and Design](med-v-infrastructure-planning-and-design.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
63
mdop/medv-v1/configuring-med-v-workspace-policies.md
Normal file
63
mdop/medv-v1/configuring-med-v-workspace-policies.md
Normal file
@ -0,0 +1,63 @@
|
|||||||
|
---
|
||||||
|
title: Configuring MED-V Workspace Policies
|
||||||
|
description: Configuring MED-V Workspace Policies
|
||||||
|
ms.assetid: 0eaed981-cbf3-4b16-a4b7-4705c5705dc7
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# Configuring MED-V Workspace Policies
|
||||||
|
|
||||||
|
|
||||||
|
A MED-V workspace policy is a group of configurable settings that define how the virtualized environment and applications perform on the host machine. The topics in this section describe all the configurable settings in the MED-V workspace policy as well as how these settings influence the MED-V workspace.
|
||||||
|
|
||||||
|
The following MED-V workspace types are available:
|
||||||
|
|
||||||
|
- **Persistent**—In a persistent MED-V workspace, all changes and additions the user makes to the MED-V workspace are saved in the MED-V workspace between sessions. Additionally, a persistent MED-V workspace is generally used in a domain environment.
|
||||||
|
|
||||||
|
- **Revertible**—In a revertible MED-V workspace, at the completion of each session (that is, when the MED-V workspace is stopped), the MED-V workspace reverts to its original state during deployment. No changes or additions that the user made are saved on the MED-V workspace between sessions. A revertible MED-V workspace cannot be used in a domain environment.
|
||||||
|
|
||||||
|
It is important to decide on the type of MED-V workspace you are creating before deploying the MED-V workspace, because it is not recommended to reconfigure the type of MED-V workspace after a policy has been deployed to users.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
When configuring a policy, a warning symbol appears next to mandatory fields that are not filled in. If a mandatory field is not filled in, the symbol appears on the tab as well.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## In This Section
|
||||||
|
|
||||||
|
|
||||||
|
<a href="" id="how-to-apply-general-settings-to-a-med-v-workspace"></a>[How to Apply General Settings to a MED-V Workspace](how-to-apply-general-settings-to-a-med-v-workspace.md)
|
||||||
|
Describes the general settings of a MED-V workspace, and how to apply them to a policy.
|
||||||
|
|
||||||
|
<a href="" id="how-to-apply-virtual-machine-settings-to-a-med-v-workspace"></a>[How to Apply Virtual Machine Settings to a MED-V Workspace](how-to-apply-virtual-machine-settings-to-a-med-v-workspace.md)
|
||||||
|
Describes the virtual machine settings for a MED-V workspace, and how to apply them to a policy.
|
||||||
|
|
||||||
|
<a href="" id="how-to-configure-a-domain-user-or-group"></a>[How to Configure a Domain User or Group](how-to-configure-a-domain-user-or-groupmedvv2.md)
|
||||||
|
Describes how to configure domain users and groups.
|
||||||
|
|
||||||
|
<a href="" id="how-to-configure-published-applications"></a>[How to Configure Published Applications](how-to-configure-published-applicationsmedvv2.md)
|
||||||
|
Describes published applications and menus, and how to apply them to a policy.
|
||||||
|
|
||||||
|
<a href="" id="how-to-configure-web-settings-for-a-med-v-workspace"></a>[How to Configure Web Settings for a MED-V Workspace](how-to-configure-web-settings-for-a-med-v-workspace.md)
|
||||||
|
Describes the Web settings available for a MED-V workspace, and how to apply them to a policy.
|
||||||
|
|
||||||
|
<a href="" id="how-to-configure-the-virtual-machine-setup-for-a-med-v-workspace"></a>[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)
|
||||||
|
Describes the virtual machine setup for a MED-V workspace, and how to apply it to a policy.
|
||||||
|
|
||||||
|
<a href="" id="how-to-apply-network-settings-to-a-med-v-workspace"></a>[How to Apply Network Settings to a MED-V Workspace](how-to-apply-network-settings-to-a-med-v-workspace.md)
|
||||||
|
Describes the network settings of a MED-V workspace, and how to apply them to a policy.
|
||||||
|
|
||||||
|
<a href="" id="how-to-apply-performance-settings-to-a-med-v-workspace"></a>[How to Apply Performance Settings to a MED-V Workspace](how-to-apply-performance-settings-to-a-med-v-workspace.md)
|
||||||
|
Describes the performance settings of a MED-V workspace, and how to apply them to a policy.
|
||||||
|
|
||||||
|
<a href="" id="how-to-import-and-export-a-policy"></a>[How to Import and Export a Policy](how-to-import-and-export-a-policy.md)
|
||||||
|
Describes how to import and export a policy.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,433 +0,0 @@
|
|||||||
---
|
|
||||||
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.
|
|
||||||
|
|
||||||
## <a href="" id="bkmk-prereq"></a>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:
|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p><strong>Package Information</strong></p></td>
|
|
||||||
<td align="left"><p>Specify a name for the MED-V workspace and select a folder where the MED-V workspace package files are saved.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p><strong>Select Windows XP Image</strong></p></td>
|
|
||||||
<td align="left"><p>Specify your prepared Windows XP Virtual PC image.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p><strong>First Time Setup</strong></p></td>
|
|
||||||
<td align="left"><p>Specify the setup process that MED-V follows during first time setup.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p><strong>MED-V Messages</strong></p></td>
|
|
||||||
<td align="left"><p>Specify the messages and optional URL for Help information that the end user sees during first time setup.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p><strong>Naming Computers</strong></p></td>
|
|
||||||
<td align="left"><p>Specify how the MED-V virtual machine is named.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p><strong>Copy Settings from Host</strong></p></td>
|
|
||||||
<td align="left"><p>Specify how the settings for the MED-V workspace are defined.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p><strong>Startup and Networking</strong></p></td>
|
|
||||||
<td align="left"><p>Specify the settings for starting the MED-V workspace, networking, and user credentials.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p><strong>Web Redirection</strong></p></td>
|
|
||||||
<td align="left"><p>Specify a text file or a list of the URLs you want redirected to Internet Explorer in the MED-V workspace.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p><strong>Summary</strong></p></td>
|
|
||||||
<td align="left"><p>Verify your MED-V workspace settings and start to build your MED-V workspace deployment package.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
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.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p><strong>Copy regional settings</strong></p></td>
|
|
||||||
<td align="left"><p>Select this check box to copy the regional settings from the host computer to the MED-V workspace.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p></p></td>
|
|
||||||
<td align="left"><p>If you select this check box, the following settings are set in the Sysprep.inf file:</p>
|
|
||||||
<pre class="syntax" space="preserve"><code>[RegionalSettings]
|
|
||||||
Language
|
|
||||||
SystemLocale
|
|
||||||
UserLocale
|
|
||||||
UserLocale_DefaultUser
|
|
||||||
InputLocale
|
|
||||||
InputLocale_DefaultUser
|
|
||||||
</code></pre></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p><strong>Copy user settings</strong></p></td>
|
|
||||||
<td align="left"><p>Select this check box to copy certain user settings, such as user name and company name, from the host to the MED-V workspace.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p></p></td>
|
|
||||||
<td align="left"><p>If you select this check box, the following settings are set in the Sysprep.inf file:</p>
|
|
||||||
<pre class="syntax" space="preserve"><code>[UserData]
|
|
||||||
OrgName
|
|
||||||
FullName</code></pre>
|
|
||||||
<div class="alert">
|
|
||||||
<strong>Note</strong>
|
|
||||||
<p>Personal settings, such as Internet browsing history, are not copied over to the MED-V workspace.</p>
|
|
||||||
</div>
|
|
||||||
<div>
|
|
||||||
|
|
||||||
</div></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p><strong>Copy domain name</strong></p></td>
|
|
||||||
<td align="left"><p>Select this check box to let the guest join the same domain as the host.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p></p></td>
|
|
||||||
<td align="left"><div class="alert">
|
|
||||||
<strong>Important</strong>
|
|
||||||
<p>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.</p>
|
|
||||||
</div>
|
|
||||||
<div>
|
|
||||||
|
|
||||||
</div></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p><strong>Copy domain organizational unit</strong></p></td>
|
|
||||||
<td align="left"><p>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.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
After you have finished, click **Next**.
|
|
||||||
|
|
||||||
9. On the **Startup and Networking** page, you can change the default behavior for the following settings:
|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p><strong>Start MED-V workspace</strong></p></td>
|
|
||||||
<td align="left"><p>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.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p></p></td>
|
|
||||||
<td align="left"><p>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.</p>
|
|
||||||
<p>You can either define this setting for the end user or let the end user control how MED-V starts.</p>
|
|
||||||
<div class="alert">
|
|
||||||
<strong>Note</strong>
|
|
||||||
<p>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 <strong>MED-V User Settings</strong>. If you define this setting for the end user, they cannot change how MED-V starts.</p>
|
|
||||||
</div>
|
|
||||||
<div>
|
|
||||||
|
|
||||||
</div></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p><strong>Networking</strong></p></td>
|
|
||||||
<td align="left"><p>Select <strong>Shared</strong> or <strong>Bridged</strong> for your networking setting. The default is <strong>Shared</strong>.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p></p></td>
|
|
||||||
<td align="left"><p><strong>Shared</strong> - The MED-V workspace uses Network Address Translation (NAT) to share the host's IP for outgoing traffic.</p>
|
|
||||||
<p><strong>Bridged</strong> - The MED-V workspace has its own network address, typically obtained through DHCP.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p><strong>Store credentials</strong></p></td>
|
|
||||||
<td align="left"><p>Choose whether you want to store the end user credentials.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p></p></td>
|
|
||||||
<td align="left"><p>The default behavior is that credential storing is disabled so that the end user must be authenticated every time that they log on.</p>
|
|
||||||
<div class="alert">
|
|
||||||
<strong>Important</strong>
|
|
||||||
<p>Even though caching the end user’s credentials provides the best user experience, you should be aware of the risks involved.</p>
|
|
||||||
<p>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.</p>
|
|
||||||
</div>
|
|
||||||
<div>
|
|
||||||
|
|
||||||
</div></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
46
mdop/medv-v1/creating-a-med-v-image.md
Normal file
46
mdop/medv-v1/creating-a-med-v-image.md
Normal file
@ -0,0 +1,46 @@
|
|||||||
|
---
|
||||||
|
title: Creating a MED-V Image
|
||||||
|
description: Creating a MED-V Image
|
||||||
|
ms.assetid: 7cbbcd22-83f5-4b60-825f-781b4c6a2d36
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# Creating a MED-V Image
|
||||||
|
|
||||||
|
|
||||||
|
## In This Section
|
||||||
|
|
||||||
|
|
||||||
|
This section describes how to configure a MED-V image on a computer on which the MED-V client and MED-V management application are installed, and explains the following:
|
||||||
|
|
||||||
|
<a href="" id="how-to-create-and-test-a-med-v-image"></a>[How to Create and Test a MED-V Image](how-to-create-and-test-a-med-v-image.md)
|
||||||
|
Describes how to create a MED-V image, and then test the image locally.
|
||||||
|
|
||||||
|
<a href="" id="how-to-pack-a-med-v-image"></a>[How to Pack a MED-V Image](how-to-pack-a-med-v-image.md)
|
||||||
|
Describes how to pack a MED-V image so that it can be added to a deployment package or uploaded to the server.
|
||||||
|
|
||||||
|
<a href="" id="how-to-upload-a-med-v-image-to-the-server"></a>[How to Upload a MED-V Image to the Server](how-to-upload-a-med-v-image-to-the-server.md)
|
||||||
|
Describes how to upload a MED-V image to the server.
|
||||||
|
|
||||||
|
<a href="" id="how-to-localize-a-med-v-image"></a>[How to Localize a MED-V Image](how-to-localize-a-med-v-image.md)
|
||||||
|
Describes how to localize a MED-V image either through extracting or downloading the image.
|
||||||
|
|
||||||
|
<a href="" id="how-to-update-a-med-v-image"></a>[How to Update a MED-V Image](how-to-update-a-med-v-image.md)
|
||||||
|
Describes how to update a MED-V image to create a new version of the image.
|
||||||
|
|
||||||
|
<a href="" id="how-to-delete-a-med-v-image"></a>[How to Delete a MED-V Image](how-to-delete-a-med-v-image.md)
|
||||||
|
Describes how to delete a MED-V image.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
After the MED-V image is configured, the computer should not be part of a domain because the join domain procedure should be performed on the client after the deployment, as part of the MED-V workspace setup.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
64
mdop/medv-v1/creating-a-med-v-workspacemedv-10-sp1.md
Normal file
64
mdop/medv-v1/creating-a-med-v-workspacemedv-10-sp1.md
Normal file
@ -0,0 +1,64 @@
|
|||||||
|
---
|
||||||
|
title: Creating a MED-V Workspace
|
||||||
|
description: Creating a MED-V Workspace
|
||||||
|
ms.assetid: 9578bb99-8a09-44c1-b88f-538901f16ad3
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# Creating a MED-V Workspace
|
||||||
|
|
||||||
|
|
||||||
|
A MED-V workspace is the desktop environment in which end users interact with the virtual machine provided by MED-V. The MED-V workspace is created and customized by the administrator. It consists of an image and the policy, which defines the rules and functionality of the MED-V workspace. Multiple MED-V workspaces can be created, 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, thereby making the MED-V workspace available only for the associated user's or group's computers.
|
||||||
|
|
||||||
|
## How to Add a MED-V Workspace
|
||||||
|
|
||||||
|
|
||||||
|
**To add a MED-V workspace**
|
||||||
|
|
||||||
|
1. Click the **Policy** management button to open the **Policy** module.
|
||||||
|
|
||||||
|
The **Policy** module consists of the **Workspaces** menu on the left and the **General**, **Virtual Machine**, **Deployment**, **Applications**, **Web**, **VM Setup**, **Network**, and **Performance** tabs.
|
||||||
|
|
||||||
|
2. On the **Policy** menu, select **New Workspace**, or click **Add** to create a new MED-V workspace.
|
||||||
|
|
||||||
|
3. On the **General** tab, in the **Name** field, enter the name of the MED-V workspace.
|
||||||
|
|
||||||
|
4. In the **Description** field, enter a description for the MED-V workspace.
|
||||||
|
|
||||||
|
5. In the **Support contact info** field, enter the contact information for technical support.
|
||||||
|
|
||||||
|
For more information about configuring a MED-V workspace, see [Configuring MED-V Workspace Policies](configuring-med-v-workspace-policies.md).
|
||||||
|
|
||||||
|
## How to Clone a MED-V Workspace
|
||||||
|
|
||||||
|
|
||||||
|
A MED-V workspace can be cloned so that you can create a MED-V workspace identical to an existing MED-V workspace.
|
||||||
|
|
||||||
|
**To clone a MED-V workspace**
|
||||||
|
|
||||||
|
1. Click the MED-V workspace to clone.
|
||||||
|
|
||||||
|
2. On the **Policy** menu, select **Clone Workspace**.
|
||||||
|
|
||||||
|
A new MED-V workspace is created with the name <Original MED-V workspace name> - 2.
|
||||||
|
|
||||||
|
## How to Delete a MED-V Workspace
|
||||||
|
|
||||||
|
|
||||||
|
**To delete a MED-V workspace**
|
||||||
|
|
||||||
|
- In the **Policy** module, while the workspace pane is in focus, click **Remove**.
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[Using the MED-V Management Console User Interface](using-the-med-v-management-console-user-interface.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
243
mdop/medv-v1/creating-a-virtual-pc-image-for-med-v.md
Normal file
243
mdop/medv-v1/creating-a-virtual-pc-image-for-med-v.md
Normal file
@ -0,0 +1,243 @@
|
|||||||
|
---
|
||||||
|
title: Creating a Virtual PC Image for MED-V
|
||||||
|
description: Creating a Virtual PC Image for MED-V
|
||||||
|
ms.assetid: 5e02ea07-25b9-41a5-a803-d70c55eef586
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# Creating a Virtual PC Image for MED-V
|
||||||
|
|
||||||
|
|
||||||
|
To create a Virtual PC (VPC) image for MED-V, you must perform the following:
|
||||||
|
|
||||||
|
1. [Create a VPC image](#bkmk-creatingavirtualmachinebyusingmicrosoftvirtualpc).
|
||||||
|
|
||||||
|
2. [Install the MED-V workspace .msi package onto the VPC image](#bkmk-howtoinstallthemedvworkspacemsipackage).
|
||||||
|
|
||||||
|
3. [Run the MED-V virtual machine prerequisites tool on the VPC image](#bkmk-howtorunthevirtualmachineprerequisitestool).
|
||||||
|
|
||||||
|
4. [Manually configure virtual machine prerequisites on the VPC image](#bkmk-howtoconfiguremedvvirtualmachinemanualinstallationprerequisites).
|
||||||
|
|
||||||
|
5. [Configure Sysprep for MED-V images](#bkmk-howtoconfiguresysprepformedvimages) (optional).
|
||||||
|
|
||||||
|
6. [Turn off Microsoft Virtual PC](#bkmk-turningoffmicrosoftvirtualpc).
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-creatingavirtualmachinebyusingmicrosoftvirtualpc"></a>Creating a Virtual PC Image by Using Microsoft Virtual PC
|
||||||
|
|
||||||
|
|
||||||
|
To create a Virtual PC image using Microsoft Virtual PC, refer to the Virtual PC documentation.
|
||||||
|
|
||||||
|
For more information, see the following:
|
||||||
|
|
||||||
|
- [Windows Virtual PC Help](http://go.microsoft.com/fwlink/?LinkId=182378)
|
||||||
|
|
||||||
|
- [Create a virtual machine and install a guest operating system](http://go.microsoft.com/fwlink/?LinkId=182379)
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-howtoinstallthemedvworkspacemsipackage"></a>How to Install the MED-V Workspace .msi Package
|
||||||
|
|
||||||
|
|
||||||
|
After the Virtual PC image is created, install the MED-V workspace .msi package onto the image.
|
||||||
|
|
||||||
|
**To install the MED-V workspace image**
|
||||||
|
|
||||||
|
1. Start the virtual machine, and copy the MED-V workspace .msi package inside.
|
||||||
|
|
||||||
|
The MED-V workspace .msi package is called *MED-V\_workspace\_x.msi*, where *x* is the version number.
|
||||||
|
|
||||||
|
For example, *MED-V\_workspace\_1.0.65.msi*.
|
||||||
|
|
||||||
|
2. Double-click the MED-V workspace .msi package, and follow the installation wizard instructions.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
When a new MED-V version is released, and an existing Virtual PC image is updated, uninstall the existing MED-V workspace .msi package, reboot the computer, and install the new MED-V workspace .msi package.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
After the MED-V workspace .msi package is installed, other products that replace GINA cannot be installed.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-howtorunthevirtualmachineprerequisitestool"></a>How to Run the Virtual Machine Prerequisites Tool
|
||||||
|
|
||||||
|
|
||||||
|
The virtual machine (VM) prerequisites tool is a wizard that automates several of the prerequisites.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
Although many parameters are configurable in the wizard, the properties required for the proper functioning of MED-V are not configurable.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**To run the virtual machine prerequisites tool**
|
||||||
|
|
||||||
|
1. After the MED-V workspace .msi package is installed, on the Windows **Start** menu, select **All Programs > MED-V > VM Prerequisites Tool**.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
The user running the virtual machine prerequisites tool must have local administrator rights and must be the only user logged in.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
The **MED-V VM Prerequisite Wizard Welcome** page appears.
|
||||||
|
|
||||||
|
2. Click **Next**.
|
||||||
|
|
||||||
|
3. On the **Windows Settings** page, from the following configurable properties, select the ones to be configured:
|
||||||
|
|
||||||
|
- **Clear users’ personal history information**
|
||||||
|
|
||||||
|
- **Clear local profiles temp directory**
|
||||||
|
|
||||||
|
- **Disable sounds on following Windows events: start, logon, logoff**
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
Do not enable Windows page saver in a group policy.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
4. Click **Next**.
|
||||||
|
|
||||||
|
5. On the **Internet Explorer Settings** page, from the following configurable properties, select the ones to be configured:
|
||||||
|
|
||||||
|
- **Don't use auto complete features**
|
||||||
|
|
||||||
|
- **Disable reuse of windows for launching shortcuts**
|
||||||
|
|
||||||
|
- **Clear browsing history**
|
||||||
|
|
||||||
|
- **Enable tabbed browsing in Internet Explorer 7**
|
||||||
|
|
||||||
|
6. Click **Next**.
|
||||||
|
|
||||||
|
7. On the **Windows Services** page, from the following configurable properties, select the ones to be configured:
|
||||||
|
|
||||||
|
- **Security center service**
|
||||||
|
|
||||||
|
- **Task scheduler service**
|
||||||
|
|
||||||
|
- **Automatic updates service**
|
||||||
|
|
||||||
|
- **System restore service**
|
||||||
|
|
||||||
|
- **Indexing service**
|
||||||
|
|
||||||
|
- **Wireless Zero Configuration**
|
||||||
|
|
||||||
|
- **Fast User Switching Compatibility**
|
||||||
|
|
||||||
|
8. Click **Next**.
|
||||||
|
|
||||||
|
9. On the **Windows Auto Logon** page, do the following:
|
||||||
|
|
||||||
|
1. Select the **Enable Windows Auto Logon** check box.
|
||||||
|
|
||||||
|
2. Assign a **User name** and **Password**.
|
||||||
|
|
||||||
|
10. Click **Apply**, and in the confirmation box that appears, click **Yes**.
|
||||||
|
|
||||||
|
11. On the **Summary** page, click **Finish** to quit the wizard
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
Verify that group policies do not overwrite the mandatory settings set in the prerequisites tool.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-howtoconfiguremedvvirtualmachinemanualinstallationprerequisites"></a>How to Configure MED-V Virtual Machine Manual Installation Prerequisites
|
||||||
|
|
||||||
|
|
||||||
|
Several of the configurations cannot be configured through the virtual machine prerequisites tool and must be performed manually.
|
||||||
|
|
||||||
|
- Virtual Machine Settings
|
||||||
|
|
||||||
|
It is recommended to configure the following virtual machine settings in the Microsoft Virtual PC console:
|
||||||
|
|
||||||
|
- Disable floppy disk drives.
|
||||||
|
|
||||||
|
- Disable undo-disks (**Settings > undo-disks**).
|
||||||
|
|
||||||
|
- Ensure that the image has only one virtual CPU.
|
||||||
|
|
||||||
|
- Eliminate interactions between the virtual machine and the user, where they are not related to published applications (such as, messages requiring user input).
|
||||||
|
|
||||||
|
- Image Settings
|
||||||
|
|
||||||
|
Configure the following manual settings inside the image:
|
||||||
|
|
||||||
|
1. In the **Power Options Properties** window, disable hibernation and sleep.
|
||||||
|
|
||||||
|
2. Apply the most recent Windows updates.
|
||||||
|
|
||||||
|
3. In the **Windows Startup and Recovery** dialog box, in the **System Failure** section, clear the **Automatically restart** check box.
|
||||||
|
|
||||||
|
4. Ensure that the image uses a VLK license key.
|
||||||
|
|
||||||
|
- Installing VPC Additions
|
||||||
|
|
||||||
|
On the **Action** menu, select **Install or Update Virtual Machine Additions**.
|
||||||
|
|
||||||
|
- Configuring Printing
|
||||||
|
|
||||||
|
You can configure printing from the MED-V workspace in either of the following ways:
|
||||||
|
|
||||||
|
- Add a printer to the virtual machine.
|
||||||
|
|
||||||
|
- Allow printing with printers that are configured on the host computer.
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-howtoconfiguresysprepformedvimages"></a>How to Configure Sysprep for MED-V Images
|
||||||
|
|
||||||
|
|
||||||
|
In a MED-V workspace, Sysprep can be configured in order to assign unique security ID (SID), particularly when multiple MED-V workspaces are run on a single computer. It is not recommended to use Sysprep to join a domain; instead, use the MED-V join domain script action as described in [How to Set Up Script Actions](how-to-set-up-script-actions.md).
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
Sysprep is Microsoft's system preparation utility for the Windows operating system.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**To configure Sysprep in a MED-V workspace**
|
||||||
|
|
||||||
|
1. Create a directory in the root of the system drive named *Sysprep*.
|
||||||
|
|
||||||
|
2. From the Windows installation CD, extract *deploy.cab* to the root of the system drive, or download the latest Deployment Tools update from the Microsoft Web site.
|
||||||
|
|
||||||
|
- For Windows 2000, see [Deployment Tools update for Windows 2000](http://go.microsoft.com/fwlink/?LinkId=143001).
|
||||||
|
|
||||||
|
- For Windows XP, see [Deployment Tools update for Windows XP](http://go.microsoft.com/fwlink/?LinkId=143000).
|
||||||
|
|
||||||
|
3. Run **Setup Manager** (setupmgr.exe).
|
||||||
|
|
||||||
|
4. Follow the Setup Manager wizard.
|
||||||
|
|
||||||
|
After Sysprep is configured and the MED-V workspace is created, Sysprep must be executed.
|
||||||
|
|
||||||
|
**To run Sysprep**
|
||||||
|
|
||||||
|
1. From the Sysprep folder located in the root of the system drive, run the System Preparation Tool (Sysprep.exe).
|
||||||
|
|
||||||
|
2. In the warning message box that appears, click **OK**.
|
||||||
|
|
||||||
|
3. In the **Sysprep Properties** dialog box, select the **Don't reset grace period for activation** and **Use Mini-Setup** check boxes.
|
||||||
|
|
||||||
|
4. Click **Reseal**.
|
||||||
|
|
||||||
|
5. If you are not satisfied with the information listed in the confirmation message box that appears, click **Cancel** and change the selections.
|
||||||
|
|
||||||
|
6. Click **OK** to complete the system preparation process.
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-turningoffmicrosoftvirtualpc"></a>Turning Off Microsoft Virtual PC
|
||||||
|
|
||||||
|
|
||||||
|
After all the components are installed and configured, close Microsoft Virtual PC and select **Turn Off**.
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
Creating a MED-V Image
|
||||||
|
[How to Set Up Script Actions](how-to-set-up-script-actions.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,150 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
## <a href="" id="bkmk-creatingavirtualmachinebyusingmicrosoftvirtualpc"></a>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.
|
|
||||||
|
|
||||||
## <a href="" id="bkmk-installingwindowsxpontovpc"></a>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).
|
|
||||||
|
|
||||||
## <a href="" id="bkmk-installingnet"></a>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.
|
|
||||||
|
|
||||||
## <a href="" id="bkmk-applypatchestovpc"></a>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
|
|
||||||
|
|
||||||
## <a href="" id="bkmk-installintegration"></a>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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,36 +0,0 @@
|
|||||||
---
|
|
||||||
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
|
|
||||||
|
|
||||||
|
|
||||||
<a href="" id="determining-how-med-v-will-be-deployed"></a>[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.
|
|
||||||
|
|
||||||
<a href="" id="identifying-the-number-and-types-of-med-v-workspaces"></a>[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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
56
mdop/medv-v1/define-the-project-scope.md
Normal file
56
mdop/medv-v1/define-the-project-scope.md
Normal file
@ -0,0 +1,56 @@
|
|||||||
|
---
|
||||||
|
title: Define the Project Scope
|
||||||
|
description: Define the Project Scope
|
||||||
|
ms.assetid: 84637d2a-2e30-417d-b150-dc81f414b3a5
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# Define the Project Scope
|
||||||
|
|
||||||
|
|
||||||
|
When defining the project scope, determine the following:
|
||||||
|
|
||||||
|
1. The MED-V end users—the location and number of end users are used in determining the location of MED-V client installations and the number of MED-V instances, as well as the number and placement of MED-V image repositories.
|
||||||
|
|
||||||
|
2. The virtual machine (VM) images to be managed by MED-V—to determine the method of distributing images and placement of image repositories.
|
||||||
|
|
||||||
|
3. The organization’s service level expectations—to determine the performance and fault-tolerance requirements for the MED-V server and database as well as the image repository.
|
||||||
|
|
||||||
|
4. Validate with the business—ensure there is a complete understanding of how the planned infrastructure affects the business.
|
||||||
|
|
||||||
|
## Define the MED-V End Users
|
||||||
|
|
||||||
|
|
||||||
|
First, determine where the end users are located, as well as the number of users in each location. Second, obtain a network infrastructure diagram that displays the user locations and the available bandwidth to those locations. Third, find out if users travel between locations. If users travel, additional capacity may be required in the design of the server infrastructure and image repositories.
|
||||||
|
|
||||||
|
## Determine the MED-V Images to Be Managed by MED-V
|
||||||
|
|
||||||
|
|
||||||
|
After the MED-V end users have been defined, determine which VMs will be managed by MED-V for the users in each location.
|
||||||
|
|
||||||
|
If any of the VMs are stored in a centralized library, determine the location of the library so that it may be evaluated for use as a MED-V repository.
|
||||||
|
|
||||||
|
## <a href="" id="determine-the-organization-s-service-level-expectations"></a>Determine the Organization’s Service Level Expectations
|
||||||
|
|
||||||
|
|
||||||
|
For each MED-V workspace, note the acceptable time for a new image to load and the timeframe for critical updates to be deployed.
|
||||||
|
|
||||||
|
If applicable, record the service level expectations for MED-V reporting, to be used in the design of the server infrastructure.
|
||||||
|
|
||||||
|
## Validate with the Business
|
||||||
|
|
||||||
|
|
||||||
|
Ask business stakeholders and application owners the following questions:
|
||||||
|
|
||||||
|
- Are there any existing images that can be combined? For example, if application A on Windows XP is one VPC image and application B on Windows XP is another VPC image, perhaps a single image can contain both applications, thereby reducing repository space and bandwidth required for image download.
|
||||||
|
|
||||||
|
- Are the in-scope applications licensable and supportable if delivered in a VM by MED-V? Check with the application supplier to ensure that licensing and support terms will not be violated by delivering the application through MED-V.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,42 +0,0 @@
|
|||||||
---
|
|
||||||
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
|
|
||||||
|
|
||||||
|
|
||||||
<a href="" id="how-to-install-the-med-v-workspace-packager"></a>[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.
|
|
||||||
|
|
||||||
<a href="" id="how-to-deploy-the-med-v-components-through-an-electronic-software-distribution-system"></a>[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.
|
|
||||||
|
|
||||||
<a href="" id="how-to-manually-install-the-med-v-host-agent"></a>[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.
|
|
||||||
|
|
||||||
<a href="" id="how-to-uninstall-the-med-v-components"></a>[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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -0,0 +1,47 @@
|
|||||||
|
---
|
||||||
|
title: Deploying a MED-V Workspace Using a Deployment Package
|
||||||
|
description: Deploying a MED-V Workspace Using a Deployment Package
|
||||||
|
ms.assetid: e07fa70a-1a9f-486f-9a86-b33593b234da
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# Deploying a MED-V Workspace Using a Deployment Package
|
||||||
|
|
||||||
|
|
||||||
|
The deployment package installation provides a method of installing MED-V client together with all its required prerequisites as well as any settings predefined by the administrator.
|
||||||
|
|
||||||
|
When using a deployment package, the package is distributed via a shared network or removable media. The image can be included in the package or can be distributed separately.
|
||||||
|
|
||||||
|
Before creating a deployment package, ensure that you have created a MED-V image ready for deployment. For more information on creating a MED-V image, see [Creating a MED-V Image](creating-a-med-v-image.md).
|
||||||
|
|
||||||
|
After the MED-V image is prepared, consider the best method for distributing the image in your environment. The image can be distributed in one of the following ways:
|
||||||
|
|
||||||
|
- Uploaded to the Web and distributed via Web download, optionally using Trim Transfer technology.
|
||||||
|
|
||||||
|
- Distributed using image pre-staging.
|
||||||
|
|
||||||
|
- Included in the deployment package and distributed together with all the other MED-V components.
|
||||||
|
|
||||||
|
If the image will be included in the package, no other configurations are necessary for the image. If the image will not be included in the deployment package, do one of the following:
|
||||||
|
|
||||||
|
- If you are deploying the image via the Web, upload the MED-V image to the image Web distribution server. For information on configuring an image Web distribution server, see [How to Configure the Image Web Distribution Server](how-to-configure-the-image-web-distribution-server.md). For information on uploading an image to the server, see [How to Upload a MED-V Image to the Server](how-to-upload-a-med-v-image-to-the-server.md).
|
||||||
|
|
||||||
|
- If you are deploying the image via image pre-staging, configure the pre-stage folder, and push the MED-V image to the folder. For more information on configuring the image pre-staging, see [How to Configure Image Pre-staging](how-to-configure-image-pre-staging.md).
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
If you are using image pre-staging, it is important to configure the image pre-stage folder prior to creating the deployment package. The folder path needs to be included in the deployment package.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Finally, create the deployment package. For more information on creating a deployment package, see [How to Configure a Deployment Package](how-to-configure-a-deployment-package.md). After the package is complete, distribute it for deployment.
|
||||||
|
|
||||||
|
After the deployment package is distributed, MED-V client can be installed and the image deployed. For more information on installing MED-V client, see [How to Install MED-V Client](how-to-install-med-v-clientdeployment-package.md). For more information on deploying the image, see [How to Deploy a Workspace Image](how-to-deploy-a-workspace-imagedeployment-package.md).
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -0,0 +1,50 @@
|
|||||||
|
---
|
||||||
|
title: Deploying a MED-V Workspace Using an Enterprise Software Distribution System
|
||||||
|
description: Deploying a MED-V Workspace Using an Enterprise Software Distribution System
|
||||||
|
ms.assetid: 867faed6-74ce-4573-84be-8bf26e66c08c
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# Deploying a MED-V Workspace Using an Enterprise Software Distribution System
|
||||||
|
|
||||||
|
|
||||||
|
MED-V client can be distributed using an enterprise software distribution system, such as Microsoft System Center Configuration Manager.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
If MED-V is installed by using Microsoft System Center Configuration Manager, when creating a package for MED-V, set the run mode to administrative rights.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Before deploying MED-V using an enterprise software distribution system, ensure that you have created a MED-V image ready for deployment. For more information on creating a MED-V image, see [Creating a MED-V Image](creating-a-med-v-image.md).
|
||||||
|
|
||||||
|
After the MED-V image is prepared, consider the best method for distributing the image in your environment. The image can be distributed in one of the following ways:
|
||||||
|
|
||||||
|
- Uploaded to the Web and distributed via Web download, optionally utilizing Trim Transfer technology.
|
||||||
|
|
||||||
|
- Distributed using image pre-staging.
|
||||||
|
|
||||||
|
## Deploying the Image via the Web
|
||||||
|
|
||||||
|
|
||||||
|
If you are deploying the image via the Web, upload the MED-V image to an image Web distribution server. For information on configuring an image Web distribution server, see [How to Configure the Image Web Distribution Server](how-to-configure-the-image-web-distribution-server.md). For information on uploading an image to the server, see [How to Upload a MED-V Image to the Server](how-to-upload-a-med-v-image-to-the-server.md).
|
||||||
|
|
||||||
|
## Deploying the Image via Pre-staging
|
||||||
|
|
||||||
|
|
||||||
|
If you are deploying the image via image pre-staging, configure the pre-stage folder, and push the MED-V image to the folder. For more information on configuring image pre-staging, see [How to Configure Image Pre-staging](how-to-configure-image-pre-staging.md).
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
If you are using image pre-staging, it is important to configure the image pre-stage folder prior to pushing the client .msi package. The folder path needs to be included in the client .msi package.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Finally, push the client .msi package using your enterprise software distribution center. MED-V can then be installed and the image deployed. For more information on installing MED-V client, see [How to Install MED-V Client](how-to-install-med-v-clientesds.md). For more information on deploying the image, see [How to Deploy a Workspace Image](how-to-deploy-a-workspace-imageesds.md).
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,42 +0,0 @@
|
|||||||
---
|
|
||||||
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
|
|
||||||
|
|
||||||
|
|
||||||
<a href="" id="how-to-deploy-a-med-v-workspace-through-an-electronic-software-distribution-system"></a>[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.
|
|
||||||
|
|
||||||
<a href="" id="how-to-deploy-a-med-v-workspace-in-a-windows-7-image"></a>[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.
|
|
||||||
|
|
||||||
<a href="" id="how-to-deploy-a-med-v-workspace-manually"></a>[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.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,43 +0,0 @@
|
|||||||
---
|
|
||||||
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
|
|
||||||
|
|
||||||
|
|
||||||
<a href="" id="end-to-end-deployment-scenario-for-med-v-2-0"></a>[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.
|
|
||||||
|
|
||||||
<a href="" id="med-v-2-0-supported-configurations"></a>[MED-V 2.0 Supported Configurations](med-v-20-supported-configurations.md)
|
|
||||||
Describes the supported configurations for MED-V 2.0.
|
|
||||||
|
|
||||||
<a href="" id="med-v-2-0-deployment-overview"></a>[MED-V 2.0 Deployment Overview](med-v-20-deployment-overview.md)
|
|
||||||
Describes the requirements for deploying MED-V 2.0.
|
|
||||||
|
|
||||||
<a href="" id="prepare-the-deployment-environment-for-med-v"></a>[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.
|
|
||||||
|
|
||||||
<a href="" id="deploy-the-med-v-components"></a>[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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,58 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
87
mdop/medv-v1/design-the-med-v-image-repositories.md
Normal file
87
mdop/medv-v1/design-the-med-v-image-repositories.md
Normal file
@ -0,0 +1,87 @@
|
|||||||
|
---
|
||||||
|
title: Design the MED-V Image Repositories
|
||||||
|
description: Design the MED-V Image Repositories
|
||||||
|
ms.assetid: e153154d-2751-4990-b94d-a2d76242c15f
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# Design the MED-V Image Repositories
|
||||||
|
|
||||||
|
|
||||||
|
After MED-V images are created and packed, they can be stored on a file server in any location. The files may be sent over HTTP or HTTPS by one or more IIS servers. The image repository can be shared by multiple MED-V instances.
|
||||||
|
|
||||||
|
To design the image repositories, you must first decide how the images will be deployed to each client and then whether that client requires a local image repository. Each repository is then designed and placed, along with its accompanying IIS server.
|
||||||
|
|
||||||
|
## Determine How Images Will Be Deployed
|
||||||
|
|
||||||
|
|
||||||
|
For each MED-V workspace, decide how you plan to deploy MED-V images to the client. This is important in determining how many repositories are necessary to store the packed images, where those repositories will be placed, and then to design those repositories.
|
||||||
|
|
||||||
|
Packed images can be deployed in the following ways:
|
||||||
|
|
||||||
|
- Downloaded over the network from an image distribution server, which comprises a file server and IIS server.
|
||||||
|
|
||||||
|
- On removable media, such as a USB drive or DVD.
|
||||||
|
|
||||||
|
- Pre-staged to an image store directory on the client computer using an enterprise software distribution center.
|
||||||
|
|
||||||
|
Decide which method, or methods, will be used to deploy MED-V images to each of the clients and whether the location will require an image repository.
|
||||||
|
|
||||||
|
## Determine the Number of Image Repositories
|
||||||
|
|
||||||
|
|
||||||
|
Now that you have determined the minimum number of repositories you need, add more if any of the following criteria apply:
|
||||||
|
|
||||||
|
- Organizational or regulatory reasons to separate the MED-V images—some MED-V images may not be able to coexist in the same repository. For example, sensitive personal data may require storage on a server that is only available to a limited set of employees who need access to the data.
|
||||||
|
|
||||||
|
- Clients in isolated networks—if images will be deployed over the network, determine whether any networks are isolated and require a separate repository. For example, organizations often isolate lab networks from production networks.
|
||||||
|
|
||||||
|
- Clients in remote networks—if images will be deployed over the network, some client machines may be separated from the repository by network links that have insufficient bandwidth to provide an adequate experience when a client loads a MED-V workspace. If necessary, design additional MED-V instances to address this need.
|
||||||
|
|
||||||
|
Add these repositories to the design. Decide on a name for each repository and the reason for designing it. Decide which MED-V images the repositories will hold and which MED-V clients will load MED-V workspaces with images from the repository.
|
||||||
|
|
||||||
|
## Design and Place the Image Repositories
|
||||||
|
|
||||||
|
|
||||||
|
When a new image is available to clients, clients begin downloading the image, possibly simultaneously. This creates a high demand on the repository and must be taken into account when designing the image repository.
|
||||||
|
|
||||||
|
For each repository, determine the amount of data it will store. Sum the sizes of images that will be stored in the repository. This is the value of the disk space required on the file server.
|
||||||
|
|
||||||
|
Next, add up the number of clients that may download MED-V images from the repository. This is the maximum number of concurrent downloads that can occur when a new MED-V image is loaded into the repository. The file server must be designed with a disk subsystem that can meet the IO demands this will create.
|
||||||
|
|
||||||
|
The image repository can reside on the same system as the MED-V server and the server running SQL Server, or on a remote file share. You can also run it in a Windows Server 2008 Hyper-V VM. Check the network location of the clients that the image repository will service, and place the repository in a network location where it will have sufficient bandwidth to meet the service level expectations of those clients.
|
||||||
|
|
||||||
|
### Fault Tolerance
|
||||||
|
|
||||||
|
If the image repository is unavailable, clients will not be able to download new or updated MED-V images. To design fault-tolerance options for the file server and fault-tolerant disks, see the [Infrastructure Planning and Design Microsoft SQL Server 2008](http://go.microsoft.com/fwlink/?LinkId=163302) guide.
|
||||||
|
|
||||||
|
## Design and Place the IIS Servers
|
||||||
|
|
||||||
|
|
||||||
|
This section is only relevant if clients will download image files over the network using HTTP or HTTPS.
|
||||||
|
|
||||||
|
The IIS server can coexist on the same system as the MED-V server and the server running SQL Server. It can also run in a Windows Server 2008 Hyper-V VM. The IIS server infrastructure must have sufficient throughput to deliver images to clients within the service level expectations of the organization. It must be designed with a disk subsystem that can meet the IO demands this creates.
|
||||||
|
|
||||||
|
For each image repository, sum the number of clients that may download MED-V images using IIS. This is the maximum number of concurrent downloads that can occur when an image is loaded into the repository. Use the throughput sum and the service level expectations determined in [Define the Project Scope](define-the-project-scope.md) to plan the design of the IIS server infrastructure and to determine the appropriate amount of bandwidth to allocate for the repository.
|
||||||
|
|
||||||
|
To design the IIS infrastructure, see the [Infrastructure Planning and Design Microsoft Internet Information Services](http://go.microsoft.com/fwlink/?LinkId=160826) guide.
|
||||||
|
|
||||||
|
### Fault Tolerance
|
||||||
|
|
||||||
|
If the IIS server infrastructure is unavailable, clients will not be able to download new or updated images. To configure fault tolerance, the Windows Server 2008-based IIS server can be placed in a failover cluster. To design the fault tolerance for the IIS server infrastructure, see the [Infrastructure Planning and Design Microsoft Internet Information Services](http://go.microsoft.com/fwlink/?LinkId=160826) guide.
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[Deploying a MED-V Workspace Using an Enterprise Software Distribution System](deploying-a-med-v-workspace-using-an-enterprise-software-distribution-system.md)
|
||||||
|
|
||||||
|
[Deploying a MED-V Workspace Using a Deployment Package](deploying-a-med-v-workspace-using-a-deployment-package.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
102
mdop/medv-v1/design-the-med-v-server-infrastructure.md
Normal file
102
mdop/medv-v1/design-the-med-v-server-infrastructure.md
Normal file
@ -0,0 +1,102 @@
|
|||||||
|
---
|
||||||
|
title: Design the MED-V Server Infrastructure
|
||||||
|
description: Design the MED-V Server Infrastructure
|
||||||
|
ms.assetid: 2781040f-880e-4e16-945d-a38c0adb4151
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# Design the MED-V Server Infrastructure
|
||||||
|
|
||||||
|
|
||||||
|
In this topic, you will design the server infrastructure for each MED-V instance. This includes determining whether the SQL Server instance will exist on the MED-V server or on a remote server, as well as the size of the SQL Server database. You will also determine the location of the management console.
|
||||||
|
|
||||||
|
## Design and Place the Server for Each MED-V Instance
|
||||||
|
|
||||||
|
|
||||||
|
The MED-V server implements policies and stores state and history data about its clients.
|
||||||
|
|
||||||
|
### Form Factor
|
||||||
|
|
||||||
|
MED-V recommends using a 2.8-GHz dual core CPU server with 2 GB of RAM. This recommendation is based on the assumption that the MED-V server will run on a dedicated machine and that SQL Server and the MED-V management console will run on separate machines.
|
||||||
|
|
||||||
|
Given this workload, the MED-V server should be relatively lightly loaded. In the absence of specific architectural guidance on the server form factor, design the server using the MED-V recommendation, with memory that matches the organization’s standard form factor. The MED-V server can be run on a virtual machine (VM) on Windows Server 2008 Hyper-V. If a VM will be used, ensure that it has access to CPU and memory resources equivalent to those specified for a physical machine.
|
||||||
|
|
||||||
|
The disk capacity the MED-V server requires must be sufficient to store the MED-V workspace configuration files. A MED-V workspace can only use one VM, and one policy, for one or more users. Therefore, the number of MED-V workspaces that must be stored depends on the degree to which different policies are required for different users of the same VM, as well as the number of VMs that will be used. The MED-V workspace XML files are around 30 KB in size for a typical MED-V workspace. To determine the required disk capacity, multiply 30 KB by the number of MED-V workspaces that the MED-V server will store.
|
||||||
|
|
||||||
|
The MED-V server’s most important network connections are the links to its clients, therefore place the server in a network location that provides the most available bandwidth and the most robust links to its clients.
|
||||||
|
|
||||||
|
### Fault Tolerance
|
||||||
|
|
||||||
|
There can only be one active MED-V server in a MED-V instance, and MED-V does not include standard capabilities to place the server in a Microsoft Cluster Server (MSCS) cluster to provide fault tolerance. A passive backup server can be manually configured.
|
||||||
|
|
||||||
|
To decide whether a passive backup server should be manually configured for the MED-V instance, determine whether users will be permitted to use the MED-V images in offline mode. For information on offline mode, see [How to Configure a Domain User or Group](how-to-configure-a-domain-user-or-groupmedvv2.md). If users are not allowed to work offline, they will be unable to continue working in the event of a MED-V server failure, even if the MED-V workspace has already been started on the client. If offline work is permitted, for each MED-V workspace, determine how long the client is allowed to work offline before it must authenticate. This is the maximum amount of time that the server can be unavailable.
|
||||||
|
|
||||||
|
## Design and Place the SQL Server Database
|
||||||
|
|
||||||
|
|
||||||
|
The MED-V server uses the SQL Server database to store client status and events. You can install the SQL Server database on the same machine as the MED-V server or you can place it on a separate server running SQL Server, which can optionally be remote. You can share the database with other MED-V instances, in which case events and alerts from those instances will be stored in the same database, and reports will include events from all instances. You can install the database in an existing SQL Server instance, and the databases of other MED-V servers can reside in that same instance.
|
||||||
|
|
||||||
|
If you place the database server in a location that is remote from the MED-V server, across networks links that do not have sufficient bandwidth available, reports may be slow to load in the console and may not display the latest data from clients. Refer to the organization service level expectations that you determined in [Define the Project Scope](define-the-project-scope.md) and use that information to decide where to place the SQL Server database.
|
||||||
|
|
||||||
|
### Form Factor
|
||||||
|
|
||||||
|
If you will run SQL Server on the same server as MED-V, and if SQL Server will only be used to store data for that server, start with the MED-V recommendation and add resources for the SQL Server load. If SQL Server will store events and alerts from more than one MED-V instance, for information on how to scale up the server form factor, see the [Infrastructure Planning and Design Microsoft SQL Server 2008](http://go.microsoft.com/fwlink/?LinkId=163302) guide (http:// go.microsoft.com/fwlink/?LinkId=163302).
|
||||||
|
|
||||||
|
The size of the database depends on the number of client events that the database will store. Events are created by normal operation of the client, such as when a MED-V workspace is started, or when there is an error in the MED-V workspace. The default interval at which the client sends events is 1 minute.
|
||||||
|
|
||||||
|
To estimate the size of the database, determine the following:
|
||||||
|
|
||||||
|
- Number of clients in the MED-V instance. The maximum is 5,000.
|
||||||
|
|
||||||
|
- Typical event arrival rate. This rate depends on client usage behavior but is approximately 15 to 20 events per day per client.
|
||||||
|
|
||||||
|
- Event size. The size is typically around 200 bytes.
|
||||||
|
|
||||||
|
- Storage amount. The number of days for which events will be stored.
|
||||||
|
|
||||||
|
Multiply these values together to calculate the size of the required data storage in bytes, and then add a safety factor to account for the following:
|
||||||
|
|
||||||
|
- Errors, which could create a large number of events from a client in a short period of time.
|
||||||
|
|
||||||
|
- Database table and organizational space.
|
||||||
|
|
||||||
|
To approximate the infrastructure optimization per second (IOPs) requirement, use the above values, multiplying the typical event arrival rate by the number of clients in the instance. This yields the number of records that can be written per day. Divide that number by 86,400 to derive the number of records written per second. If a write operations can be equated with a single infrastructure optimization (IO) operation, this number is the write IOPs required. Add a buffer to that for reporting activity. This is difficult to determine but depends on the number of consoles in use with the instance and the frequency with which they are used to generate reports.
|
||||||
|
|
||||||
|
### Fault Tolerance
|
||||||
|
|
||||||
|
When MED-V client is running, if the server is unavailable, events will be backed up on the client and reports will be unavailable in the management console. Refer to the organization’s service level expectations determined in [Define the Project Scope](define-the-project-scope.md) to decide whether the design of a fault-tolerant SQL Server infrastructure is necessary.
|
||||||
|
|
||||||
|
MED-V does not provide support for running SQL Server in an MSCS cluster. In order to provide warm standby and to avoid data loss in the event of a failure, you can place SQL Server in a log shipping configuration. For information on log shipping, see the [Infrastructure Planning and Design Microsoft SQL Server 2008](http://go.microsoft.com/fwlink/?LinkId=163302) guide (http://go.microsoft.com/fwlink/?LinkId=163302).
|
||||||
|
|
||||||
|
## Design the Management Console
|
||||||
|
|
||||||
|
|
||||||
|
Part of the functionality of the MED-V management console is to test VMs before they are packed for distribution to MED-V clients. Therefore, the management console should be designed with a form factor that resembles, as closely as possible, the form factor of a typical MED-V client machine.
|
||||||
|
|
||||||
|
The management console application is installed together with the MED-V client and uses Microsoft Virtual PC 2007 SP1 with the hotfix that is described in Microsoft Knowledge Base article 974918. A client operating system must be used; the MED-V management console cannot run on the same system as the MED-V server.
|
||||||
|
|
||||||
|
You cannot share a management console with multiple MED-V server instances. The address of the MED-V server is specified during the installation of the management console’s MED-V client; this can be changed after installation, but at any time the management console can only work with a single MED-V server.
|
||||||
|
|
||||||
|
You can use multiple management consoles with a single MED-V server. To avoid conflicts, a mechanism is available that notifies other console users when one console has made changes to a MED-V workspace.
|
||||||
|
|
||||||
|
For each MED-V instance, determine how many management consoles will be needed and where they will be placed. Select a typical MED-V client form factor to be used for the management console.
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[MED-V 1.0 SP1 Supported Configurations](med-v-10-sp1-supported-configurationsmedv-10-sp1.md)
|
||||||
|
|
||||||
|
[Configuring MED-V Server for Cluster Mode](configuring-med-v-server-for-cluster-mode.md)
|
||||||
|
|
||||||
|
[How to Install MED-V Client and MED-V Management Console](how-to-install-med-v-client-and-med-v-management-console.md)
|
||||||
|
|
||||||
|
[Using the MED-V Management Console User Interface](using-the-med-v-management-console-user-interface.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,87 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,41 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,50 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,64 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,42 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,43 +0,0 @@
|
|||||||
---
|
|
||||||
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
|
|
||||||
|
|
||||||
|
|
||||||
<a href="" id="example-med-v-environment-planning-checklist"></a>[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.
|
|
||||||
|
|
||||||
<a href="" id="example-med-v-project-planning-checklist"></a>[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.
|
|
||||||
|
|
||||||
<a href="" id="example-med-v-system-installation-checklist"></a>[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.
|
|
||||||
|
|
||||||
<a href="" id="example-med-v-image-preparation-checklist"></a>[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.
|
|
||||||
|
|
||||||
<a href="" id="example-med-v-workspace-deployment-checklist"></a>[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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,53 +0,0 @@
|
|||||||
---
|
|
||||||
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.
|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Step</th>
|
|
||||||
<th align="left">Reference</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Review the components of a MED-V deployment.</p></td>
|
|
||||||
<td align="left"><p>[High-Level Architecture](high-level-architecturemedv2.md)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Ensure that your computing environment meets the supported configurations required for installing MED-V 2.0.</p></td>
|
|
||||||
<td align="left"><p>[MED-V 2.0 Supported Configurations](med-v-20-supported-configurations.md)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Determine how you want to design your MED-V deployment.</p></td>
|
|
||||||
<td align="left"><p>[Define and Plan your MED-V Deployment](define-and-plan-your-med-v-deployment.md)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Review the list of best practices for ensuring that your MED-V deployment environment is more secure.</p></td>
|
|
||||||
<td align="left"><p>[Security and Protection for MED-V](security-and-protection-for-med-v.md)</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,49 +0,0 @@
|
|||||||
---
|
|
||||||
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.
|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Step</th>
|
|
||||||
<th align="left">Reference</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Create a virtual machine that is running Windows XP SP3 with updates and additions.</p></td>
|
|
||||||
<td align="left"><p>[Creating a Windows Virtual PC Image for MED-V](creating-a-windows-virtual-pc-image-for-med-v.md)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Install any predeployment software that you want on the MED-V image.</p></td>
|
|
||||||
<td align="left"><p>[Installing Applications on a Windows Virtual PC Image](installing-applications-on-a-windows-virtual-pc-image.md)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Package the MED-V image by using Sysprep.</p></td>
|
|
||||||
<td align="left"><p>[Configuring a Windows Virtual PC Image for MED-V](configuring-a-windows-virtual-pc-image-for-med-v.md)</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,53 +0,0 @@
|
|||||||
---
|
|
||||||
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.
|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Step</th>
|
|
||||||
<th align="left">Reference</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Determine how you can use MED-V to help solve your application compatibility issues.</p></td>
|
|
||||||
<td align="left"><p>[Planning for Application Operating System Compatibility](planning-for-application-operating-system-compatibility.md)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Plan an end-to-end deployment scenario for your organization.</p></td>
|
|
||||||
<td align="left"><p>[End-to-End Planning Scenario for MED-V 2.0](end-to-end-planning-scenario-for-med-v-20.md)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Define the project scope by defining the end users and determining the MED-V images to be managed.</p></td>
|
|
||||||
<td align="left"><p>[Define and Plan your MED-V Deployment](define-and-plan-your-med-v-deployment.md)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Review the list of best practices for ensuring that your MED-V deployment is more secure.</p></td>
|
|
||||||
<td align="left"><p>[Security and Protection for MED-V](security-and-protection-for-med-v.md)</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,53 +0,0 @@
|
|||||||
---
|
|
||||||
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.
|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Step</th>
|
|
||||||
<th align="left">Reference</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Ensure that your computing environment meets the supported configurations that are required for installing MED-V 2.0.</p></td>
|
|
||||||
<td align="left"><p>[MED-V 2.0 Supported Configurations](med-v-20-supported-configurations.md)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Plan and design the MED-V deployment.</p></td>
|
|
||||||
<td align="left"><p>[Planning for MED-V](planning-for-med-v.md)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Verify that the required installation prerequisites are configured.</p></td>
|
|
||||||
<td align="left"><p>[Configure Installation Prerequisites](configure-installation-prerequisites.md)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Install the MED-V Host Agent and MED-V Workspace Packager.</p></td>
|
|
||||||
<td align="left"><p>[Deploy the MED-V Components](deploy-the-med-v-components.md)</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,53 +0,0 @@
|
|||||||
---
|
|
||||||
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.
|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Step</th>
|
|
||||||
<th align="left">Reference</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Prepare the MED-V image for deployment.</p></td>
|
|
||||||
<td align="left"><p>[Prepare a MED-V Image](prepare-a-med-v-image.md)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Create the MED-V workspace deployment package.</p></td>
|
|
||||||
<td align="left"><p>[Create a MED-V Workspace Package](create-a-med-v-workspace-package.md)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Test the MED-V workspace installer package.</p></td>
|
|
||||||
<td align="left"><p>[Testing the MED-V Workspace Package](testing-the-med-v-workspace-package.md)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Deploy the MED-V workspace installer package.</p></td>
|
|
||||||
<td align="left"><p>[Deploying the MED-V Workspace Package](deploying-the-med-v-workspace-package.md)</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
66
mdop/medv-v1/examples-of-virtual-machine-configurationsv2.md
Normal file
66
mdop/medv-v1/examples-of-virtual-machine-configurationsv2.md
Normal file
@ -0,0 +1,66 @@
|
|||||||
|
---
|
||||||
|
title: Examples of Virtual Machine Configurations
|
||||||
|
description: Examples of Virtual Machine Configurations
|
||||||
|
ms.assetid: 5937601e-41ab-4ca2-8fa1-3c9154710cd6
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# Examples of Virtual Machine Configurations
|
||||||
|
|
||||||
|
|
||||||
|
The following are examples of typical virtual machine configurations: one in a persistent MED-V workspace and one in a revertible MED-V workspace.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
These examples are not intended for use in all environments. Adjust the configuration according to your environment.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**To configure a typical domain setup in a persistent MED-V workspace**
|
||||||
|
|
||||||
|
1. Configure Sysprep on the base image to create a unique SID. For more information, see [Creating a Virtual PC Image for MED-V](creating-a-virtual-pc-image-for-med-v.md#bkmk-howtoconfiguresysprepformedvimages).
|
||||||
|
|
||||||
|
2. On the **VM Setup** tab, select the **Run VM Setup** check box.
|
||||||
|
|
||||||
|
3. In the **VM Computer Name Pattern** section, configure the pattern for the machine image name. For more information, see [How to Configure VM Computer Name Pattern Properties](how-to-configure-vm-computer-name-pattern-propertiesmedvv2.md).
|
||||||
|
|
||||||
|
4. Click **Script Editor**, and in the **VM Setup Script Editor** dialog box, configure the following actions:
|
||||||
|
|
||||||
|
1. **Rename Computer**
|
||||||
|
|
||||||
|
2. **Restart Windows**
|
||||||
|
|
||||||
|
3. **Check Connectivity**
|
||||||
|
|
||||||
|
4. **Join Domain**
|
||||||
|
|
||||||
|
5. **Disable Auto-Logon**
|
||||||
|
|
||||||
|
For more information, see [How to Set Up Script Actions](how-to-set-up-script-actions.md).
|
||||||
|
|
||||||
|
5. On the **Policy** menu, click **Commit**.
|
||||||
|
|
||||||
|
**To configure a typical setup in a revertible workspace**
|
||||||
|
|
||||||
|
1. On the **VM Setup** tab, select the **Rename the VM based on the computer name pattern** check box.
|
||||||
|
|
||||||
|
2. In the **VM Computer Name Pattern** section, configure the pattern for the machine image name. For more information, see [How to Configure VM Computer Name Pattern Properties](how-to-configure-vm-computer-name-pattern-propertiesmedvv2.md).
|
||||||
|
|
||||||
|
3. On the **Policy** menu, click **Commit**.
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[How to Configure the Virtual Machine Setup for a MED-V Workspace](how-to-configure-the-virtual-machine-setup-for-a-med-v-workspacemedvv2.md)
|
||||||
|
|
||||||
|
[How to Configure VM Computer Name Pattern Properties](how-to-configure-vm-computer-name-pattern-propertiesmedvv2.md)
|
||||||
|
|
||||||
|
[How to Set Up Script Actions](how-to-set-up-script-actions.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
33
mdop/medv-v1/getting-started-with-med-v.md
Normal file
33
mdop/medv-v1/getting-started-with-med-v.md
Normal file
@ -0,0 +1,33 @@
|
|||||||
|
---
|
||||||
|
title: Getting Started with MED-V
|
||||||
|
description: Getting Started with MED-V
|
||||||
|
ms.assetid: 5832cdb3-3892-4048-b29d-7644e75117f0
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# Getting Started with MED-V
|
||||||
|
|
||||||
|
|
||||||
|
This section provides general information for administrators using Microsoft Enterprise Desktop Virtualization (MED-V) 1.0 and MED-V 1.0 SP1.
|
||||||
|
|
||||||
|
## In This Section
|
||||||
|
|
||||||
|
|
||||||
|
<a href="" id="overview-of-med-v"></a>[Overview of MED-V](overview-of-med-v.md)
|
||||||
|
|
||||||
|
<a href="" id="high-level-architecture"></a>[High-Level Architecture](high-level-architecturemedv.md)
|
||||||
|
|
||||||
|
<a href="" id="key-scenarios-for-using-med-v"></a>[Key Scenarios for Using MED-V](key-scenarios-for-using-med-v.md)
|
||||||
|
|
||||||
|
<a href="" id="about-med-v-1-0"></a>[About MED-V 1.0](about-med-v-10.md)
|
||||||
|
|
||||||
|
<a href="" id="about-med-v-1-0-sp1"></a>[About MED-V 1.0 SP1](about-med-v-10-sp1.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,40 +0,0 @@
|
|||||||
---
|
|
||||||
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
|
|
||||||
|
|
||||||
|
|
||||||
<a href="" id="overview-of-med-v"></a>[Overview of MED-V](overview-of-med-vmedv2.md)
|
|
||||||
Provides general information about the MED-V solution to your application compatibility issues.
|
|
||||||
|
|
||||||
<a href="" id="planning-for-application-operating-system-compatibility"></a>[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.
|
|
||||||
|
|
||||||
<a href="" id="high-level-architecture"></a>[High-Level Architecture](high-level-architecturemedv2.md)
|
|
||||||
Describes the components of a MED-V deployment.
|
|
||||||
|
|
||||||
<a href="" id="about-med-v-2-0"></a>[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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
40
mdop/medv-v1/high-level-architecturemedv.md
Normal file
40
mdop/medv-v1/high-level-architecturemedv.md
Normal file
@ -0,0 +1,40 @@
|
|||||||
|
---
|
||||||
|
title: High-Level Architecture
|
||||||
|
description: High-Level Architecture
|
||||||
|
ms.assetid: a78e12ad-5aa6-40e0-ae8b-51acaf005712
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# High-Level Architecture
|
||||||
|
|
||||||
|
|
||||||
|
The MED-V solution comprises the following elements:
|
||||||
|
|
||||||
|
- **Administrator-defined virtual machine**—Encapsulates a full desktop environment, including an operating system, applications, and optional management and security tools.
|
||||||
|
|
||||||
|
- **Image repository**—Stores all virtual images on a standard IIS server and enables virtual images version management, client-authenticated image retrieval, and efficient download (of a new image or updates) via Trim Transfer technology.
|
||||||
|
|
||||||
|
- **Management server**—Associates virtual images from the image repository along with administrator usage policies to Active Directory® users or groups. The management server also aggregates clients' events and stores them in an external database (Microsoft SQL Server®) for monitoring and reporting purposes.
|
||||||
|
|
||||||
|
- **Management console**—Enables administrators to control the management server and the image repository.
|
||||||
|
|
||||||
|
- **End-user client**
|
||||||
|
|
||||||
|
1. Virtual image life-cycle—Authentication, image retrieval, enforcement of usage policies.
|
||||||
|
|
||||||
|
2. Virtual machine session management—Start, stop, lock the virtual machine.
|
||||||
|
|
||||||
|
3. Single desktop experience—Applications installed in the virtual machine seamlessly available through the standard desktop Start menu and integrated with other applications on the user desktop.
|
||||||
|
|
||||||
|
All communication between the client and the servers (management server and image repository) is carried on top of a standard HTTP or HTTPS channel.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,72 +0,0 @@
|
|||||||
---
|
|
||||||
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:
|
|
||||||
|
|
||||||
<a href="" id="---------------med-v-host"></a> **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.
|
|
||||||
|
|
||||||
<a href="" id="-------------------med-v-host-agent"></a> **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.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
<a href="" id="esd-system"></a>**ESD System**
|
|
||||||
Your existing software distribution method that lets you deploy and install the MED-V workspace package files that MED-V creates.
|
|
||||||
|
|
||||||
<a href="" id="registry-management-system"></a>**Registry Management System**
|
|
||||||
Your existing method of managing Group Policy settings and preferences.
|
|
||||||
|
|
||||||
<a href="" id="windows-virtual-pc-image"></a>**Windows Virtual PC Image**
|
|
||||||
An administrator-defined virtual machine that contains the following components:
|
|
||||||
|
|
||||||
<a href="" id="corporate-operating-system"></a>**Corporate Operating System**
|
|
||||||
Your standard corporate operating system.
|
|
||||||
|
|
||||||
<a href="" id="management-and-security-tools"></a>**Management and Security Tools**
|
|
||||||
Your standard management and security tools, such as virus protection.
|
|
||||||
|
|
||||||
<a href="" id="-----------------------med-v-guest"></a> **MED-V Guest**
|
|
||||||
A Windows XP SP3 environment, as part of a Windows Virtual PC running on Windows 7 that contains the following components:
|
|
||||||
|
|
||||||
<a href="" id="---------------------------med-v-guest-agent"></a> **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.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
<a href="" id="esd-client"></a>**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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,67 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -0,0 +1,99 @@
|
|||||||
|
---
|
||||||
|
title: How to Apply General Settings to a MED-V Workspace
|
||||||
|
description: How to Apply General Settings to a MED-V Workspace
|
||||||
|
ms.assetid: 6152dced-e301-4fa2-bfa0-aecf3c23f23a
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Apply General Settings to a MED-V Workspace
|
||||||
|
|
||||||
|
|
||||||
|
The general settings enable you to configure the basic user experience when working with a MED-V workspace, by defining whether the MED-V workspace will appear in seamless integration or full desktop mode. Seamless integration includes legacy applications in the host desktop so that they appear as if they are installed directly on the host. Full desktop presents the desktop of the MED-V workspace operating system in a separate window on the host.
|
||||||
|
|
||||||
|
All general settings are configured in the **Policy** module, on the **General** tab.
|
||||||
|
|
||||||
|
**To apply general settings to a MED-V workspace**
|
||||||
|
|
||||||
|
1. Click the MED-V workspace to configure.
|
||||||
|
|
||||||
|
2. Configure the general properties as described in the following table.
|
||||||
|
|
||||||
|
3. On the **Policy** menu, select **Commit**.
|
||||||
|
|
||||||
|
**General Workspace Properties**
|
||||||
|
|
||||||
|
Property
|
||||||
|
Description
|
||||||
|
*Workspace Properties*
|
||||||
|
|
||||||
|
Name
|
||||||
|
|
||||||
|
The name of the MED-V workspace.
|
||||||
|
|
||||||
|
**Warning**
|
||||||
|
Do not rename an existing MED-V workspace while it is running on a client computer.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Description
|
||||||
|
|
||||||
|
Description of the MED-V workspace, which can include the content or status of the MED-V workspace and any other useful information.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
The description is for administrator use and has no impact on the policy.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Support contact info
|
||||||
|
|
||||||
|
The contact information for technical support. The information entered will be displayed in the support contact information screen that can be accessed from the MED-V client notification area.
|
||||||
|
|
||||||
|
*Workspace UI*
|
||||||
|
|
||||||
|
Seamless Integration
|
||||||
|
|
||||||
|
Select this option for the MED-V workspace windows, taskbar, and notification area icons to integrate seamlessly into the host desktop.
|
||||||
|
|
||||||
|
Draw a frame around each workspace window
|
||||||
|
|
||||||
|
When using seamless integration, select this option to create a colored border around all applications running within the MED-V workspace and a colored background for all taskbar button icons. In the **Frame color** field, select the color.
|
||||||
|
|
||||||
|
Full Desktop
|
||||||
|
|
||||||
|
Select this option to display the MED-V workspace as the entire desktop, without integrating with the host.
|
||||||
|
|
||||||
|
*Host Verification*
|
||||||
|
|
||||||
|
Command line
|
||||||
|
|
||||||
|
Type a command line to run on the host before starting the MED-V workspace.
|
||||||
|
|
||||||
|
Do not start the Workspace if the verification fails (exit code is not '0')
|
||||||
|
|
||||||
|
Select this check box if you are using a command line and want to start the MED-V workspace only if the script is completed successfully.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
A command line can be run on the host prior to starting the MED-V workspace.
|
||||||
|
|
||||||
|
**To run a command line before starting a MED-V workspace**
|
||||||
|
|
||||||
|
1. In the **Command line** field, enter a command line.
|
||||||
|
|
||||||
|
2. To start the MED-V workspace only if the command line was successful, select the **Do not start the workspace if the verification fails** check box.
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[Using the MED-V Management Console User Interface](using-the-med-v-management-console-user-interface.md)
|
||||||
|
|
||||||
|
[Creating a MED-V Workspace](creating-a-med-v-workspacemedv-10-sp1.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -0,0 +1,81 @@
|
|||||||
|
---
|
||||||
|
title: How to Apply Network Settings to a MED-V Workspace
|
||||||
|
description: How to Apply Network Settings to a MED-V Workspace
|
||||||
|
ms.assetid: 641f46b3-a56f-478a-823b-1d90aa1716b3
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Apply Network Settings to a MED-V Workspace
|
||||||
|
|
||||||
|
|
||||||
|
Administrators can define the network settings for each MED-V workspace.
|
||||||
|
|
||||||
|
All network settings are configured in the **Policy** module, on the **Network** tab.
|
||||||
|
|
||||||
|
**To apply network settings to a MED-V workspace**
|
||||||
|
|
||||||
|
1. Click the MED-V workspace to configure.
|
||||||
|
|
||||||
|
2. In the **Network** pane, configure the settings as described in the following table.
|
||||||
|
|
||||||
|
3. On the **Policy** menu, select **Commit**.
|
||||||
|
|
||||||
|
**MED-V Workspace Network Properties**
|
||||||
|
|
||||||
|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="50%" />
|
||||||
|
<col width="50%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead>
|
||||||
|
<tr class="header">
|
||||||
|
<th align="left">Property</th>
|
||||||
|
<th align="left">Description</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>TCP/IP Properties</p></td>
|
||||||
|
<td align="left"><ul>
|
||||||
|
<li><p><strong>Use host's IP address (NAT)</strong>—The workspace will use NAT to share the host's IP for outgoing traffic.</p></li>
|
||||||
|
<li><p><strong>Use different IP address than host (Bridge)</strong>—The MED-V workspace will have its own network address, usually obtained via DHCP.</p></li>
|
||||||
|
</ul>
|
||||||
|
<p>Select the <strong>Map multiple adapters into Workspace</strong> check box when the host computer has multiple adapters. It is recommended to use this configuration when the host moves between different networks using different adapters.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>DNS Server</p></td>
|
||||||
|
<td align="left"><ul>
|
||||||
|
<li><p><strong>Don't change</strong>—DNS settings that are set within the MED-V workspace virtual machine will not be changed.</p></li>
|
||||||
|
<li><p><strong>Use Host's DNS address</strong>—MED-V workspace DNS settings will be synchronized to match the host's settings. The DNS synchronization is dynamic. It is synchronized periodically with the host so that if it is changed on the host, it will change dynamically in the MED-V workspace.</p></li>
|
||||||
|
<li><p><strong>Use specific DNS addresses</strong>—The MED-V workspace will use a specific DNS, as specified.</p>
|
||||||
|
<p>In the <strong>Primary</strong> and <strong>Secondary</strong> fields, enter the primary and secondary DNS addresses.</p>
|
||||||
|
<p>Select the <strong>Append Host's DNS addresses</strong> check box to append the host to the configured DNS addresses.</p></li>
|
||||||
|
</ul></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Assign DNS Suffixes</p></td>
|
||||||
|
<td align="left"><ul>
|
||||||
|
<li><p><strong>Assign the following suffixes</strong>—Select this check box to assign specific DNS suffixes; in the box, enter a suffix or multiple suffixes separated by commas.</p></li>
|
||||||
|
<li><p><strong>Append host suffixes</strong>—Select this check box to append the host suffixes to the DNS address.</p></li>
|
||||||
|
</ul></td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[Creating a MED-V Workspace](creating-a-med-v-workspacemedv-10-sp1.md)
|
||||||
|
|
||||||
|
[Using the MED-V Management Console User Interface](using-the-med-v-management-console-user-interface.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -0,0 +1,66 @@
|
|||||||
|
---
|
||||||
|
title: How to Apply Performance Settings to a MED-V Workspace
|
||||||
|
description: How to Apply Performance Settings to a MED-V Workspace
|
||||||
|
ms.assetid: e0fed1e1-6e8f-4d65-ab83-b950a17661c0
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Apply Performance Settings to a MED-V Workspace
|
||||||
|
|
||||||
|
|
||||||
|
The following performance setting can be defined for each MED-V workspace:
|
||||||
|
|
||||||
|
VM memory allocation
|
||||||
|
|
||||||
|
Performance settings are configured in the **Policy** module, on the **Performance** tab.
|
||||||
|
|
||||||
|
**To apply performance settings to a MED-V workspace**
|
||||||
|
|
||||||
|
1. Click the MED-V workspace to configure.
|
||||||
|
|
||||||
|
2. In the **Performance** pane, configure the settings as described in the following table.
|
||||||
|
|
||||||
|
3. On the **Policy** menu, select **Commit**.
|
||||||
|
|
||||||
|
**Performance Settings Properties**
|
||||||
|
|
||||||
|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="50%" />
|
||||||
|
<col width="50%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead>
|
||||||
|
<tr class="header">
|
||||||
|
<th align="left">Property</th>
|
||||||
|
<th align="left">Description</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Adjust VM memory, based on amount of the Host machine's physical memory</p></td>
|
||||||
|
<td align="left"><p>Select this check box, and configure the following virtual machine properties in the table:</p>
|
||||||
|
<ul>
|
||||||
|
<li><p><strong>Host Memory</strong>—Define the common host RAM configuration in your organization based on any numbers of groups to configure.</p></li>
|
||||||
|
<li><p><strong>VM Memory</strong>—Enter the amount of host memory to allocate to the virtual machine.</p></li>
|
||||||
|
</ul></td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[Creating a MED-V Workspace](creating-a-med-v-workspacemedv-10-sp1.md)
|
||||||
|
|
||||||
|
[Using the MED-V Management Console User Interface](using-the-med-v-management-console-user-interface.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -0,0 +1,148 @@
|
|||||||
|
---
|
||||||
|
title: How to Apply Virtual Machine Settings to a MED-V Workspace
|
||||||
|
description: How to Apply Virtual Machine Settings to a MED-V Workspace
|
||||||
|
ms.assetid: b50d0dfb-8d61-4543-9607-a29bbb1ed45f
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Apply Virtual Machine Settings to a MED-V Workspace
|
||||||
|
|
||||||
|
|
||||||
|
Every MED-V workspace must have a Microsoft Virtual PC image associated with it. The virtual machine settings enable you to assign a Virtual PC image as well as set other virtual machine properties.
|
||||||
|
|
||||||
|
All virtual machine settings are configured in the **Policy** module, on the **Virtual Machine Settings** tab.
|
||||||
|
|
||||||
|
**To apply virtual machine settings to a MED-V workspace**
|
||||||
|
|
||||||
|
1. Click the MED-V workspace to configure.
|
||||||
|
|
||||||
|
2. Configure the virtual machine properties as described in the following table.
|
||||||
|
|
||||||
|
3. On the **Policy** menu, select **Commit**.
|
||||||
|
|
||||||
|
**Virtual Machine Properties**
|
||||||
|
|
||||||
|
Property
|
||||||
|
Description
|
||||||
|
*Virtual Machine Settings*
|
||||||
|
|
||||||
|
Assigned Image
|
||||||
|
|
||||||
|
The actual Microsoft Virtual PC image assigned to the MED-V workspace. The menu provides a list of all available Virtual PC images. The following image types are in the **Active** image list:
|
||||||
|
|
||||||
|
- **Local test images**—Images on the local computer that are not yet packed. These image names are followed by the word “test” in parentheses (test) and are for testing purposes only.
|
||||||
|
|
||||||
|
- **Local packed images**—Packed images on the local computer. These images are followed by the word “local” in parentheses (local) and cannot be downloaded by clients until the administrator uploads them to the server.
|
||||||
|
|
||||||
|
A local image can be selected if you are creating a package that will be distributed to the client via removable media (such as USB or DVD).
|
||||||
|
|
||||||
|
- **Packed images on server**—Images that are on the server and are available for download by clients. Click Refresh to refresh the images list.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
Each MED-V workspace image can only be used by one Windows user.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Workspace is persistent
|
||||||
|
|
||||||
|
Select this check box to configure the MED-V workspace as persistent. In a persistent MED-V workspace, when the MED-V workspace is stopped, changes and additions to the MED-V workspace are saved in the MED-V workspace.
|
||||||
|
|
||||||
|
For a Domain MED-V workspace, this option must be selected.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
This setting should not be changed after a MED-V workspace is deployed to users.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Shut down the VM when stopping the Workspace
|
||||||
|
|
||||||
|
Select this check box to shut down the virtual machine when stopping the MED-V workspace. If this check box is cleared, at the completion of each session, the virtual machine is not shut down but instead takes a snapshot of the virtual machine. Upon the initiation of a new session, Windows starts from the snapshot (that is, Windows does not restart and no login is required).
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
This property is enabled only if **Workspace is persistent** is selected.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Logon to Windows in VM using MED-V credentials (SSO)
|
||||||
|
|
||||||
|
Select this check box to log in to Windows on the virtual machine by using the MED-V credentials entered when logging in to MED-V client.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
This property is enabled only when **Workspace is persistent** is selected.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Workspace is revertible
|
||||||
|
|
||||||
|
Select this check box to configure the MED-V workspace as revertible. In a revertible MED-V workspace, at the completion of each session (that is, when the user stops the MED-V workspace), the MED-V workspace reverts to the original state it was in during deployment. No changes or additions that the user made are saved on the MED-V workspace between sessions.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
This setting should not be changed after a MED-V workspace is deployed to users.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Synchronize Workspace time zone with host
|
||||||
|
|
||||||
|
Select this check box to synchronize the time zone in the MED-V workspace with the host.
|
||||||
|
|
||||||
|
The synchronization works differently depending on whether the MED-V workspace is persistent or revertible, as follows:
|
||||||
|
|
||||||
|
- In a persistent MED-V workspace, the time zone first tries to synchronize with the server. If that fails, it synchronizes with the host.
|
||||||
|
|
||||||
|
- In a revertible MED-V workspace, the time zone synchronizes with the host.
|
||||||
|
|
||||||
|
*Lock Settings*
|
||||||
|
|
||||||
|
Lock the Workspace on host standby/hibernate event
|
||||||
|
|
||||||
|
Select this check box to automatically lock the MED-V workspace when the host computer goes into standby or hibernate.
|
||||||
|
|
||||||
|
Lock the Workspace after
|
||||||
|
|
||||||
|
Select this check box to lock the MED-V workspace when the MED-V workspace is idle for a specified period of time. When selected, the number box is enabled. Enter the number of minutes of idle time before locking the MED-V workspace.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
The idle time refers to the MED-V workspace applications (not the host applications).
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
*Image Update Settings*
|
||||||
|
|
||||||
|
Keep only
|
||||||
|
|
||||||
|
Select this check box to limit the number of old image versions to keep.
|
||||||
|
|
||||||
|
When selected, the number box is enabled. Enter the number of old versions to keep.
|
||||||
|
|
||||||
|
Suggest update when a new version is available
|
||||||
|
|
||||||
|
Select this check box to suggest (but not force) an update when a new version of the image is available.
|
||||||
|
|
||||||
|
Clients should use Trim Transfer when downloading images for this Workspace
|
||||||
|
|
||||||
|
Select this check box to enable Trim Transfer (for more information, see [MED-V Trim Transfer Technology](med-v-trim-transfer-technology-medvv2.md)) when downloading images associated with this MED-V workspace. If this check box is cleared, the full image will be downloaded.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
Trim Transfer requires indexing the hard drive, which might take a considerable amount of time. It is recommended to use Trim Transfer when indexing the hard drive is more efficient than downloading the new image version, such as when downloading an image version that is similar to the existing version.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[Creating a MED-V Image](86bd1301-0d0b-448a-a37c-b606d839aa0e)
|
||||||
|
|
||||||
|
[Using the MED-V Management Console User Interface](using-the-med-v-management-console-user-interface.md)
|
||||||
|
|
||||||
|
[Creating a MED-V Workspace](creating-a-med-v-workspacemedv-10-sp1.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
54
mdop/medv-v1/how-to-back-up-and-restore-a-med-v-server.md
Normal file
54
mdop/medv-v1/how-to-back-up-and-restore-a-med-v-server.md
Normal file
@ -0,0 +1,54 @@
|
|||||||
|
---
|
||||||
|
title: How to Back Up and Restore a MED-V Server
|
||||||
|
description: How to Back Up and Restore a MED-V Server
|
||||||
|
ms.assetid: 8d05e3a4-279b-4ce6-a319-8a09e7a30c60
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Back Up and Restore a MED-V Server
|
||||||
|
|
||||||
|
|
||||||
|
XML files located on the server can be backed up and then restored in case of loss of data on the server.
|
||||||
|
|
||||||
|
**To back up a MED-V server**
|
||||||
|
|
||||||
|
- Back up the following files, located in *<InstallDir>\\Servers\\ConfigurationServer*:
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
If the configuration has been changed from the default, the files might be stored in a different location.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- ClientPolicy.xml
|
||||||
|
|
||||||
|
- ClientSettings.xml
|
||||||
|
|
||||||
|
- ConfigurationFiles.xml
|
||||||
|
|
||||||
|
- OrganizationPolicy.xml
|
||||||
|
|
||||||
|
- WorkspaceKeys.xml
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
The ServerSettings.xml file can be backed up as well. However, if a specific configuration has been changed (for example, on the original server, the MED-V VMS directory is located in "*C:\\Vms*" and such a directory does not exist on the new server), it can cause an error.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**To restore a MED-V server**
|
||||||
|
|
||||||
|
1. Install a new MED-V server.
|
||||||
|
|
||||||
|
2. Copy the backup files to the following directory:
|
||||||
|
|
||||||
|
*<InstallDir>\\Servers\\ConfigurationServer*
|
||||||
|
|
||||||
|
3. Restart the MED-V service.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
151
mdop/medv-v1/how-to-configure-a-deployment-package.md
Normal file
151
mdop/medv-v1/how-to-configure-a-deployment-package.md
Normal file
@ -0,0 +1,151 @@
|
|||||||
|
---
|
||||||
|
title: How to Configure a Deployment Package
|
||||||
|
description: How to Configure a Deployment Package
|
||||||
|
ms.assetid: 748272a1-6af2-476e-a3f1-87435b8e94b1
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Configure a Deployment Package
|
||||||
|
|
||||||
|
|
||||||
|
The Packaging wizard walks you through the creation of a package by creating a folder on your local computer and transferring all the required installation files to the single folder. The contents of the folder can then be moved to multiple removable media drives for distribution.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
A single package cannot contain installation files for both x86 and x64 systems.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## How to Create a Deployment Package
|
||||||
|
|
||||||
|
|
||||||
|
**To create a deployment package**
|
||||||
|
|
||||||
|
1. Verify in the **Images** module that you have created at least one local packed image.
|
||||||
|
|
||||||
|
2. On the **Tools** menu, select **Packaging wizard**.
|
||||||
|
|
||||||
|
3. On the **Packaging wizard** welcome page, click **Next**.
|
||||||
|
|
||||||
|
4. On the **Workspace Image** page, select the **Include image in the package** check box to include an image in the package.
|
||||||
|
|
||||||
|
The **Image** field is enabled.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
An image is not required in a MED-V package; the package can be created without an image. In such a case, the image should be uploaded to the server so that it can later be downloaded over the network to the client, or pushed to an image pre-stage folder.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
5. Click the **Image** list to view all available images. Select the image to be copied to the package. Click **Refresh** to refresh the list of available images.
|
||||||
|
|
||||||
|
6. Click **Next**.
|
||||||
|
|
||||||
|
7. On the **MED-V Installation Settings** page, select the MED-V installation file by doing one of the following:
|
||||||
|
|
||||||
|
- In the **MED-V installation file** field, type the full path to the directory where the installation file is located.
|
||||||
|
|
||||||
|
- Click **...** to browse to the directory where the installation file is located.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
This field is mandatory, and the wizard will not continue without a valid file name.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
8. In the **Server address** field, type the server name or IP address.
|
||||||
|
|
||||||
|
9. In the **Server port** field, type the server port.
|
||||||
|
|
||||||
|
10. Select the **Server is accessed using https** check box to require an https connection to connect to the server.
|
||||||
|
|
||||||
|
11. Do one of the following:
|
||||||
|
|
||||||
|
- Click **Default installation settings**, and then click **Next** to continue and leave the default settings.
|
||||||
|
|
||||||
|
- Click **Custom installation settings**, and then click **Next** to customize the installation settings.
|
||||||
|
|
||||||
|
1. On the **MED-V Installation Custom Settings** page, in the **Installation folder** field, type the path of the folder where the MED-V files will be installed on the host computer.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
It is recommended to use variables in the path rather than constants, which might vary from computer to computer.
|
||||||
|
|
||||||
|
For example, use *%ProgramFiles%\\MED-V* instead of *c:\\MED-V*.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
2. In the **Virtual machines images folder** field, type the path of the folder where the virtual images files will be installed on the host computer.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
If you are using image pre-staging, this is the image pre-stage folder where the image is located.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
3. In the **Minimal required RAM** field, enter the RAM required to install a MED-V package. If the user installing the MED-V package does not have the minimal required RAM, the installation will fail.
|
||||||
|
|
||||||
|
4. Select the **Install the MED-V management application** check box to include the MED-V management console application in the installation.
|
||||||
|
|
||||||
|
5. Select the **Create a shortcut to MED-V on the desktop** check box to create a shortcut to MED-V on the host's desktop.
|
||||||
|
|
||||||
|
6. Select the **Start automatically on computer startup** check box to start MED-V automatically on startup.
|
||||||
|
|
||||||
|
7. Click **Next**.
|
||||||
|
|
||||||
|
12. On the **Additional Installations** page, select the **Include installation of virtualization software** check box to include the Virtual PC installation in the package.
|
||||||
|
|
||||||
|
The **Installation file** field is enabled. Type the full path of the virtualization software installation file, or click **...** to browse to the directory.
|
||||||
|
|
||||||
|
13. Select the **Include installation of Virtual PC QFE** check box to include Virtual PC update installation in the package.
|
||||||
|
|
||||||
|
The **Installation file** field is enabled. Type the full path of the Virtual PC update installation file, or click **...** to browse to the directory.
|
||||||
|
|
||||||
|
14. Select the **Include installation of Microsoft .NET Framework 2.0** check box to include the Microsoft .NET Framework 2.0 installation in the package.
|
||||||
|
|
||||||
|
The **Installation file** field is enabled. Type the full path of the Microsoft .NET Framework 2.0 installation file, or click **...** to browse to the directory.
|
||||||
|
|
||||||
|
15. Click **Next**.
|
||||||
|
|
||||||
|
16. On the **Finalize** page, select the location where the package should be saved by doing one of the following:
|
||||||
|
|
||||||
|
- In the **Package destination** field, type the full path to the directory where the package should be saved.
|
||||||
|
|
||||||
|
- Click **...** to browse to the directory where the installation files should be saved.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
Building the package might consume more space than the actual package size. It is therefore recommended to build the package on the hard drive. After the package is created, it can then be copied to the USB.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
17. In the **Package name** field, enter a name for the package.
|
||||||
|
|
||||||
|
18. Click **Finish** to create the package.
|
||||||
|
|
||||||
|
The package is created. This might take several minutes.
|
||||||
|
|
||||||
|
After the package is created, a message appears notifying you that it has been completed successfully.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
If you saved all the files locally, and not directly on the removable media, ensure that you copy only the contents of the folder and not the folder itself to the removable media.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
The removable media must be large enough so that the package contents consume a maximum of only three-quarters of the removable media's memory.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
When creating the package, up to double the size of the actual package size might be required when the build is complete.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[Creating a MED-V Image](creating-a-med-v-image.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
163
mdop/medv-v1/how-to-configure-a-domain-user-or-groupmedvv2.md
Normal file
163
mdop/medv-v1/how-to-configure-a-domain-user-or-groupmedvv2.md
Normal file
@ -0,0 +1,163 @@
|
|||||||
|
---
|
||||||
|
title: How to Configure a Domain User or Group
|
||||||
|
description: How to Configure a Domain User or Group
|
||||||
|
ms.assetid: 055aba81-a9c9-4b98-969d-775e603becf3
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Configure a Domain User or Group
|
||||||
|
|
||||||
|
|
||||||
|
The deployment settings enable you to control which users or groups can access the MED-V workspace, as well as how long the MED-V workspace can be utilized and whether it can be used offline. You can also configure additional rules to control access between the MED-V workspace and the host.
|
||||||
|
|
||||||
|
All MED-V workspace permissions are configured in the **Policy** module, on the **Deployment** tab.
|
||||||
|
|
||||||
|
To allow users to utilize the MED-V workspace, you must first add domain users or groups to the MED-V workspace permissions. You can then set permissions for each user or group.
|
||||||
|
|
||||||
|
## How to Add a Domain User or Group
|
||||||
|
|
||||||
|
|
||||||
|
**To add a domain user or group**
|
||||||
|
|
||||||
|
1. In the **Users / Groups** window, click **Add.**
|
||||||
|
|
||||||
|
2. In the **Enter User or Group names** dialog box, select domain users or groups by doing one of the following:
|
||||||
|
|
||||||
|
- In the **Enter User or Group names** field, type a user or group that exists in the domain or as a local user or group on the computer. Then click **Check Names** to resolve it to the full existent name.
|
||||||
|
|
||||||
|
- Click **Find** to open the standard **Select Users or Groups** dialog box. Then select domain users or groups.
|
||||||
|
|
||||||
|
3. Click **OK**.
|
||||||
|
|
||||||
|
The domain users or groups are added.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
Users from trusted domains should be added manually.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**Warning**
|
||||||
|
Do not run the management application from a computer that is part of a domain that is not trusted by the domain the server is installed on.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## How to Remove a Domain User or Group
|
||||||
|
|
||||||
|
|
||||||
|
**To remove a domain user or group**
|
||||||
|
|
||||||
|
1. In the **Users / Groups** window, select a user or group.
|
||||||
|
|
||||||
|
2. Click **Remove**.
|
||||||
|
|
||||||
|
The user or group is deleted.
|
||||||
|
|
||||||
|
## How to Set Permissions for a User or a Group
|
||||||
|
|
||||||
|
|
||||||
|
**To set permissions for a user or a group**
|
||||||
|
|
||||||
|
1. Click the user or group for which you are setting the permissions.
|
||||||
|
|
||||||
|
2. Configure the MED-V workspace properties as described in the following table.
|
||||||
|
|
||||||
|
3. On the **Policy** menu, select **Commit**.
|
||||||
|
|
||||||
|
**Workspace Deployment Properties**
|
||||||
|
|
||||||
|
Property
|
||||||
|
Description
|
||||||
|
*General*
|
||||||
|
|
||||||
|
Enable Workspace for <user or group>
|
||||||
|
|
||||||
|
Select this check box to enable the MED-V workspace for this user or group.
|
||||||
|
|
||||||
|
Workspace expires on this date
|
||||||
|
|
||||||
|
Select this check box to assign an expiration date for the permissions set for this user or group.
|
||||||
|
|
||||||
|
When selected, the date box is enabled. Set the date, and permissions will expire at the end of the date specified.
|
||||||
|
|
||||||
|
Offline work is restricted to
|
||||||
|
|
||||||
|
Select this check box to assign a time period in which the policy must be refreshed for this user or group. When selected, the time period box is enabled. Set the number of days or hours, and at the end of the specified time period, the user or group will not be able to connect if the policy is not refreshed.
|
||||||
|
|
||||||
|
Workspace deletion options
|
||||||
|
|
||||||
|
Click to set the MED-V workspace deletion options. For more information, see [How to Set MED-V Workspace Deletion Options](how-to-set-med-v-workspace-deletion-options.md).
|
||||||
|
|
||||||
|
*Data Transfer*
|
||||||
|
|
||||||
|
Support clipboard between host and Workspace
|
||||||
|
|
||||||
|
Select this check box to enable copying and pasting between the host and the MED-V workspace.
|
||||||
|
|
||||||
|
Support file transfer between the host and Workspace
|
||||||
|
|
||||||
|
Select this check box to enable transferring files between the host and MED-V workspace. Select one of the following options from the **File Transfer** box:
|
||||||
|
|
||||||
|
- **Both**—Enable transferring files between the host and the MED-V workspace.
|
||||||
|
|
||||||
|
- **Host to Workspace**—Enable transferring files from the host to the MED-V workspace.
|
||||||
|
|
||||||
|
- **Workspace to Host**—Enable transferring files from the MED-V workspace to the host.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
If a user without permissions attempts to transfer files, a window will appear prompting him to enter the credentials of a user with permissions to perform the file transfer.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**Important**
|
||||||
|
To support file transfer in Windows XP SP3, you must disable offline file synchronization by editing the registry as follows:
|
||||||
|
|
||||||
|
`REG ADD HKLM\software\microsoft\windows\currentversion\netcache /V Enabled /T REG_DWORD /F /D 0`
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Advanced
|
||||||
|
|
||||||
|
Click to set the advanced file transfer options. For more information, see [How to Set Advanced File Transfer Options](how-to-set-advanced-file-transfer-options.md).
|
||||||
|
|
||||||
|
*Device Control*
|
||||||
|
|
||||||
|
Enable printing to printers connected to the host
|
||||||
|
|
||||||
|
Select this check box to enable users to print from the MED-V workspace using the host printer.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
The printing is performed by the printers defined on the host.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Enable access to CD / DVD
|
||||||
|
|
||||||
|
Select this check box to allow access to a CD or DVD drive from this MED-V workspace.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**Multiple Memberships**
|
||||||
|
|
||||||
|
1. If the user is part of a group and permissions are applied to the user as well as to the group they are part of, all permissions are applied.
|
||||||
|
|
||||||
|
2. If the user is a member of two different groups, the least restrictive permissions are applied.
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[Using the MED-V Management Console User Interface](using-the-med-v-management-console-user-interface.md)
|
||||||
|
|
||||||
|
[Creating a MED-V Workspace](creating-a-med-v-workspacemedv-10-sp1.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)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
116
mdop/medv-v1/how-to-configure-image-pre-staging.md
Normal file
116
mdop/medv-v1/how-to-configure-image-pre-staging.md
Normal file
@ -0,0 +1,116 @@
|
|||||||
|
---
|
||||||
|
title: How to Configure Image Pre-staging
|
||||||
|
description: How to Configure Image Pre-staging
|
||||||
|
ms.assetid: 92781b5a-208f-45a4-a078-ee90cf9efd9d
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Configure Image Pre-staging
|
||||||
|
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
Image pre-staging is useful only for the initial image download. It is not supported for image update.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## How to Configure Image Pre-staging
|
||||||
|
|
||||||
|
|
||||||
|
**To configure image pre-staging**
|
||||||
|
|
||||||
|
1. On the client computer, under the image store directory, create a folder for the pre-staging image, and name it *MED-V Images*.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
This folder must be called *MED-V Images*.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
2. Inside the MED-V Images folder, create a subfolder and name it *PrestagedImages*.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
This folder must be called *PrestagedImages*.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
3. To apply Access Control Lists (ACL) security to the *MED-V Images* folder, set the following ACL:
|
||||||
|
|
||||||
|
**NT AUTHORITY\\Authenticated Users:(OI)(CI)(special access:)**
|
||||||
|
|
||||||
|
**READ\_CONTROL**
|
||||||
|
|
||||||
|
**SYNCHRONIZE**
|
||||||
|
|
||||||
|
**FILE\_GENERIC\_READ**
|
||||||
|
|
||||||
|
**FILE\_READ\_DATA**
|
||||||
|
|
||||||
|
** FILE\_APPEND\_DATA**
|
||||||
|
|
||||||
|
**FILE\_READ\_EA**
|
||||||
|
|
||||||
|
**FILE\_READ\_ATTRIBUTES**
|
||||||
|
|
||||||
|
**NT AUTHORITY\\SYSTEM:(OI)(CI)F**
|
||||||
|
|
||||||
|
**BUILTIN\\Administrators:(OI)(CI)F**
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
It is recommended to apply ACL security to the *MED-V Images* folder.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
4. To apply ACL security to the *PrestagedImages* folder, set the following ACL:
|
||||||
|
|
||||||
|
**NT AUTHORITY\\Authenticated Users:(OI)(CI)(special access:)**
|
||||||
|
|
||||||
|
** READ\_CONTROL**
|
||||||
|
|
||||||
|
** SYNCHRONIZE**
|
||||||
|
|
||||||
|
** FILE\_GENERIC\_READ**
|
||||||
|
|
||||||
|
** FILE\_READ\_DATA**
|
||||||
|
|
||||||
|
** FILE\_READ\_EA**
|
||||||
|
|
||||||
|
** FILE\_READ\_ATTRIBUTES**
|
||||||
|
|
||||||
|
**NT AUTHORITY\\SYSTEM:(OI)(CI)F**
|
||||||
|
|
||||||
|
**BUILTIN\\Administrators:(OI)(CI)F**
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
It is recommended to apply ACL security to the *PrestagedImages* folder.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
5. Push the image files (CKM and INDEX files) to the *PrestagedImages* folder.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
After the image files have been pushed to the pre-stage folder, it is recommended to run a data integrity check and to mark the files as read-only.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
6. Include the following parameter in the MED-V client installation: *Client.MSI VMSFOLDER=”C:\\MED-V Images”*.
|
||||||
|
|
||||||
|
## How to Update the Pre-stage Location
|
||||||
|
|
||||||
|
|
||||||
|
**To update the pre-stage location**
|
||||||
|
|
||||||
|
1. The registry key, *PrestagedImagesPath*, points to the default image location. It is located in the following directory:
|
||||||
|
|
||||||
|
- On an x86 - `KEY_LOCAL_MACHINE\SOFTWARE\Kidaro`
|
||||||
|
|
||||||
|
- On an x64 - `HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432node`
|
||||||
|
|
||||||
|
2. If the image is in a different location, change the path.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
236
mdop/medv-v1/how-to-configure-published-applicationsmedvv2.md
Normal file
236
mdop/medv-v1/how-to-configure-published-applicationsmedvv2.md
Normal file
@ -0,0 +1,236 @@
|
|||||||
|
---
|
||||||
|
title: How to Configure Published Applications
|
||||||
|
description: How to Configure Published Applications
|
||||||
|
ms.assetid: 43a59ff7-5d4e-49dc-84e5-1082bc4dd8f4
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Configure Published Applications
|
||||||
|
|
||||||
|
|
||||||
|
Applications that are not compatible with the host operating system can be run within the MED-V workspace and initiated from within the MED-V workspace the same way they are initiated from the desktop—from the Start menu or from a local host shortcut. Applications selected and defined are called published applications. The procedures in this section describe how to add and remove published applications.
|
||||||
|
|
||||||
|
An application can be published in one of the following ways:
|
||||||
|
|
||||||
|
- As an application—Select a specific application by typing in the command line for the application. Only the application selected is published.
|
||||||
|
|
||||||
|
- As a menu—Select a folder that contains multiple applications. All applications within the folder are published and displayed as a menu.
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-addingapublishedapplication"></a>How to Add a Published Application to a MED-V Workspace
|
||||||
|
|
||||||
|
|
||||||
|
**To add an application to the MED-V workspace**
|
||||||
|
|
||||||
|
1. Click the MED-V workspace to configure.
|
||||||
|
|
||||||
|
2. In the **Applications** pane, in the **Published Applications** section, click **Add** to add a new application.
|
||||||
|
|
||||||
|
3. Configure the application properties as described in the following table.
|
||||||
|
|
||||||
|
4. On the **Policy** menu, select **Commit**.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
If you are setting Internet Explorer as a published application to ensure that Web redirection works properly, make certain that any parameters are not in parentheses.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**Published Application Properties**
|
||||||
|
|
||||||
|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="50%" />
|
||||||
|
<col width="50%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead>
|
||||||
|
<tr class="header">
|
||||||
|
<th align="left">Property</th>
|
||||||
|
<th align="left">Description</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Enabled</p></td>
|
||||||
|
<td align="left"><p>Select this check box to enable the published application.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Display name</p></td>
|
||||||
|
<td align="left"><p>The name of the shortcut in the user's Windows Start menu.</p>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>The display name is <strong>not</strong> case sensitive.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Description</p></td>
|
||||||
|
<td align="left"><p>A description of the published application, which appears as a tooltip when the user's mouse hovers over the shortcut.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Command line</p></td>
|
||||||
|
<td align="left"><p>The command used to run the application from within the MED-V workspace. The full path is required, and the parameters can be passed to the application in a similar fashion as in any other Windows command.</p>
|
||||||
|
<p>In a revertible MED-V workspace, you can map a network drive with MapNetworkDrive syntax: "<em>MapNetworkDrive <drive> <path></em>"—for example, "<em>MapNetworkDrive t: \\tux\date</em>".</p>
|
||||||
|
<p>For example, to publish Windows Explorer, use the following syntax: "<em>c:\</em>" or "<em>c:\windows</em>."</p>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>To have a name resolution, you need to perform one of the following:</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div>
|
||||||
|
<ul>
|
||||||
|
<li><p>Configure the DNS in the base MED-V workspace image.</p></li>
|
||||||
|
<li><p>Verify the DNS resolution is defined in the host, and configure it to use the host DNS.</p></li>
|
||||||
|
<li><p>Use the IP for defining the network drive.</p></li>
|
||||||
|
</ul>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>If the path includes spaces, the entire path must be inside quotation marks.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>The path should not end with a backslash ().</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Start menu</p></td>
|
||||||
|
<td align="left"><p>Select this check box to create a shortcut for the application in the user's Windows Start menu.</p></td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
All published applications appear as shortcuts in the Windows **Start** menu (**Start >All Programs> MED-V Applications**).
|
||||||
|
|
||||||
|
## How to Remove a Published Application from a MED-V Workspace
|
||||||
|
|
||||||
|
|
||||||
|
**To remove an application from the MED-V workspace**
|
||||||
|
|
||||||
|
1. Click a MED-V workspace.
|
||||||
|
|
||||||
|
2. In the **Applications** pane, in the **Published Applications** section, select an application to remove.
|
||||||
|
|
||||||
|
3. Click **Remove**.
|
||||||
|
|
||||||
|
The application is removed from the list of published applications.
|
||||||
|
|
||||||
|
4. On the **Policy** menu, select **Commit**.
|
||||||
|
|
||||||
|
## How to Add a Published Menu to a MED-V Workspace
|
||||||
|
|
||||||
|
|
||||||
|
**To add a published menu to the MED-V workspace**
|
||||||
|
|
||||||
|
1. Click the MED-V workspace to configure.
|
||||||
|
|
||||||
|
2. In the **Applications** pane, in the **Published Menus** section, click **Add** to add a new menu.
|
||||||
|
|
||||||
|
3. Configure the menu properties as described in the following table.
|
||||||
|
|
||||||
|
4. On the **Policy** menu, select **Commit**.
|
||||||
|
|
||||||
|
**Published Menu Properties**
|
||||||
|
|
||||||
|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="50%" />
|
||||||
|
<col width="50%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead>
|
||||||
|
<tr class="header">
|
||||||
|
<th align="left">Property</th>
|
||||||
|
<th align="left">Description</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Enabled</p></td>
|
||||||
|
<td align="left"><p>Select this check box to enable the published menu.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Display name</p></td>
|
||||||
|
<td align="left"><p>The name of the shortcut in the user's Windows Start menu.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Description</p></td>
|
||||||
|
<td align="left"><p>The description, which appears as a tooltip when the user's mouse hovers over the shortcut.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Folder in workspace</p></td>
|
||||||
|
<td align="left"><p>Select the folder to publish as a menu containing all the applications within the folder.</p>
|
||||||
|
<p>The text displayed is a relative path from the Programs folder.</p>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>If left blank, all programs on the host will be published as a menu.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div></td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
All published menus appear as shortcuts in the Windows **Start** menu (**Start >All Programs> MED-V Applications**). You can change the name of the shortcut in the **Start-menu shortcuts folder** field.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
When configuring two MED-V workspaces, it is recommended to configure a different name for the Start menu shortcuts folder.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## How to Remove a Published Menu from a MED-V Workspace
|
||||||
|
|
||||||
|
|
||||||
|
**To remove a published menu from a MED-V workspace**
|
||||||
|
|
||||||
|
1. Click a MED-V workspace.
|
||||||
|
|
||||||
|
2. In the **Applications** pane, in the **Published Menus** section, select a menu to remove.
|
||||||
|
|
||||||
|
3. Click **Remove**.
|
||||||
|
|
||||||
|
The menu is removed from the list of published menus.
|
||||||
|
|
||||||
|
4. On the **Policy** menu, select **Commit**.
|
||||||
|
|
||||||
|
## Running a Published Application from a Command Line on the Client
|
||||||
|
|
||||||
|
|
||||||
|
The administrator can run published applications from any location, such as a desktop shortcut, using the following command:
|
||||||
|
|
||||||
|
``` syntax
|
||||||
|
"<Install path>\Manager\KidaroCommands.exe" /run "<published application name>" "<MED-V workspace name>"
|
||||||
|
```
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
The MED-V workspace in which the published application is defined must be running.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[How to Edit a Published Application with Advanced Settings](how-to-edit-a-published-application-with-advanced-settings.md)
|
||||||
|
|
||||||
|
[Using the MED-V Management Console User Interface](using-the-med-v-management-console-user-interface.md)
|
||||||
|
|
||||||
|
[Creating a MED-V Workspace](creating-a-med-v-workspacemedv-10-sp1.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -0,0 +1,60 @@
|
|||||||
|
---
|
||||||
|
title: How to Configure the Image Web Distribution Server
|
||||||
|
description: How to Configure the Image Web Distribution Server
|
||||||
|
ms.assetid: 2d32ae79-dff5-4c05-a412-dd15452b6007
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Configure the Image Web Distribution Server
|
||||||
|
|
||||||
|
|
||||||
|
An image repository is an optional server that is used for image distribution (where administrators upload new images and client computers check the server every 15 minutes and update their image if a new one is available).
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-configuringanimagereporitoryusingiis"></a>
|
||||||
|
|
||||||
|
|
||||||
|
An image distribution server requires the following:
|
||||||
|
|
||||||
|
- Internet Information Services (IIS)—For information, see [Internet Information Services](http://go.microsoft.com/fwlink/?LinkId=142995).
|
||||||
|
|
||||||
|
During the IIS installation, when adding role services, select the following supported authentication methods:
|
||||||
|
|
||||||
|
- **Basic Authentication**
|
||||||
|
|
||||||
|
- **Windows Authentication**
|
||||||
|
|
||||||
|
- **Client Certificate Mapping Authentication**
|
||||||
|
|
||||||
|
When configuring IIS, include the following:
|
||||||
|
|
||||||
|
- Add a virtual directory, with the alias named **MEDVImages**. The physical path should point to the location of the images.
|
||||||
|
|
||||||
|
- Enable BITS.
|
||||||
|
|
||||||
|
- Add the following MIME types:
|
||||||
|
|
||||||
|
- **.ckm (application/octet-stream)**
|
||||||
|
|
||||||
|
- **.index (application/octet-stream**)
|
||||||
|
|
||||||
|
- On the MED-V site, add read permissions to **Everyone**.
|
||||||
|
|
||||||
|
- Restart IIS.
|
||||||
|
|
||||||
|
- BITS Server Extensions for IIS—For information, see [Install BITS Server Extensions](http://go.microsoft.com/fwlink/?LinkId=142996).
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[Supported Configurations](supported-configurationsmedv-orientation.md)
|
||||||
|
|
||||||
|
[Design the MED-V Image Repositories](design-the-med-v-image-repositories.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -0,0 +1,43 @@
|
|||||||
|
---
|
||||||
|
title: How to Configure the Virtual Machine Setup for a MED-V Workspace
|
||||||
|
description: How to Configure the Virtual Machine Setup for a MED-V Workspace
|
||||||
|
ms.assetid: a4659b4d-18b2-45b1-9605-8b5adc438f53
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Configure the Virtual Machine Setup for a MED-V Workspace
|
||||||
|
|
||||||
|
|
||||||
|
The procedures in this section describe how to configure the virtual machine for first-time setup.
|
||||||
|
|
||||||
|
The virtual machine setup configures the setup performed when the virtual machine is run on the client for the first time. The virtual machine setup is configured differently for persistent and revertible MED-V workspaces. For more information about persistent and revertible MED-V workspaces, see [Configuring MED-V Workspace Policies](configuring-med-v-workspace-policies.md).
|
||||||
|
|
||||||
|
## In This Section
|
||||||
|
|
||||||
|
|
||||||
|
<a href="" id="how-to-configure-the-virtual-machine-setup-for-a-med-v-workspace"></a>[How to Configure the Virtual Machine Setup for a MED-V Workspace](how-to-configure-the-virtual-machine-setup-for-a-med-v-workspacemedvv2.md)
|
||||||
|
Describes how to configure the virtual machine setup for persistent and revertible MED-V workspaces.
|
||||||
|
|
||||||
|
<a href="" id="how-to-configure-vm-computer-name-pattern-properties"></a>[How to Configure VM Computer Name Pattern Properties](how-to-configure-vm-computer-name-pattern-propertiesmedvv2.md)
|
||||||
|
Describes how to configure virtual machine computer name pattern properties for persistent and revertible MED-V workspaces.
|
||||||
|
|
||||||
|
<a href="" id="examples-of-virtual-machine-configurations"></a>[Examples of Virtual Machine Configurations](examples-of-virtual-machine-configurationsv2.md)
|
||||||
|
Provides examples of virtual machine configurations in both persistent and revertible MED-V workspaces.
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[Using the MED-V Management Console User Interface](using-the-med-v-management-console-user-interface.md)
|
||||||
|
|
||||||
|
[Creating a MED-V Workspace](creating-a-med-v-workspacemedv-10-sp1.md)
|
||||||
|
|
||||||
|
[How to Set Up Script Actions](how-to-set-up-script-actions.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -0,0 +1,130 @@
|
|||||||
|
---
|
||||||
|
title: How to Configure the Virtual Machine Setup for a MED-V Workspace
|
||||||
|
description: How to Configure the Virtual Machine Setup for a MED-V Workspace
|
||||||
|
ms.assetid: 50bbf58b-842c-4b63-bb93-3783903f6c7d
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Configure the Virtual Machine Setup for a MED-V Workspace
|
||||||
|
|
||||||
|
|
||||||
|
All virtual machine setup configuration settings are configured in the **Policy** module, on the **VM Setup** tab.
|
||||||
|
|
||||||
|
## How to Configure the Virtual Machine Setup for a Persistent MED-V Workspace
|
||||||
|
|
||||||
|
|
||||||
|
**To configure the virtual machine setup for a persistent MED-V workspace**
|
||||||
|
|
||||||
|
1. Click a persistent MED-V workspace to be configured.
|
||||||
|
|
||||||
|
2. In the **Persistent VM Setup** section, configure the properties as described in the following table.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
The persistent VM setup properties are enabled only for a persistent MED-V workspace.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
3. On the **Policy** menu, select **Commit**.
|
||||||
|
|
||||||
|
**Persistent VM Setup Properties**
|
||||||
|
|
||||||
|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="50%" />
|
||||||
|
<col width="50%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead>
|
||||||
|
<tr class="header">
|
||||||
|
<th align="left">Property</th>
|
||||||
|
<th align="left">Description</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Run VM Setup</p></td>
|
||||||
|
<td align="left"><p>Select this check box to run a setup script the first time the MED-V workspace is run.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Script Editor</p></td>
|
||||||
|
<td align="left"><p>Click to configure the setup script. For more information, see [How to Set Up Script Actions](how-to-set-up-script-actions.md).</p>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>This button is enabled only when <strong>Run VM Setup script</strong> is selected.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Message displayed when script is running</p></td>
|
||||||
|
<td align="left"><p>A message to be displayed while the script is running. If left blank, the default message is displayed.</p>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>This field is enabled only when <strong>Run VM Setup script</strong> is checked.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div></td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## How to Configure the Virtual Machine Setup for a Revertible MED-V Workspace
|
||||||
|
|
||||||
|
|
||||||
|
**To configure the virtual machine setup for a revertible MED-V workspace**
|
||||||
|
|
||||||
|
1. Click a revertible MED-V workspace to configure.
|
||||||
|
|
||||||
|
2. In the **Revertible VM Setup** section, configure the properties as described in the following table.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
The revertible VM setup properties are enabled only for a revertible MED-V workspace.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
3. On the **Policy** menu, select **Commit**.
|
||||||
|
|
||||||
|
**Revertible VM Setup Properties**
|
||||||
|
|
||||||
|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="50%" />
|
||||||
|
<col width="50%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead>
|
||||||
|
<tr class="header">
|
||||||
|
<th align="left">Property</th>
|
||||||
|
<th align="left">Description</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Rename the VM based on the computer name pattern</p></td>
|
||||||
|
<td align="left"><p>Select this check box to assign a unique name to each computer using the MED-V workspace so that you can differentiate between multiple computers using the same MED-V workspace.</p>
|
||||||
|
<p>For more information on configuring computer image names, see [How to Configure VM Computer Name Pattern Properties](how-to-configure-vm-computer-name-pattern-propertiesmedvv2.md).</p></td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[Using the MED-V Management Console User Interface](using-the-med-v-management-console-user-interface.md)
|
||||||
|
|
||||||
|
[Creating a MED-V Workspace](creating-a-med-v-workspacemedv-10-sp1.md)
|
||||||
|
|
||||||
|
[Examples of Virtual Machine Configurations](examples-of-virtual-machine-configurationsv2.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -0,0 +1,126 @@
|
|||||||
|
---
|
||||||
|
title: How to Configure VM Computer Name Pattern Properties
|
||||||
|
description: How to Configure VM Computer Name Pattern Properties
|
||||||
|
ms.assetid: ddf79ace-8cc3-4ee6-be5a-5940b4df5c36
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Configure VM Computer Name Pattern Properties
|
||||||
|
|
||||||
|
|
||||||
|
A virtual machine computer name pattern can be assigned both for revertible and for persistent MED-V workspaces.
|
||||||
|
|
||||||
|
- Revertible—Administrators can assign a unique name to each revertible MED-V workspace instance to differentiate between multiple computers using the same MED-V workspace.
|
||||||
|
|
||||||
|
- Persistent—In a persistent MED-V workspace, administrators can set a computer to be renamed during a setup script.
|
||||||
|
|
||||||
|
## How to Assign a Virtual Machine Computer Name Pattern to a Revertible MED-V Workspace
|
||||||
|
|
||||||
|
|
||||||
|
**To assign a virtual machine computer name pattern to a revertible MED-V workspace**
|
||||||
|
|
||||||
|
1. Click the revertible MED-V workspace to configure.
|
||||||
|
|
||||||
|
2. In the **Revertible VM Setup** section, select the **Rename the VM based on the computer name pattern** check box.
|
||||||
|
|
||||||
|
3. In the **VM Computer Name Pattern** section, enter the pattern to use for naming virtual machine images, using the following options:
|
||||||
|
|
||||||
|
- **Constant**—Enter free text that will be constant on all computers using the MED-V workspace.
|
||||||
|
|
||||||
|
- **Variable**—Enter a variable, by clicking **Insert Variable**, and select from one of the following:
|
||||||
|
|
||||||
|
- **User name**
|
||||||
|
|
||||||
|
- **Domain name**
|
||||||
|
|
||||||
|
- **Host name**
|
||||||
|
|
||||||
|
- **Workspace name**
|
||||||
|
|
||||||
|
- **Virtual machine name**
|
||||||
|
|
||||||
|
The variable selected will be specific to the computer using the MED-V workspace. For example, if **Domain name** is selected, the unique name for each computer will include the computer's domain name.
|
||||||
|
|
||||||
|
- **Random characters**—Enter “\#” for each random character to include in the pattern. Each computer using the MED-V workspace will have a suffix of the length specified, which is generated randomly.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
The computer name has a limit of 15 characters. If the pattern exceeds the limit, it will be truncated.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
4. On the **Policy** menu, select **Commit**.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
A revertible VM computer name pattern can be assigned only when **Rename the VM based on the computer name patterns** (in the **Revertible VM Setup** section) is checked.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
A unique computer name can be assigned only if it is configured prior to MED-V workspace setup. Changing the name will not affect MED-V workspaces that were already set up.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## How to Assign a Virtual Machine Computer Name Pattern to a Persistent MED-V Workspace
|
||||||
|
|
||||||
|
|
||||||
|
**To assign a virtual machine computer name pattern to a persistent MED-V workspace**
|
||||||
|
|
||||||
|
1. Click the persistent MED-V workspace to configure.
|
||||||
|
|
||||||
|
2. In the **Persistent VM Setup** section, click **Script Editor**.
|
||||||
|
|
||||||
|
3. In the **Script Actions** dialog box, click **Add**, and on the submenu, click **Rename Computer**.
|
||||||
|
|
||||||
|
4. Click **OK** to close the **Script Actions** dialog box.
|
||||||
|
|
||||||
|
5. On the **VM Setup** tab, in the **VM Computer Name Pattern** section, enter the pattern to use for renaming the computer, using the following:
|
||||||
|
|
||||||
|
- **Constant**— Enter free text that will be included in the computer name.
|
||||||
|
|
||||||
|
- **Variable**—Enter a variable, by clicking **Insert Variable**, and select from one of the following:
|
||||||
|
|
||||||
|
- **User name**
|
||||||
|
|
||||||
|
- **Domain name**
|
||||||
|
|
||||||
|
- **Host name**
|
||||||
|
|
||||||
|
- **Workspace name**
|
||||||
|
|
||||||
|
- **Virtual machine name**
|
||||||
|
|
||||||
|
The variable selected will be specific to the computer that is being renamed. For example, if **Domain name** is selected, the computer name will include the computer's domain name.
|
||||||
|
|
||||||
|
- **Random characters**— Enter “\#” for each random character to include in the pattern. The computer will have a suffix of the length specified, which is generated randomly.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
The computer name has a limit of 15 characters. If the pattern exceeds the limit, it will be truncated.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
6. On the **Policy** menu, select **Commit**.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
The computer will be renamed only if it is set as an action in the **Script Actions** dialog box. For detailed information, see [How to Set Up Script Actions](how-to-set-up-script-actions.md).
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[Using the MED-V Management Console User Interface](using-the-med-v-management-console-user-interface.md)
|
||||||
|
|
||||||
|
[Creating a MED-V Workspace](creating-a-med-v-workspacemedv-10-sp1.md)
|
||||||
|
|
||||||
|
[How to Set Up Script Actions](how-to-set-up-script-actions.md)
|
||||||
|
|
||||||
|
[Examples of Virtual Machine Configurations](examples-of-virtual-machine-configurationsv2.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -0,0 +1,131 @@
|
|||||||
|
---
|
||||||
|
title: How to Configure Web Settings for a MED-V Workspace
|
||||||
|
description: How to Configure Web Settings for a MED-V Workspace
|
||||||
|
ms.assetid: 9a6cd28f-7e4f-468f-830a-7b1d9abd3af3
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Configure Web Settings for a MED-V Workspace
|
||||||
|
|
||||||
|
|
||||||
|
Web sites that can only be displayed in older versions of Internet Explorer and that do not exist in the host operating system can be viewed in older versions of Internet Explorer within the MED-V workspace. The user does not need to open a browser in the MED-V workspace to view the specified Web sites. The user can open a browser on the host and automatically be redirected to the MED-V workspace and vice versa.
|
||||||
|
|
||||||
|
The following procedures describe how you can set a list of Web browsing rules for a MED-V workspace. All sites included in the rules can be browsed either in the MED-V workspace or on the host, as defined by the administrator. All sites not defined within the rules are browsed from the environment in which they were requested. However, you can configure them as a group as well, to be browsed in the MED-V workspace or the host.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
Web settings are applied only to Internet Explorer and to no other browsers.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
All Web settings are configured in the **Policy** module, on the **Web** tab.
|
||||||
|
|
||||||
|
## How to Configure Web Settings for the MED-V Workspace
|
||||||
|
|
||||||
|
|
||||||
|
**To configure Web settings for the MED-V workspace**
|
||||||
|
|
||||||
|
1. Click the MED-V workspace to be configured.
|
||||||
|
|
||||||
|
2. Select the **Browse the list of URLs defined in the following table** check box to redirect the user to a browser within the MED-V workspace or host, when the user browses to a URL that conforms to the Web rules specified.
|
||||||
|
|
||||||
|
3. Click one of the following:
|
||||||
|
|
||||||
|
- **In the Workspace**—Redirect to a browser in the MED-V workspace.
|
||||||
|
|
||||||
|
- **In the host**—Redirect to a browser on the host.
|
||||||
|
|
||||||
|
4. Select the **Browse all other URLs** check box to redirect all URLs excluded from the Web rules to the host or MED-V workspace.
|
||||||
|
|
||||||
|
5. Click one of the following:
|
||||||
|
|
||||||
|
- **In the Workspace**—Redirect all other URLs to a browser in the MED-V workspace.
|
||||||
|
|
||||||
|
- **In the host**—Redirect all other URLs to a browser on the host.
|
||||||
|
|
||||||
|
6. On the **Policy** menu, select **Commit**.
|
||||||
|
|
||||||
|
## How to Add a Web Rule
|
||||||
|
|
||||||
|
|
||||||
|
**To add a Web rule**
|
||||||
|
|
||||||
|
1. Select the **Browse the list of URLs defined in the following table** check box to enable the Web browsing rules.
|
||||||
|
|
||||||
|
2. Click **Add**.
|
||||||
|
|
||||||
|
A new Web rule is added.
|
||||||
|
|
||||||
|
3. Configure the Web rule properties as described in the following table.
|
||||||
|
|
||||||
|
4. On the **Policy** menu, select **Commit**.
|
||||||
|
|
||||||
|
**MED-V Workspace Web Properties**
|
||||||
|
|
||||||
|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="50%" />
|
||||||
|
<col width="50%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead>
|
||||||
|
<tr class="header">
|
||||||
|
<th align="left">Property</th>
|
||||||
|
<th align="left">Description</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Type</p></td>
|
||||||
|
<td align="left"><ul>
|
||||||
|
<li><p><strong>Domain suffix</strong>—Access to any host address ending with the suffix specified in the <strong>Value</strong> property and is set according to the option set in <strong>Web Browsing</strong>.</p></li>
|
||||||
|
<li><p><strong>IP Prefix</strong>—Access to any full or partial IP address in the range of the prefix specified in the <strong>Value</strong> property and is set according to the option set in <strong>Web Browsing</strong>.</p></li>
|
||||||
|
<li><p><strong>All Local Addresses</strong>—Access to all addresses without a '.' and is set according to the option set in <strong>Web Browsing</strong>.</p></li>
|
||||||
|
</ul></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Value</p></td>
|
||||||
|
<td align="left"><ul>
|
||||||
|
<li><p>If <strong>Domain suffix</strong> is selected in the <strong>Type</strong> property, enter a domain suffix.</p>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<ul>
|
||||||
|
<li><p>Do not enter "*" before the suffix.</p></li>
|
||||||
|
<li><p>Domain suffixes support aliases as well.</p></li>
|
||||||
|
</ul>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div></li>
|
||||||
|
<li><p>If IP Prefix is selected in the <strong>Type</strong> property, enter a full or partial IP address.</p></li>
|
||||||
|
</ul></td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## How to Delete a Web Rule
|
||||||
|
|
||||||
|
|
||||||
|
**To delete a Web rule**
|
||||||
|
|
||||||
|
1. In the **Web** pane, select the Web rule to delete.
|
||||||
|
|
||||||
|
2. Click **Remove**.
|
||||||
|
|
||||||
|
The Web rule is deleted.
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[Using the MED-V Management Console User Interface](using-the-med-v-management-console-user-interface.md)
|
||||||
|
|
||||||
|
[Creating a MED-V Workspace](creating-a-med-v-workspacemedv-10-sp1.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,85 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
147
mdop/medv-v1/how-to-create-and-test-a-med-v-image.md
Normal file
147
mdop/medv-v1/how-to-create-and-test-a-med-v-image.md
Normal file
@ -0,0 +1,147 @@
|
|||||||
|
---
|
||||||
|
title: How to Create and Test a MED-V Image
|
||||||
|
description: How to Create and Test a MED-V Image
|
||||||
|
ms.assetid: 40e4aba6-12cb-4794-967d-2c09dc20d808
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Create and Test a MED-V Image
|
||||||
|
|
||||||
|
|
||||||
|
The MED-V administrator creates a MED-V image so that it can be uploaded, associated with a MED-V workspace, and then distributed to the client over the Web, added to a MED-V package, or downloaded to the client by using a third-party system. It is recommended to first create a test image and test it on MED-V client before deploying it.
|
||||||
|
|
||||||
|
When creating a MED-V image, it goes through the following stages:
|
||||||
|
|
||||||
|
1. **Local test image**—A basic image that can be tested locally.
|
||||||
|
|
||||||
|
2. **Local packed image**—After the image is tested, the image is packed as it existed prior to testing. No changes made during testing are included in the packed image.
|
||||||
|
|
||||||
|
3. **Packed image on server**—The packed image is uploaded to the server.
|
||||||
|
|
||||||
|
## How to Create a MED-V Test Image
|
||||||
|
|
||||||
|
|
||||||
|
**To create a new MED-V test image**
|
||||||
|
|
||||||
|
1. Click the **Images** management button.
|
||||||
|
|
||||||
|
The **Images** module appears.
|
||||||
|
|
||||||
|
- The **Images** module consists of the following panes:
|
||||||
|
|
||||||
|
- **Local Test Images**—Local unpacked images.
|
||||||
|
|
||||||
|
- **Local Packed Images**—All packed images on the local computer.
|
||||||
|
|
||||||
|
- **Packed Images on Server**—All images that have been packed and uploaded to the server.
|
||||||
|
|
||||||
|
- In the **Local Packed Images** and **Packed Images on Server** panes, the most recent version of each image is displayed as the parent node. Click the parent node to view all other existing versions of the image.
|
||||||
|
|
||||||
|
2. In the **Local Test Images** pane, click **New**.
|
||||||
|
|
||||||
|
3. On the **Test Image Creation** dialog box, select the virtual machine image that you want to configure as a MED-V test image by doing one of the following:
|
||||||
|
|
||||||
|
- In the **Base image** file field, type the full path to the directory where the Microsoft Virtual PC image prepared for MED-V is located.
|
||||||
|
|
||||||
|
- Click **Browse** to browse to the directory where the Microsoft Virtual PC image prepared for MED-V is located.
|
||||||
|
|
||||||
|
4. In the **Image name** field, type or select the desired name.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
The following characters cannot be included in the image name: space " < > | \\ / : \* ?
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
5. Click **OK**.
|
||||||
|
|
||||||
|
A new MED-V test image is created on your host computer with the properties defined in the following table.
|
||||||
|
|
||||||
|
For more information about configuring the MED-V workspace image, refer to [Configuring MED-V Workspace Policies](configuring-med-v-workspace-policies.md).
|
||||||
|
|
||||||
|
**Local Test Images Properties**
|
||||||
|
|
||||||
|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="50%" />
|
||||||
|
<col width="50%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead>
|
||||||
|
<tr class="header">
|
||||||
|
<th align="left">Property</th>
|
||||||
|
<th align="left">Description</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Image Name</p></td>
|
||||||
|
<td align="left"><p>The name of the test image as it was defined when the administrator created the image.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Image Path</p></td>
|
||||||
|
<td align="left"><p>The local path of the test image.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Created</p></td>
|
||||||
|
<td align="left"><p>The date the test image was created.</p></td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## How to Test a MED-V Image from the MED-V Client
|
||||||
|
|
||||||
|
|
||||||
|
After a MED-V test image is created, use the following procedure to test the image locally.
|
||||||
|
|
||||||
|
**To test a MED-V image**
|
||||||
|
|
||||||
|
1. Click the **Policy** management button.
|
||||||
|
|
||||||
|
2. In the **Policy** module, assign the MED-V test image to a MED-V workspace by doing the following:
|
||||||
|
|
||||||
|
1. Click the **Virtual Machine** tab.
|
||||||
|
|
||||||
|
2. In the **Assigned Image** field, select the MED-V test image you created. If your test image is not in the list, click **Refresh**.
|
||||||
|
|
||||||
|
3. On the toolbar, click **Save changes**.
|
||||||
|
|
||||||
|
3. Configure any other MED-V workspace settings to be tested. For more information, see [Configuring MED-V Workspace Policies](configuring-med-v-workspace-policies.md).
|
||||||
|
|
||||||
|
4. Start MED-V client.
|
||||||
|
|
||||||
|
5. In the **Confirm Running Test** confirmation box, click **Use Test Image**.
|
||||||
|
|
||||||
|
6. Test the MED-V workspace test image.
|
||||||
|
|
||||||
|
For information about starting and running MED-V client, see [MED-V Client Operations](med-v-client-operations.md).
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
While testing an image, do not open VPC and make changes to the image.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
When testing an image, no changes are saved to the image between sessions; instead, they are saved in a separate, temporary file. This is to ensure that when the image is packed and run on the production environment, it is the original, clean image.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[Creating a Virtual PC Image for MED-V](creating-a-virtual-pc-image-for-med-v.md)
|
||||||
|
|
||||||
|
[Creating a MED-V Workspace](creating-a-med-v-workspacemedv-10-sp1.md)
|
||||||
|
|
||||||
|
[Configuring MED-V Workspace Policies](configuring-med-v-workspace-policies.md)
|
||||||
|
|
||||||
|
[MED-V Client Operations](med-v-client-operations.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
34
mdop/medv-v1/how-to-delete-a-med-v-image.md
Normal file
34
mdop/medv-v1/how-to-delete-a-med-v-image.md
Normal file
@ -0,0 +1,34 @@
|
|||||||
|
---
|
||||||
|
title: How to Delete a MED-V Image
|
||||||
|
description: How to Delete a MED-V Image
|
||||||
|
ms.assetid: 974a493a-7627-4c64-9294-89441f127916
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Delete a MED-V Image
|
||||||
|
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-deletinganimage"></a>How to Delete a MED-V Image
|
||||||
|
|
||||||
|
|
||||||
|
**To delete a MED-V image**
|
||||||
|
|
||||||
|
1. Click the image or the version of the image to delete.
|
||||||
|
|
||||||
|
2. On the **Images** menu, click **Delete**.
|
||||||
|
|
||||||
|
The image is deleted.
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[How to Create and Test a MED-V Image](how-to-create-and-test-a-med-v-image.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,57 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,74 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,179 +0,0 @@
|
|||||||
---
|
|
||||||
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:
|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Argument</th>
|
|
||||||
<th align="left">Description</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>/norestart</p></td>
|
|
||||||
<td align="left"><p>Prevents the installation of Windows Virtual PC and the Windows Virtual PC update from restarting the host computer.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>/quiet</p></td>
|
|
||||||
<td align="left"><p>Installs the MED-V components in quiet mode without user interaction.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>/qn</p></td>
|
|
||||||
<td align="left"><p>Installs the MED-V components without a user interface.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>IGNORE_PREREQUISITES</p></td>
|
|
||||||
<td align="left"><p>Installs without checking for Windows Virtual PC.</p>
|
|
||||||
<div class="alert">
|
|
||||||
<strong>Note</strong>
|
|
||||||
<p>Only specify this argument if you are installing Windows Virtual PC as part of this installation.</p>
|
|
||||||
</div>
|
|
||||||
<div>
|
|
||||||
|
|
||||||
</div></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>OVERWRITEVHD</p></td>
|
|
||||||
<td align="left"><p>Forces the installation of the MED-V workspace and prevents any prompts that it might generate.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## 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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -0,0 +1,86 @@
|
|||||||
|
---
|
||||||
|
title: How to Deploy a Workspace Image
|
||||||
|
description: How to Deploy a Workspace Image
|
||||||
|
ms.assetid: b2c77e0d-101d-4956-a27c-8beb0e4f262e
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Deploy a Workspace Image
|
||||||
|
|
||||||
|
|
||||||
|
When using a deployment package, a new image can be deployed onto client computers in one of the following ways:
|
||||||
|
|
||||||
|
- [Web download](#bkmk-howtodeployaworkspaceimageviatheweb)
|
||||||
|
|
||||||
|
- [Image pre-staging](#bkmk-howtodeployaworkspaceimageusingimageprestaging)
|
||||||
|
|
||||||
|
- [Deploying the image inside the deployment package](#bkmk-howtodeployaworkspaceimageusingadeploymentapackage)
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-howtodeployaworkspaceimageviatheweb"></a>How to Deploy a Workspace Image via the Web
|
||||||
|
|
||||||
|
|
||||||
|
**To deploy a workspace image via the Web**
|
||||||
|
|
||||||
|
1. Upload the MED-V image to the server.
|
||||||
|
|
||||||
|
For information on uploading the image, see [How to Upload a MED-V Image to the Server](how-to-upload-a-med-v-image-to-the-server.md).
|
||||||
|
|
||||||
|
2. Create a deployment package, and include the server path to the location of the image.
|
||||||
|
|
||||||
|
For information on creating a deployment package, see [How to Configure a Deployment Package](how-to-configure-a-deployment-package.md).
|
||||||
|
|
||||||
|
3. Deploy the package to end users.
|
||||||
|
|
||||||
|
For information on deploying the package, see [How to Install MED-V Client](how-to-install-med-v-clientdeployment-package.md).
|
||||||
|
|
||||||
|
MED-V client is installed and started for the first time. On first-time startup, the client downloads the image from the server address specified in the client installation.
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-howtodeployaworkspaceimageusingimageprestaging"></a>How to Deploy a Workspace Image Using Image Pre-staging
|
||||||
|
|
||||||
|
|
||||||
|
**To deploy a workspace image using image pre-staging**
|
||||||
|
|
||||||
|
1. Create an image pre-stage folder, and push the image to the folder.
|
||||||
|
|
||||||
|
For information on configuring image pre-staging, see [How to Configure Image Pre-staging](how-to-configure-image-pre-staging.md).
|
||||||
|
|
||||||
|
2. Create a deployment package, and include the path to the image pre-stage folder.
|
||||||
|
|
||||||
|
For information on creating a deployment package, see [How to Configure a Deployment Package](how-to-configure-a-deployment-package.md).
|
||||||
|
|
||||||
|
3. Deploy the package to end users.
|
||||||
|
|
||||||
|
For information on deploying the package, see [How to Install MED-V Client](how-to-install-med-v-clientdeployment-package.md).
|
||||||
|
|
||||||
|
MED-V client is installed and started for the first time. On first-time startup, the client fetches the image from the pre-stage folder specified in the client installation.
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-howtodeployaworkspaceimageusingadeploymentapackage"></a>How to Deploy a Workspace Image Using a Deployment Package
|
||||||
|
|
||||||
|
|
||||||
|
**To deploy a workspace image using a deployment package**
|
||||||
|
|
||||||
|
1. Create a deployment package, and include the image in the package.
|
||||||
|
|
||||||
|
For information on creating a deployment package, see [How to Configure a Deployment Package](how-to-configure-a-deployment-package.md).
|
||||||
|
|
||||||
|
2. Deploy the package to end users.
|
||||||
|
|
||||||
|
For information on deploying the package, see [How to Install MED-V Client](how-to-install-med-v-clientdeployment-package.md).
|
||||||
|
|
||||||
|
The image is imported to the host as part of the package installation.
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[How to Configure the Image Web Distribution Server](how-to-configure-the-image-web-distribution-server.md)
|
||||||
|
|
||||||
|
[How to Configure a Deployment Package](how-to-configure-a-deployment-package.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
59
mdop/medv-v1/how-to-deploy-a-workspace-imageesds.md
Normal file
59
mdop/medv-v1/how-to-deploy-a-workspace-imageesds.md
Normal file
@ -0,0 +1,59 @@
|
|||||||
|
---
|
||||||
|
title: How to Deploy a Workspace Image
|
||||||
|
description: How to Deploy a Workspace Image
|
||||||
|
ms.assetid: ccc8e89b-1625-4b58-837e-4c6d93d46070
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Deploy a Workspace Image
|
||||||
|
|
||||||
|
|
||||||
|
When using an enterprise software distribution system, a new image can be deployed onto client computers in one of the following ways:
|
||||||
|
|
||||||
|
- [Web download](#bkmk-howtodeployaworkspaceimageviatheweb)
|
||||||
|
|
||||||
|
- [Image pre-staging](#bkmk-howtodeployaworkspaceimageusingimageprestaging)
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-howtodeployaworkspaceimageviatheweb"></a>How to Deploy a Workspace Image via the Web
|
||||||
|
|
||||||
|
|
||||||
|
**To deploy a workspace image via the Web**
|
||||||
|
|
||||||
|
1. Upload the MED-V image to the server.
|
||||||
|
|
||||||
|
For information on uploading the image, see [How to Upload a MED-V Image to the Server](how-to-upload-a-med-v-image-to-the-server.md).
|
||||||
|
|
||||||
|
2. Using your enterprise software distribution system, install the MED-V client .msi package on users’ computers.
|
||||||
|
|
||||||
|
For information on installing the MED-V client .msi package, see [How to Install MED-V Client](how-to-install-med-v-clientesds.md).
|
||||||
|
|
||||||
|
MED-V client is installed and started for the first time. On first-time startup, the client downloads the image from the server address specified in the client installation.
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-howtodeployaworkspaceimageusingimageprestaging"></a>How to Deploy a Workspace Image Using Image Pre-staging
|
||||||
|
|
||||||
|
|
||||||
|
**To deploy a workspace image using image pre-staging**
|
||||||
|
|
||||||
|
1. Create an image pre-stage folder, and push the image to the folder.
|
||||||
|
|
||||||
|
For information on configuring image pre-staging, see [How to Configure Image Pre-staging](how-to-configure-image-pre-staging.md).
|
||||||
|
|
||||||
|
2. Using your enterprise software distribution system, install the MED-V client .msi package on users’ computers.
|
||||||
|
|
||||||
|
For information on installing the MED-V client .msi package, see [How to Install MED-V Client](how-to-install-med-v-clientesds.md).
|
||||||
|
|
||||||
|
MED-V client is installed and started for the first time. On first-time startup, the client fetches the image from the pre-stage folder specified in the client installation.
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[How to Configure the Image Web Distribution Server](how-to-configure-the-image-web-distribution-server.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,182 +0,0 @@
|
|||||||
---
|
|
||||||
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:
|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Argument</th>
|
|
||||||
<th align="left">Description</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>/norestart</p></td>
|
|
||||||
<td align="left"><p>Prevents the installation of Windows Virtual PC and the Windows Virtual PC update from restarting the host computer.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>/quiet</p></td>
|
|
||||||
<td align="left"><p>Installs the MED-V components in quiet mode without user interaction.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>/qn</p></td>
|
|
||||||
<td align="left"><p>Installs the MED-V components without a user interface.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>IGNORE_PREREQUISITES</p></td>
|
|
||||||
<td align="left"><p>Installs without checking for Windows Virtual PC.</p>
|
|
||||||
<div class="alert">
|
|
||||||
<strong>Note</strong>
|
|
||||||
<p>Only specify this argument if you are installing Windows Virtual PC as part of this installation.</p>
|
|
||||||
</div>
|
|
||||||
<div>
|
|
||||||
|
|
||||||
</div></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>OVERWRITEVHD</p></td>
|
|
||||||
<td align="left"><p>Forces the installation of the MED-V workspace and prevents any prompts that it might generate.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## 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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -0,0 +1,137 @@
|
|||||||
|
---
|
||||||
|
title: How to Edit a Published Application with Advanced Settings
|
||||||
|
description: How to Edit a Published Application with Advanced Settings
|
||||||
|
ms.assetid: 06a79049-9ce9-490f-aad7-fd4fdf185590
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Edit a Published Application with Advanced Settings
|
||||||
|
|
||||||
|
|
||||||
|
After a published application has been added and configured, the published application can be edited and additional advanced settings can be configured.
|
||||||
|
|
||||||
|
**To edit a published application with advanced settings**
|
||||||
|
|
||||||
|
1. In the **Applications** pane, add and configure a published application.
|
||||||
|
|
||||||
|
2. Select the published application to edit.
|
||||||
|
|
||||||
|
3. Click **Edit**.
|
||||||
|
|
||||||
|
4. In the **Published Application** dialog box, configure the parameters as described in the following table.
|
||||||
|
|
||||||
|
5. Click **OK**.
|
||||||
|
|
||||||
|
6. On the **Policy** menu, select **Commit**.
|
||||||
|
|
||||||
|
**Editing Published Application Properties**
|
||||||
|
|
||||||
|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="50%" />
|
||||||
|
<col width="50%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead>
|
||||||
|
<tr class="header">
|
||||||
|
<th align="left">Property</th>
|
||||||
|
<th align="left">Description</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Display name</p></td>
|
||||||
|
<td align="left"><p>The name of the shortcut in the user's Windows Start menu.</p>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>The display name is <strong>not</strong> case sensitive.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Description</p></td>
|
||||||
|
<td align="left"><p>A description of the published menu.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Start in</p></td>
|
||||||
|
<td align="left"><p>The directory from which to start the application.</p>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>The path does not need to include quotation marks.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Command line</p></td>
|
||||||
|
<td align="left"><p>The command with which to run the application from within the MED-V workspace.</p>
|
||||||
|
<p>The full path is required, and the parameters can be passed to the application in a similar fashion as in any other Windows command.</p>
|
||||||
|
<p>In a domain configuration, a shared drive usually exists on the server where all domain computers map to. The directory should be mapped here, and if it is a folder that requires user authentication, the <strong>Use MED-V credentials to run this application</strong> check box must be selected.</p>
|
||||||
|
<p>In a revertible MED-V workspace, you can map a network drive with MapNetworkDrive syntax: "<em>MapNetworkDrive <drive> <path></em>"—for example, "<em>MapNetworkDrive t: \\tux\data</em>".</p>
|
||||||
|
<p>For example, to publish Windows Explorer, use the following syntax: "<em>c:\" or "c:\windows</em>".</p>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>To have a name resolution, you need to perform one of the following:</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div>
|
||||||
|
<ul>
|
||||||
|
<li><p>Configure the DNS in the base MED-V workspace image.</p></li>
|
||||||
|
<li><p>Verify that the DNS resolution is defined in the host, and configure it to use the host DNS.</p></li>
|
||||||
|
<li><p>Use the IP for defining the network drive.</p></li>
|
||||||
|
</ul>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>If the path includes spaces, the entire path must be inside quotation marks.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>The path should not end with a backslash ().</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Add a shortcut in the host Windows Start menu</p></td>
|
||||||
|
<td align="left"><p>Select this check box to create a shortcut for the application in the user's Windows Start menu.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Launch this application when the Workspace is started</p></td>
|
||||||
|
<td align="left"><p>Select this check box to run the application automatically when the MED-V workspace starts.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Use MED-V credentials to run this application</p></td>
|
||||||
|
<td align="left"><p>Select this check box to authenticate applications that request a user name and password using the MED-V credentials instead of the credentials set for the application.</p>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>When using SSO, the command line should be <strong>C:\Windows\Explorer.exe "folder path"</strong>. When not using SSO, the command line should be "<strong>folder path</strong>".</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div></td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[How to Configure Published Applications](how-to-configure-published-applicationsmedvv2.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
311
mdop/medv-v1/how-to-generate-reports-medvv2.md
Normal file
311
mdop/medv-v1/how-to-generate-reports-medvv2.md
Normal file
@ -0,0 +1,311 @@
|
|||||||
|
---
|
||||||
|
title: How to Generate Reports
|
||||||
|
description: How to Generate Reports
|
||||||
|
ms.assetid: 9f8ba28e-1993-4c11-a28a-493718051e5d
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Generate Reports
|
||||||
|
|
||||||
|
|
||||||
|
The following report types can be created by administrators in MED-V:
|
||||||
|
|
||||||
|
- [Status](#bkmk-generatingastatusreport)—Use the status report to review the current status of all active users and all MED-V workspaces of each user based on a defined period of time. This includes viewing computers that are currently connected to the server or, if they are not currently connected, the date and time they were last connected to the server, the status of each computer, and other relevant information.
|
||||||
|
|
||||||
|
- [Activity Log](#bkmk-generatinganactivitylogreport)—Use this report to review events that originated from a specific host or user in a defined date range.
|
||||||
|
|
||||||
|
- [Error Log](#bkmk-generatinganerrorlogreport)—Use this report to view errors that originated from a specific host or user in a defined date range.
|
||||||
|
|
||||||
|
The report results can be sorted by any column by clicking the appropriate column name.
|
||||||
|
|
||||||
|
The report results can be grouped by dragging a column header to the top of the report. Drag multiple column headers to group one column after another.
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-generatingastatusreport"></a>How to Generate a Status Report
|
||||||
|
|
||||||
|
|
||||||
|
**To generate a status report**
|
||||||
|
|
||||||
|
1. Click the **Reports** management button.
|
||||||
|
|
||||||
|
2. In the **Reports** module, on the **Report Types** menu, select **Status**, and click **Generate**.
|
||||||
|
|
||||||
|
The Report Parameters dialog box appears.
|
||||||
|
|
||||||
|
3. In the **Report Parameters** dialog box, in the **Number of days** field, enter a number or use the arrows to select the number of days to include in the status report, and click **OK**.
|
||||||
|
|
||||||
|
A status report is generated. The report parameters are defined in the following table.
|
||||||
|
|
||||||
|
**Client MED-V Workspace Properties**
|
||||||
|
|
||||||
|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="50%" />
|
||||||
|
<col width="50%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead>
|
||||||
|
<tr class="header">
|
||||||
|
<th align="left">Property</th>
|
||||||
|
<th align="left">Description</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Time</p></td>
|
||||||
|
<td align="left"><p>The date and time the event occurred.</p>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>By default, the events are displayed in descending date order. However, it can be changed by clicking the Time Received column.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>User Name</p></td>
|
||||||
|
<td align="left"><p>The user who initiated the event.</p>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>If the event occurred before a user logged on, the user name is SYSTEM.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Host Name</p></td>
|
||||||
|
<td align="left"><p>The name of the host computer.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Workspace Name</p></td>
|
||||||
|
<td align="left"><p>The name of the MED-V workspace.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Workspace Computer Name</p></td>
|
||||||
|
<td align="left"><p>The name of the computer the MED-V workspace is running on.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Online</p></td>
|
||||||
|
<td align="left"><p>The current state of the client computer:</p>
|
||||||
|
<ul>
|
||||||
|
<li><p><strong>Stopped</strong></p></li>
|
||||||
|
<li><p><strong>Started at <date and time the workspace was started></strong></p></li>
|
||||||
|
</ul></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Client Version</p></td>
|
||||||
|
<td align="left"><p>The version number of the client.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Policy Version</p></td>
|
||||||
|
<td align="left"><p>The policy version that the MED-V workspace is currently using.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Image Name</p></td>
|
||||||
|
<td align="left"><p>The name of the image.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Image Version</p></td>
|
||||||
|
<td align="left"><p>The image version that the MED-V workspace is currently using.</p>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>MED-V workspace version can be Unknown if it has not yet been downloaded onto a computer.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div></td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-generatinganactivitylogreport"></a>How to Generate an Activity Log Report
|
||||||
|
|
||||||
|
|
||||||
|
**To generate an activity log report**
|
||||||
|
|
||||||
|
1. Click the **Reports** management button.
|
||||||
|
|
||||||
|
The Reports module appears.
|
||||||
|
|
||||||
|
2. In the **Reports** module, on the **Report Types** menu, select **Activity Log**, and click **Generate**.
|
||||||
|
|
||||||
|
3. In the **Report Parameters** dialog box, configure one or more of the following parameters:
|
||||||
|
|
||||||
|
- **Number of days**—The number of days to display in the report.
|
||||||
|
|
||||||
|
- **User name contains**—Any event where the user name contains the text entered is included in the report.
|
||||||
|
|
||||||
|
- **Host name contains**—Any event where the host name contains the text entered is included in the report.
|
||||||
|
|
||||||
|
4. Click **OK**.
|
||||||
|
|
||||||
|
A report is generated with the events and dates selected. The report parameters are defined in the following table.
|
||||||
|
|
||||||
|
**Activity Log Report Properties**
|
||||||
|
|
||||||
|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="50%" />
|
||||||
|
<col width="50%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead>
|
||||||
|
<tr class="header">
|
||||||
|
<th align="left">Property</th>
|
||||||
|
<th align="left">Description</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Event ID</p></td>
|
||||||
|
<td align="left"><p>The event ID.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Severity</p></td>
|
||||||
|
<td align="left"><p><strong>Information, Error, Warning</strong></p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Category</p></td>
|
||||||
|
<td align="left"><p>The module that the report is referring to.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Description</p></td>
|
||||||
|
<td align="left"><p>A description of the event.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Time Received</p></td>
|
||||||
|
<td align="left"><p>The date and time the event was received on the server.</p>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>If the client is working offline, the server receives the reports when the client is online.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>By default, the events are displayed in descending date order. However, it can be changed by clicking the <strong>Time Received</strong> column.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Client Time</p></td>
|
||||||
|
<td align="left"><p>The date and time the event occurred according to the client clock.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Host Name</p></td>
|
||||||
|
<td align="left"><p>The name of the host computer.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>User Name</p></td>
|
||||||
|
<td align="left"><p>The user who initiated the event.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Workspace Name</p></td>
|
||||||
|
<td align="left"><p>The name of the MED-V workspace.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Workspace Computer Name</p></td>
|
||||||
|
<td align="left"><p>The name of the computer the MED-V workspace is running on.</p></td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-generatinganerrorlogreport"></a>How to Generate an Error Log Report
|
||||||
|
|
||||||
|
|
||||||
|
**To generate an error log report**
|
||||||
|
|
||||||
|
1. Click the **Reports** management button.
|
||||||
|
|
||||||
|
2. In the **Reports** module, on the **Report Types** menu, select **Error Log**, and click **Generate**.
|
||||||
|
|
||||||
|
3. In the **Report Parameters** dialog box, configure one or more of the following parameters:
|
||||||
|
|
||||||
|
- **Number of days**—The number of days to display in the report.
|
||||||
|
|
||||||
|
- **User name contains**—Any event where the user name contains the text entered is included in the report.
|
||||||
|
|
||||||
|
- **Host name contains**—Any event where the host name contains the text entered is included in the report.
|
||||||
|
|
||||||
|
4. Click **OK**.
|
||||||
|
|
||||||
|
A report is generated with the events and dates selected. The report parameters are defined in the following table.
|
||||||
|
|
||||||
|
**Error Log Report Properties**
|
||||||
|
|
||||||
|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="50%" />
|
||||||
|
<col width="50%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead>
|
||||||
|
<tr class="header">
|
||||||
|
<th align="left">Property</th>
|
||||||
|
<th align="left">Description</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Event ID</p></td>
|
||||||
|
<td align="left"><p>The event ID.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Category</p></td>
|
||||||
|
<td align="left"><p>The module that the report is referring to.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Description</p></td>
|
||||||
|
<td align="left"><p>A description of the event.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Time Received</p></td>
|
||||||
|
<td align="left"><p>The date and time the event was received on the server.</p>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>If the client is working offline, the server receives the reports when the client is online.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>By default, the events are displayed in descending date order. However, it can be changed by clicking the <strong>Time Received</strong> column.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Client Time</p></td>
|
||||||
|
<td align="left"><p>The date and time the event occurred according to the client clock.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Host Name</p></td>
|
||||||
|
<td align="left"><p>The name of the host computer.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>User Name</p></td>
|
||||||
|
<td align="left"><p>The user who initiated the event.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Workspace Name</p></td>
|
||||||
|
<td align="left"><p>The name of the MED-V workspace.</p></td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
55
mdop/medv-v1/how-to-import-and-export-a-policy.md
Normal file
55
mdop/medv-v1/how-to-import-and-export-a-policy.md
Normal file
@ -0,0 +1,55 @@
|
|||||||
|
---
|
||||||
|
title: How to Import and Export a Policy
|
||||||
|
description: How to Import and Export a Policy
|
||||||
|
ms.assetid: c86455de-2096-4bb1-b9d3-22efb42f3317
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Import and Export a Policy
|
||||||
|
|
||||||
|
|
||||||
|
A MED-V workspace policy can be imported into MED-V or exported from MED-V.
|
||||||
|
|
||||||
|
## How to Import a Policy
|
||||||
|
|
||||||
|
|
||||||
|
**To import an existing policy**
|
||||||
|
|
||||||
|
1. In the **Policy** module, on the **Policy** menu, select **Import**.
|
||||||
|
|
||||||
|
2. In the **Import policy** dialog box, browse to the file containing the policy to import.
|
||||||
|
|
||||||
|
3. Click **Open**.
|
||||||
|
|
||||||
|
The policy is imported, replacing the existing policy.
|
||||||
|
|
||||||
|
## How to Export a Policy
|
||||||
|
|
||||||
|
|
||||||
|
**To export a policy**
|
||||||
|
|
||||||
|
1. In the **Policy** module, on the **Policy** menu, select **Export**.
|
||||||
|
|
||||||
|
2. In the **Export policy** dialog box, browse to the directory where the policy will be exported.
|
||||||
|
|
||||||
|
3. Enter a name for the policy file.
|
||||||
|
|
||||||
|
4. Click **Save**.
|
||||||
|
|
||||||
|
The policy is exported.
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[Creating a MED-V Workspace](creating-a-med-v-workspacemedv-10-sp1.md)
|
||||||
|
|
||||||
|
[Using the MED-V Management Console User Interface](using-the-med-v-management-console-user-interface.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -0,0 +1,186 @@
|
|||||||
|
---
|
||||||
|
title: How to Install and Configure the MED-V Server Component
|
||||||
|
description: How to Install and Configure the MED-V Server Component
|
||||||
|
ms.assetid: 2d3c5b15-df2c-4ab6-bf78-f47ef8ae7418
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Install and Configure the MED-V Server Component
|
||||||
|
|
||||||
|
|
||||||
|
This section explains how to [install](#bkmk-howtoinstallthemedvserver) and [configure](#bkmk-howtoconfigurethemedvserver) the MED-V server.
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-howtoinstallthemedvserver"></a>How to Install the MED-V Server
|
||||||
|
|
||||||
|
|
||||||
|
**To install the MED-V server**
|
||||||
|
|
||||||
|
1. Install the MED-V Server .msi package.
|
||||||
|
|
||||||
|
The MED-V Server .msi package is called *MED-V\_Server\_x.msi*, where x is the version number.
|
||||||
|
|
||||||
|
For example, *MED-V\_Server\_1.0.65.msi*.
|
||||||
|
|
||||||
|
2. When the **InstallShield Wizard Welcome** screen appears, click **Next**.
|
||||||
|
|
||||||
|
3. On the **License Agreement** screen, read the license agreement, click **I accept the terms in the license agreement**, and then click **Next**.
|
||||||
|
|
||||||
|
The **Destination Folder** screen appears, with the default installation folder displayed.
|
||||||
|
|
||||||
|
The default installation folder is *%systemdrive%\\Program Files\\Microsoft Enterprise Desktop Virtualization\\*.
|
||||||
|
|
||||||
|
- To change the folder where MED-V should be installed, click **Change** and browse to an existing folder.
|
||||||
|
|
||||||
|
4. Click **Next**.
|
||||||
|
|
||||||
|
5. On the **Ready to Install the Program** screen, click **Install**.
|
||||||
|
|
||||||
|
The MED-V server installation starts. This can take several minutes, and the screen might not display text. During installation, several progress screens appear. If a message appears, follow the instructions provided.
|
||||||
|
|
||||||
|
6. When the **InstallShield Wizard Completed** screen appears, click **Finish** to complete the wizard.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
If you are installing the MED-V server via Microsoft Remote Desktop, use the following syntax: **mstsc/admin**. Ensure that your RDP session is directed to the console.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-howtoconfigurethemedvserver"></a>How to Configure the MED-V Server
|
||||||
|
|
||||||
|
|
||||||
|
The following server settings can be configured:
|
||||||
|
|
||||||
|
- [Connections](#bkmk-configuringconnections)
|
||||||
|
|
||||||
|
- [Images](#bkmk-configuringimages)
|
||||||
|
|
||||||
|
- [Permissions](#bkmk-configuringpermissions)
|
||||||
|
|
||||||
|
- [Reports](#bkmk-configuringreports)
|
||||||
|
|
||||||
|
### <a href="" id="bkmk-configuringconnections"></a>Configuring Connections
|
||||||
|
|
||||||
|
**To configure connections**
|
||||||
|
|
||||||
|
1. On the Windows Start menu, select **All Programs > MED-V > MED-V Server Configuration Manager**.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
Note: If you selected the **Launch MED-V Server Configuration Manager** check box during the server installation, the MED-V server configuration manager starts automatically after the server installation is complete.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
The MED-V Server Configuration Manager appears.
|
||||||
|
|
||||||
|
2. On the **Connections** tab, configure the following client connections settings:
|
||||||
|
|
||||||
|
- **Enable unencrypted connections (http), using port**—Select this check box to enable unencrypted connections using a specified port. In the port box, enter the server port on which to accept unencrypted connections (http).
|
||||||
|
|
||||||
|
- **Enable encrypted connections (https), using port**—Select this check box to enable encrypted connections using a specified port. In the port box, enter the server port on which to accept encrypted connections (https).
|
||||||
|
|
||||||
|
Https is an optional configuration which can be set to ensure secure transactions between the MED-V server and MED-V clients. To configure https, you must perform the following procedures:
|
||||||
|
|
||||||
|
- Configure a certificate on the server.
|
||||||
|
|
||||||
|
- Associate the server certificate with the port specified using netsh. For information, see the following:
|
||||||
|
|
||||||
|
- [Netsh Commands for Hypertext Transfer Protocol (HTTP)](http://go.microsoft.com/fwlink/?LinkId=183314)
|
||||||
|
|
||||||
|
- [How to: Configure a Port with an SSL Certificate](http://go.microsoft.com/fwlink/?LinkID=183315)
|
||||||
|
|
||||||
|
- [How to: Configure a Port with an SSL Certificate](http://msdn.microsoft.com/library/ms733791.aspx)
|
||||||
|
|
||||||
|
3. Click **OK**.
|
||||||
|
|
||||||
|
### <a href="" id="bkmk-configuringimages"></a>Configuring Images
|
||||||
|
|
||||||
|
**To configure images**
|
||||||
|
|
||||||
|
1. Click the **Images** tab.
|
||||||
|
|
||||||
|
2. Configure the following image management settings:
|
||||||
|
|
||||||
|
- **VMs Directory**—The virtual machine directory (the directory where the images are stored). This field contains a UNC path to the image directory on the image distribution server that should be accessible from the MED-V server.
|
||||||
|
|
||||||
|
- **VMs URL**—The location of the server where the images are stored.
|
||||||
|
|
||||||
|
3. Click **OK**.
|
||||||
|
|
||||||
|
### <a href="" id="bkmk-configuringpermissions"></a>Configuring Permissions
|
||||||
|
|
||||||
|
**To configure permissions**
|
||||||
|
|
||||||
|
1. Click the **Permissions** tab.
|
||||||
|
|
||||||
|
2. A list of all users who can log in is provided. To apply read and write permissions to a user, select the check box next to the user. To apply read-only permissions to a user, clear the check box.
|
||||||
|
|
||||||
|
3. To add domain users or groups, click **Add**.
|
||||||
|
|
||||||
|
The **Enter User or Group names** dialog box appears.
|
||||||
|
|
||||||
|
1. Select domain users or groups by doing one of the following:
|
||||||
|
|
||||||
|
- In the **Enter User or Group names** field, type a user or group that exists in the domain or exists as a local user or group on the computer. Then click **Check Names** to resolve it to the full existent name.
|
||||||
|
|
||||||
|
- Click **Find** to open the standard **Select Users or Groups** dialog box. Then select domain users or groups.
|
||||||
|
|
||||||
|
2. Click **OK**.
|
||||||
|
|
||||||
|
4. To remove domain users or groups, select a user or group and click **Remove**.
|
||||||
|
|
||||||
|
5. Click **OK**.
|
||||||
|
|
||||||
|
### <a href="" id="bkmk-configuringreports"></a>Configuring Reports
|
||||||
|
|
||||||
|
**To configure reports**
|
||||||
|
|
||||||
|
1. Click the **Reports** tab.
|
||||||
|
|
||||||
|
2. To support reports, select **Enable reports**.
|
||||||
|
|
||||||
|
3. In the **Connection String** box, enter a connection string for the MSSQL database.
|
||||||
|
|
||||||
|
- When SQL Server is installed on a remote server, use the following connection string:
|
||||||
|
|
||||||
|
`Data Source=<ServerName>;Initial Catalog=<DBName>;uid=sa;pwd=<Password>;`
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
Note: To connect to SQL Express, use: `Data Source=<ServerName>\sqlexpress.`
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
4. To create the database, click **Create Database**.
|
||||||
|
|
||||||
|
5. To test the connection, click **Test Connection**.
|
||||||
|
|
||||||
|
6. To configure database clearing options, click **Clear Options**.
|
||||||
|
|
||||||
|
The **Clear Database Options** dialog box appears.
|
||||||
|
|
||||||
|
1. Choose one of the following options:
|
||||||
|
|
||||||
|
- **Clear data older than**—Clear all data older than the number of days specified; in the number box, enter a number of days.
|
||||||
|
|
||||||
|
- **Clear all data from database**—Clear all existent data in the database.
|
||||||
|
|
||||||
|
- **Drop database**—Delete the database.
|
||||||
|
|
||||||
|
2. Click **OK** to apply changes and close the dialog box.
|
||||||
|
|
||||||
|
7. Click **OK** to save the changes, or click **Cancel** to close the dialog box without saving changes.
|
||||||
|
|
||||||
|
8. If prompted, restart the MED-V server service to apply changes to the network settings.
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[Supported Configurations](supported-configurationsmedv-orientation.md)
|
||||||
|
|
||||||
|
[Design the MED-V Server Infrastructure](design-the-med-v-server-infrastructure.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -0,0 +1,96 @@
|
|||||||
|
---
|
||||||
|
title: How to Install MED-V Client and MED-V Management Console
|
||||||
|
description: How to Install MED-V Client and MED-V Management Console
|
||||||
|
ms.assetid: 8a5f3010-3a50-487e-99d8-e352e5cb51c6
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Install MED-V Client and MED-V Management Console
|
||||||
|
|
||||||
|
|
||||||
|
The following MED-V components are included in the client .msi package:
|
||||||
|
|
||||||
|
- MED-V client—The MED-V software that must be installed on client computers for running MED-V workspaces.
|
||||||
|
|
||||||
|
- MED-V management console—The administrative tool that administrators can use to create and maintain images, MED-V workspaces, and policies.
|
||||||
|
|
||||||
|
The MED-V management console and the MED-V client are both installed from the MED-V client .msi package. The MED-V client, however, can be installed independently without the MED-V management console by clearing the **Install the MED-V Management application** check box during installation.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
The MED-V client and MED-V management console can only be installed on Windows 7-, Windows Vista-, and Windows XP-based computers. They cannot be installed on server products.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
Do not install the MED-V client using the Windows **runas** command.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**To install the MED-V client**
|
||||||
|
|
||||||
|
1. Log in as a user with local administrator rights on the local computer.
|
||||||
|
|
||||||
|
2. Run the MED-V .msi package.
|
||||||
|
|
||||||
|
The MED-V .msi package is called *MED-V\_x.msi*, where *x* is the version number.
|
||||||
|
|
||||||
|
For example, *MED-V\_1.0.65.msi*.
|
||||||
|
|
||||||
|
3. When the **InstallShield Wizard Welcome** screen appears, click **Next**.
|
||||||
|
|
||||||
|
4. On the **License Agreement** screen, read the license agreement, click **I accept the terms in the license agreement**, and click **Next**.
|
||||||
|
|
||||||
|
The **Destination Folder** screen appears, with the default installation folder displayed.
|
||||||
|
|
||||||
|
The default installation folder is the directory where the operating system is installed.
|
||||||
|
|
||||||
|
- To change the folder where MED-V should be installed, click **Change**, and browse to an existing folder.
|
||||||
|
|
||||||
|
5. Click **Next**.
|
||||||
|
|
||||||
|
6. On the **MED-V Settings** screen, configure the MED-V installation as follows:
|
||||||
|
|
||||||
|
- Select the **Install the MED-V management application** check box to include the management component in the installation.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
Enterprise Desktop Virtualization administrators should install the MED-V management application. This application is required for configuring desktop images and MED-V workspaces.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- Select the **Load MED-V when Windows starts** check box to start MED-V automatically on startup.
|
||||||
|
|
||||||
|
- Select the **Add a MED-V shortcut to my desktop** check box to create a MED-V shortcut on your desktop.
|
||||||
|
|
||||||
|
- In the **Server address** field, type the server address.
|
||||||
|
|
||||||
|
- In the **Server port** field, type the server's port.
|
||||||
|
|
||||||
|
- Select the **Server requires encrypted connections (https)** check box to work with https.
|
||||||
|
|
||||||
|
- The default virtual machine images folder is displayed. The default installation folder is *%systemdrive%\\MED-V Images\\*. To change the folder where MED-V should be installed, click **Change**, and browse to an existing folder.
|
||||||
|
|
||||||
|
7. Click **Next**.
|
||||||
|
|
||||||
|
8. On the **Ready to Install the Program** screen, click **Install**.
|
||||||
|
|
||||||
|
The MED-V client installation starts. This can take several minutes, and the screen might not display text. During installation, several progress screens appear. If a message appears, follow the instructions provided.
|
||||||
|
|
||||||
|
Upon successful installation, the **InstallShield Wizard Completed** screen appears.
|
||||||
|
|
||||||
|
9. Click **Finish** to close the wizard.
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[Supported Configurations](supported-configurationsmedv-orientation.md)
|
||||||
|
|
||||||
|
[Installation and Upgrade Checklists](installation-and-upgrade-checklists.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -0,0 +1,68 @@
|
|||||||
|
---
|
||||||
|
title: How to Install MED-V Client
|
||||||
|
description: How to Install MED-V Client
|
||||||
|
ms.assetid: bfac6de7-d96d-4b3e-bd8b-183e051e53c8
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Install MED-V Client
|
||||||
|
|
||||||
|
|
||||||
|
In a deployment package-based scenario, the MED-V client installation is included in the deployment package and installed directly from the package.
|
||||||
|
|
||||||
|
**Important**
|
||||||
|
When using a deployment package that does not include an image, ensure that the image is uploaded to the Web or pushed to the pre-stage folder prior to installing the deployment package.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**To install a deployment package**
|
||||||
|
|
||||||
|
1. Do one of the following:
|
||||||
|
|
||||||
|
- Download the MED-V package from the Web.
|
||||||
|
|
||||||
|
- Insert the deployment USB or DVD into the host drive.
|
||||||
|
|
||||||
|
2. If MED-V does not launch automatically, double-click MED-VAutoInstaller.exe.
|
||||||
|
|
||||||
|
A dialog box appears listing the components that are already installed and those that are currently being installed.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
If a version of the Microsoft Virtual PC that is not supported exists on the host computer, a message will appear telling you to uninstall the existing version and run the installer again.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
If an older version of the MED-V client exists, it will prompt you asking whether you want to upgrade.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Depending on the components that have been installed, you might need to reboot. If rebooting is necessary, a message appears notifying you that you must reboot.
|
||||||
|
|
||||||
|
3. If necessary, reboot the computer.
|
||||||
|
|
||||||
|
When the installation is complete, MED-V starts and a message appears notifying you that the installation is complete.
|
||||||
|
|
||||||
|
4. Log in to MED-V using the following user name and password:
|
||||||
|
|
||||||
|
- Type in the domain name and user name followed by the password of the domain user who is permitted to work with MED-V.
|
||||||
|
|
||||||
|
Example: "domain\_name\\user\_name", "password"
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[How to Configure a Deployment Package](how-to-configure-a-deployment-package.md)
|
||||||
|
|
||||||
|
[How to Upload a MED-V Image to the Server](how-to-upload-a-med-v-image-to-the-server.md)
|
||||||
|
|
||||||
|
[Client Installation Command Line Reference](client-installation-command-line-reference.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
22
mdop/medv-v1/how-to-install-med-v-clientesds.md
Normal file
22
mdop/medv-v1/how-to-install-med-v-clientesds.md
Normal file
@ -0,0 +1,22 @@
|
|||||||
|
---
|
||||||
|
title: How to Install MED-V Client
|
||||||
|
description: How to Install MED-V Client
|
||||||
|
ms.assetid: fb35f618-684c-474f-9053-b70bb29c3cc0
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Install MED-V Client
|
||||||
|
|
||||||
|
|
||||||
|
Before installing the MED-V client .msi package on users’ computers, ensure that the image is uploaded to the Web or pushed to the image pre-stage folder.
|
||||||
|
|
||||||
|
To install MED-V client using an enterprise software distribution center, refer to the documentation on how to install applications using the system you are using.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,70 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
58
mdop/medv-v1/how-to-localize-a-med-v-image.md
Normal file
58
mdop/medv-v1/how-to-localize-a-med-v-image.md
Normal file
@ -0,0 +1,58 @@
|
|||||||
|
---
|
||||||
|
title: How to Localize a MED-V Image
|
||||||
|
description: How to Localize a MED-V Image
|
||||||
|
ms.assetid: adc148b3-8cfe-42a0-8847-be6b689a673a
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Localize a MED-V Image
|
||||||
|
|
||||||
|
|
||||||
|
A MED-V image can be localized, either by unpacking a packed image or by downloading an image from the server. All local images appear in the local repository.
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-extractinganimageforusebythelocalclient"></a>How to Extract a MED-V Image for Use by the Local Client
|
||||||
|
|
||||||
|
|
||||||
|
A packed image can be unpacked to the local repository by extracting it. It then does not need to be downloaded from the server.
|
||||||
|
|
||||||
|
**To extract a MED-V image**
|
||||||
|
|
||||||
|
1. In the **Local Packed Images** pane, select an image.
|
||||||
|
|
||||||
|
2. Right-click, and from the drop-down menu, select **Extract image**.
|
||||||
|
|
||||||
|
The image is extracted to the local drive and can now be used by the local client running on the computer.
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-downloadinganimagetothelocalrepoitory"></a>How to Download a MED-V Image to the Local Repository
|
||||||
|
|
||||||
|
|
||||||
|
**To download a MED-V image**
|
||||||
|
|
||||||
|
1. In the **Packed Images on Server** pane, select the image or version of the image to download.
|
||||||
|
|
||||||
|
2. Click **Download**.
|
||||||
|
|
||||||
|
The image is downloaded to your local computer.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
The downloaded image will not appear in the **Local Images** pane until you refresh the page. Click Refresh to see the downloaded image in the **Local Images** pane.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[How to Install MED-V Client and MED-V Management Console](how-to-install-med-v-client-and-med-v-management-console.md)
|
||||||
|
|
||||||
|
[Using the MED-V Management Console User Interface](using-the-med-v-management-console-user-interface.md)
|
||||||
|
|
||||||
|
[How to Upload a MED-V Image to the Server](how-to-upload-a-med-v-image-to-the-server.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
44
mdop/medv-v1/how-to-lock-and-unlock-a-workspace.md
Normal file
44
mdop/medv-v1/how-to-lock-and-unlock-a-workspace.md
Normal file
@ -0,0 +1,44 @@
|
|||||||
|
---
|
||||||
|
title: How to Lock and Unlock a Workspace
|
||||||
|
description: How to Lock and Unlock a Workspace
|
||||||
|
ms.assetid: 027166b9-0e06-4a4e-a8ac-a4d5f429656f
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Lock and Unlock a Workspace
|
||||||
|
|
||||||
|
|
||||||
|
## How to Lock a Workspace
|
||||||
|
|
||||||
|
|
||||||
|
**To lock a MED-V workspace that is currently running**
|
||||||
|
|
||||||
|
1. In the notification area, right-click the MED-V icon.
|
||||||
|
|
||||||
|
2. On the submenu, click **Lock Workspace**.
|
||||||
|
|
||||||
|
The MED-V workspace is locked.
|
||||||
|
|
||||||
|
## How to Unlock a Workspace
|
||||||
|
|
||||||
|
|
||||||
|
**To unlock a MED-V workspace**
|
||||||
|
|
||||||
|
1. In the notification area, right-click the MED-V icon.
|
||||||
|
|
||||||
|
2. On the submenu, click **Unlock Workspace**.
|
||||||
|
|
||||||
|
3. In the **Unlock Workspace** dialog box, enter your **Password**.
|
||||||
|
|
||||||
|
4. Click **Unlock**.
|
||||||
|
|
||||||
|
The MED-V workspace is unlocked.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,59 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,64 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
107
mdop/medv-v1/how-to-pack-a-med-v-image.md
Normal file
107
mdop/medv-v1/how-to-pack-a-med-v-image.md
Normal file
@ -0,0 +1,107 @@
|
|||||||
|
---
|
||||||
|
title: How to Pack a MED-V Image
|
||||||
|
description: How to Pack a MED-V Image
|
||||||
|
ms.assetid: e1ce2307-0f1b-4bf8-b146-e4012dc138d2
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Pack a MED-V Image
|
||||||
|
|
||||||
|
|
||||||
|
A MED-V image must be packed before it can be added to a deployment package or uploaded to the server.
|
||||||
|
|
||||||
|
**To create a packed MED-V image**
|
||||||
|
|
||||||
|
1. Click the **Images** management button.
|
||||||
|
|
||||||
|
2. In the **Images** module, in the **Local Packed Images** pane, click **New**.
|
||||||
|
|
||||||
|
3. In the **Packed Image Creation** dialog box, select the virtual machine image by doing one of the following:
|
||||||
|
|
||||||
|
- In the **Base image file** field, type the full path to the directory where the Microsoft Virtual PC image prepared for MED-V is located.
|
||||||
|
|
||||||
|
- Click **Browse** to browse to the directory where the Microsoft Virtual PC image prepared for MED-V is located.
|
||||||
|
|
||||||
|
4. Specify the name of the new image by doing one of the following:
|
||||||
|
|
||||||
|
- In the **Image name** field, type the desired name.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
The following characters cannot be included in the image name: space " < > | \\ / : \* ?
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
A new packed image will be created.
|
||||||
|
|
||||||
|
- From the drop-down list, select an existing name.
|
||||||
|
|
||||||
|
A new version of the existing image will be created.
|
||||||
|
|
||||||
|
5. Click **OK**.
|
||||||
|
|
||||||
|
A new MED-V packed image is created on your host computer with the properties defined in the following table.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
In the **Local Packed Images** and **Packed Images on Server** panes, the most recent version of each image is displayed as the parent node. Click the parent node to view all other existing versions of the image.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**Local Packed Images Properties**
|
||||||
|
|
||||||
|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="50%" />
|
||||||
|
<col width="50%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead>
|
||||||
|
<tr class="header">
|
||||||
|
<th align="left">Property</th>
|
||||||
|
<th align="left">Description</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Image Name</p></td>
|
||||||
|
<td align="left"><p>The name of the packed image as it was defined when the administrator created the image.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Version</p></td>
|
||||||
|
<td align="left"><p>The version of the displayed image.</p>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>All previous versions are kept unless deleted.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>File Size (compressed)</p></td>
|
||||||
|
<td align="left"><p>The physical compressed size of the image.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Image Size (uncompressed)</p></td>
|
||||||
|
<td align="left"><p>The physical uncompressed size of the image.</p></td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[How to Install MED-V Client and MED-V Management Console](how-to-install-med-v-client-and-med-v-management-console.md)
|
||||||
|
|
||||||
|
[Using the MED-V Management Console User Interface](using-the-med-v-management-console-user-interface.md)
|
||||||
|
|
||||||
|
[Creating a Virtual PC Image for MED-V](creating-a-virtual-pc-image-for-med-v.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,102 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
61
mdop/medv-v1/how-to-set-advanced-file-transfer-options.md
Normal file
61
mdop/medv-v1/how-to-set-advanced-file-transfer-options.md
Normal file
@ -0,0 +1,61 @@
|
|||||||
|
---
|
||||||
|
title: How to Set Advanced File Transfer Options
|
||||||
|
description: How to Set Advanced File Transfer Options
|
||||||
|
ms.assetid: 5e9f8749-a5a9-48c6-9bfc-6b8e0cbe6cab
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Set Advanced File Transfer Options
|
||||||
|
|
||||||
|
|
||||||
|
**To set advanced file transfer options**
|
||||||
|
|
||||||
|
1. In the **Deployment** pane, click **Advanced**.
|
||||||
|
|
||||||
|
2. In the **File Transfer Options** dialog box, configure the parameters as described in the following table.
|
||||||
|
|
||||||
|
3. Click **OK**.
|
||||||
|
|
||||||
|
**File Transfer Options Properties**
|
||||||
|
|
||||||
|
Property
|
||||||
|
Description
|
||||||
|
*Workspace to Host*
|
||||||
|
|
||||||
|
Run command on received files
|
||||||
|
|
||||||
|
Select this check box to run a command line on all files transferred to the host. In the command-line box, enter the command line to run on all received files.
|
||||||
|
|
||||||
|
File types
|
||||||
|
|
||||||
|
- **Allow all file extensions**—Click to enable transferring files of any file name extension from the MED-V workspace to the host.
|
||||||
|
|
||||||
|
- **Allow the following file extensions**—Click to enable only files with specified file name extensions to be transferred. In the empty field, enter all file name extensions allowed, separated by commas.
|
||||||
|
|
||||||
|
*Host to Workspace*
|
||||||
|
|
||||||
|
Run command on received files
|
||||||
|
|
||||||
|
Select this check box to run a command line on all files transferred to the MED-V workspace. In the command-line box, enter the command line to run on all transferred files.
|
||||||
|
|
||||||
|
File types
|
||||||
|
|
||||||
|
- **Allow all file extensions**—Click to enable transferring files of any file name extension.
|
||||||
|
|
||||||
|
- **Allow the following file extensions**—Click to enable only files with specified file name extensions to be transferred from the host to the MED-V workspace. In the empty field, enter all file name extensions allowed, separated by colons.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[How to Configure a Domain User or Group](how-to-configure-a-domain-user-or-groupmedvv2.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
42
mdop/medv-v1/how-to-set-med-v-workspace-deletion-options.md
Normal file
42
mdop/medv-v1/how-to-set-med-v-workspace-deletion-options.md
Normal file
@ -0,0 +1,42 @@
|
|||||||
|
---
|
||||||
|
title: How to Set MED-V Workspace Deletion Options
|
||||||
|
description: How to Set MED-V Workspace Deletion Options
|
||||||
|
ms.assetid: 0f85aa81-c188-4115-9141-ceba2473c00e
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Set MED-V Workspace Deletion Options
|
||||||
|
|
||||||
|
|
||||||
|
## Workspace Deletion Options
|
||||||
|
|
||||||
|
|
||||||
|
The administrator can set the MED-V workspace deletion options for each user or group so that the MED-V workspace is automatically deleted under certain conditions.
|
||||||
|
|
||||||
|
**To set MED-V workspace deletion options**
|
||||||
|
|
||||||
|
1. In the **Deployment** pane, click **Workspace deletion options**.
|
||||||
|
|
||||||
|
2. In the **Workspace Deletion Options** dialog box, select from the following options:
|
||||||
|
|
||||||
|
- **The Workspace has been disabled**—If the administrator disables the MED-V workspace, the MED-V workspace is deleted from the user or group computer.
|
||||||
|
|
||||||
|
- **The Workspace has expired**—If the MED-V workspace expires according to the date specified, the MED-V workspace is deleted from the user or group computer.
|
||||||
|
|
||||||
|
- **User is offline for more than the allowed period**—If the policy is not refreshed in the time period specified since the user was offline, the MED-V workspace is deleted from the user or group computer.
|
||||||
|
|
||||||
|
3. Click **OK**.
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[How to Configure a Domain User or Group](how-to-configure-a-domain-user-or-groupmedvv2.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
265
mdop/medv-v1/how-to-set-up-script-actions.md
Normal file
265
mdop/medv-v1/how-to-set-up-script-actions.md
Normal file
@ -0,0 +1,265 @@
|
|||||||
|
---
|
||||||
|
title: How to Set Up Script Actions
|
||||||
|
description: How to Set Up Script Actions
|
||||||
|
ms.assetid: 367e28f1-d8c2-4845-a01b-2fff9128ccfd
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Set Up Script Actions
|
||||||
|
|
||||||
|
|
||||||
|
The script actions editor allows the administrator to create actions to be performed during MED-V workspace setup, as well as to define the order in which they are performed.
|
||||||
|
|
||||||
|
The following is a list of actions that can be added to the domain setup script:
|
||||||
|
|
||||||
|
- **Restart Windows**—Restart Windows.
|
||||||
|
|
||||||
|
- **Join Domain**—If joining a domain, include this action and configure the user name, password, fully qualified domain name, NetBIOS domain name, and organization unit (optional).
|
||||||
|
|
||||||
|
- **Check Connectivity**—Configure a server to connect to and verify that the MED-V workspace can connect to a network resource (such as the domain server).
|
||||||
|
|
||||||
|
- **Command Line**—Configure a script in the MED-V workspace, and enter a command line that includes the path of the script and the script arguments.
|
||||||
|
|
||||||
|
- **Rename Computer**—Rename the virtual machine computer based on the defined settings.
|
||||||
|
|
||||||
|
- **Disable Auto-Logon**—Disable Windows Auto-Logon. This action should be added at the end of scripts that add the computer to the domain.
|
||||||
|
|
||||||
|
## <a href="" id="how-to-set-up-script-actions-"></a>How to Set Up Script Actions
|
||||||
|
|
||||||
|
|
||||||
|
**To set up script actions**
|
||||||
|
|
||||||
|
1. On the **VM Setup** tab, click **Script Editor**.
|
||||||
|
|
||||||
|
2. In the **Script Actions** dialog box, click **Add**, and on the submenu, click the desired actions.
|
||||||
|
|
||||||
|
3. Configure the actions as described in the following tables.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
**Rename Computer** is configured in the **VM Settings** tab. For more information, see [How to Configure VM Computer Name Pattern Properties](how-to-configure-vm-computer-name-pattern-propertiesmedvv2.md).
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
To rename a computer, Windows must be restarted. It is recommended to add a Restart Windows action following a Rename Computer action.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
4. Set the order of the actions by selecting an action and clicking **Up** or **Down**.
|
||||||
|
|
||||||
|
5. Click **OK**.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
When running the Join Domain script, for the script to work, the user logged into the MED-V workspace virtual machine must have local administrator rights.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
When running the Disable Auto-Logon script, it is recommended to disable the local guest account used for the auto-logon once the initial setup is complete.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
### <a href="" id="bkmk-joindomainproperties"></a>
|
||||||
|
|
||||||
|
**Join Domain Properties**
|
||||||
|
|
||||||
|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="50%" />
|
||||||
|
<col width="50%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead>
|
||||||
|
<tr class="header">
|
||||||
|
<th align="left">Property</th>
|
||||||
|
<th align="left">Description</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Credentials to use when joining the VM to the domain</p></td>
|
||||||
|
<td align="left"><p>Select one of the following credentials to use when joining the VM to the domain:</p>
|
||||||
|
<ul>
|
||||||
|
<li><p><strong>Use MED-V credentials</strong>—The end-user credentials.</p></li>
|
||||||
|
<li><p><strong>Use the following credentials</strong>—The credentials specified; enter a user name and password in the corresponding fields.</p></li>
|
||||||
|
</ul>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>The credentials you enter are visible to all MED-V workspace users. It is not recommended to provide domain administrator credentials.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Domain to join</p></td>
|
||||||
|
<td align="left"><p>Select one of the following:</p>
|
||||||
|
<ul>
|
||||||
|
<li><p><strong>Use the domain name utilized in starting the Workspace</strong>—Join the domain entered by the end user when logging into the MED-V client.</p>
|
||||||
|
<p>To define the mapping from NetBIOS to fully qualified domain names, click <strong>Global domain mapping table</strong>. In the global domain mapping table, click <strong>Add</strong>, enter a <strong>NetBIOS domain name</strong> and a <strong>Fully qualified domain name</strong>, and click <strong>OK</strong>.</p></li>
|
||||||
|
<li><p><strong>Use the following domain name</strong>—Join the domain specified; enter a domain name and NetBIOS domain name in the corresponding fields.</p></li>
|
||||||
|
</ul></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Organization Unit</p></td>
|
||||||
|
<td align="left"><p>An organization unit (OU) may be specified to join the computer to a specific OU. The format must follow an OU distinguished name: OU=<Organization Unit>,<Domain Controller> (for example, OU=QATest, DC=il, DC=MED-V, DC=com).</p>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Warning</strong>
|
||||||
|
<p>Only a single level OU is supported as is shown in the example above.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div></td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
### <a href="" id="bkmk-checkconnectivityproperties"></a>
|
||||||
|
|
||||||
|
**Check Connectivity Properties**
|
||||||
|
|
||||||
|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="50%" />
|
||||||
|
<col width="50%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead>
|
||||||
|
<tr class="header">
|
||||||
|
<th align="left">Property</th>
|
||||||
|
<th align="left">Description</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>IP Address</p></td>
|
||||||
|
<td align="left"><p>The IP Address of the server that you are verifying connection to.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Port</p></td>
|
||||||
|
<td align="left"><p>The port of the server that you are verifying connection to.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Timeout</p></td>
|
||||||
|
<td align="left"><p>The number of seconds to wait for a response before timing out.</p></td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
### <a href="" id="bkmk-commandlineproperties"></a>
|
||||||
|
|
||||||
|
**Command-Line Properties**
|
||||||
|
|
||||||
|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="50%" />
|
||||||
|
<col width="50%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead>
|
||||||
|
<tr class="header">
|
||||||
|
<th align="left">Property</th>
|
||||||
|
<th align="left">Description</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Path</p></td>
|
||||||
|
<td align="left"><p>The path of the command line.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Arguments</p></td>
|
||||||
|
<td align="left"><p>Command-line arguments.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Wait for exit</p></td>
|
||||||
|
<td align="left"><p>Select the check box to wait for a return before continuing with the script actions.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Fail on error</p></td>
|
||||||
|
<td align="left"><p>Select this check box if the return is anything but the value specified.</p>
|
||||||
|
<p>Enter the value that will indicate the command as a success.</p>
|
||||||
|
<p>Default: <strong>0</strong></p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Perform only once</p></td>
|
||||||
|
<td align="left"><p>Select this check box to run the command line only once. If the script fails or is canceled, this command will not be performed again.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>This command line causes a restart of Windows in the Workspace</p></td>
|
||||||
|
<td align="left"><p>Select this check box if the command line causes a restart after completion.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Allow interaction</p></td>
|
||||||
|
<td align="left"><p>Select this check box if the command will require user interaction.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Progress message</p></td>
|
||||||
|
<td align="left"><p>Message to be displayed to the user while the command is running.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Failure message</p></td>
|
||||||
|
<td align="left"><p>Message to be displayed to the user if the command fails.</p></td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
When configuring the command-line action, several variables can be used as defined in the following table.
|
||||||
|
|
||||||
|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="33%" />
|
||||||
|
<col width="33%" />
|
||||||
|
<col width="33%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead>
|
||||||
|
<tr class="header">
|
||||||
|
<th align="left">Parameter</th>
|
||||||
|
<th align="left">Value</th>
|
||||||
|
<th align="left">Description</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>%MEDVUser%</p></td>
|
||||||
|
<td align="left"><p>An authenticated user name.</p></td>
|
||||||
|
<td align="left"><p>MED-V authenticated user name. The user name and password can be used in the join domain VM setup script.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>%MEDVPassword%</p></td>
|
||||||
|
<td align="left"><p>An authenticated password.</p></td>
|
||||||
|
<td align="left"><p>MED-V authenticated password. The user name and password can be used in the join domain VM setup script.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>%MEDVDomain%</p></td>
|
||||||
|
<td align="left"><p>Configured domain.</p></td>
|
||||||
|
<td align="left"><p>The domain configured in the MED-V authentication. It can be used on the VM setup script.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>%DesiredMachineName%</p></td>
|
||||||
|
<td align="left"><p>Computer name.</p></td>
|
||||||
|
<td align="left"><p>The unique computer name configured in the management application. It can be used in the VM setup script.</p></td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[How to Configure the Virtual Machine Setup for a MED-V Workspace](how-to-configure-the-virtual-machine-setup-for-a-med-v-workspacemedvv2.md)
|
||||||
|
|
||||||
|
[How to Configure VM Computer Name Pattern Properties](how-to-configure-vm-computer-name-pattern-propertiesmedvv2.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -0,0 +1,66 @@
|
|||||||
|
---
|
||||||
|
title: How to Share Folders Between the Host and the MED-V Workspace
|
||||||
|
description: How to Share Folders Between the Host and the MED-V Workspace
|
||||||
|
ms.assetid: 3cb295f2-c07e-4ee6-aa3c-ce4c8c45c191
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Share Folders Between the Host and the MED-V Workspace
|
||||||
|
|
||||||
|
|
||||||
|
You can share folders between the host and the MED-V workspace. The shared folders can be stored on the following:
|
||||||
|
|
||||||
|
- An external computer on the network
|
||||||
|
|
||||||
|
- The host computer
|
||||||
|
|
||||||
|
The following procedures demonstrate how to share folders between the host and the MED-V workspace.
|
||||||
|
|
||||||
|
**To share folders located on the network**
|
||||||
|
|
||||||
|
1. Configure MED-V in full desktop mode.
|
||||||
|
|
||||||
|
2. In MED-V management, on the Network tab, click **Use different IP address than host (Bridge)**.
|
||||||
|
|
||||||
|
3. Do the following on the host computer:
|
||||||
|
|
||||||
|
1. In Control Panel, click **View network status and tasks**, and set **Network discovery** to **On**.
|
||||||
|
|
||||||
|
2. On the Start menu, right-click **Computer**, and click **Map network drive**.
|
||||||
|
|
||||||
|
3. In the **Map Network Drive** dialog box, in the **Drive** field, select a drive.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
Ensure that the same drive letter is not in use on both computers.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
4. Click **Browse**.
|
||||||
|
|
||||||
|
5. In the **Browse For Folder** dialog box, browse to the shared drive, and click **OK**.
|
||||||
|
|
||||||
|
6. Click **Finish**.
|
||||||
|
|
||||||
|
4. Repeat step 3 in the MED-V workspace. Point to the same drive as on the host computer.
|
||||||
|
|
||||||
|
**To share folders located on the host**
|
||||||
|
|
||||||
|
1. Configure the folder to be shared with the appropriate permissions.
|
||||||
|
|
||||||
|
2. From the MED-V workspace, go to **My network places** and locate the shared folder.
|
||||||
|
|
||||||
|
3. From the MED-V workspace, locate the shared folder.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
Ensure that both the host and MED-V workspace computers are in the same domain or workgroup.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
38
mdop/medv-v1/how-to-start-and-exit-the-med-v-client.md
Normal file
38
mdop/medv-v1/how-to-start-and-exit-the-med-v-client.md
Normal file
@ -0,0 +1,38 @@
|
|||||||
|
---
|
||||||
|
title: How to Start and Exit the MED-V Client
|
||||||
|
description: How to Start and Exit the MED-V Client
|
||||||
|
ms.assetid: 3762bad1-6937-40fa-ab5d-61a905865214
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Start and Exit the MED-V Client
|
||||||
|
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-tostarthemed-vclient"></a>
|
||||||
|
|
||||||
|
|
||||||
|
**To start the MED-V client**
|
||||||
|
|
||||||
|
- On the Windows Start menu, point to **All Programs**, point to **MED V**, and then click **MED-V** or, on the desktop, double-click the **MED-V** icon.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
MED-V cannot be started from an elevated command prompt.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**To exit the MED-V client**
|
||||||
|
|
||||||
|
1. In the notification area, right-click the MED-V icon.
|
||||||
|
|
||||||
|
2. On the submenu, click **Exit**.
|
||||||
|
|
||||||
|
The MED-V client exits.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -0,0 +1,87 @@
|
|||||||
|
---
|
||||||
|
title: How to Start, Stop, and Restart a MED-V Workspace
|
||||||
|
description: How to Start, Stop, and Restart a MED-V Workspace
|
||||||
|
ms.assetid: 54ce139c-8f32-499e-944b-72f123ebfd2d
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Start, Stop, and Restart a MED-V Workspace
|
||||||
|
|
||||||
|
|
||||||
|
**To start a MED-V workspace**
|
||||||
|
|
||||||
|
1. In the notification area, right-click the MED-V icon.
|
||||||
|
|
||||||
|
2. On the submenu, click **Start Workspace**.
|
||||||
|
|
||||||
|
- If there are multiple MED-V workspaces running on the computer, the **Workspace Selection** window appears.
|
||||||
|
|
||||||
|
1. Select a MED-V workspace.
|
||||||
|
|
||||||
|
2. Select the **Start the selected Workspace without asking me** check box to skip this window the next time the client is started and to automatically open the selected MED-V workspace.
|
||||||
|
|
||||||
|
3. Click **OK**.
|
||||||
|
|
||||||
|
The **Start Workspace Authentication** window appears.
|
||||||
|
|
||||||
|
- If there are several MED-V workspaces on the computer and you have opted to use a specified MED-V workspace, the window shown in the following figure appears.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- If there is only one MED-V workspace on the computer, the “Start last used Workspace” option is unavailable.
|
||||||
|
|
||||||
|
3. Type in your domain user credentials.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
The first time a MED-V workspace is started, the user name should be in the following format: <domain name>\\<user name>.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
4. Select **Save my password** to save your password between sessions.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
To enable the save password feature, the EnableSavePassword attribute must be set to True in the ClientSettings.xml file. The file can be found in the *Servers\\Configuration Server\\* folder.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
5. Clear the **Start last used workspace** check box to choose a different MED-V workspace.
|
||||||
|
|
||||||
|
6. Click **OK**.
|
||||||
|
|
||||||
|
Several status screens appear depending on the MED-V workspace configuration.
|
||||||
|
|
||||||
|
The **Starting Workspace** screen appears.
|
||||||
|
|
||||||
|
**To restart a MED-V workspace**
|
||||||
|
|
||||||
|
1. When the client is running, in the notification area, right-click the MED-V icon.
|
||||||
|
|
||||||
|
2. On the submenu, click **Restart Workspace**.
|
||||||
|
|
||||||
|
The MED-V workspace is restarted.
|
||||||
|
|
||||||
|
- In a persistent MED-V workspace, the virtual machine is shut down and then restarted.
|
||||||
|
|
||||||
|
- In a revertible MED-V workspace, the virtual machine does not actually shut down; instead, it returns to its original state.
|
||||||
|
|
||||||
|
**To stop a MED-V workspace**
|
||||||
|
|
||||||
|
1. In the notification area, right-click the MED-V icon.
|
||||||
|
|
||||||
|
2. On the submenu, click **Stop Workspace**.
|
||||||
|
|
||||||
|
The MED-V workspace is stopped.
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[How to Start and Exit the MED-V Client](how-to-start-and-exit-the-med-v-client.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,71 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,70 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
46
mdop/medv-v1/how-to-uninstall-med-v-componentsmedvv2.md
Normal file
46
mdop/medv-v1/how-to-uninstall-med-v-componentsmedvv2.md
Normal file
@ -0,0 +1,46 @@
|
|||||||
|
---
|
||||||
|
title: How to Uninstall MED-V Components
|
||||||
|
description: How to Uninstall MED-V Components
|
||||||
|
ms.assetid: 91bdf488-14e7-43ab-972d-9d92421acb86
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Uninstall MED-V Components
|
||||||
|
|
||||||
|
|
||||||
|
This section explains how to uninstall the MED-V client and server.
|
||||||
|
|
||||||
|
## How to Uninstall the MED-V Client
|
||||||
|
|
||||||
|
|
||||||
|
**To uninstall MED-V client**
|
||||||
|
|
||||||
|
1. If using Windows XP:
|
||||||
|
|
||||||
|
- In Control Panel, open **Add or Remove Programs**.
|
||||||
|
|
||||||
|
2. If using Windows Vista:
|
||||||
|
|
||||||
|
- In Control Panel, open **Uninstall a Program**.
|
||||||
|
|
||||||
|
3. Select **Microsoft Enterprise Desktop Virtualization**, and click **Uninstall**.
|
||||||
|
|
||||||
|
4. It is recommended to delete the MED-V virtual machine folder. (The default folder is *C:\\MED-V Images*.)
|
||||||
|
|
||||||
|
## How to Uninstall the MED-V Server
|
||||||
|
|
||||||
|
|
||||||
|
**To uninstall the MED-V server**
|
||||||
|
|
||||||
|
1. In Control Panel, open **Add or Remove Programs**.
|
||||||
|
|
||||||
|
2. Select **Microsoft Enterprise Desktop Virtualization (Server)**, and click **Uninstall**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,87 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
60
mdop/medv-v1/how-to-update-a-med-v-image.md
Normal file
60
mdop/medv-v1/how-to-update-a-med-v-image.md
Normal file
@ -0,0 +1,60 @@
|
|||||||
|
---
|
||||||
|
title: How to Update a MED-V Image
|
||||||
|
description: How to Update a MED-V Image
|
||||||
|
ms.assetid: 61eacf50-3a00-4bb8-b2f3-7350a6467fa1
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Update a MED-V Image
|
||||||
|
|
||||||
|
|
||||||
|
## How to Update a MED-V Image
|
||||||
|
|
||||||
|
|
||||||
|
An existing MED-V image can be updated, thereby creating a new version of the image. The new version can then be deployed on client computers, replacing the existing image.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
When a new version is deployed on the client, it overwrites the existing image. When updating an image, ensure that no data on the client needs to be saved.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**To update a MED-V image**
|
||||||
|
|
||||||
|
1. Open the existing image in Virtual PC 2007.
|
||||||
|
|
||||||
|
2. Make the required changes to the image, updating the image (such as installing new software).
|
||||||
|
|
||||||
|
3. Close Virtual PC 2007.
|
||||||
|
|
||||||
|
4. Test the image.
|
||||||
|
|
||||||
|
5. After the image is tested, pack it to the local repository, using the same name as the existing image.
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
If you name the image a different name than the existing version, a new image will be created rather than a new version of the existing image.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
6. Upload the new version to the server or distribute it via a deployment package.
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[Creating a Virtual PC Image for MED-V](creating-a-virtual-pc-image-for-med-v.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)
|
||||||
|
|
||||||
|
[Updating a MED-V Workspace Image](updating-a-med-v-workspace-image.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
90
mdop/medv-v1/how-to-upload-a-med-v-image-to-the-server.md
Normal file
90
mdop/medv-v1/how-to-upload-a-med-v-image-to-the-server.md
Normal file
@ -0,0 +1,90 @@
|
|||||||
|
---
|
||||||
|
title: How to Upload a MED-V Image to the Server
|
||||||
|
description: How to Upload a MED-V Image to the Server
|
||||||
|
ms.assetid: 0e70dfdf-3e3a-4860-970c-535806caa907
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Upload a MED-V Image to the Server
|
||||||
|
|
||||||
|
|
||||||
|
After a MED-V image has been tested, it can be packed and then uploaded to the server. For information on configuring an image Web distribution server, see [How to Configure the Image Web Distribution Server](how-to-configure-the-image-web-distribution-server.md).
|
||||||
|
|
||||||
|
Once a MED-V image is packed and uploaded to the server, it can be distributed to users by using an enterprise software distribution center, or it can be downloaded by users using a deployment package. For information on deployment using an enterprise software distribution center, see [Deploying a MED-V Workspace Using an Enterprise Software Distribution System](deploying-a-med-v-workspace-using-an-enterprise-software-distribution-system.md). For information on deployment using a package, see [Deploying a MED-V Workspace Using a Deployment Package](deploying-a-med-v-workspace-using-a-deployment-package.md).
|
||||||
|
|
||||||
|
**Note**
|
||||||
|
Before uploading an image, verify that a Web proxy is not defined in your browser settings and that Windows Update is not currently running.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
**To upload a MED-V image to the server**
|
||||||
|
|
||||||
|
1. In the **Local Packed Images** pane, select the image you created.
|
||||||
|
|
||||||
|
2. Click **Upload**.
|
||||||
|
|
||||||
|
The image is uploaded to the server. This might take a considerable amount of time.
|
||||||
|
|
||||||
|
Images on the server are defined with the properties listed in the following table.
|
||||||
|
|
||||||
|
**Packed Images on Server Properties**
|
||||||
|
|
||||||
|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="50%" />
|
||||||
|
<col width="50%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead>
|
||||||
|
<tr class="header">
|
||||||
|
<th align="left">Property</th>
|
||||||
|
<th align="left">Description</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Image Name</p></td>
|
||||||
|
<td align="left"><p>The name of the packed image as it was defined when the administrator created the image.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Version</p></td>
|
||||||
|
<td align="left"><p>The version of the displayed image.</p>
|
||||||
|
<div class="alert">
|
||||||
|
<strong>Note</strong>
|
||||||
|
<p>All previous versions are kept unless deleted.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
|
||||||
|
</div></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>File Size (compressed)</p></td>
|
||||||
|
<td align="left"><p>The physical compressed size of the image.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Image Size (uncompressed)</p></td>
|
||||||
|
<td align="left"><p>The physical uncompressed size of the image.</p></td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
|
[How to Install MED-V Client and MED-V Management Console](how-to-install-med-v-client-and-med-v-management-console.md)
|
||||||
|
|
||||||
|
[Using the MED-V Management Console User Interface](using-the-med-v-management-console-user-interface.md)
|
||||||
|
|
||||||
|
[Creating a Virtual PC Image for MED-V](creating-a-virtual-pc-image-for-med-v.md)
|
||||||
|
|
||||||
|
[How to Pack a MED-V Image](how-to-pack-a-med-v-image.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,102 +0,0 @@
|
|||||||
---
|
|
||||||
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)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -0,0 +1,75 @@
|
|||||||
|
---
|
||||||
|
title: How to View MED-V Settings and General Information
|
||||||
|
description: How to View MED-V Settings and General Information
|
||||||
|
ms.assetid: c14e3f30-c4e5-47a3-8ad1-0570fc62d991
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to View MED-V Settings and General Information
|
||||||
|
|
||||||
|
|
||||||
|
## How to View MED-V Settings
|
||||||
|
|
||||||
|
|
||||||
|
**To view MED-V settings**
|
||||||
|
|
||||||
|
1. In the notification area, right-click the MED-V icon.
|
||||||
|
|
||||||
|
2. On the submenu, click **Settings**.
|
||||||
|
|
||||||
|
3. In the **Settings** dialog box, select the **Load MED-V after Windows logon** check box to load MED-V on startup.
|
||||||
|
|
||||||
|
4. Select the **Start Workspace when MED-V starts** check box to automatically start the MED-V workspace on startup.
|
||||||
|
|
||||||
|
5. Configure the server properties described in the following table.
|
||||||
|
|
||||||
|
**Server Settings**
|
||||||
|
|
||||||
|
<table>
|
||||||
|
<colgroup>
|
||||||
|
<col width="50%" />
|
||||||
|
<col width="50%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead>
|
||||||
|
<tr class="header">
|
||||||
|
<th align="left">Property</th>
|
||||||
|
<th align="left">Description</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Server address</p></td>
|
||||||
|
<td align="left"><p>The server's DNS name or IP address.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="even">
|
||||||
|
<td align="left"><p>Server port</p></td>
|
||||||
|
<td align="left"><p>The server's port.</p></td>
|
||||||
|
</tr>
|
||||||
|
<tr class="odd">
|
||||||
|
<td align="left"><p>Encrypt connections (HTTPS)</p></td>
|
||||||
|
<td align="left"><p>Select this check box to use encrypted connections.</p></td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## How to View MED-V General Information
|
||||||
|
|
||||||
|
|
||||||
|
**To view MED-V general information**
|
||||||
|
|
||||||
|
1. In the notification area, right-click the MED-V icon.
|
||||||
|
|
||||||
|
2. On the submenu, point to **Help**, and then click **About**.
|
||||||
|
|
||||||
|
The **About Microsoft Enterprise Desktop Virtualization** screen appears.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
82
mdop/medv-v1/how-to-work-with-reports.md
Normal file
82
mdop/medv-v1/how-to-work-with-reports.md
Normal file
@ -0,0 +1,82 @@
|
|||||||
|
---
|
||||||
|
title: How to Work with Reports
|
||||||
|
description: How to Work with Reports
|
||||||
|
ms.assetid: b7a660c6-74c3-4ced-a395-9e76a4362a46
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# How to Work with Reports
|
||||||
|
|
||||||
|
|
||||||
|
The following functions can be used to work with MED-V reports:
|
||||||
|
|
||||||
|
- [Refreshing an existing report](#bkmk-howtorefreshanexistingreport)
|
||||||
|
|
||||||
|
- [Editing report parameters](#bkmk-howtoeditreportparameters)
|
||||||
|
|
||||||
|
- [Exporting a report to Microsoft Excel](#bkmk-howtoexportareporttoexcel)
|
||||||
|
|
||||||
|
- [Closing a report](#bkmk-howtocoseareport)
|
||||||
|
|
||||||
|
Report results can be sorted by any column by clicking the appropriate column name.
|
||||||
|
|
||||||
|
The report results can be grouped by dragging a column header to the top of the report. Drag multiple column headers to group one column after another.
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-howtorefreshanexistingreport"></a>How to Refresh an Existing Report
|
||||||
|
|
||||||
|
|
||||||
|
**To refresh an existing report**
|
||||||
|
|
||||||
|
1. Select the report to refresh.
|
||||||
|
|
||||||
|
2. On the management toolbar, click **Refresh**.
|
||||||
|
|
||||||
|
The report is regenerated.
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-howtoeditreportparameters"></a>How to Edit Report Parameters
|
||||||
|
|
||||||
|
|
||||||
|
**To edit report parameters**
|
||||||
|
|
||||||
|
1. Generate a report.
|
||||||
|
|
||||||
|
2. On the management toolbar, click **Edit report**.
|
||||||
|
|
||||||
|
The Report Parameters dialog box appears.
|
||||||
|
|
||||||
|
3. In the **Report Parameters** dialog box, configure the parameters, and click **OK**.
|
||||||
|
|
||||||
|
The report is regenerated with the new parameters.
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-howtoexportareporttoexcel"></a>How to Export a Report to Microsoft Excel
|
||||||
|
|
||||||
|
|
||||||
|
**To export a report to Microsoft Excel**
|
||||||
|
|
||||||
|
1. Generate a report.
|
||||||
|
|
||||||
|
2. On the management toolbar, click **Export to Excel**.
|
||||||
|
|
||||||
|
3. In the **Save Report** dialog box, enter a name, and click **Save**.
|
||||||
|
|
||||||
|
The report is exported to Microsoft Excel.
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-howtocoseareport"></a>How to Close a Report
|
||||||
|
|
||||||
|
|
||||||
|
**To close a report**
|
||||||
|
|
||||||
|
1. Select the report to close.
|
||||||
|
|
||||||
|
2. On the management toolbar, click **Close report**.
|
||||||
|
|
||||||
|
The report closes.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
49
mdop/medv-v1/identify-the-number-of-med-v-instances.md
Normal file
49
mdop/medv-v1/identify-the-number-of-med-v-instances.md
Normal file
@ -0,0 +1,49 @@
|
|||||||
|
---
|
||||||
|
title: Identify the Number of MED-V Instances
|
||||||
|
description: Identify the Number of MED-V Instances
|
||||||
|
ms.assetid: edea9bdf-a28c-4d24-9298-7bd6536c3a94
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
---
|
||||||
|
|
||||||
|
# Identify the Number of MED-V Instances
|
||||||
|
|
||||||
|
|
||||||
|
You need to determine the number of MED-V instances, as well as define the scope for each instance so that you can design the server infrastructure. A MED-V instance includes the following:
|
||||||
|
|
||||||
|
- The MED-V server and the MED-V workspaces stored on the server, including Active Directory permissions.
|
||||||
|
|
||||||
|
- A SQL Server database that stores client events. The database may be shared by multiple MED-V instances.
|
||||||
|
|
||||||
|
- The image repository for the packed MED-V images. The repository may be shared by multiple MED-V instances.
|
||||||
|
|
||||||
|
- The management console used to create and pack images and to create MED-V workspaces. The console cannot be used simultaneously by multiple MED-V instances, but it can be disconnected from one MED-V server and then connected to a different MED-V server.
|
||||||
|
|
||||||
|
- MED-V clients that receive MED-V workspaces, and authorization to use them, from the server.
|
||||||
|
|
||||||
|
Separate MED-V instances cannot be integrated or share MED-V workspaces. Therefore, each additional instance decentralizes the virtualization management.
|
||||||
|
|
||||||
|
## Determine the Number of MED-V Instances Required
|
||||||
|
|
||||||
|
|
||||||
|
Start by assuming you are using one MED-V instance. Then, consider the following conditions, and add additional instances for each condition that applies to your infrastructure.
|
||||||
|
|
||||||
|
- Number of supported users—Each MED-V instance can support up to 5,000 concurrently active clients. Concurrently active means the client is online with the MED-V server and sending polls to the server for policy and image updates, as well as events. If your infrastructure will include more than 5,000 active users, add one instance for every 5,000 users.
|
||||||
|
|
||||||
|
- Users in untrusted domains—The MED-V server associates MED-V workspace permissions with Active Directory users and/or groups. This requires MED-V users to exist within the trust boundary of the MED-V server. Add one MED-V instance for each group of MED-V users that is in a separate, untrusted domain.
|
||||||
|
|
||||||
|
- Clients in isolated networks—Determine whether any clients reside in networks that are isolated and therefore require a separate MED-V instance. For example, organizations often isolate lab networks from production networks. Add a MED-V instance for each isolated network that will contain MED-V clients.
|
||||||
|
|
||||||
|
- Organizational requirements—The organization may require that a group of clients be managed by a separate MED-V instance for security reasons, such as when sensitive applications are delivered only to a restricted set of users within a domain. For example, the payroll department may deny users from other departments access to the MED-V instance that stores policy for payroll processing. Additionally, if the organization uses a distributed management model, a separate MED-V instance may be required for each business group having MED-V clients in order to enable the group to manage its own virtualized environment. Add one MED-V instance for each separate organizational requirement.
|
||||||
|
|
||||||
|
- Legal considerations—National security or privacy issues and fiduciary laws could require the separation of certain data or prevent other data from crossing national borders. If necessary, add additional MED-V instances to address this need.
|
||||||
|
|
||||||
|
After you determine the number of MED-V instances required for your infrastructure, as well as the reasoning for each one, provide a name for each instance.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user