Archive

Posts Tagged ‘VPC’

Help! My Virtual PC Appears to be Possessed!!!! (a.k.a – the Case of the Auto-Hibernating Virtual PC)


I recently encountered a customer issue where, periodically, for what appears to be no reason at all, while a user is working in a Virtual PC (virtual machine in Windows Virtual PC for Windows 7) – it will hibernate on its own. In some cases, the user was in the process of doing work.

At first I did not think that would be possible but it was quickly confirmed. A quick investigation confirmed that MED-V 2.0 was installed – yet the user was working outside of MED-v using the Virtual PC in VPC only – or full desktop mode.

We also noticed the following event was being logged in the MED-V event log at the same time this was occuring.

Event ID: 11004

Task Category: Guest Patching

Message: “VM is being stopped during the configured update window.”

It turns out the Virtual PC was interrupted by the Guest Patching Service of MED-V 2.0. What we did to resolve this was adjust the registry value GuestUpdateDuration in the registry key (HKEY_LOCAL_MACHINESOFTWAREMicrosoftMedvv2VM) to 0. This prevented the problem from re-occuring.

MED-V assumes it will be waking a VM up when not in use by MED-V. When the same VM used by MED-V is currently opened exclusively by VPC in full desktop mode, MED-V tiggers VPC to close the VPC using its default action (hibernate.) The value GuestUpdateDuration defines the number of minutes that MED-V should keep the MED-V workspace awake for updating, starting at the time contained in GuestUpdateTime. Enter 0 to disable.

Remember that MED-V v2.0 was only designed for provisioning applications to run in seamless mode.

Advertisements

MED-V: Support for Multiple Drives within MED-V

July 12, 2011 1 comment

Support for multiple drives and volumes within a virtual PC (workspace) used by MED-V will depend on the version of MED-V being used. MED-V v2 only supports the use of one fixed disk volume within a single virtual hard disk (VHD.)

It is technically possible to use more than one partition/volume within a single virtual hard disk but it is not recommended if it can be avoided.

MED-V v1 supported the use of multiple virtual hard disks (VHDs.) In addition, MED-V also supported multiple volumes (drives) as well as the use of the SUBST command to mount drive letters to local directories.

Categories: MED-V, VPC Tags: , , , , , ,

MED-V: Performance Issues when using Internet Explorer 8 and later in a v1 workspace


Due to performance limitations of Virtual PC 2007 and the additional resources required for Internet Explorer version 8 and later to function properly, it is not recommended to use any version greater than Internet Explorer 7 in the MED-V 1.0 Workspace.

Only Windows Internet Explorer 6 SP2 and Windows Internet Explorer 7 are officially supported for the MED-V 1.0 SP1 workspace installation. This is referenced on the following link:

http://technet.microsoft.com/en-us/library/ff603753.aspx

For Version 2 of MED-V, Windows Internet Explorer 6, Windows Internet Explorer 7, Windows Internet Explorer 8, and Windows Internet Explorer 9 are supported for the MED-V 2.0 workspace installation.

Categories: MED-V, VPC Tags: , , , , , ,

MED-V 1.0: Error: “MED-V Workspace cannot start because the version of Virtual PC on your computer is not supported by MED-V”


When you attempt to start a MED-V v1 workspace, if you get the following error, you may not have properly deployed all of the appropriate pre-requisites:

MED-V Workspace cannot start because the version of Virtual PC on your computer is not supported by MED-V.

This can happen if you upgraded MED-V v 1.0 to either v1.0 SP1 or SP2 and the updated Virtual PC 2007 QFE patch was never applied to the client (KB974918.MSP.)

You will need to verify that the version of Virtual PC on the computer is at least at version 6.0.213 to ensure the KB974918 patch has been deployed. This patch must be deployed in order to meet the supported requirements for operation.

Categories: MED-V, VPC Tags: , , ,

MED-V 1.0: Errors that can occur when you allocate too little Memory to the Virtual PC


If you fail to allocate enough memory to the MED-V Guest Workspace operating system, you will find yourself having a tremendous amount of performance problems and possibly including the following errors:

“Your computer is running low on free memory. This may cause the Workspace to run slowly. Please close applications you are not using and try again.”

and/or

“Workspace ‘<NAME>’ failed to start. Please try starting the Workspace again.”

“Encountered an unexpected error. Internal error: Timed out waiting for VM to load: <IMAGENAME>”

The workspace policy option in MED-V v1 bases allocation of memory based upon a matrix constructed of specific memory allocations based on physical memory ranges on the host. Too often the memory is configured with the ratio allocatting an insufficient amount of memory to the workspace (i.e. where only 256MB memory is allocated to the workspace when the physical memory is 1GB or above; 128MB of memory if lower then 1GB of physical memory.)

The settings for these can be adjusted in the MED-V Management Console and confirmed in the ClientPolicy.XML file within the following section:

<PerformanceSettings>
              <WorkspaceId>27</WorkspaceId>
              <MemoryEnabled>true</MemoryEnabled>
            </PerformanceSettings>
            <MemoryRules>
              <WorkspaceId>27</WorkspaceId>
              <Host>0</Host>
              <VM>128</VM>
            </MemoryRules>
            <MemoryRules>
              <WorkspaceId>27</WorkspaceId>
              <Host>550</Host>
              <VM>192</VM>
            </MemoryRules>
            <MemoryRules>
              <WorkspaceId>27</WorkspaceId>
              <Host>1100</Host>
              <VM>256</VM>
            </MemoryRules>
            <Images>

 

Categories: MED-V, VPC Tags: , , ,

MED-V 1.0: Error: “Failed to fetch policy from the server”


After upgrading the MED-V 1.0 Server to either SP1 or SP2, the MED-V clients may get the following error:

“Failed to fetch policy from the server.”

You may also get this same error when trying to open up the MED-V Management console.

This can happen if the server version is newer than the client. For example, the server may be version 1.0.200 yet the clients may be 1.0.105.

Upgrading the clients to the same version (or later) than the server is the only solution to this problem.

Categories: MED-V Tags: , , ,

MED-V 1.0 SP1: CD/DVD/Optical Drive Access Appears Problematic


MED-V V1 SP1 running on either Vista or Windows 7:

If a workspace configured by policy to use the host machine’s optical drive starts without Optical Media injected (in either full desktop mode or seamless mode) the following may happen:

When you insert an optical disk post workspace start, the drive in Explorer will show the proper-media injected however when you try to open the workspace while the workspace is running you will get the error:

“Please Insert a disk into <TYPE> Drive (n:).”

Likewise – the same also happens inside the guest operating system as well.

After restarting the workspace, it is, however available to the host and guest.

This is caused by a combination of the process for VirtualPC not being elevated and the drive is captured only at startup for a standard user process.

There are four ways to work around this:

1.) Simply restart the workspace with the disk in the drive.

2.) Start the MED-V Client elevated (run as admin.)

3.) Disable UAC.

4.) Disable the feature in the workspace policy.

If required for guest OS’es use a drive mapping to the shared optical drive.

Categories: MED-V, VPC Tags: , , , , ,