Dual boot of R class and Z class devices

Uniplat will not help on any driver incompatibility issues, but with Unitplate you do not have the issue with the systray icon and is more flexible when you have devices with wirless adapters for example.

What OS language are you running?

If you are not able to manage to overcome the issue it seems easier for you to create a combined image using uniplat.

Hi,

I'm afraid I'm getting the same error as reported earlier. The log is below; there is recurring errors about not being able to view some of the registry keys - I have tried adding permissions to all the keys mentioned and repeating but it doesn't further the process.

To be clear my process is:
1. Install Win 7 SP1 VL (from licensing.microsoft.com) on R class reference device
2. At this point the registry keys mentioned is unreadable (therefore is there a problem with the version of windows being used - I have tried non SP1 as well).
3. Install WSM client 4.1
4. Restart
5. Image disk and restart
6. Boot R class from new image and reboot (twice) in private mode.
7. Now install Windows 7 SP1 (same disk) on Z class reference device.
8. Install Z class NIC drivers and reboot.
9. Install WSM client and reboot.
10. Run driver injection.

Please let me know if you have any ideas or want a full copy of the log posted.

Cheers
Gavin


04112012 [15:43:38:833] [2040] INFO: FindUpper(SYSTEM\CurrentControlSet\, OSM Network Stack Miniport)...
04112012 [15:43:38:833] [2040] WARNING: Fail to open sub key Properties - 5
04112012 [15:43:38:833] [2040] ERROR: Cannot find upper bind for OSM Network Stack Miniport
04112012 [15:43:38:833] [2040] INFO: FindOSMNSUpperInW7(SYSTEM\CurrentControlSet\, Realtek PCIe GBE Family Controller, {3ED31FD7-563B-4D8E-ABA5-13F5B351D0E9})...
04112012 [15:43:38:833] [2040] DEBUG: Found potential ISATAP node at NetClass subkey "0009", GUID = "{346B0F4A-31CD-4A80-8D93-266B5F908106}"
04112012 [15:43:38:833] [2040] ERROR: Cannot find upper bind for SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}
04112012 [15:43:38:864] [2040] INFO: Unloaded registry hive "{_SYSTEM_}"
04112012 [15:43:38:864] [2040] ERROR: Fail to inject NIC - Failed to find upper node for OSM Network Stack Miniport in source
04112012 [15:43:38:864] [2040] INFO: InjectDriver() returns -1

You must start with capturing the image from the R-Class and boot the target image in private mode at least once before attempting to inject the drivers from Z-Class.

One more thing to keep in mind, while driver injection does work on these two platforms with Windows 7, the video drivers for these two platforms do not play nice together (AMD driver issue). Please refer to the product release notes for more information.

Thanks mhaase,

I will try the method again tonight and report back.

As there is the video driver issue with driver injection would you recommend using the Uniplat tool to create the image?

Creating a Golden Image using Uniplat works for sure, have done it several times in my lab.
Start with the R-Class and then restore onto the Z-Class. 
Make sure to install the Windows 7 hot fixes in the restored image on the Z-class before you install the WSM Client and capture the OS Image.
Take care of the display driver installation instructions mentioned in the product release notes and only use the generic Windows display drivers on R-Class and do not install CCC on the Z-Class

The reason why the usage of PS/2 Mouse on the second platform is advisable (but not mandatory) is because the USB controller may be detected and installed after you already need it (i.e. to point to driver sources), and PS/2 will always work. If I remember correct it was not required for R/Z-Class with Win7, but I will try again in my lab if time permits.

Hi,

Uniplat has worked to some extent. I now have a working image that can boot both devices but there are a few things that worry me about putting this image into production.

I'll go through the process I followed for Uniplat and point out where I had issues.

1. Install Win 7 SP1 on R class
2. Take uniplat image onto server
3. Boot Z class onto working individual WSM image
4. Install uniplat
5. Restore R class .wup file onto fresh HDD keeping critical drivers from Z class.
6. Reboot from physical HDD on Z class. ** this is where I had the first issue; as there is no 100Mb system reserved boot partition on the fresh HDD I had to run startup repair a couple of times to fix. Is this normal? **
7. Install drivers on Z class
8. Install hotfix ** second issue - the hotfix would not install, I was getting a load of errors in event log around this issue "The Cryptographic Services service failed to initialize the Catalog Database. The ESENT error was: -1032". I searched around and redid some permissions on C: and c:\windows and also activated Windows. This allowed the update to be installed after a couple of reboots.
9. Install WSM client, image, reboot from image to Z class. Works from small amount of testing.
10. Boot image into R class. Boots but there are now permission errors on some things namely the event log has access denied.

