burnzdog Posted March 13, 2013 Report post Posted March 13, 2013 HI All, Have created a Windows 7 deployment which is all working apart from the machine being added to the domain. Im currently using a unattend.xml file which has the following entered: <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Identification> <Credentials> <Domain>Domain.local</Domain> <Password>PASSWORD</Password> <Username>USERNAME</Username> </Credentials> <MachineObjectOU>OU=WINDOWS&,DC=DOMAIN,DC=local</MachineObjectOU> <JoinDomain>DOMAIN.LOCAL</JoinDomain> </Identification> </component> The unattend is working during the build as the other settings are applied. I have checked the credentials, the OU settings and they are correct. The setact.log from the machine looks like this: 2013-03-13 10:08:29, Info [setup.exe] UnattendSearchExplicitPath: Found unattend file at [C:\WINDOWS\Panther\Unattend\unattend.xml]; examining for applicability. 2013-03-13 10:08:29, Info [setup.exe] UnattendSearchExplicitPath: Found usable unattend file for pass [specialize] at [C:\WINDOWS\Panther\Unattend\unattend.xml]. 2013-03-13 10:08:30, Info IBS Callback_Unattend_InitEngine:Using unattend file found at [C:\WINDOWS\Panther\Unattend\unattend.xml]. 2013-03-13 10:08:30, Info [setup.exe] ValidateSMIPass: serialized settings stream; status 0x00000000 2013-03-13 10:08:30, Info [setup.exe] ValidateSMIPass: construct settings context; status 0x00000000 2013-03-13 10:08:30, Info [setup.exe] ValidateSMIPass: load SMI settings; status 0x00000000 2013-03-13 10:08:30, Info [0x0600c0] IBS Callback_Unattend_InitEngine:Successfully deserialized and validated unattend file [C:\WINDOWS\Panther\Unattend\unattend.xml]. 2013-03-13 10:08:30, Info [0x0604d4] IBS Callback_ConfigSetProcessUnattend: UseConfigurationSet is false. 2013-03-13 10:08:30, Info DIAG Callback_Diagnostic_Unattend: Setup was started from Phase 4. Disabling Diagnostics [ ProcessUnattend ] in this scenario 2013-03-13 10:08:30, Info [0x064047] IBSLIB MarkUnattendSettingAsProcessed: Marking unattend setting [ProductKey\ProductKey] as processed. 2013-03-13 10:08:30, Info [0x064047] IBSLIB MarkUnattendSettingAsProcessed: Marking unattend setting [userData\ComputerName] as processed. 2013-03-13 10:08:30, Info [0x064047] IBSLIB MarkUnattendSettingAsProcessed: Marking unattend setting [setupUI\SkipEula] as processed. 2013-03-13 10:08:30, Info [0x064047] IBSLIB MarkUnattendSettingAsProcessed: Marking unattend setting [PrepareDisks] as processed. 2013-03-13 10:08:30, Info [0x064047] IBSLIB MarkUnattendSettingAsProcessed: Marking unattend setting [LangPacks] as processed. 2013-03-13 10:08:30, Info [0x060590] IBS CallBack_LanguagePacks_Unattend:Unattend already processed. 2013-03-13 10:08:30, Info PnPIBS: Entering PnP callback to validate unattend.xml settings for component Microsoft-Windows-PnPCustomizationsWinPE ... 2013-03-13 10:08:30, Info PnPIBS: Unattend settings need not be processed. Nothing more to be done here! 2013-03-13 10:08:30, Info [0x064047] IBSLIB MarkUnattendSettingAsProcessed: Marking unattend setting [setupComplianceCheck] as processed. 2013-03-13 10:08:30, Info [0x064047] IBSLIB MarkUnattendSettingAsProcessed: Marking unattend setting [RegionalSettings] as processed. 2013-03-13 10:08:30, Info [0x0605fb] IBS Callback_Locale_ProcessUnattendSettings: Layered Driver from downlevel system [1] 2013-03-13 10:08:30, Info IBS CallBack_Unattend_InitiatePass: Initiating unattend settings pass [specialize] 2013-03-13 10:08:30, Info [setup.exe] Current pass status for [specialize] is [0x0] 2013-03-13 10:08:30, Info [setup.exe] Applying data-only settings overrides using SMI... 2013-03-13 10:08:31, Info CSI 00000001@2013/3/13:10:08:31.109 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fefa86e94d @0x7fef7179480 @0x7fef7193ec6 @0x7fef7165478 @0x7fef71643c7 @0x7fefbadba2b) 2013-03-13 10:08:31, Info [setup.exe] Successfully applied data-only settings overrides. 2013-03-13 10:08:31, Info [setup.exe] Calling into RunSMIActionPass to execute unattend GCs for pass [specialize] 2013-03-13 10:08:31, Info [setup.exe] [Action Queue] : GenerateActionQueue begin 2013-03-13 10:08:31, Info [setup.exe] [Action Queue] : Processing pass = specialize 2013-03-13 10:08:31, Info [setup.exe] [Action Queue] : Generating queue file to C:\WINDOWS\panther\actionqueue\specialize.uaq 2013-03-13 10:08:31, Info [setup.exe] [Action Queue] : Identity 0: Microsoft-Windows-Shell-Setup, Culture=neutral, Version=6.1.7601.17514, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS 2013-03-13 10:08:31, Info [setup.exe] [Action Queue] : Identity 1: Microsoft-Windows-UnattendedJoin, Culture=neutral, Version=6.1.7601.17514, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS 2013-03-13 10:08:31, Info [setup.exe] [Action Queue] : Identity 2: Microsoft-Windows-Deployment, Culture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS 2013-03-13 10:08:31, Info [setup.exe] [Action Queue] : Using component order file C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\GlobalInstallOrder.xml 2013-03-13 10:08:31, Info CSI 00000001@2013/3/13:10:08:31.187 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fefa86e94d @0x7fef7aa0920 @0x7fef7a9f9f0 @0x7fef7a9f7f5 @0x7fefbadb504 @0x7fefbadacea) 2013-03-13 10:08:31, Info [setup.exe] [Action Queue] : Found manifest file C:\WINDOWS\Winsxs\Manifests\x86_microsoft-windows-shell-setup_31bf3856ad364e35_6.1.7601.17514_none_d4623c9747e247a7.manifest 2013-03-13 10:08:31, Info [setup.exe] [Action Queue] : Found manifest file C:\WINDOWS\Winsxs\Manifests\amd64_microsoft-windows-unattendedjoin_31bf3856ad364e35_6.1.7601.17514_none_113aea0e8374286d.manifest 2013-03-13 10:08:31, Info [setup.exe] [Action Queue] : Found manifest file C:\WINDOWS\Winsxs\Manifests\amd64_microsoft-windows-deployment_31bf3856ad364e35_6.1.7600.16385_none_57e3e87206ff08ca.manifest 2013-03-13 10:08:31, Info [setup.exe] [Action Queue] : GenerateActionQueue finish (hr = 0x0) 2013-03-13 10:08:31, Info [setup.exe] [Action Queue] : ProcessActionQueue start 2013-03-13 10:08:31, Info [setup.exe] [Action Queue] : ProcessActionQueue using queue file C:\WINDOWS\panther\actionqueue\specialize.uaq 2013-03-13 10:08:31, Info [setup.exe] [Action Queue] : Command Line = C:\WINDOWS\SYSWOW64\RUNDLL32.EXE / arguments = shsetup.dll,SHUnattendedSetup / pass = specialize / manifest path = C:\WINDOWS\Winsxs\Manifests\x86_microsoft-windows-shell-setup_31bf3856ad364e35_6.1.7601.17514_none_d4623c9747e247a7.manifest 2013-03-13 10:08:31, Info [setup.exe] [Action Queue] : Command Line = C:\WINDOWS\SYSTEM32\DJOIN.EXE / arguments = / pass = specialize / manifest path = C:\WINDOWS\Winsxs\Manifests\amd64_microsoft-windows-unattendedjoin_31bf3856ad364e35_6.1.7601.17514_none_113aea0e8374286d.manifest 2013-03-13 10:08:31, Info [setup.exe] [Action Queue] : Command Line = C:\WINDOWS\SYSTEM32\SETUPUGC.EXE / arguments = / pass = specialize / manifest path = C:\WINDOWS\Winsxs\Manifests\amd64_microsoft-windows-deployment_31bf3856ad364e35_6.1.7600.16385_none_57e3e87206ff08ca.manifest 2013-03-13 10:08:31, Info [setup.exe] [Action Queue] : Executing command "C:\WINDOWS\SYSWOW64\RUNDLL32.EXE" shsetup.dll,SHUnattendedSetup specialize 2013-03-13 10:08:32, Info [setup.exe] [Action Queue] : process exit code = 0 2013-03-13 10:08:32, Info [setup.exe] [Action Queue] : Unattend action returned operation complete. 2013-03-13 10:08:32, Info [setup.exe] [Action Queue] : Executing command "C:\WINDOWS\SYSTEM32\DJOIN.EXE" specialize 2013-03-13 10:08:33, Info [setup.exe] [Action Queue] : process exit code = 1 2013-03-13 10:08:33, Info [setup.exe] [Action Queue] : Unattend action requested delayed reboot. 2013-03-13 10:08:33, Info [setup.exe] [Action Queue] : Executing command "C:\WINDOWS\SYSTEM32\SETUPUGC.EXE" specialize 2013-03-13 10:08:33, Info [setup.exe] [Action Queue] : process exit code = 0 2013-03-13 10:08:33, Info [setup.exe] [Action Queue] : Unattend action returned operation complete. 2013-03-13 10:08:33, Info [setup.exe] [Action Queue] : ProcessActionQueue finish (hr = 0x1f1000) 2013-03-13 10:08:33, Info [setup.exe] One or more unattend GCs requested a delayed reboot; we will reboot the computer 2013-03-13 10:08:33, Info [0x0606cc] IBS Flushing registry to disk... 2013-03-13 10:08:35, Info [0x0606cc] IBS Flush took 2219 As part of the build its prompts for name of the machine which I was hoping when its gets added to the domain it will use this. Any ideas appreciated... Thanks. Matt Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted March 13, 2013 Report post Posted March 13, 2013 Is the user USERNAME a member of domain admins? Also is it not possible in 2007 to simply specify these settings on the task sequence itself without having to add these settings on an answerfile? Quote Share this post Link to post Share on other sites More sharing options...
Jorgen Nilsson Posted March 14, 2013 Report post Posted March 14, 2013 HI,The SCCM 2007 OSD deployment will overwrite the Changes you make in the unattend.xml file so you should really use the Apply Network settings step. Regards,Jörgen Quote Share this post Link to post Share on other sites More sharing options...
burnzdog Posted March 14, 2013 Report post Posted March 14, 2013 User account is correct. I have disabled the "apply network settings" for this very reason. I would use this stage because it does add the machine to the domain, but I cannot change the computer name it just adds it the machine with a randomly generated name. My answer file prompts me during the build for the machine but this is ignored of the machine is later added to the domain by the "apply network settings" sequence. Any ideas? Quote Share this post Link to post Share on other sites More sharing options...
mogwuy Posted March 15, 2013 Report post Posted March 15, 2013 I had this issue myself, it turned out to be two simple things 1.) Make sure username and password are correct that the username is part of the domain admin group and 2.) Make sure you have the machine actually connected to the network Quote Share this post Link to post Share on other sites More sharing options...