Just a quick note in case anyone else runs across this.
My linked clone (Windows 7 Pro, 64-bit) deployment process looks like this:
Install/update the apps I need on my master image (the VM is not joined to the domain)
Update VMware tools and the View Client for new releases
Clone the machine to a new VM
Run sysprep on the clone (mainly to get the admin profile copied to the default profile for new users - the "right" way to do it in Windows 7)
Join the clone to the domain and log in to get GP to run (adds printers, ScriptLogic agent etc.)
Shut down the clone, snap it, and use it as my base image for deploying my linked clones (using quickprep)
All good, been working great for a year, and then I upgraded to 5.2. As soon as I did that, USB redirection stopped working. The VMware USB devices in device manager show "working" and there are no errors in the event logs. In the View client logs from a zero client I see this:
03/28/2013, 07:06:29.688> LVL:2 RC: 0 SOFT_USB :usb_urboip_process_plugin2: Plugging in device USB\Vid_013fd&Pid_0842 (device_handle 0x00000403)
03/28/2013, 07:06:29.688> LVL:1 RC: 0 SOFT_USB :VHUBLIB(error): Failed to plugin virtual device handle: 01013CC8, error: 0x1
03/28/2013, 07:06:29.688> LVL:1 RC:-500 SOFT_USB :usb_urboip_winif_vhublib_plugin_complete_cback: deferred plugin failed (9)! (device_handle 0x00000403)
03/28/2013, 07:06:29.688> LVL:1 RC:-500 SOFT_USB :usb_urboip_winif_plugin2: Vhublib_PluginDevice failed (9)
03/28/2013, 07:06:29.688> LVL:1 RC:-500 SOFT_USB :usb_urboip_process_rx_buffer: failed to process PLUGIN2
Figured it may have been a failed View Client upgrade, so I went back to my master (non-sysprepped image) and re-ran the View Client install. No help - deployed it again and still no USB. Decided to eliminate some steps and published my master (non-sysprepped) machine in a manual pool. Connected to it from a zero client and USB worked.
To make a long story - and about fours hours on the phone with VMware support - shorter, it looks like sysprep is breaking USB redirection with the 5.2 client. We don't know why, but if I reinstall or repair the View Client after running sysprep it's fixed. I have a dead-simple sysprep unattend file that adds a couple of user accounts, tells sysprep to copy the admin profile to the default profile, sets the language and license keys, and that's it. Nothing for devices (no full PnP rescan), just a "generalize" and "/oobe" on the command line. But even with those simple settings settings it's breaking redirection.
Support is going to try to repro the problem in the lab, but I figured I would post this here in case anyone else runs across the issue.
Geoff
Hi Geoff
we have seen some people with similar issues. We believe there may be a problem when the upgrade is done from an earlier version of View. In your original post you mention:
"if I reinstall or repair the View Client after running sysprep it's fixed". Did you mean reinstall/repair the agent rather than the client? The problems we have been investigating have all been caused by agent side issues rather than client problems.
Wondering if you could try something to see if this resolves the problem.
After getting your agent to the required version of view, but before performing the sysPrep operation. Please first confirm that the agent works for USB redirection. In order to solve the problem you are facing there are one of 2 possible ways to achieve this. One way works for some people, and another works for others. Would appreciate any feedback on your findings.
prior to doing the sysPrep but having confirmed USB redirection is working;
Method 1: (not works for some people, not all)
1. go into Device Manager, and delete the "VMWare View Virtual USB Hub" device.
2. right click in device manager, and scan for hardware changes. This should re-install the latest version of the vhub driver.
3. reboot the agent
Now check if USB is still working, and then try your sysPrep as before.
Method 2: (again prior to doing the sysPrep operation)
1. search the machine for "vmwvhub.sys". There will be several versions found, including in C:\Windows\System32\drivers\ and c:\Windows\System32\DriverStore\FileRepository. The version saved in C:\Program Files\VMware\VMware View\Agent\bin\drivers\should be the latest version for your agent install. (probably 5.5.0 xxxx)
2. delete instances of these files that have a version other than the latest of 5.5.0 build-949580. The older View drivers will probably shows a version of 5.1.0 build-668184.
3. now reboot, and confirm USB still functions. The driver loaded in device manager should be shown a 5.5.0.
Now try the sysPrep operation.
Let me know if one or other of these works for you,
Kind Regards
Peter Brown
I too just ran into this same thing except with Full Clones (that is the only thing I am sysprepping). Reinstalling the View 5.2 agent restored the USB redirection functionality.
I still have not heard back from VMware on this, so if you'd like to add to my ticket (13303822603) maybe someone else reporting the problem will spur some action.
Geoff
Hi Geoff
we have seen some people with similar issues. We believe there may be a problem when the upgrade is done from an earlier version of View. In your original post you mention:
"if I reinstall or repair the View Client after running sysprep it's fixed". Did you mean reinstall/repair the agent rather than the client? The problems we have been investigating have all been caused by agent side issues rather than client problems.
Wondering if you could try something to see if this resolves the problem.
After getting your agent to the required version of view, but before performing the sysPrep operation. Please first confirm that the agent works for USB redirection. In order to solve the problem you are facing there are one of 2 possible ways to achieve this. One way works for some people, and another works for others. Would appreciate any feedback on your findings.
prior to doing the sysPrep but having confirmed USB redirection is working;
Method 1: (not works for some people, not all)
1. go into Device Manager, and delete the "VMWare View Virtual USB Hub" device.
2. right click in device manager, and scan for hardware changes. This should re-install the latest version of the vhub driver.
3. reboot the agent
Now check if USB is still working, and then try your sysPrep as before.
Method 2: (again prior to doing the sysPrep operation)
1. search the machine for "vmwvhub.sys". There will be several versions found, including in C:\Windows\System32\drivers\ and c:\Windows\System32\DriverStore\FileRepository. The version saved in C:\Program Files\VMware\VMware View\Agent\bin\drivers\should be the latest version for your agent install. (probably 5.5.0 xxxx)
2. delete instances of these files that have a version other than the latest of 5.5.0 build-949580. The older View drivers will probably shows a version of 5.1.0 build-668184.
3. now reboot, and confirm USB still functions. The driver loaded in device manager should be shown a 5.5.0.
Now try the sysPrep operation.
Let me know if one or other of these works for you,
Kind Regards
Peter Brown
"Did you mean reinstall/repair the agent rather than the client? The problems we have been investigating have all been caused by agent side issues rather than client problems."
Yeah, sorry, I meant an agent repair. And yes, we did update the agent from 5.1 to 5.2 on the master images, so if it's an update vs clean install issue, then I would definitely be susceptible. In the testing I have already done, USB redirection works fine after upgrading the agent, prior to sysprep.
We'll be recomposing some pools tomorrow after the May MS updates are released so I'll try both your suggestions and report the results.
Geoff
thanks for the update Geoff. and glad we are on the same page ref agent/client as I would have been very confused if the problem was fixed by reinstalling the client/ =D
let me know how you get on tomorrow,
cheers
peterB
Ended up with some time to test this today.
Method 1 does not work. Still no USB connectivity after sysprep. Note that device manager was showing the latest (5.5.0) driver prior to me uninstalling and reinstalling the device. After reinstall (PnP scan) it was still showing 5.5.0.
Method 2 - Works!
Thanks for the workaround!
Geoff
Thanks for the update Geoff. Glad the workaround worked.
We are trying to reproduce the problem, but many attempts to do so have always worked. We will keep trying to repro and find root cause.
Anyway, I'm glad method2 worked for you,
cheers
peterB
we have published a KB detailing this issue and its workaround; see http://kb.vmware.com/kb/2051801
