You will also need to set the appropriate COM port settings in the base .VMC file. You can do this through the user interface by editing the settings of the virtual machine.
You can also modify the VMC directly. The XML for the .VMC pertaining to the serial port is below. The below XML represents COM1 enabled for serial port usage:
<serial_port id="0"> <connect_immediately type="boolean">true</connect_immediately> <port_name type="string">COM1</port_name> <port_type type="integer">1</port_type> </serial_port>
You may also need to ensure the settings are verified on the guest OS as well (inside Device Manager within the guest operating system.)
Registry values include:
- DesktopShortcut: A REG_SZ value that determines if the client will auto place a desktop shortcut.
- PrestagedImagesPath: A REG_SZ value that determines the path to CKM images that have been predeployed.
- StartAutomatically: A REG_SZ value that determines if the client starts at logon.
Most of the other information is stored here:
This is the MED-V Client Profile. The client profile is where the information set during the installation is stored. This serves as a template for the actual Windows user running the client. The user working copy is always stored in the %LOCALAPPDATA%\MED-V\Profile directory.
If you were to manually modify the MED-V server, you will want to modify <ServerAddress>
<Kidaro> <ServerAddress type="System.String">http://localhost:80</ServerAddress> <ImageDistributionEnabled type="System.Boolean">True</ImageDistributionEnabled> <ConfigurationFolder type="System.String">C:\ProgramData\MED-V\Local\Config</ConfigurationFolder> <VmsFolder type="System.String">C:\MED-V Images\</VmsFolder> <ClientCertificateThumbprint type="System.String"> </ClientCertificateThumbprint> <ClientId type="System.String"> </ClientId> <KidaroDomain type="System.String"> </KidaroDomain> <DataFolder type="System.String">C:\ProgramData\MED-V</DataFolder> </Kidaro>
This (Profileinfo.xml) and the other files explained in my blog post on the MED-V Team Blog:
If you want to modify the password save policy for all of your clients, you will need to modify the global clientsettings.xml file in the C:\Program Files\Microsoft Enterprise Desktop Virtualization\Servers\ConfigurationServer directory.
Please refer to this blog on modifying this file – particularly the version modification.
1.) To change the Password save policy
2.) Back up ClientSettings.xml file.
3.) Edit clientsettings.xml file
Here’s an issue I have seen firsthand at least once or twice in testing and with one particular customer scenario. A user may encounter problems spawning alternative browsers when long URLs (i.e. URLs greater then 254 characters) are being intercepted by the MED-V BHO (browser helper object) when using web redirection.
For example, if you are redirecting URLs going to the domain name contoso.com to the guest browser and you type URLs that may be long such as the following:
you may find that the guest browser does not spawn when typing or pasting the URL in the “Run” dialog box, the host browser, or the Windows Explorer address bar. The guest browser may not spawn if you simply click on a link on a web page in the host browser.
Another example may be a URL containing a local address and you are redirecting all local addresses:
This is due to MED-V v1 spawning the instance of the browser with the URL as a command-line argument. This manner is causing the limitation of chracters in the argument to be reached.
Microsoft has confirmed this to be an issue in version 1.0 SP1 of MED-V and will be fixed in the next release of MED-V.
In the meantime, the recommended workaround is to open the guest browser instance in advance of activating the URL. This prevents the browser process from having to be spawned.
An unexpected error occurred. Report the following error code to your System Administrator.
Error code: 4605F3-07D0070C-0000003D
Upon further investigation you will also find the SFTLOG.TXT shows the following as well:
corrupt cp file detected (‘Q:\Reader 9.0\osguard.cp’). osguard cp file, NO CORRECTIVE ACTION TAKEN
HKLM\System\CurrentControlSet\Services\RemovableStorageService, add a new REG_MULTI_SZ (multi string value) named ‘DependOnService’ and set its value to ‘sftvsa’ and ‘sftlist’