Sysprep + script issue

[m3zzr]

Hi All,

I wonder if anyone as any advice on the following:

I have used sysprep to prepare a image ready to deploy to 20 other computers(all same make/model/spec)

The part of the sysprep im having issues with is the run command part (run one time part).

The computers have card readers in which when Windows assigns drive letters tp then conflict with network mapped drives. I have created a Diskpart script that changes the conflicting drive letters to non-conflicting letters and this works fine when manually run from within Windows. However, when I tell sysprep to run the script (batch file) after the user logs in the scrip opens and then closes without completing the drive letter rename. The computer then procedes to create the profile for the user that has just logged in (personalised settings box)

I usually then have to run the script/batch file manually once the users profile has been created.

I have also tried placing the batch file in the Administrators startup menu which is the first user that logs in after sysprep is run... again, the script runs before the personalised settings part of logging the user in and fails.

Is there any way to get the script to run after the Administrator account logs in and the profile is created?

[m3zzr]

I managed to sort this issue. Diskpart script had to be placed in the OEM folder within the Sysprep folder.

[maggi35]

Use Setup Manager (setupmgr.exe) to create the unattended answer file for sysprep. Depending on the version of the deployment tools you are using, the default name of the answer file will either be sysprep.inf or unattended.txt. Save the file as Sysprep.inf and place it in the Sysprep directory at the root of the system drive.

Launch sysprep.exe manually to use a GUI to configure sysprep options or run sysprep from the command-line. This will prepare Windows for the first-run Out-Of-Box-Experience (OOBE).