Windows 10 appears to have a problem detecting new hardware during Windows Setup.  You will be able to import your Gold just fine, but when creating desktops, they may hang during Setup.  This appears to be related to SCSI disk controllers, but has also been observed with other hardware configurations.  If Windows 10 hangs with a spinning circle during Setup, follow this KB.

Please do the following on the OS layer you have already imported.  The procedure can also be performed on the Gold if you have deleted your OS layer.

1.    In the UDMC in the OS layers tab, select the OS you want to update and "Add Version" following all of the normal steps.

2.    Wait for the install machine to indicate that it is up and running and you are ready to edit the revision.

3.    Using vSphere edit the settings on the IM desktop machine.

4.    Note the type of "Network adapter". Remove the board (you will put it back in later).

5.    Add a hard disk (Create new, Disk Size of 1 MB, Virtual Device Node of SCSI (1:0)
Add a hard disk (Create new, Disk Size of 1 MB, Virtual Device Node of SCSI (2:0)
Add a hard disk (Create new, Disk Size of 1 MB, Virtual Device Node of SCSI (3:0)

NOTE: If using the vSphere web client. You need to first add new SCSI controllers before the new disk will let you select nodes 1:0, 2:0, and 3:0. I am unsure if you even still need to add the new disks at this point but it doesn't hurt to still do so.

6.    Click OK to complete the edit. You should see vSphere update the desktop settings. Wait for that to complete.

7.    We have seen times where Windows and VMWare have not updated the information or places the information in the wrong location within the registry, so the IM is required to be shutdown at this time. Do NOT simply reboot, the IM must be completely powered off and then restarted.

8.    Log into the IM using an administrator account.

9.    Open a command window selecting "Run as administrator". Navigate to c:\Program Files\Unidesk\Uniservice. Issue the command: "uniservice -s".

10.  Verify that the settings have been added to the registry by doing a regedit. Navigate to HKLM\System\CurrentControlSet\Services\Uniservice\SCSIControllers:

Verify that the UINumber for controller 0 is set to A0.
Verify that the UINumber for controller 1 is set to C0.
Verify that the UINumber for controller 2 is set to E0.
Verify that the UINumber for controller 3 is set to 100.

11.  Go back to vSphere and edit the settings of the IM desktop again. Add the network board back by selecting the "Ethernet Adapter", setting the Adapter Type to the type that you removed, and make sure that you select the correct network. Click to remove the three small disks that were added, and select that you want to remove them from virtual machine and delete them from disk. Click to remove the SCSI controllers as well.

12.  Click the OK to complete the edit. You should see vSphere update the desktop settings. Wait for that to complete.

13.  We have seen times where Windows and VMWare have not updated the information or places the information in the wrong location within the registry, so the IM is required to be shutdown at this time. Do NOT simply reboot, the IM must be completely powered off and then restarted.

14.  Once the IM has been restarted, edit the following file:  C:\Windows\Panther\unattend.xml

15.  Put this section anywhere in your unattend.xml, after any other </settings> tag:

<settings pass="generalize">
    <component name="Microsoft-Windows-PnpSysprep" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
           <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
    </component>
</settings>

16.  Then run RegEdit and put in these two keys:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Settings\sppnp]
"DoNotCleanUpNonPresentDevices"=dword:00000001
"PersistAllDeviceInstalls"=dword:00000001

17.  Finalize the OS revision.

You are now ready to deploy the new O/S revision to the desktops.