Archive

Archive for December, 2010

MED-V 1.0: How to Use Serial Ports with MED-V

December 31, 2010 1 comment

Use of applications that depend on serial ports will work in MED-V pending that the underlying virtual PC configuration is done.You will need to sync settings with the local port settings on the host operating system.

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.)

Advertisements
Categories: MED-V, Virtualization Tags: , , , ,

MED-V 1.0: Locations where Key Client Configuration is Stored

December 30, 2010 Leave a comment

Very little MED-V client configuration is stored in the registry. What is stored is found under this key:HKEY_LOCAL_MACHINE\SOFTWARE\Kidaro

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:

%ALLUSERSPROFILE%\MED-V\Profile\ProfileInfo.XML

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:

 http://blogs.technet.com/b/medv/archive/2010/06/07/a-closer-look-at-the-med-v-image-and-data-repositories.aspx

Categories: MED-V Tags: , , , ,

MED-V 1.0: How to make Global Changes to the Password Save Policy

December 29, 2010 Leave a comment

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.

http://blogs.technet.com/b/medv/archive/2009/04/22/med-v-tips-on-modifying-the-clientsettings-xml-file.aspx

1.) To change the Password save policy

2.) Back up ClientSettings.xml file.

3.) Edit clientsettings.xml file

Change             

<EnableSavePassword type=”System.Boolean”>true</EnableSavePassword>

To             

<EnableSavePassword type=”System.Boolean”>false</EnableSavePassword>

MED-V 1.0: Issue with Long URLs

December 28, 2010 Leave a comment

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:

http://sharepoint.contoso.com/directory1/directory2/directory3/directory4/directory5/directory6/directory7/directory8/directory9/directory10/directory11/directory12/directory13/directory14/directory15/directory16/directory17/directory18/directory19/directory20/

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:

http://sharepoint/Shared%20Documents/Forms/AllItems.aspx?RootFolder=%2fShared%20Documents%2fFolder1%2fFolder2%2ffolder%2dlength1234567890123456789012345678901234567890%2ffolder%2dlength%2d12345678901234567890&FolderCTID=&View=%7b465EA817%2dFF5A%2d4E66%2d8C91%2d160D0B0B53AC%7d
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.

Categories: IE, MED-V Tags: , ,

Another Odd Issue When Trying to Upload Images to a MED-V Image Distribution Server

December 22, 2010 Leave a comment

You have dealt with this issue before if you have used MED-V with TrimTransfer. User gets the following error message when trying to upload image to Image Distribution Server from the MED-V Management Console:
 
Failed uploading image to the server. Please verify that the server is configured correctly.
 
Error details: The image file http://servername:80/virtualdirectory/image_name_1.ckm.test already exists on the server. Remove the file from the server and try uploading theimage again.
 
Appropriate CREATOR OWNER access and other permission are also set correctly in spite of this error.
 
The Cause of this is the App Pool running the server side extensions are running under the machine context rather than the user context.
Resolution
On the IIS 7 image distribution server, you will need to change the application pool’s settings to load its identity profile. The command that does this is as follows:
 
“%windir%\sytem32\inetsrv\appcmd set apppool "AppPoolName" -processModel.loadUserProfile:true
This normally does not need to be set as the default value is true.
The "processModel.loadUserProfile" option specifies whether IIS loads the user profile for the application pool identity. Setting this value to false causes IIS to revert to IIS 6.0 behavior. IIS 6.0 does not load the user profile for an application pool identity.
If the IIS server was configured to operate in IIS 6 mode, this may also occur.
NOTE: If you need to make the change on the default app pool, use the following command:
%windir%\system32\inetsrv\appcmd set config /section:applicationPools /[name=’DefaultAppPool’].processModel.loadUserProfile:true
 
Categories: MED-V Tags: , , , , ,

Is Guardian Edge Software Preventing App-V Applications from Running?

December 12, 2010 1 comment

If you are running 3rd Party Encryption Software, you may find  this application is viewing the App-V Drive (drive Q: by default) as removable preventing applications from launching. It will throw the following error:

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

 
So what is going on? This actually caused by a combination of these applications not knowing enough about each other as well as service load timing. One common example is the Guardian Edge Removable Storage Digital Protection software. Newer versiosn of both App-V and GE should not have this issue but GE still requires App-V to be loaded before the RSM service loads
 
Make sure you are at App-V 4.6 or 4.5 SP2 and GERS 3.5.1 Also you will need to go to the following registry keys on the clients:
HKLM\System\CurrentControlSet\Services\RemovableStorageService, add a new REG_MULTI_SZ (multi string value) named ‘DependOnService’ and set its value to ‘sftvsa’ and ‘sftlist’
 
Hope this helps,
 
Steve
 
Categories: App-V Tags: , ,