diff --git a/mdop/medv-v1/about-med-v-10-sp1.md b/mdop/medv-v1/about-med-v-10-sp1.md new file mode 100644 index 0000000000..498d0c89f2 --- /dev/null +++ b/mdop/medv-v1/about-med-v-10-sp1.md @@ -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 + + +[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. + +[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. + +[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) + + + + + + + + + diff --git a/mdop/medv-v1/about-med-v-10.md b/mdop/medv-v1/about-med-v-10.md new file mode 100644 index 0000000000..433e4f2e97 --- /dev/null +++ b/mdop/medv-v1/about-med-v-10.md @@ -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: + +[MED-V 1.0 Supported Configurations](med-v-10-supported-configurationsmedv-10.md) +Delineates the supported configurations for MED-V 1.0. + +[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. + +[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) + + + + + + + + + diff --git a/mdop/medv-v1/about-med-v-20.md b/mdop/medv-v1/about-med-v-20.md deleted file mode 100644 index 46d295b60c..0000000000 --- a/mdop/medv-v1/about-med-v-20.md +++ /dev/null @@ -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: - -[What's New in MED-V 2.0](whats-new-in-med-v-20.md) -Describes system requirements and new and changed features in MED-V 2.0. - -[MED-V 2.0 Supported Configurations](med-v-20-supported-configurations.md) -Describes the supported configurations for MED-V 2.0. - -[MED-V 2.0 Release Notes](med-v-20-release-notes.md) -Provides a list of known issues with MED-V 2.0. - -## Related topics - - -[Getting Started with MED-V](getting-started-with-med-vmedv2.md) - - - - - - - - - diff --git a/mdop/medv-v1/about-this-guidemedv.md b/mdop/medv-v1/about-this-guidemedv.md new file mode 100644 index 0000000000..87cc84e5e5 --- /dev/null +++ b/mdop/medv-v1/about-this-guidemedv.md @@ -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 + + + + + + + + + diff --git a/mdop/medv-v1/authentication-of-med-v-end-users.md b/mdop/medv-v1/authentication-of-med-v-end-users.md deleted file mode 100644 index ea5f477e8b..0000000000 --- a/mdop/medv-v1/authentication-of-med-v-end-users.md +++ /dev/null @@ -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: - -
Value | -Configuration | -Result | -
---|---|---|
DisablePasswordSaving |
-Disabled |
-The MED-V prompt is presented and a check box to accept is available and cleared. If the end user selects the check box, credentials are cached for subsequent use. The end user also has the benefit of only being prompted when the password expires. - |
-
- | - | If the end user does not select the check box, the Remote Desktop Connection (RDC) Client prompt is presented instead of the MED-V prompt, and the check box to accept is cleared. If the end user selects the check box, the RDC Client credential is stored for later use. -
-Important
-
-RDC does not validate credentials when the end user enters them. If the end user caches the credentials through the RDC prompt, there is a risk that incorrect credentials might be stored. In this case, the incorrect credentials must be deleted in the Windows Credential Manager. -
-
- |
-
DisablePasswordSaving |
-Enabled |
-
-Note
-
-This configuration is more secure because it does not allow end user credentials to be cached. -
-
- |
-
Parameter | +Value | +Description | +
---|---|---|
/quiet |
++ | Silent installation |
+
/log <full path to log file> |
+The full path to the log file. |
++ |
INSTALLDIR |
+The full path to the installation directory. |
++ |
VMSFOLDER |
+The full path to the virtual machine folder. |
++ |
INSTALL_ADMIN_TOOLS |
+1,0 +Default: 0 |
+Installs MED-V administration tools. |
+
START_AUTOMATICALLY |
+1,0 +Default: 0 |
+Automatically starts MED-V client every time the user logs on to Windows. |
+
SERVER_ADDRESS |
+host name or IP |
++ |
SERVER_PORT |
+port |
++ |
SERVER_SSL |
+1,0 +for https or http |
++ |
START_MEDV |
+1,0 +Default: 1 |
+Starts MED-V at the completion of the MED-V installation. +
+Note
+
+It is recommended to set START_MEDV=0 in case MED-V is installed by the system. +
+
+ |
+
DESKTOP_SHORTCUT |
+1,0 +Default: 1 |
+Creates a shortcut on the desktop, which starts MED-V client. |
+
MINIMAL_RAM_REQUIRED |
+RAM in MB |
+When installing MED-V, checks whether the computer has the minimum amount of RAM specified. If not, installation is aborted. |
+
SKIP_OS_CHECK |
+1,0 |
+Omits the operating system validation. |
+
Installation File | -Argument | -Accepted Values | -Type | -Description | -Default | -
---|---|---|---|---|---|
Host Agent |
-MEDVDIR |
-<install path> |
-Installation |
-Change installed directory |
-Installation goes to Program Files\Microsoft Enterprise Desktop Virtualization. |
-
MED-V Workspace Packager |
-MEDVDIR |
-<install path> |
-Installation |
-Change installed directory |
-Installation goes to Program Files\Microsoft Enterprise Desktop Virtualization. |
-
MED-V workspace |
-INSTALLDIR |
-<install path> |
-Installation |
-Change installed directory |
-Installation goes to ProgramData\Microsoft\Medv\Workspace. |
-
MED-V workspace |
-OVERWRITE VHD |
-0 or 1 |
-Installation |
-Fail installation if VHD exists(0) or overwrite existing VHD(1). |
-Overwrite does not occur and installation fails if a virtual hard disk (VHD) already exists. |
-
MED-V workspace |
-SUPPRESSMEDVLAUNCH |
-0 or 1 |
-Installation |
-Start(0) or do not start(1) MED-V after MED-V workspace is installed. |
-If the MED-V workspace was installed with the user interface (UI), a check box on the Finish page controls whether to start MED-V. |
-
MED-V workspace |
-DELETEDIFFDISKS |
-0 or 1 |
-Uninstallation |
-Keep(0) or delete(1) VHDs created by MED-V |
-No VHDs are deleted. |
-
Package Information |
- Specify a name for the MED-V workspace and select a folder where the MED-V workspace package files are saved. |
-
Select Windows XP Image |
- Specify your prepared Windows XP Virtual PC image. |
-
First Time Setup |
- Specify the setup process that MED-V follows during first time setup. |
-
MED-V Messages |
- Specify the messages and optional URL for Help information that the end user sees during first time setup. |
-
Naming Computers |
- Specify how the MED-V virtual machine is named. |
-
Copy Settings from Host |
- Specify how the settings for the MED-V workspace are defined. |
-
Startup and Networking |
- Specify the settings for starting the MED-V workspace, networking, and user credentials. |
-
Web Redirection |
- Specify a text file or a list of the URLs you want redirected to Internet Explorer in the MED-V workspace. |
-
Summary |
- Verify your MED-V workspace settings and start to build your MED-V workspace deployment package. |
-
Copy regional settings |
- Select this check box to copy the regional settings from the host computer to the MED-V workspace. |
-
- | If you select this check box, the following settings are set in the Sysprep.inf file: -
|
-
Copy user settings |
- Select this check box to copy certain user settings, such as user name and company name, from the host to the MED-V workspace. |
-
- | If you select this check box, the following settings are set in the Sysprep.inf file: -
-
- Note
-
- Personal settings, such as Internet browsing history, are not copied over to the MED-V workspace. -
-
- |
-
Copy domain name |
- Select this check box to let the guest join the same domain as the host. |
-
- |
- Important
-
- The MED-V guest must be configured to join a domain that lets users log on by using the credentials that they use to log on to the MED-V host. -
-
- |
-
Copy domain organizational unit |
- Select this check box to copy the domain organizational unit from the host computer to the MED-V workspace. This check box is only enabled if you select to copy the domain name from the host computer. |
-
Start MED-V workspace |
- Choose whether to start the MED-V workspace at user logon, at first use, or to let the end user decide when the MED-V workspace starts. |
-
- | The MED-V workspace starts in one of two ways: either when the end user logs on or when they first start an action that requires MED-V, such as opening a published application or entering a URL that requires redirection. -You can either define this setting for the end user or let the end user control how MED-V starts. -
- Note
-
- If you specify that the end user decides, the default behavior they experience is that the MED-V workspace starts when they log on. They can change the default by right-clicking the MED-V icon in the notification area and selecting MED-V User Settings. If you define this setting for the end user, they cannot change how MED-V starts. -
-
- |
-
Networking |
- Select Shared or Bridged for your networking setting. The default is Shared. |
-
- | Shared - The MED-V workspace uses Network Address Translation (NAT) to share the host's IP for outgoing traffic. -Bridged - The MED-V workspace has its own network address, typically obtained through DHCP. |
-
Store credentials |
- Choose whether you want to store the end user credentials. |
-
- | The default behavior is that credential storing is disabled so that the end user must be authenticated every time that they log on. -
- Important
-
- Even though caching the end user’s credentials provides the best user experience, you should be aware of the risks involved. -The end user’s domain credential is stored in a reversible format in the Windows Credential Manager. As a result, an attacker could write a program that retrieves the password and could gain access to the user’s credentials. You can only lessen this risk by disabling the storing of end-user credentials. -
-
- |
-
Step | -Reference | -
---|---|
Review the components of a MED-V deployment. |
-[High-Level Architecture](high-level-architecturemedv2.md) |
-
Ensure that your computing environment meets the supported configurations required for installing MED-V 2.0. |
-[MED-V 2.0 Supported Configurations](med-v-20-supported-configurations.md) |
-
Determine how you want to design your MED-V deployment. |
-[Define and Plan your MED-V Deployment](define-and-plan-your-med-v-deployment.md) |
-
Review the list of best practices for ensuring that your MED-V deployment environment is more secure. |
-[Security and Protection for MED-V](security-and-protection-for-med-v.md) |
-
Step | -Reference | -
---|---|
Create a virtual machine that is running Windows XP SP3 with updates and additions. |
-[Creating a Windows Virtual PC Image for MED-V](creating-a-windows-virtual-pc-image-for-med-v.md) |
-
Install any predeployment software that you want on the MED-V image. |
-[Installing Applications on a Windows Virtual PC Image](installing-applications-on-a-windows-virtual-pc-image.md) |
-
Package the MED-V image by using Sysprep. |
-[Configuring a Windows Virtual PC Image for MED-V](configuring-a-windows-virtual-pc-image-for-med-v.md) |
-
Step | -Reference | -
---|---|
Determine how you can use MED-V to help solve your application compatibility issues. |
-[Planning for Application Operating System Compatibility](planning-for-application-operating-system-compatibility.md) |
-
Plan an end-to-end deployment scenario for your organization. |
-[End-to-End Planning Scenario for MED-V 2.0](end-to-end-planning-scenario-for-med-v-20.md) |
-
Define the project scope by defining the end users and determining the MED-V images to be managed. |
-[Define and Plan your MED-V Deployment](define-and-plan-your-med-v-deployment.md) |
-
Review the list of best practices for ensuring that your MED-V deployment is more secure. |
-[Security and Protection for MED-V](security-and-protection-for-med-v.md) |
-
Step | -Reference | -
---|---|
Ensure that your computing environment meets the supported configurations that are required for installing MED-V 2.0. |
-[MED-V 2.0 Supported Configurations](med-v-20-supported-configurations.md) |
-
Plan and design the MED-V deployment. |
-[Planning for MED-V](planning-for-med-v.md) |
-
Verify that the required installation prerequisites are configured. |
-[Configure Installation Prerequisites](configure-installation-prerequisites.md) |
-
Install the MED-V Host Agent and MED-V Workspace Packager. |
-[Deploy the MED-V Components](deploy-the-med-v-components.md) |
-
Step | -Reference | -
---|---|
Prepare the MED-V image for deployment. |
-[Prepare a MED-V Image](prepare-a-med-v-image.md) |
-
Create the MED-V workspace deployment package. |
-[Create a MED-V Workspace Package](create-a-med-v-workspace-package.md) |
-
Test the MED-V workspace installer package. |
-[Testing the MED-V Workspace Package](testing-the-med-v-workspace-package.md) |
-
Deploy the MED-V workspace installer package. |
-[Deploying the MED-V Workspace Package](deploying-the-med-v-workspace-package.md) |
-
Property | +Description | +
---|---|
TCP/IP Properties |
+
Select the Map multiple adapters into Workspace 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. |
+
DNS Server |
+
|
+
Assign DNS Suffixes |
+
|
+
Property | +Description | +
---|---|
Adjust VM memory, based on amount of the Host machine's physical memory |
+Select this check box, and configure the following virtual machine properties in the table: +
|
+
Property | +Description | +
---|---|
Enabled |
+Select this check box to enable the published application. |
+
Display name |
+The name of the shortcut in the user's Windows Start menu. +
+Note
+
+The display name is not case sensitive. +
+
+ |
+
Description |
+A description of the published application, which appears as a tooltip when the user's mouse hovers over the shortcut. |
+
Command line |
+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. +In a revertible MED-V workspace, you can map a network drive with MapNetworkDrive syntax: "MapNetworkDrive <drive> <path>"—for example, "MapNetworkDrive t: \\tux\date". +For example, to publish Windows Explorer, use the following syntax: "c:\" or "c:\windows." +
+Note
+
+To have a name resolution, you need to perform one of the following: +
+
+
+
+Note
+
+If the path includes spaces, the entire path must be inside quotation marks. +
+
+
+
+Note
+
+The path should not end with a backslash (). +
+
+ |
+
Start menu |
+Select this check box to create a shortcut for the application in the user's Windows Start menu. |
+
Property | +Description | +
---|---|
Enabled |
+Select this check box to enable the published menu. |
+
Display name |
+The name of the shortcut in the user's Windows Start menu. |
+
Description |
+The description, which appears as a tooltip when the user's mouse hovers over the shortcut. |
+
Folder in workspace |
+Select the folder to publish as a menu containing all the applications within the folder. +The text displayed is a relative path from the Programs folder. +
+Note
+
+If left blank, all programs on the host will be published as a menu. +
+
+ |
+
Property | +Description | +
---|---|
Run VM Setup |
+Select this check box to run a setup script the first time the MED-V workspace is run. |
+
Script Editor |
+Click to configure the setup script. For more information, see [How to Set Up Script Actions](how-to-set-up-script-actions.md). +
+Note
+
+This button is enabled only when Run VM Setup script is selected. +
+
+ |
+
Message displayed when script is running |
+A message to be displayed while the script is running. If left blank, the default message is displayed. +
+Note
+
+This field is enabled only when Run VM Setup script is checked. +
+
+ |
+
Property | +Description | +
---|---|
Rename the VM based on the computer name pattern |
+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. +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). |
+
Property | +Description | +
---|---|
Type |
+
|
+
Value |
+
|
+
Property | +Description | +
---|---|
Image Name |
+The name of the test image as it was defined when the administrator created the image. |
+
Image Path |
+The local path of the test image. |
+
Created |
+The date the test image was created. |
+
Argument | -Description | -
---|---|
/norestart |
-Prevents the installation of Windows Virtual PC and the Windows Virtual PC update from restarting the host computer. |
-
/quiet |
-Installs the MED-V components in quiet mode without user interaction. |
-
/qn |
-Installs the MED-V components without a user interface. |
-
IGNORE_PREREQUISITES |
-Installs without checking for Windows Virtual PC. -
-Note
-
-Only specify this argument if you are installing Windows Virtual PC as part of this installation. -
-
- |
-
OVERWRITEVHD |
-Forces the installation of the MED-V workspace and prevents any prompts that it might generate. |
-
Argument | -Description | -
---|---|
/norestart |
-Prevents the installation of Windows Virtual PC and the Windows Virtual PC update from restarting the host computer. |
-
/quiet |
-Installs the MED-V components in quiet mode without user interaction. |
-
/qn |
-Installs the MED-V components without a user interface. |
-
IGNORE_PREREQUISITES |
-Installs without checking for Windows Virtual PC. -
-Note
-
-Only specify this argument if you are installing Windows Virtual PC as part of this installation. -
-
- |
-
OVERWRITEVHD |
-Forces the installation of the MED-V workspace and prevents any prompts that it might generate. |
-
Property | +Description | +
---|---|
Display name |
+The name of the shortcut in the user's Windows Start menu. +
+Note
+
+The display name is not case sensitive. +
+
+ |
+
Description |
+A description of the published menu. |
+
Start in |
+The directory from which to start the application. +
+Note
+
+The path does not need to include quotation marks. +
+
+ |
+
Command line |
+The command with which 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. +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 Use MED-V credentials to run this application check box must be selected. +In a revertible MED-V workspace, you can map a network drive with MapNetworkDrive syntax: "MapNetworkDrive <drive> <path>"—for example, "MapNetworkDrive t: \\tux\data". +For example, to publish Windows Explorer, use the following syntax: "c:\" or "c:\windows". +
+Note
+
+To have a name resolution, you need to perform one of the following: +
+
+
+
+Note
+
+If the path includes spaces, the entire path must be inside quotation marks. +
+
+
+
+Note
+
+The path should not end with a backslash (). +
+
+ |
+
Add a shortcut in the host Windows Start menu |
+Select this check box to create a shortcut for the application in the user's Windows Start menu. |
+
Launch this application when the Workspace is started |
+Select this check box to run the application automatically when the MED-V workspace starts. |
+
Use MED-V credentials to run this application |
+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. +
+Note
+
+When using SSO, the command line should be C:\Windows\Explorer.exe "folder path". When not using SSO, the command line should be "folder path". +
+
+ |
+
Property | +Description | +
---|---|
Time |
+The date and time the event occurred. +
+Note
+
+By default, the events are displayed in descending date order. However, it can be changed by clicking the Time Received column. +
+
+ |
+
User Name |
+The user who initiated the event. +
+Note
+
+If the event occurred before a user logged on, the user name is SYSTEM. +
+
+ |
+
Host Name |
+The name of the host computer. |
+
Workspace Name |
+The name of the MED-V workspace. |
+
Workspace Computer Name |
+The name of the computer the MED-V workspace is running on. |
+
Online |
+The current state of the client computer: +
|
+
Client Version |
+The version number of the client. |
+
Policy Version |
+The policy version that the MED-V workspace is currently using. |
+
Image Name |
+The name of the image. |
+
Image Version |
+The image version that the MED-V workspace is currently using. +
+Note
+
+MED-V workspace version can be Unknown if it has not yet been downloaded onto a computer. +
+
+ |
+
Property | +Description | +
---|---|
Event ID |
+The event ID. |
+
Severity |
+Information, Error, Warning |
+
Category |
+The module that the report is referring to. |
+
Description |
+A description of the event. |
+
Time Received |
+The date and time the event was received on the server. +
+Note
+
+If the client is working offline, the server receives the reports when the client is online. +
+
+
+
+Note
+
+By default, the events are displayed in descending date order. However, it can be changed by clicking the Time Received column. +
+
+ |
+
Client Time |
+The date and time the event occurred according to the client clock. |
+
Host Name |
+The name of the host computer. |
+
User Name |
+The user who initiated the event. |
+
Workspace Name |
+The name of the MED-V workspace. |
+
Workspace Computer Name |
+The name of the computer the MED-V workspace is running on. |
+
Property | +Description | +
---|---|
Event ID |
+The event ID. |
+
Category |
+The module that the report is referring to. |
+
Description |
+A description of the event. |
+
Time Received |
+The date and time the event was received on the server. +
+Note
+
+If the client is working offline, the server receives the reports when the client is online. +
+
+
+
+Note
+
+By default, the events are displayed in descending date order. However, it can be changed by clicking the Time Received column. +
+
+ |
+
Client Time |
+The date and time the event occurred according to the client clock. |
+
Host Name |
+The name of the host computer. |
+
User Name |
+The user who initiated the event. |
+
Workspace Name |
+The name of the MED-V workspace. |
+
Property | +Description | +
---|---|
Image Name |
+The name of the packed image as it was defined when the administrator created the image. |
+
Version |
+The version of the displayed image. +
+Note
+
+All previous versions are kept unless deleted. +
+
+ |
+
File Size (compressed) |
+The physical compressed size of the image. |
+
Image Size (uncompressed) |
+The physical uncompressed size of the image. |
+
Property | +Description | +
---|---|
Credentials to use when joining the VM to the domain |
+Select one of the following credentials to use when joining the VM to the domain: +
+Note
+
+The credentials you enter are visible to all MED-V workspace users. It is not recommended to provide domain administrator credentials. +
+
+ |
+
Domain to join |
+Select one of the following: +
|
+
Organization Unit |
+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). +
+Warning
+
+Only a single level OU is supported as is shown in the example above. +
+
+ |
+
Property | +Description | +
---|---|
IP Address |
+The IP Address of the server that you are verifying connection to. |
+
Port |
+The port of the server that you are verifying connection to. |
+
Timeout |
+The number of seconds to wait for a response before timing out. |
+
Property | +Description | +
---|---|
Path |
+The path of the command line. |
+
Arguments |
+Command-line arguments. |
+
Wait for exit |
+Select the check box to wait for a return before continuing with the script actions. |
+
Fail on error |
+Select this check box if the return is anything but the value specified. +Enter the value that will indicate the command as a success. +Default: 0 |
+
Perform only once |
+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. |
+
This command line causes a restart of Windows in the Workspace |
+Select this check box if the command line causes a restart after completion. |
+
Allow interaction |
+Select this check box if the command will require user interaction. |
+
Progress message |
+Message to be displayed to the user while the command is running. |
+
Failure message |
+Message to be displayed to the user if the command fails. |
+
Parameter | +Value | +Description | +
---|---|---|
%MEDVUser% |
+An authenticated user name. |
+MED-V authenticated user name. The user name and password can be used in the join domain VM setup script. |
+
%MEDVPassword% |
+An authenticated password. |
+MED-V authenticated password. The user name and password can be used in the join domain VM setup script. |
+
%MEDVDomain% |
+Configured domain. |
+The domain configured in the MED-V authentication. It can be used on the VM setup script. |
+
%DesiredMachineName% |
+Computer name. |
+The unique computer name configured in the management application. It can be used in the VM setup script. |
+
Property | +Description | +
---|---|
Image Name |
+The name of the packed image as it was defined when the administrator created the image. |
+
Version |
+The version of the displayed image. +
+Note
+
+All previous versions are kept unless deleted. +
+
+ |
+
File Size (compressed) |
+The physical compressed size of the image. |
+
Image Size (uncompressed) |
+The physical uncompressed size of the image. |
+
Property | +Description | +
---|---|
Server address |
+The server's DNS name or IP address. |
+
Server port |
+The server's port. |
+
Encrypt connections (HTTPS) |
+Select this check box to use encrypted connections. |
+
Type | -Location | -Files | -
---|---|---|
Base VHD |
-%ProgramData%\Microsoft\Medv\Workspace |
-InternalName.vhd - Where InternalName is the name of the virtual hard disk that you selected in the MED-V Workspace Packager. |
-
Differencing Disk |
-%LocalAppData%\Microsoft\MEDV\v2\Virtual Machines |
-WorkspaceName.vhd |
-
Saved State File |
-%LocalAppData%\Microsoft\MEDV\v2\Virtual Machines |
-WorkspaceName.vsv |
-
Name | -Type | -Data/Default | -Description | -
---|---|---|---|
EventLogLevel |
-DWORD |
-Default=3 |
-The type of information that is logged in the event log. Levels include the following: 0 (None), 1 (Error), 2 (Warning), 3 (Information), 4 (Debug). |
-
Name | -Type | -Data/Default | -Description | -
---|---|---|---|
AddUserToAdminGroupEnabled |
-DWORD |
-Default=0 |
-Configures whether first time setup automatically adds the end user to the administrator's group. 0 = false; 1 = true. |
-
- | - | - | 0 = false: First time setup does not automatically add the end user to the administrator's group. |
-
- | - | - | 1 = true: First time setup automatically adds the end user to the administrator's group. |
-
ComputerNameMask |
-SZ |
-MEDV* |
-The computer name mask that is used to create the guest virtual machine's computer name. |
-
- | - | - | The mask can contain a %username% tag to insert the username as part of the computer name. Likewise, the %hostname% tag inserts the name of the host computer. -Every "#" character in the mask is replaced by a random digit. An asterisk (*) character at the end of the mask is replaced by random alphanumeric characters. -A specific number of characters from %hostname% and %username% can be captured by using square brackets. For example, "%username%[3]" would use the first three characters of the username. |
-
DeleteVMStateTimeout |
-DWORD |
-Default=90 |
-The time-out value, in seconds, when first time setup tries to delete the virtual machine. Range = 0 to 2147483647. |
-
DetachVfdTimeout |
-DWORD |
-Default=120 |
-The time-out value, in seconds, when first time setup tries to detach the virtual floppy disk from the virtual machine. Range = 0 to 2147483647. |
-
DialogUrl |
-SZ |
-- | Customizable URL that links to internal webpage and is displayed by first time setup dialog messages. |
-
ExplorerTimeout |
-DWORD |
-Default=900 |
-The time-out value, in seconds, that first time setup waits for Windows Explorer. Range = 0 to 2147483647. |
-
FailureDialogMsg |
-MULTI_SZ |
-Message is found in resource file |
-Customizable message that is displayed to the end user when first time setup cannot be completed. |
-
GiveUserGroupRightsMaxRetryCount |
-DWORD |
-Default=3 |
-The maximum number of times that MED-V tries to give an end user group rights. Exceeding the specified retry value without being able to successfully give an end user group rights most likely causes a virtual machine preparation failure that is then subject to the MaxRetryCount value. Range = 0 to 2147483647. |
-
GiveUserGroupRightsTimeout |
-DWORD |
-Default=300 |
-The time-out value, in seconds, when giving a user group rights. Range = 0 to 2147483647. |
-
LogFilePaths |
-MULTI_SZ |
-- | A list of the log file paths that MED-V collects during first time setup. |
-
MaxPostponeTime |
-DWORD |
-Default=120 |
-The maximum number of hours that first time setup can be postponed by the end user. Range = 0 to 2147483647. |
-
MaxRetryCount |
-DWORD |
-Default=3 |
-The maximum number of times that MED-V tries to prepare a virtual machine if each attempt ends in a failure other than a software error. When virtual machine preparation fails and the number of first time setup retries is exceeded, then MED-V informs the end user about the failure and does not give the option to retry. The count is re-set every time that MED-V is started. Range = 0 to 2147483647. |
-
Mode |
-SZ |
-Default=Unattended |
-Configures how first time setup interacts with the user. Possible values are as follows: |
-
- | - | - | Attended. The end user must enter information during first time setup. -
-Note
-
-If you created the Sysprep.inf file so that Mini-Setup requires user input to complete, then you must select Attended mode or problems might occur during first time setup. -
-
- |
-
- | - | - | Unattended. The virtual machine is not shown to the end user during first time setup, but the end user is prompted before first time setup starts. |
-
- | - | - | Silent. The virtual machine is not shown to the end user at all during first time setup. |
-
NonInteractiveRetryTimeoutInc |
-DWORD |
-Default=15 |
-The time-out value, in minutes, that first time setup must be completed in first time setup interactive mode when re-attempting setup. Range = 0 to 2147483647. |
-
NonInteractiveTimeout |
-DWORD |
-Default=45 |
-The time-out value, in minutes, that first time setup must be completed in first time setup interactive mode. Range = 0 to 2147483647. |
-
PostponeUtcDateTimeLimit |
-SZ |
-- | The date and time, in UTC DateTime format, that first time setup can be postponed. Enter in the format "yyyy-MM-dd hh:mm" with hours specified by using the 24-hour clock standard. |
-
RetryDialogMsg |
-MULTI_SZ |
-Message is found in resource file |
-Customizable message that is displayed to the end user when first time setup must re-attempt setup. |
-
SetComputerNameEnabled |
-DWORD |
-Default=0 |
-Configures whether the ComputerName entry under the [UserData] section of the Sysprep.inf file in the guest should be updated according to the specified ComputerNameMask. 0 = false; 1 = true. |
-
- | - | - | 0 = false: The ComputerName entry in the Sysprep.inf file is not updated according to the ComputerNameMask. |
-
- | - | - | 1 = true: The ComputerName entry in the Sysprep.inf file is updated according to the ComputerNameMask. |
-
SetJoinDomainEnabled |
-DWORD |
-Default=0 |
-Configures whether the JoinDomain setting under the [Identification] section of the Sysprep.inf file in the guest should be updated to match the settings on the host. 0 = false; 1 = true. |
-
- | - | - | 0 = false: The JoinDomain setting in the Sysprep.inf file is not updated to match the settings on the host. |
-
- | - | - | 1 = true: The JoinDomain setting in the Sysprep.inf file is updated to match the settings on the host. |
-
SetMachineObjectOUEnabled |
-DWORD |
-Default=0 |
-Configures whether the MachineObjectOU setting under the [Identification] section of the Sysprep.inf file in the guest is updated to match the host. 0 = false; 1 = true. |
-
- | - | - | 0 = false: The MachineObjectOU setting in the Sysprep.inf file is not updated to match the settings on the host. |
-
- | - | - | 1 = true: The MachineObjectOU setting in the Sysprep.inf file is updated to match the settings on the host. |
-
SetRegionalSettingsEnabled |
-DWORD |
-Default=0 |
-Configures whether the settings under the [RegionalSettings] section of the Sysprep.inf file in the guest are updated to match the host. 0 = false; 1 = true. -
-Note
-
-By default, the setting for TimeZone in the guest is always synchronized with the TimeZone setting in the host. -
-
- |
-
- | - | - | 0 = false: The settings under the [RegionalSettings] section of the Sysprep.inf file in the guest are not updated to match the host. |
-
- | - | - | 1 = true: The settings under the [RegionalSettings] section of the Sysprep.inf file in the guest are updated to match the host. |
-
SetUserDataEnabled |
-DWORD |
-Default=0 |
-Configures whether the FullName and the OrgName settings under the [UserData] section of the Sysprep.inf file in the guest are updated to match the settings on the host. 0 = false; 1 = true. |
-
- | - | - | 0 = false: The FullName and OrgName settings in the Sysprep.inf file are not updated to match the settings on the host. |
-
- | - | - | 1 = true: The FullName and OrgName settings in the Sysprep.inf file are updated to match the settings on the host. |
-
StartDialogMsg |
-MULTI_SZ |
-Message is found in resource file |
-Customizable message that is displayed to the end user when first time setup is ready to start. |
-
TaskCancelTimeout |
-DWORD |
-Default=30 |
-The time-out value, in seconds, that first time setup waits for a response from the virtual machine for a Cancel operation. Range = 0 to 2147483647. |
-
TaskVMTurnOffTimeout |
-DWORD |
-Default=60 |
-The time-out value, in seconds, that first time setup waits for the virtual machine to shut down. Range = 0 to 2147483647. |
-
UpgradeTimeout |
-DWORD |
-Default=600 |
-The time, in seconds, before an attempted upgrade of the MED-V Guest Agent software times out. Range = 0 to 2147483647. |
-
Name | -Type | -Data/Default | -Description | -
---|---|---|---|
AppPublishingEnabled |
-DWORD |
-Default=1 |
-Configures whether application publication from the guest to the host is enabled. 0 = false; 1 = true. |
-
- | - | - | 0 = false: Disables application publishing from the guest to the host. |
-
- | - | - | 1 = true: Enables application publishing from the guest to the host. |
-
AudioSharingEnabled |
-DWORD |
-Default=1 |
-Configures whether the sharing of the audio I/O device between the guest and the host is enabled. 0 = false; 1 = true. |
-
- | - | - | 0 = false: Disables the sharing of the audio I/O device between the guest and the host. |
-
- | - | - | 1 = true: Enables the sharing of the audio I/O device between the guest and the host. |
-
ClipboardSharingEnabled |
-DWORD |
-Default=1 |
-Configures whether the sharing of the Clipboard between the guest and the host is enabled. 0 = false; 1 = true. |
-
- | - | - | 0 = false: Disables the sharing of the Clipboard between the guest and the host. |
-
- | - | - | 1 = true: Enables the sharing of the Clipboard between the guest and the host. |
-
DialogTimeout |
-DWORD |
-Default=300 |
-The time, in seconds, before the first time setup Start Dialog times out. Range = 0 to 2147483647. |
-
HideVmTimeout |
-DWORD |
-Default=30 |
-The time-out value, in minutes, that the full-screen virtual machine window is hidden from the end user during a long logon attempt. |
-
LogonStartEnabled |
-DWORD |
-Default=1 |
-Configures whether the guest should be started when the end user logs on to the desktop or when the first guest application is started. 0 = false; 1 = true. |
-
- | - | - | 0 = false: The guest is started when the first guest application is started. |
-
- | - | - | 1 = true: The guest is started when the end user logs on to the desktop. |
-
PrinterSharingEnabled |
-DWORD |
-Default=1 |
-Configures whether the sharing of printers between the guest and the host is enabled. 0 = false; 1 = true. |
-
- | - | - | 0 = false: Disables the sharing of printers between the guest and the host. |
-
- | - | - | 1 = true: Enables the sharing of printers between the guest and the host. |
-
RebootAbsoluteDelayTimeout |
-DWORD |
-Default=1440 |
-The time-out value, in minutes, that first time setup waits for a restart. Range = 0 to 2147483647. |
-
RedirectUrls |
-MULTI_SZ |
-Specified URL list |
-Specifies a list of URLs to be redirected from the host to the guest. |
-
SmartCardLogonEnabled |
-DWORD |
-Default=0 |
-Configures whether smart cards can be used to authenticate users to MED-V. 0 = false; 1 = true. |
-
- | - | - | 0 = false: Does not let Smart Cards authenticate end users to MED-V. |
-
- | - | - | 1 = true: Lets Smart Cards authenticate end users to MED-V. -
-Important
-
-If SmartCardLogonEnabled and CredentialCacheEnabled are both enabled, SmartCardLogonEnabled overrides CredentialCacheEnabled. -
-
- |
-
SmartCardSharingEnabled |
-DWORD |
-Default=1 |
-Configures whether the sharing of Smart Cards between the guest and the host is enabled. 0 = false; 1 = true. |
-
- | - | - | 0 = false: Disables the sharing of Smart Cards between the guest and the host. |
-
- | - | - | 1 = true: Enables the sharing of Smart Cards between the guest and the host. |
-
USBDeviceSharingEnabled |
-DWORD |
-Default=1 |
-Configures whether the sharing of USB devices between the guest and the host is enabled. 0 = false; 1 = true. |
-
- | - | - | 0 = false: Disables the sharing of USB devices between the guest and the host. |
-
- | - | - | 1 = true: Enables the sharing of USB devices between the guest and the host. |
-
Name | -Type | -Data/Default | -Description | -
---|---|---|---|
CloseAction |
-SZ |
-Default=HIBERNATE |
-The action that the virtual machine performs after the last application that is running is closed. This setting is ignored if the LogonStartEnabled value is enabled. Possible options are as follows: |
-
- | - | - | HIBERNATE . This option releases all physical resources that the virtual machine is using, such as memory and CPU, and saves the state of all running applications and operations. |
-
- | - | - | SHUTDOWN . This option shuts down the guest operating system safely and then releases all physical resources that the virtual machine is using, such as memory and CPU. |
-
- | - | - | TURN-OFF. This option can cause data loss because it is the same as turning off the power button or pulling out the power cord on a physical computer. Use this option only if you cannot use one of the other two options. |
-
GuestMemFromHostMem |
-MULTI_SZ |
-378, 512, 1024, 1536, 2048 |
-A list of memory (MB) values for the guest. This value is used to determine how much RAM is available to the guest. Combined with HostMemToGuestMem, a lookup table is created to determine how much RAM to allocate on the guest virtual machine. Possible values can be from 128 to 3712. |
-
GuestUpdateDuration |
-DWORD |
-Default=240 |
-The number of minutes that MED-V should keep the guest awake for automatic updating, starting at the time specified in the GuestUpdateTime value. Range = 0 to 1440. Setting this value to zero (0) disables the guest patching functionality. -For more information about guest patching for automatic updating, see [Managing Automatic Updates for MED-V Workspaces](managing-automatic-updates-for-med-v-workspaces.md). |
-
GuestUpdateTime |
-SZ |
-Default=00:00 |
-The hour and minute each day when MED-V should wake up the guest for automatic updating, by using the 24-hour clock standard. Specify the time in the format HH:MM -For more information about guest patching for automatic updating, see [Managing Automatic Updates for MED-V Workspaces](managing-automatic-updates-for-med-v-workspaces.md). |
-
HostMemToGuestMem |
-MULTI_SZ |
-1024, 2048, 4096, 8192, 16384 |
-A list of memory (MB) values for the guest, determined by the RAM available on the host. Combined with GuestMemFromHostMem, a lookup table is created to determine how much RAM to allocate on the guest virtual machine. Possible values can be from 1024 to 16384. |
-
HostMemToGuestMemCalcEnabled |
-DWORD |
-Default=1 |
-Configures whether the memory allocated for the guest is calculated from the memory present on the host. 0 = false; 1 = true. |
-
- | - | - | 0 = false: The memory allocated for the guest is not calculated from the memory present on the host. |
-
- | - | - | 1 = true: The memory allocated for the guest is calculated from the memory present on the host. |
-
Memory |
-DWORD |
-Default=512 |
-The RAM (MB) that should be allocated for the guest virtual machine. This setting is ignored if the HostMemToGuestMemEnabled setting is enabled. Range=128 to 2048. |
-
MultiUserEnabled |
-DWORD |
-Default=0 |
-Configures whether multiple users share the same MED-V workspace. 0 = false; 1 = true. |
-
- | - | - | 0 = false: Multiple users do not share the same MED-V workspace. |
-
- | - | - | 1 = true: Multiple users share the same MED-V workspace. |
-
NetworkingMode |
-SZ |
-Default=NAT |
-The kind of network connection used on the guest. Possible values are as follows: |
-
- | - | - | Bridged. MED-V has its own network address, typically obtained through DHCP. |
-
- | - | - | NAT. MED-V uses Network Address Translation (NAT) to share the host's IP for outgoing traffic. |
-
TaskTimeout |
-DWORD |
-Default=600 |
-A general time-out value, in seconds, that MED-V waits for a task to be completed, such as restarting and shutting down. Range = 0 to 2147483647. |
-
Name | -Type | -Data/Default | -Description | -
---|---|---|---|
EnableGPWorkarounds |
-DWORD |
-Default=1 |
-Configures how MED-V handles the keys BufferPolicyReads and GroupPolicyMinTransferRate. |
-
- | - | - | By default, MED-V sets these keys as follows: -BufferPolicyReads=1 and GroupPolicyMinTransferRate=0. -Create the EnableGPWorkarounds key, if it is necessary, and set the key to zero if you do not want MED-V to change the default settings of BufferPolicyReads and GroupPolicyMinTransferRate. -
-Note
-
-If your MED-V workspace is running in NAT mode, EnableGPWorkarounds affects the registry keys BufferPolicyReads and GroupPolicyMinTransferRate. If your MED-V workspace is running in BRIDGED mode, EnableGPWorkarounds only affects the registry key BufferPolicyReads. -
-
-
-1=true: MED-V sets the keys BufferPolicyReads=1 and GroupPolicyMinTransferRate=0 (if running in NAT mode) or just BufferPolicyReads=1 (if running in BRIDGED mode). -0=false: MED-V does not make any changes to the keys BufferPolicyReads and GroupPolicyMinTransferRate. |
-
Start MED-V workspace |
- Choose whether to start the MED-V workspace at user logon, at first use, or to let the end user decide when the MED-V workspace starts. |
-
- | The MED-V workspace starts in one of two ways: either when the end user logs on or when they first perform an action that requires MED-V, such as opening a published application or entering a URL that requires redirection. -You can either define this setting for the end user or let the end user control how MED-V starts. -
- Note
-
- If you specify that the end user decides, the default behavior they experience is that the MED-V workspace starts when they log on. They can change the default by right-clicking the MED-V icon in the notification area and selecting MED-V User Settings. If you define this setting for the end user, they cannot change the way in which MED-V starts. -
-
- |
-
Networking |
- Select Shared or Bridged for your networking setting. The default is Shared. |
-
- | Shared - The MED-V workspace uses Network Address Translation (NAT) to share the host's IP for outgoing traffic. -Bridged - The MED-V workspace has its own network address, typically obtained through DHCP. |
-
Store credentials |
- Choose whether you want to store the end user credentials. |
-
- | The default behavior is that credential storing is disabled so that the end user must be authenticated every time that they log on. -
- Important
-
- Even though caching the end user’s credentials provides the best user experience, you should be aware of the risks involved. -The end user’s domain credential is stored in a reversible format in the Windows Credential Manager. An attacker could write a program that retrieves the password and thus gain access to the user’s credentials. You can only lessen this risk by disabling the storing of end user credentials. -
-
- |
-
Step | +Reference | +
---|---|
Ensure your computing environment meets the supported configurations required for installing MED-V 1.0. |
+[MED-V 1.0 Supported Configurations](med-v-10-supported-configurationsmedv-10.md) |
+
Plan and design the MED-V server infrastructure. |
+[MED-V Infrastructure Planning and Design](med-v-infrastructure-planning-and-design.md) |
+
Verify the required prerequisites are configured. |
+[MED-V Installation Prerequisites](med-v-installation-prerequisites.md) |
+
Install and configure the MED-V server. |
+[How to Install and Configure the MED-V Server Component](how-to-install-and-configure-the-med-v-server-component.md) |
+
If using an image repository, configure the image Web distribution server. |
+[How to Configure the Image Web Distribution Server](how-to-configure-the-image-web-distribution-server.md) |
+
Install the MED-V client and management console. |
+[How to Install MED-V Client and MED-V Management Console](how-to-install-med-v-client-and-med-v-management-console.md) |
+
Operating System | +Edition | +Service Pack | +System Architecture | +
---|---|---|---|
Windows XP |
+Professional Edition |
+SP2 or SP3 |
+x86 |
+
Windows Vista |
+Business, Enterprise, or Ultimate |
+SP1 or SP2 |
+x86 |
+
Windows 7 |
+Professional, Enterprise, or Ultimate |
+None |
+x86 or x64 |
+
Operating System | +Minimal Required RAM | +
---|---|
Windows XP Professional |
+1 GB |
+
Windows Vista |
+2 GB |
+
Windows 7 x86 |
+2 GB |
+
Windows 7 x64 |
+3 GB |
+
Operating System | +Edition | +Service Pack | +System Architecture | +
---|---|---|---|
Windows 2000 |
+Professional |
+SP4 |
+X86 |
+
Windows XP |
+Professional Edition |
+SP2 or SP3 +
+Note
+
+SP3 is recommended to ensure that the MED-V workspace will be compatible with future versions of MED-V. +
+
+ |
+x86 |
+
Operating System | +Edition | +Service Pack | +System Architecture | +
---|---|---|---|
Windows Server 2008 |
+Standard or Enterprise |
+SP1 or SP2 |
+X86 or x64 |
+
Windows Server 2008 R2 |
+Standard or Enterprise |
+None |
+x64 |
+
SQL Server Version | +Edition | +Service Pack | +System Architecture | +
---|---|---|---|
SQL Server 2005 |
+Express, Standard, or Enterprise Edition |
+SP2 |
+X86 or x64 |
+
SQL Server 2008 |
+Express, Standard, or Enterprise |
+None |
+X86 or x64 |
+
Operating System | +Edition | +Service Pack | +System Architecture | +
---|---|---|---|
Windows XP |
+Professional Edition |
+SP2 or SP3 |
+x86 |
+
Windows Vista |
+Business, Enterprise, or Ultimate Edition |
+SP1 or SP2 |
+x86 |
+
Operating System | +Edition | +Service Pack | +System Architecture | +
---|---|---|---|
Windows 2000 |
+Professional |
+SP4 |
+X86 |
+
Windows XP |
+Professional Edition |
+SP2 or SP3 +
+Note
+
+SP3 is recommended to ensure that the MED-V workspace will be compatible with future versions of MED-V. +
+
+ |
+x86 |
+
Operating System | +Edition | +Service Pack | +System Architecture | +
---|---|---|---|
Windows Server 2008 |
+Standard or Enterprise |
+None |
+X86 or x64 |
+
SQL Server Version | +Edition | +Service Pack | +System Architecture | +
---|---|---|---|
SQL Server 2005 |
+Express, Standard, or Enterprise Edition |
+SP2 |
+X86 or x64 |
+
SQL Server 2008 |
+Express, Standard, or Enterprise |
+None |
+X86 or x64 |
+
Operating System | -Edition | -Service Pack | -System Architecture | -
---|---|---|---|
Windows 7 |
-Professional, Enterprise, or Ultimate |
-None or SP1 |
-x86 or x64 |
-
Operating System | -Minimum Required RAM | -
---|---|
Windows 7 x86 |
-2GB |
-
Windows 7 x64 |
-2GB |
-
Operating System | -Edition | -Service Pack | -System Architecture | -
---|---|---|---|
Windows XP |
-Professional Edition |
-SP3 |
-x86 |
-
Property | -Description | -
---|---|
Machine |
-Read Only property that contains the name of the guest virtual machine provisioned by first time setup. This key contains the name that the guest would have had on first time setup failure. |
-
StatusCode |
-Read Only property that contains zero if first time setup succeeded. Any other value returned equals the event ID for the error that is logged. |
-
Time |
-The UTC time that first time setup completed. |
-
User |
-The user for which first time setup was run. |
-