Task Sequece Configuration vs Sysprep.inf
Hi All,
I have a Windows XP Image (it's a captured reference image). Also I have SCCM 2007 SP2 R2 with MDT.
So, I created a Microsoft Deployment Task Sequence and I selected in Apply Operative System Image the Sysprep.inf
I configured my Task Sequece options Like Organization Name, Product Key, FullName, etc.
But in Sysprep.inf I saw this:
---------------------------------------------------------------------------
[Unattended]
OemSkipEula = Yes
OemPnPDriversPath = "\Drivers\NET"
DriverSigningPolicy = Ignore
ExtendOemPartition = 1
KeepPageFile = 0
UpdateInstalledDrivers = Yes
[GuiRunOnce]
"cscript.exe C:\MININT\Scripts\LiteTouch.wsf /start"
"cscript.exe D:\MININT\Scripts\LiteTouch.wsf /start"
"cscript.exe E:\MININT\Scripts\LiteTouch.wsf /start"
"cscript.exe F:\MININT\Scripts\LiteTouch.wsf /start"
[Networking]
InstallDefaultComponents=Yes
[Display]
BitsPerPel=16
Xresolution=1024
YResolution=768
Vrefresh=60
[TapiLocation]
AreaCode=888
CountryCode=1
; Dialing=Tone
; LongDistanceACcess=9
[RegionalSettings]
LanguageGroup=1
Language=00000409
[GuiUnattended]
AdminPassword=local
OEMSkipWelcome=1
OEMSkipRegional=1
TimeZone=010
AutoLogon="Yes"
AutoLogonCount=999
[Identification]
CreateComputerAccountInDomain=Yes
; JoinDomain=CONTOSO
; MachineObjectOU= "OU=Workstations, dc=contoso, dc=com"
; DomainAdmin=Contoso\Administrator
; DomainAdminPassword=password
[UserData]
ComputerName=*
FullName="Full Name"
OrgName="Organization Name"
ProductKey=XXXXX-YYYYY-ZZZZZ-AAAAA-BBBBB
[URL]
Home_Page=http://www.microsoft.com/
[LicenseFilePrintData]
AutoMode=PerSeat
; AutoUsers=50
[Sysprep]
BuildMassStorageSection = Yes
[SysprepMassStorage]
---------------------------------------------------------------------------
As you can see there is settings for Organization Name, Product Key, FullName, etc, but I had configured on my Task Sequence.
So, What Settings will be applied?
Regards.
October 6th, 2010 5:21am
it will take the settings from your Task Sequence and merge them into your sysprep.inf file, you can verify this during the installation by pressing f8 prior to sysprep being run and viewing the contents of the file
My step by step
SCCM Guides
I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
October 6th, 2010 8:04am
Hi Niall,
Sorry, I'm new with sysprep.inf.
So, you say the Task Sequence Settings will applied over sysprep.inf file, right?
What is the directory to verifiy that?.
Regards.
October 6th, 2010 9:28am
c:\sysprep\sysprep.inf
(the c:\sysprep folder will be automatically deleted after sysprep has run on the deployed machine)
Free Windows Admin Tool Kit Click here and download it now
October 6th, 2010 9:33am
So, how do i verify when Task Sequence Settings merge with sysprep.inf settings (especified in task sequence-apply operating system image)?
Regards.
October 6th, 2010 10:01am
You can view the file during image capture, to see what the Capture task sequense has merged into the sysprep.inf file.
You can also mount the captured .wim file with imagex from Windows AIK (
http://technet.microsoft.com/en-us/library/cc749447(WS.10).aspx ) after capture and view the file from windows explorer.
Or.. you can view the content during the deployment when the task sequense apply the image, before the first reboot. After the first reboot mini-setup runs and the settings from the sysprep.inf are applied, and the sysprep folder is deleted.
You can also choose not to use a sysprep file from the task sequense, but then you need to add a preconfigured sysprep.inf file to the sysprep package.
Free Windows Admin Tool Kit Click here and download it now
October 6th, 2010 10:27am
Hi Henrik,
I already have a captured image (windows XP reference). I want to specified some settings on Sysprep.inf when I deploy my windows xp image.
In task sequence-Applying Operating System Image I specified the Sysprep.inf to be used.
I specified the following section in Syprep.inf:
--------------------------------------------------------------------------------
[Display]
BitsPerPel=16
Xresolution=800
YResolution=600
Vrefresh=60
[NetProtocols]
MS_TCPIP=params.MS_TCPIP
[params.MS_TCPIP]
DNSDomain=localdomain.local
DNSSuffixSearchOrder=localdomain1.local,localdomain2.local,localdomain3.local
-------------------------------------------------------------------------------------
When the task sequence finish I the DISPLAY setting was applied, but the
DNS Suffix Names were not applied.
Is the something wrong?
Regards.
October 6th, 2010 11:09am
the ms_tcpip setting should go in unattend.txt and not in sysprep.inf
that's why it's getting ignored
cheers
niall
My step by step
SCCM Guides
I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
October 6th, 2010 11:20am
Hi Niall,
Please, would you explain me the difference between Sysprep.inf and Unattend.txt?
I´m not sure, but i read in a Post that Sysprep.inf is for deploy custom images (captured images) and Unattend.txt is for deploy new images from scratch.
Regards.
October 6th, 2010 11:26am
I would either use your own sysprep.inf and make shure that that file is present in the c:\sysprep\ folder when you deploy the image (and not set the task sequense to use a syspep.inf)
OR
You can use the "Apply network settings" in the task sequense (at the bottom, click add) to set your DNS
Free Windows Admin Tool Kit Click here and download it now
October 6th, 2010 11:33am
Hi Enrik,
Ok, so for DNS Suffix I can configure it in Task Sequece as you said.
Why you said "not set the task sequense to use a sysprep.inf"?
I think we can use Sysprep.inf for settings that are not available in Task Sequence?
Regards.
October 6th, 2010 11:42am
If you already have a sysprep.inf that you don't want the task sequense to interfear with, you can put it in the image (c:\sysprep\) and "not set the task sequense to use a sysprep.inf"
In that way your own sysprep.inf, that you have put into the .wim image, will be used
But if you want the task sequense to help you insert information into sysprep.inf you
should "set the task sequense to use a sysprep.inf"
Either way sysprep.exe needs a sysprep.inf to install unattended, the question is what information that file holds when sysprep runs.
That's why pressing f8 and take a look at the file before reboot is a good idea.
Free Windows Admin Tool Kit Click here and download it now
October 6th, 2010 12:17pm
Hi,
I configured this in
unattend.txt :
--------------------------------------------------
[NetProtocols]
MS_TCPIP=params.MS_TCPIP
[params.MS_TCPIP]
DNSDomain=localdomain.local
DNSSuffixSearchOrder=localdomain1.local,localdomain2.local,localdomain3.local
-------------------------------------------------
But this didn´t apply,
Is there something Wrong?
Regards.
October 6th, 2010 4:20pm