after deploying image - no network driver
-
@robertkwild Yes and yes The setupcomplete.cmd is a windows thing, where winsetup will automatically call that batch file at the end of oobe and just before the login prompt is displayed. It is used for the lite touch method of image deployment. Google that file name to find out the details and its location.
Or just create the batch file and leave it on the administrators desktop and you can manually run it. It doesn’t need to be called setupcomplete.cmd that is only for the unattended install. In my case Once I start FOG’s image deployment I don’t touch the computer until its finished and ready to move to the users work location. It is totally touchless once fog imaging has started.
-
@george1421 is there any way to auto call that batch file after the oobe generalise has finished
bear in mind im not using an unattended.xml answer file
Ok I save it here
%WINDIR%\Setup\Scripts\SetupComplete.cmd
In that setup complete CMD it’s
pnputil.exe /add-driver “C:\Drivers*.inf” /subdirs /install
But how do I get fog to dump the script in there in the first place
-
@robertkwild AFAIK the unattend.xml file and the setupcomplete.cmd files are not connected they can be used independently of each other. I believe the setupcomplete.cmd is a function of sysprep and not unattend.xml. But I can say I use both so I’ve never tried using one without the other.
-
@george1421 ok i feel this won’t work for me as when I captured the image I ran a sysprep without an unattended answer file, so I fear I’m going to have to run the sysprep again this time specifying an answer file
As how do I get Windows or fog to run the script after my oobe generalise
i mean this script
SetupComplete.cmd
pnputil.exe /add-driver “C:\Drivers*.inf” /subdirs /install
-
great thanks @george1421 i understand now, basically to do this right, you need to sysprep using an unattended xml file which i dont do, so best case scenario is i can just leave the drivers there and install once im on the desktop,
thanks again george