How to create a Golden Image using the Wyse UniPlat toolIn an ideal world, there's only a single OS Image that supports multiple hardware platforms so you have to update and patch only one Image instead of keeping multiple Images up to date.
But to stream the OS, it must include the drivers for base system components like CPU, network card and video card. To create an image that supports multiple hardware platforms, Windows must have the drivers for all of them. Wyse delivers a tool that helps you to run through the various steps of creating a so called "Golden Image".
Wyse UniPlat Tool (UPT) is part of the WSM Client Utilities package. Using the UPT, you can create a single OS image which can be used on multiple hardware platforms. After you create the golden image, you can convert it into an OS image and stream the image to multiple platforms using Wyse WSM. This process allows you to easily create a universal image for use with various platforms.
This example outlines how to create a Golden Image for the Wyse V00L/LE, R00L/LE and C00L Zero Clients.
Before you start, ensure you have:
Here are the steps to follow - more information can be found in the WSM Admin Guide.
If you want to create a Golden Image that runs on the old (pre 2008) and the new VL Hardware, you just need to
Note: The Windows version installed on all reference devices must bear the same major version number. Hence Reference devices cannot have a mix between XP and Windows 7,Furthermore, the final golden VDisk must have the lowest common HAL among all supported platforms. To change the HAL, open Device Manager, right click the Entry under Computer and select Update Driver Software / Browse my computer for driver software / Let me pick from a list of device drivers on my computer.
I tried using the UniPlat tool to make a backup of the C: drive, but encountered a problem. I can make a backup of the C:\windows subdirectory, but when selecting C:\ (drive root), the UniPlat tool uses 100% CPU and never finishes the backup. Surely this job is not expected to take several hours?I tried this on R00L and Xx0c clients.
Same problem here hdlnd. However I am testing it on a laptop, shouldn't be a difference tho. I start the tool, create the .wup on a network drive or USB disk (tried both), change options to allow for bootable, streaming and delete all files before restoring. also tried with and without the keep drivers check box. When I select the .wup and click backup, and select C:\, it starts but it never calculates time remaning, doesnt show any files being copied, just seems like it never starts, there is no animation either. It uses 50% cpu and a few megabytes of memory when its like this. Im guessing it would have used 100% CPU if the tool could utilize two cores.
Try this HDLND, Ive not tried it my self, but as the error seems to come during formating new drives, Im quite positive this might be the solution (found in the archives)
The WSM client is using the command "Format" w/ option "/y" to force a no prompt formatting of the hard disk. This may cause the WSM Client to fail in Step 2 of 6 of the provisioning process when using Non-English OS Images. (just pick out the bits about the refistry as this was written for a problem regarding mobile mode failing)
In such scenario, the "/y" option must be translated to other letters for a Non-English OS, e.g. in German it must be "/J", in French "/O". You can specify a different letter to use when formatting the drive. Note that you don't need this if "Y" is the correct letter to use.
The steps:1. Find out your current language identifier on msdn.microsoft.com/.../libr...93(VS.85).aspxFor example, in a typical English OS the langid is 0x0009 (Primary 09, sublanguage 00), German is 0x0007 (Primary 07, sublanguage 00), French is 0x000C, sublanguage 00), Norwegian is 0x0014.
2. Change the OS Image to private mode and stream it to a device
3. Create a key under HKLM\Software\Wyse\WSM\ClientConfig\L<4 digits langid> ("e.g. "L000C" for French or "L0014" for Norwegian)
4. Add registry value "Yes" = "<letter equivalent to Y(es) in local language>"
There are a few samples in the registry we shipped.
This is a known issue and has been fixed in WSM 3.6.1 and above.