You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been trying to figure this out for a few days now messing with the $global.MyOSDCloud variables and have not been able to come up with a solution (at least on my own). Any help would be greatly appreciated.
I would like to use the driver function of OSDeploy to run after I have already deployed a custom .wim to the drive.
How if at all possible could I call OSDeploy to run but skip everything but the detection of what system I am currently running on so it can download the proper Windows Updates, Windows Drivers, and OEM Device Drivers, and then run them during first boot?
I have tried to set $global.MyOSDCloud variables like I mentioned before, but when I tried skipping the Image sections, the script didnt like that and stopped running.
I have an unattend.xml file I am already using, so I dont want to overwrite that, but if I am able to add a command to run manually that would work.
I would just like to make sure that the different devices I am installing this image to get the drivers and updates they need without having to constantly update the image with new drivers/firmware.
The text was updated successfully, but these errors were encountered:
I would suggest you to import the OSD PS module and use it in the OOBE phase, with oobe.cmd.
But if you just want to install OS and driver updates, you can use the following two one-liners:
Install-WindowsUpdate -UpdateType Driver -AcceptAll -IgnoreReboot
I dont see it in the documentation, but does the OOBEDeploy function and install OEM driver and firmware just like OSDCloud will do from inside WindowsPE? Im wanting to get the same function where it will autodectect the device and OS, then download the driver pack and save it to the drive to then install later during the OOBE section.
Thats the function I am looking to use. From what I can see OOBEDeploy will only pull from Windows update, correct?
I have been trying to figure this out for a few days now messing with the $global.MyOSDCloud variables and have not been able to come up with a solution (at least on my own). Any help would be greatly appreciated.
I would like to use the driver function of OSDeploy to run after I have already deployed a custom .wim to the drive.
How if at all possible could I call OSDeploy to run but skip everything but the detection of what system I am currently running on so it can download the proper Windows Updates, Windows Drivers, and OEM Device Drivers, and then run them during first boot?
I have tried to set $global.MyOSDCloud variables like I mentioned before, but when I tried skipping the Image sections, the script didnt like that and stopped running.
I have an unattend.xml file I am already using, so I dont want to overwrite that, but if I am able to add a command to run manually that would work.
I would just like to make sure that the different devices I am installing this image to get the drivers and updates they need without having to constantly update the image with new drivers/firmware.
The text was updated successfully, but these errors were encountered: