Out of interest, does windows see the USB device at all before you remove it and plug it back in? Are we talking USB2 or 3?
Would you get the same effect as removing and re-adding if you reboot the device?
If this is a USB3, is there a USB2 socket you could put it in? Just in case it is falling foul of a driver order where it can't install the main driver because the USB driver is not in place yet.
MarXtar Ltd/MarXtar Corporation
Ivanti One Development Partner
Try MarXtar Enterprise Notifer for Ivanti to Better Communicate with Your Service Subscribers
Try MarXtar State Management for Ivanti to Better Understand and Manage your Assets
Aye - remember that much of the USB3 shenanigans will only work (after a reboot) once the regular USB/USB2 stuff is installed. Could be related nonsense like that?
When I go into Device Manager it appears that Windows cannot see the USB before I unplug and reinsert it.
If i reboot before doing that it does then pick it up when going back into Windows 10, so it looks to be on the initial reboot it fails to find it.
I gather it is USB 3.0 though I can't try another port as it is the only one it has.
You may have to "cheat" then and incorporate that "first reboot" of the OS properly (USB3 has this most annoying thing where it can only be detected/installed after the base USB drivers are down & then a reboot follows).
There's topics on USB3 and provisioning here:
That may help you along .
Sorry to be a pain but what do you mean by cheating with regards to the first reboot? Can you possibly elaborate on what you are suggesting?
Not a problem.
Essentially - conceptually get your Win-10 image to behave something like this - essentially, a locally "auto-run" script on first run:
- Your Windows-10 image is booting up for the first time after your proivisioning stuff has done its thing.
- Your win-10 image gets a few minutes, to properly detect hardware & install drivers (among them - the initial USB 1/2 driver). May or may not need actually significant time.
- Your win-10 image then reboots ... and this 2nd time around, picks up / installs the USB3-driver, meaning that "provisioning as normal" can continue (since you now have networking).
... That's what I'm suggesting. It's a bit of a klutz, but since you don't have network connectivity (because no USB3) until the 2nd reboot, you need to essentially hard-code the first series of steps (since we can't tell the client, on account of no networking). .
Does that make more sense logically?
Ahhh OK I see what you are getting at, so I will need to put something into RunOnce possibly?
So would i need to add a task in the TS at the OS installation stage whilst it is still in Win PE and before it has rebooted into Windows 10?
Maybe I could use something like devcon to force a hardware scan?
Possible - however, if USB3 is similarly annoying in Win-10 as it is for the rest of provisioning (hence we have that article), I'm not sure that this "reboot before I can even detect USB3" is something that can be circumvented.
Would be nice to be wrong on this count (and - granted - I don't get quite *WHY* Windows "must" have a reboot before being able to detect USB3, but meh) ... so you may end up having to have either a special image or a special template for these devices (that injects those "auto-run" commands into the Win-10 image while in WinPE).
Getting Win-10 to auto-logon & auto-run stuff shouldn't be super hard ... (he claims, optimistically).
If you can get that USB3 thing sorted out - that's your big one ... usually it's "less" of an issue, as most tablets tend to get imaged in a cradle of some kind, and thus have "a proper NIC adapter" and don't rely on USB3 working for the "proper OS" provisioning stage ... joy .
(hope this helps a tiny bit).
Thanks again, appreciate your assistance.
Before I look further into this I just tried the build with a USB 2.0 hub plugged into the USB 3.0 port and, hey presto, it worked.
More of a workaround that a solution but at least I can build them until I have looked further into it your advice.
These 2 in 1 HP X2 210 devices seem to be a bit of a pain in truth!
Oh - it's not just the devices.
The dongles have other surprises in store too.
Some NIC dongles use "their own" MAC-address, so you end up with wonderful situations where (for the purposes of imaging) "all of your tablets" have one of (insert number of dongles here) X possible MAC-addresses ... joy .
OS Provisioning never gets old ... if it's not PXE keeping life interesting, it's things that "make life easier for the user" (but not the poor admins that no one things about... ).
And happy to help .