First, it's not the task sequence that launches OOBE, it's Windows Setup that does.

Second, why are you supplying a sysprep.inf at all instead of letting ConfigMgr build one for you? There's nothing special whatsoever about what you have above.

Thank you for your reply Jason. Being new to this I'm reaaly not sure what you mean by "let Config Mgr build one for me."

So given the fact that I do in fact have Windows Setting included in my task sequence, I am still getting the OOBE screens at OS launch??

You don't need to supply a sysprep.inf at all, the task sequence engine will by default create one and use it during task sequence and will populate correctly and with information supplied in the Apply Windows Settings and Apply Network Settings tasks.

I have

• Syspreped a Windows XP Embedded system using Sysprep v2.0 (_quiet -reseal -shutdown)
• Captured the image using Imagex
• Created a task sequence.
• I created a package called "unattend" and then distributed it to the DP (Did not create a program).
• In my O/S I selected "Use an Unattended or Sysprep answer file.
• Selected the package
• File name = sysprep.inf

[Sysprep]

[GuiUnattended]
   OEMDuplicatorString=Microsoft SMS OS Deployment Agent
   OEMSkipRegional=1
   OEMSkipWelcome=1
   TimeZone=085
   AdminPassword=
   EncryptedAdminPassword=NO

[Identification]
   JoinDomain=
   DomainAdmin=
   DomainAdminPassword=
   MachineObjectOU=

[Networking]
   InstallDefaultComponents=yes

[Unattended]
   InstallFilesPath=C:\sysprep\i386
   DriverSigningPolicy=ignore
   UpdateInstalledDrivers=yes
   OemPnPDriversPath="Drivers\LAN;Drivers\Audio;Drivers\Chipset;Drivers\PCI;Drivers\Graphics;Drivers\System Device"
   OEMSkipEula=Yes
   UnattendMode=FullUnattended

[UserData]
   FullName=
   OrgName=
   ProductKey=
   ComputerName=*

[LicenseFilePrintData]

[SysprepMassStorage]

[NetProtocols]
   MS_TCPIP=params.TCPIP

[NetClients]
   MS_MSClient=params.MS_MSClient

[params.MS_MSClient]

[params.TCPIP]
   EnableSecurity=No

[SysprepCleanup]

The Task sequence is still launching OOBE which I assume means that the sysprep.inf file was not read.

Does anyone have any suggestions??

P.S. The entries that have no data have been intentionally o