Just copy that one before reboot in the Setup windows and ConfigMgr step.

With Windows XP, Vista or 7 there will be different files created for using a unattend installation.

All information set in the Task Sequence will be used for creating that specific file.

Only a dynamically computername is missing here How to assign a dynamic computername during OSD, thats the question In a Task Sequence used for OSD, this information can be placed in Apply Windows Settings and Apply Network Settings.

In Apply Windows Settings the following information is (most of times) set: UserOrganization name.

The sysprep.inf file will be createdplaced at C:Sysprep (with the deployment tools).

The unattend.xml will be createdplaced at C:WindowsPantherUnattend.

During above steps (Apply Windows Settings and Apply Network Settings) these files will be generated.

During Setup windows and ConfigMgr these files will be used for having a unattend installation.

Sysprep Set Computer Name How To Set The

The only information missing here is how to set the computername With MDT integration an additional step is used for making that possible.

Then a Task Sequence variable can be used for dynamically assigning a computername.

Most of times I disable both Apply Windows Settings and Apply Network Settings steps in the Task Sequence, and making use of the sysprep.inf andor unattend.xml which is created by ConfigMgr during OSD.

The only change I make then is to replace the Computername with an sign, and create a separate package from this file.

Then I put that file (as package) at the Apply Operating System step.

The package which contains the script (converted to executable) is put in an additional step, in this case: Assettag To Unattend.

Then it works also on Dell devices.

Sysprep Set Computer Name Download And Install

Wilfred Hanekamp for sharing the script) Download and install AutoIt for making changes to this script, and building a executable file from it.

With this script, assigning a dynamic computername is possible, without using MDT integration ConfigMgr rocks again Update 15-11-2011: Because of some comments that the script isnt working I replaced the script with additional values.

Update 16-3-2012: Again I replaced the script with additional values.

I am a little confused by this part though: Most of times I disable both Apply Windows Settings and Apply Network Settings steps in the Task Sequence, and making use of the sysprep.inf andor unattend.xml which is created by ConfigMgr during OSD.

Could you elaborate on this So, you disable the two steps in the TS.

But then, what do you do next Thanks, Reply Delete Replies Reply Henk Hoogendoorn June 27, 2011 at 10:25 PM Hi, its true you can disable both steps in your task sequence.

This because they will be used to create a sysprep.inf or unattend.xml which can be manually created and customized also.

During deployment (when above steps are still enabled) an answer file will be created.

Sysprep Set Computer Name Serial Number