Solved!
Go to SolutionvWorkspace 7.1 MR1 - VMWare Linked Clones Integration
Hi,
I am currently trying to use the VMware linked clones functionality through vWorkspace 7.1 MR1 and am finding that when the VDI’s are syspreped they appear to be getting the US keyboard. I have imported my own unattend.xml file which specifies the locale to be EN-GB but this setting seems to be overwritten by vWorkspace when VDI’s are deployed.
When moving through the menus for the new sysprep customization, the advanced regional settings don’t give the option for the locale to be set to UK and in addition there is no option to leave this box blank (ultimately allowing windows to take the settings from the unattend.xml). I believe not having the option to set a UK locale or to leave the box blank is causing the settings in the unattend.xml file to be overwritten.
Is there any way to get round this issue?
I would appreciate your inputs.
Thank you
Nisit
Michel Roth
173 Posts
410
0
Posted October 20th, 2010 12:00
C:\windows\temp\vmware-inc\guestcust.log on the deployed VM should tell you which unattend.xml was used. If you take a look at that one you can see actually which value was used to see the keyboard layout.
I don't think it has anything to do with Linked Clones specifically, or have you established that?
In any case, you can use Group Policy Preferences to set the default keyboard layout after the VM has been deployed if that works for you: http://technet.microsoft.com/en-us/library/cc754496.aspx
What also could be worth trying is set En-GB in the template and then create a new deployment where you do not select the keyboard layout at all.
DELL-Adam Dr
28 Posts
410
1
Posted October 20th, 2010 13:00
Nisit,
The missing GB locale is a known issue with the sysprep wizard and has been fixed in 7.2.
-Adam