Is having to startup repair normal?
Would the permissions problem be solved by naming the two computers exactly the same?

As I said above I wouldn't want to put this image into production with permission errors as I don't know what problems it could cause in the future. Hopefully it can be solved relatively easily.

Thanks for your help so far.
Gavin

It is installing with English (United Kingdom).

I have tried Uniplat before obviously without success. I will try it again tomorrow and report any issues I have with it then.

With Uniplat should the Z be the first device and R be the second? Going from the admin guide the second device should have PS2 keyboard/mice?

I think you have run in some procedural issues here, but trust me, this is all feasible and just takes a bit of practice to get used to the process.

Please perform the restore action on a Z-Class reference device with Windows installed on the local disk and not being streamed from the network.

Below are some more best practice/tips when using Uniplat. 

1. Preparing units for Uniplat:

a. Install fresh OS on a single partition. For Windows 7 uses this procedures: http://www.sevenforums.com/installat...new-drive.html. Make sure to leave enough room in HDD for additional partitions for Uniplat restore.
b. Install all applicable hotfix and patches. After latest updates are applied, disable “Windows Update” feature until all Uniplat backup/restore operations are done. This is because if Windows update runs in the background while Uniplat performing Backup, inconsistent windows files may be captured within the same .wup file. Windows Update can be re-enabled after a final combined .wup file is created.
c. Do not install applications. Installing applications on the based platform before creating a based .wup file results in bigger .wup file and longer time to backup/restore. Additional applications can be installed after a final combined image is created.

2. When performing backup:

a. always enable “Prepare image for Wyse OS Streaming”. This is also the default.
b. Backing up Windows 7 OS takes 2 rounds. After the first round is done, you should see message “To complete the process for backing up current OS image, a reboot is required. Please make sure to log in as an administrator after the reboot. The final step will happen automatically after the reboot. Press OK to reboot now, CANCEL to reboot later manually”. I always press “OK”. If you do not press OK right away, make sure you do not wait a long time before rebooting the unit. This is to ensure that the files captured between 1st and 2nd rounds are consistent (that no windows updates are done in-between that may cause any inconsistency). Also one may forget to complete the 2nd round totally. After reboot, make sure you log in to the same Administrator account so Uniplat can complete the 2nd round.

3. When performing restore:

a. It is recommended to always format the Restore partition to NTFS before restoring so that the restore partition starts clean. 
b. “Delete all file before restoring” option is not necessary if the restored partition was formatted right before.
c. Always enable “This image is bootable” option
d. “Keep critical drivers from current Windows session” option can be skipped on Windows 7 OS because Windows 7 contains drivers essentials for boot up for most platforms. 
e. “Perform post restore fix up only” is for troubleshooting and should not be enabled (the default)

4. After Uniplat restore, when reboot unit to restored partition,

a. Windows 7 displays “Windows did not shutdown properly, ..”. This is expected. Make sure you press the default “Start Windows normally”. Do NOT try to repair windows. 
b. if external USB HDD was used, make sure you unplug USB HDD before boot. Some USB HDD is set up to have active partition. If BIOS is configured to boot from USB HDD before local HDD, unit will try to boot to USB HDD. You may see various boot up error message depends on how your USB HDD was formatted/setup.

5. It is recommended to start with the newest platform and create a based .wup file from this platform. With the exception that for R&Z Class you should start with R-Class.

6. If advanced display or audio functions are not required, it is recommended to skip installing specific display/audio driver and just use windows generic drivers for target platforms. This is because some display/audio driver packages, when co-exist with drivers from other platforms, cause conflict and may result in error/warning/boot failure or even BSOD.

FYI, I just created a combined Win7 SP1 US English OS Image for R, Z and Xm Class using Uniplat and WSM 4.0.1 :-)