Jump to content


nandystam

OSD Task Sequence fails to complete, but does not report an error

Recommended Posts

Hi all

The problem I am facing with OSD is basically a carbon copy of this.

The OSD task begins, downloads and applies the Windows 7 Pro SP1 OS image, downloads and installs some drivers (as per the task sequence), but when it goes to the task to Setup Windows and ConfigMgr, it never completes the install of the SCCM client. It reboots, configures some drivers and then goes to the usual CTRL-ALT-DEL login prompt, and is joined to the domain. Any tasks after Setup Windows and ConfigMgr never run, it just seems to exit the task silently without generating an error.

There is only an smsts.log file in C:\_SMSTaskSequence\Logs\. An excerpt is below (the last line is the actual end of the log):

VerifyContentHash: Hash algorithm is 32780	OSDSetupHook	27/07/2018 2:03:54 PM	1080 (0x0438)
c:\_smstasksequence\packages\brw00069\i386 is a directory. Setting directory security	OSDSetupHook	27/07/2018 2:03:56 PM	1080 (0x0438)
c:\_smstasksequence\packages\brw00069\x64 is a directory. Setting directory security	OSDSetupHook	27/07/2018 2:03:56 PM	1080 (0x0438)
c:\_smstasksequence\packages\brw00069\i386\clientupdate is a directory. Setting directory security	OSDSetupHook	27/07/2018 2:03:59 PM	1080 (0x0438)
c:\_smstasksequence\packages\brw00069\i386\languagepack is a directory. Setting directory security	OSDSetupHook	27/07/2018 2:03:59 PM	1080 (0x0438)
c:\_smstasksequence\packages\brw00069\x64\clientupdate is a directory. Setting directory security	OSDSetupHook	27/07/2018 2:04:02 PM	1080 (0x0438)
c:\_smstasksequence\packages\brw00069\x64\languagepack is a directory. Setting directory security	OSDSetupHook	27/07/2018 2:04:02 PM	1080 (0x0438)
Content successfully downloaded at C:\_SMSTaskSequence\Packages\BRW00069.	OSDSetupHook	27/07/2018 2:04:02 PM	1080 (0x0438)
Copying SMS client package source from "C:\_SMSTaskSequence\Packages\BRW00069" to "C:\_SMSTaskSequence\OSD\BRW00069".	OSDSetupHook	27/07/2018 2:04:02 PM	1080 (0x0438)
Locating architecture-specific OSDGina.dll	OSDSetupHook	27/07/2018 2:04:03 PM	1080 (0x0438)
Successfully copied file OSDSETUPHOOK.EXE to C:\Windows\SYSTEM32	OSDSetupHook	27/07/2018 2:04:03 PM	1080 (0x0438)
Successfully copied file TSProgressUI.exe to C:\Windows\SYSTEM32\_SMSOSDSetup	OSDSetupHook	27/07/2018 2:04:03 PM	1080 (0x0438)
Successfully copied file tsres.dll to C:\Windows\SYSTEM32\_SMSOSDSetup\1033	OSDSetupHook	27/07/2018 2:04:03 PM	1080 (0x0438)
Saving desktop wallpaper information.	OSDSetupHook	27/07/2018 2:04:03 PM	1080 (0x0438)
ReleaseSource() for C:\_SMSTaskSequence\Packages\BRW00069.	OSDSetupHook	27/07/2018 2:04:03 PM	1080 (0x0438)
reference count 1 for the source C:\_SMSTaskSequence\Packages\BRW00069 before releasing	OSDSetupHook	27/07/2018 2:04:03 PM	1080 (0x0438)
Released the resolved source C:\_SMSTaskSequence\Packages\BRW00069	OSDSetupHook	27/07/2018 2:04:03 PM	1080 (0x0438)
Exiting ConfigureEx: 0x00000000	OSDSetupHook	27/07/2018 2:04:03 PM	1080 (0x0438)
Process completed with exit code 0	OSDSetupWindows	27/07/2018 2:04:03 PM	1068 (0x042C)
Installing hook to 'C:\Windows'	OSDSetupWindows	27/07/2018 2:04:03 PM	1068 (0x042C)
Command line for extension .EXE is "%1" %*	OSDSetupWindows	27/07/2018 2:04:03 PM	1068 (0x042C)
Set command line: "X:\sms\bin\x64\OSDSETUPHOOK.EXE" "/install:C:\Windows" /version:6.1	OSDSetupWindows	27/07/2018 2:04:03 PM	1068 (0x042C)
Executing command line: "X:\sms\bin\x64\OSDSETUPHOOK.EXE" "/install:C:\Windows" /version:6.1	OSDSetupWindows	27/07/2018 2:04:03 PM	1068 (0x042C)
Installing OSD setup hook	OSDSetupHook	27/07/2018 2:04:03 PM	1396 (0x0574)
Setup hook install completed successfully	OSDSetupHook	27/07/2018 2:04:03 PM	1396 (0x0574)
Process completed with exit code 0	OSDSetupWindows	27/07/2018 2:04:03 PM	1068 (0x042C)
OfflineRegistry::Init("C:\Windows")	OSDSetupWindows	27/07/2018 2:04:03 PM	1068 (0x042C)
Loading offline registry hive "C:\Windows\system32\config\software" into HKLM\OfflineRegistry1	OSDSetupWindows	27/07/2018 2:04:03 PM	1068 (0x042C)
Loading offline registry hive "C:\Windows\system32\config\system" into HKLM\OfflineRegistry2	OSDSetupWindows	27/07/2018 2:04:04 PM	1068 (0x042C)
CurrentControlSet is mapped to ControlSet001	OSDSetupWindows	27/07/2018 2:04:05 PM	1068 (0x042C)
SMS Client is not installed	OSDSetupWindows	27/07/2018 2:04:05 PM	1068 (0x042C)
Unloading offline SOFTWARE registry hive	OSDSetupWindows	27/07/2018 2:04:05 PM	1068 (0x042C)
Unloading offline SYSTEM registry hive	OSDSetupWindows	27/07/2018 2:04:05 PM	1068 (0x042C)
Exiting with code 0x00000000	OSDSetupWindows	27/07/2018 2:04:05 PM	1068 (0x042C)
Process completed with exit code 0	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
!--------------------------------------------------------------------------------------------!	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Successfully completed the action (Setup Windows and ConfigMgr) with the exit win32 code 0	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
MP server http://sccm.server.local. Ports 80,443. CRL=false.	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Setting authenticator	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Set authenticator in transport	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Sending StatusMessage	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Setting message signatures.	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Setting the authenticator.	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
CLibSMSMessageWinHttpTransport::Send: WinHttpOpenRequest - URL: sccm.server.local:80  CCM_POST /ccm_system/request	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Request was successful.	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Set a global environment variable _SMSTSLastActionRetCode=0	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Set a global environment variable _SMSTSLastActionSucceeded=true	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Expand a string: %_SMSTSMDataPath%\Logs	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Clear local default environment	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
The action (Setup Windows and ConfigMgr) requested a retry	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Reboot to local harddisk	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
_OSDGinaIsConfigured variable set to TRUE	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
_SMSTSServiceStartType variable set to 	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Created volatile registry entry for pending reboot initiated by this task sequence	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Command line for extension .exe is "%1" %*	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Set command line: "bcdedit.exe"	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Executing command line: "bcdedit.exe"	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Process completed with exit code 0	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Calling RebootSystem()	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
TSUEFIDrive: 	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
OSD type of task sequence. ignore the service window setting	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Updated security on object S:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Path variable OSDisk converted from C: to 4D0F7E130000F01500000000:	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Updated security on object C:\_SMSTaskSequence.	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Set a global environment variable _SMSTSNextInstructionPointer=7	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Set a TS execution environment variable _SMSTSNextInstructionPointer=7	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Set a global environment variable _SMSTSInstructionStackString=	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Set a TS execution environment variable _SMSTSInstructionStackString=	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Save the current environment block	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)
Expand a string: %_SMSTSMDataPath%\Logs	TSManager	27/07/2018 2:04:05 PM	1328 (0x0530)

I can see in the logs that is says "SMS Client is not installed    OSDSetupWindows    27/07/2018 2:04:05 PM    1068 (0x042C)", but it doesn't say why, and there are no ccmsetup.log files to try and locate a root cause. 

I've updated SCCM to the latest version (with hotfixes), tried the OSD Task Sequence with different clients and boot images (as per the suggested solution in the link) but the result is always the same. I did not create the image (this was done by someone else), but there was no problem capturing it using the standard capture media tools. I did note Windows was not activated at the time of capturing but I don't believe this would be an issue otherwise sysprep would not have succeeded?

Other OSD Tasks for other OS images complete successfully so I am really out of ideas - unless the actual image itself is somehow bad? I did check the HDD of source PC used to create the image and there were no SMART warnings or read errors from a surface scan. 

Any help would be greatly appreciated as it's doing my head in... Thanks 🙂

 

Share this post


Link to post
Share on other sites


You could also check the deployment for errors in the SCCM console.

First, get the deployment ID of the deployment:

Go to the task sequence (Software Library -> Operating Systems -> Task Sequences)

Open the Deployments tab. Make sure the Deployment ID is enabled by rightclicking the columns)

Next:

Open Monitoring -> System Status -> Status Message Queries

Open 'All Status Messages for a Specific Deployment at a Specific Site'.

Fill out the Deployment ID, the Sitecode and the period to search (1hr or 6hrs should be OK).

Hopefully you can find the error here which is troubling you right now.

 

Share this post


Link to post
Share on other sites
Severity	Type	Site code	Date / Time	System	Component	Message ID	Description
Information	Milestone	BRW	31/07/2018 11:40:31 AM	TESTVM	Task Sequence Engine	11142	The task sequence execution engine performed a system reboot initiated by the action (Setup Windows and ConfigMgr) in the group ().
Information	Milestone	BRW	31/07/2018 11:39:30 AM	TESTVM	Task Sequence Engine	11134	The task sequence execution engine successfully completed the action (Setup Windows and ConfigMgr) in the group () with exit code 0  Action output: ... BRW00069. reference count 1 for the source C:\_SMSTaskSequence\Packages\BRW00069 before releasing Released the resolved source C:\_SMSTaskSequence\Packages\BRW00069 Exiting ConfigureEx: 0x00000000 Process completed with exit code 0 Installing hook to 'C:\Windows' Command line for extension .EXE is "%1" %* Set command line: "X:\sms\bin\x64\OSDSETUPHOOK.EXE" "/install:C:\Windows" /version:6.1 Executing command line: "X:\sms\bin\x64\OSDSETUPHOOK.EXE" "/install:C:\Windows" /version:6.1 InstallingOSD setup hook Setup hook install completed successfully Process completed with exit code 0 OfflineRegistry::Init("C:\Windows") Loading offline registry hive "C:\Windows\system32\config\software" into HKLM\OfflineRegistry1 Loading offline registry hive "C:\Windows\system32\config\system" into HKLM\OfflineRegistry2 CurrentControlSet is mapped to ControlSet001 SMS Client is not installed Unloading offline SOFTWARE registry hive Unloading offline SYSTEM registry hive Exiting with code 0x00000000.
Information	Milestone	BRW	31/07/2018 11:39:03 AM	TESTVM	Task Sequence Engine	11134	The task sequence execution engine successfully completed the action (Apply Driver Package) in the group () with exit code 0  Action output: ...  completed with exit code 0 Dism successfully added drivers to the offline driver store. Successfully added "C:\_SMSTaskSequence\Packages\BRW00007\BCA7F059-7059-40DF-9464-453C2D9AC9F6" to the Windows driver store. Adding "C:\_SMSTaskSequence\Packages\BRW00007\DC16F376-26B8-4F53-8F73-8AA3CF5FC27A" to Windows driver store. Setting %SystemRoot% to "C:\Windows" GImage Version: 6.1.7601.23505  The operation completed successfully. Process completed with exit code 0 Dism successfully added driversto the offline driver store. Successfully added "C:\_SMSTaskSequence\Packages\BRW00007\DC16F376-26B8-4F53-8F73-8AA3CF5FC27A" to the Windows driver store. Successfully got a list of drivers to apply from the driver package "BRW00007" and installed them.ReleaseSource() for C:\_SMSTaskSequence\Packages\BRW00007. reference count 1 for the source C:\_SMSTaskSequence\Packages\BRW00007 before releasing Released the resolved source C:\_SMSTaskSequence\Packages\BRW00007 Exiting with return code 0x00000000.
Information	Milestone	BRW	31/07/2018 11:38:24 AM	TESTVM	Task Sequence Engine	11134	The task sequence execution engine successfully completed the action (Apply Network Settings) in the group () with exit code 0  Action output: ==============================[ OSDNetSettings.exe ]=========================== Command line: "osdnetsettings.exe" configure Setting %SystemRoot% to "C:\Windows" Loading existing answer file "C:\Windows\panther\unattend\unattend.xml" Configuring global network settings Join type: 0 Joining domain: sccm.local Getting namespace "Microsoft-Windows-UnattendedJoin" for architecture "amd64" DNS domain:  DNS domain search order:  IP filter sec enabled: false No adapters found in environment.  Performing global configuration only. Writing configuration information to C:\Windows\panther\unattend\unattend.xml Successfully saved configuration information to C:\Windows\panther\unattend\unattend.xml Configuring "OSDNetSettings.exe finalize" to run on first boot OSDNetSettings finished: 0x00000000.
Information	Milestone	BRW	31/07/2018 11:38:24 AM	TESTVM	Task Sequence Engine	11134	The task sequence execution engine successfully completed the action (Apply Windows Settings) in the group () with exit code 0  Action output: ============================[ OSDWinSettings.exe ]============================ Command line: "osdwinsettings.exe" /config Setting %SystemRoot% to "C:\Windows" Loading existing answer file "C:\Windows\panther\unattend\unattend.xml" Computer Name: TESTVM Getting namespace "Microsoft-Windows-Shell-Setup" for architecture "amd64" Registered Owner: XYZ Getting namespace "Microsoft-Windows-Shell-Setup" for architecture "amd64" Registered Organization: ABC Time Zone: AUS Eastern Standard Time Time zone: AUS Eastern Standard Time Setting product key. Generating random administrator password. Setting local admin password. Writing configuration information to C:\Windows\panther\unattend\unattend.xml Successfully saved configuration information to C:\Windows\panther\unattend\unattend.xml Exiting with return code 0x00000000.
Information	Milestone	BRW	31/07/2018 11:38:22 AM	TESTVM	Task Sequence Engine	11134	The task sequence execution engine successfully completed the action (Apply Operating System Image) in the group () with exit code 0  Action output: ... ). m_oOfflineRegistry.OpenKey( pszRegistryKey, uAccess, keyReg ), HRESULT=80070002 (..\offlineos.cpp,789) Creating new Windows Update SubKey on target system Unloading offline SOFTWARE registry hive Unloading offline SYSTEM registry hive Setting%SystemRoot% to "C:\Windows" Getting namespace "Microsoft-Windows-Deployment" for architecture "amd64" Getting namespace "Microsoft-Windows-Shell-Setup" for architecture "amd64" Getting namespace "Microsoft-Windows-International-Core" for architecture"amd64" Writing configuration information to C:\Windows\panther\unattend\unattend.xml Successfully saved configuration information to C:\Windows\panther\unattend\unattend.xml Image installation completed successfully. Closing image file C:\_SMSTaskSequence\Packages\BRW0005F\image-v1.wim ReleaseSource() for C:\_SMSTaskSequence\Packages\BRW0005F. reference count 1 for the source C:\_SMSTaskSequence\Packages\BRW0005F before releasing Released the resolved source C:\_SMSTaskSequence\Packages\BRW0005F.
Information	Milestone	BRW	31/07/2018 11:19:18 AM	TESTVM	Task Sequence Engine	11134	The task sequence execution engine successfully completed the action (Set OSDPreserveDriveLetter Variable) in the group () with exit code 0  Action output: Finished with error code 0.
Information	Milestone	BRW	31/07/2018 11:19:18 AM	TESTVM	Task Sequence Engine	11134	The task sequence execution engine successfully completed the action (Format and Partition Disk) in the group () with exit code 0  Action output: ... ve: A: Adding logical drive: C: Skipping non-local logical drive: E: Adding logical drive: S: Skipping non-local logical drive: X: Formatting drive C: with NTFS filesystem, method quick Creating instance of service loader Loading service Waiting for service to initialize Querying for software providers Found a VDS software provider Querying for IVdsSwProvider Querying for packs Found a VDS pack Querying for IVdsPack Querying for volumes Found a VDS software provider Querying for IVdsSwProvider Querying for packs Found a VDS pack Querying for IVdsPack Querying for volumes Found a VDS volume Querying for IVdsVolumeMF Querying for access paths Found a VDS pack Querying for IVdsPack Querying for volumes Found a VDS volume Querying for IVdsVolumeMF Querying for access paths Found a VDS volume Querying for IVdsVolumeMF Querying for access paths Found a volume with access path 'C:\' Querying for IVdsVolume Querying for IVdsVolumeMF OSDDiskPart.exe completed successfully.
Information	Milestone	BRW	31/07/2018 11:19:07 AM	TESTVM	Task Sequence Engine	11140	The task sequence execution engine started execution of a task sequence.
Information	Milestone	BRW	31/07/2018 11:17:45 AM	TESTVM	Task Sequence Engine	11142	The task sequence execution engine performed a system reboot initiated by the action (Restart Computer) in the group ().
Information	Milestone	BRW	31/07/2018 11:15:48 AM	TESTVM	Task Sequence Engine	11134	The task sequence execution engine successfully completed the action (Restart Computer) in the group () with exit code 0  Action output: ========================= [ smsboot.exe ] ========================= Command line: '"smsboot.exe" /target:WinPE' SMSTSRebootDelay=60 SMSTSRebootMessage=A new Microsoft Windows operating system is being installed. The computer must restart to continue.SMSTSRebootRequested=WinPE.
Information	Milestone	BRW	31/07/2018 11:15:48 AM	TESTVM	Task Sequence Engine	11144	The task sequence execution engine from a non-client started execution of a task sequence.
Information	Milestone	BRW	31/07/2018 11:15:48 AM	TESTVM	Task Sequence Engine	11140	The task sequence execution engine started execution of a task sequence.
Information	Milestone	BRW	31/07/2018 11:12:59 AM	sccm.server.local	SMS_OFFER_MANAGER	3900	SMS Offer Manager successfully processed new deployment DeployHESTAImage(dev)_BRW00061_VirtualMachines.
Information	Audit	BRW	31/07/2018 11:12:47 AM	sccm.server.local	Microsoft.ConfigurationManagement.exe	30006	User "DOMAIN\sccmadmin" created a deployment named "DeployHESTAImage(dev)_BRW00061_VirtualMachines" (BRW200D4) deploying program "*".

Sadly I don't think this reveals anything new? 😥

Share this post


Link to post
Share on other sites

Does the reboot after the 'Setup Windows and ConfigMgr' step go to the default installed OS or back to the boot image?
What happens if you disable the reboot step?

Can you post a screenshot of the task sequence steps?

Share this post


Link to post
Share on other sites

I've attached the task sequence steps. The reboot after 'Setup Windows and ConfigMgr' setups some drivers and so on, reboots again, and then goes to the default installed OS. The SCCM client is never installed. In essence the 'Setup Windows and ConfigMgr' task never really completes... 

Appreciate your help on this so far 😃

 

Share this post


Link to post
Share on other sites

Same result it seems:

VerifyContentHash: Hash algorithm is 32780	OSDSetupHook	1/08/2018 9:53:42 AM	1356 (0x054C)
c:\_smstasksequence\packages\brw00069\i386 is a directory. Setting directory security	OSDSetupHook	1/08/2018 9:53:44 AM	1356 (0x054C)
c:\_smstasksequence\packages\brw00069\x64 is a directory. Setting directory security	OSDSetupHook	1/08/2018 9:53:44 AM	1356 (0x054C)
c:\_smstasksequence\packages\brw00069\i386\clientupdate is a directory. Setting directory security	OSDSetupHook	1/08/2018 9:53:48 AM	1356 (0x054C)
c:\_smstasksequence\packages\brw00069\i386\languagepack is a directory. Setting directory security	OSDSetupHook	1/08/2018 9:53:48 AM	1356 (0x054C)
c:\_smstasksequence\packages\brw00069\x64\clientupdate is a directory. Setting directory security	OSDSetupHook	1/08/2018 9:53:51 AM	1356 (0x054C)
c:\_smstasksequence\packages\brw00069\x64\languagepack is a directory. Setting directory security	OSDSetupHook	1/08/2018 9:53:51 AM	1356 (0x054C)
Content successfully downloaded at C:\_SMSTaskSequence\Packages\BRW00069.	OSDSetupHook	1/08/2018 9:53:51 AM	1356 (0x054C)
Copying SMS client package source from "C:\_SMSTaskSequence\Packages\BRW00069" to "C:\_SMSTaskSequence\OSD\BRW00069".	OSDSetupHook	1/08/2018 9:53:51 AM	1356 (0x054C)
Locating architecture-specific OSDGina.dll	OSDSetupHook	1/08/2018 9:53:52 AM	1356 (0x054C)
Successfully copied file OSDSETUPHOOK.EXE to C:\Windows\SYSTEM32	OSDSetupHook	1/08/2018 9:53:52 AM	1356 (0x054C)
Successfully copied file TSProgressUI.exe to C:\Windows\SYSTEM32\_SMSOSDSetup	OSDSetupHook	1/08/2018 9:53:53 AM	1356 (0x054C)
Successfully copied file tsres.dll to C:\Windows\SYSTEM32\_SMSOSDSetup\1033	OSDSetupHook	1/08/2018 9:53:53 AM	1356 (0x054C)
Saving desktop wallpaper information.	OSDSetupHook	1/08/2018 9:53:53 AM	1356 (0x054C)
ReleaseSource() for C:\_SMSTaskSequence\Packages\BRW00069.	OSDSetupHook	1/08/2018 9:53:53 AM	1356 (0x054C)
reference count 1 for the source C:\_SMSTaskSequence\Packages\BRW00069 before releasing	OSDSetupHook	1/08/2018 9:53:53 AM	1356 (0x054C)
Released the resolved source C:\_SMSTaskSequence\Packages\BRW00069	OSDSetupHook	1/08/2018 9:53:53 AM	1356 (0x054C)
Exiting ConfigureEx: 0x00000000	OSDSetupHook	1/08/2018 9:53:53 AM	1356 (0x054C)
Process completed with exit code 0	OSDSetupWindows	1/08/2018 9:53:53 AM	1088 (0x0440)
Installing hook to 'C:\Windows'	OSDSetupWindows	1/08/2018 9:53:53 AM	1088 (0x0440)
Command line for extension .EXE is "%1" %*	OSDSetupWindows	1/08/2018 9:53:53 AM	1088 (0x0440)
Set command line: "X:\sms\bin\x64\OSDSETUPHOOK.EXE" "/install:C:\Windows" /version:6.1	OSDSetupWindows	1/08/2018 9:53:53 AM	1088 (0x0440)
Executing command line: "X:\sms\bin\x64\OSDSETUPHOOK.EXE" "/install:C:\Windows" /version:6.1	OSDSetupWindows	1/08/2018 9:53:53 AM	1088 (0x0440)
Installing OSD setup hook	OSDSetupHook	1/08/2018 9:53:53 AM	220 (0x00DC)
Setup hook install completed successfully	OSDSetupHook	1/08/2018 9:53:53 AM	220 (0x00DC)
Process completed with exit code 0	OSDSetupWindows	1/08/2018 9:53:53 AM	1088 (0x0440)
OfflineRegistry::Init("C:\Windows")	OSDSetupWindows	1/08/2018 9:53:53 AM	1088 (0x0440)
Loading offline registry hive "C:\Windows\system32\config\software" into HKLM\OfflineRegistry1	OSDSetupWindows	1/08/2018 9:53:53 AM	1088 (0x0440)
Loading offline registry hive "C:\Windows\system32\config\system" into HKLM\OfflineRegistry2	OSDSetupWindows	1/08/2018 9:53:54 AM	1088 (0x0440)
CurrentControlSet is mapped to ControlSet001	OSDSetupWindows	1/08/2018 9:53:54 AM	1088 (0x0440)
SMS Client is not installed	OSDSetupWindows	1/08/2018 9:53:54 AM	1088 (0x0440)
Unloading offline SOFTWARE registry hive	OSDSetupWindows	1/08/2018 9:53:54 AM	1088 (0x0440)
Unloading offline SYSTEM registry hive	OSDSetupWindows	1/08/2018 9:53:54 AM	1088 (0x0440)
Exiting with code 0x00000000	OSDSetupWindows	1/08/2018 9:53:54 AM	1088 (0x0440)
Process completed with exit code 0	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
!--------------------------------------------------------------------------------------------!	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
Successfully completed the action (Setup Windows and ConfigMgr) with the exit win32 code 0	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
MP server http://sccm.server.local. Ports 80,443. CRL=false.	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
Setting authenticator	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
Set authenticator in transport	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
Sending StatusMessage	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
Setting message signatures.	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
Setting the authenticator.	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
CLibSMSMessageWinHttpTransport::Send: WinHttpOpenRequest - URL: sccm.server.local:80  CCM_POST /ccm_system/request	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
Request was successful.	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
Set a global environment variable _SMSTSLastActionRetCode=0	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
Set a global environment variable _SMSTSLastActionSucceeded=true	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
Expand a string: %_SMSTSMDataPath%\Logs	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
Clear local default environment	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
The action (Setup Windows and ConfigMgr) requested a retry	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
Reboot to local harddisk	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
_OSDGinaIsConfigured variable set to TRUE	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
_SMSTSServiceStartType variable set to 	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
Created volatile registry entry for pending reboot initiated by this task sequence	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
Command line for extension .exe is "%1" %*	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
Set command line: "bcdedit.exe"	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
Executing command line: "bcdedit.exe"	TSManager	1/08/2018 9:53:54 AM	1372 (0x055C)
Process completed with exit code 0	TSManager	1/08/2018 9:53:55 AM	1372 (0x055C)
Calling RebootSystem()	TSManager	1/08/2018 9:53:55 AM	1372 (0x055C)
TSUEFIDrive: 	TSManager	1/08/2018 9:53:55 AM	1372 (0x055C)
OSD type of task sequence. ignore the service window setting	TSManager	1/08/2018 9:53:55 AM	1372 (0x055C)
Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.	TSManager	1/08/2018 9:53:55 AM	1372 (0x055C)
Updated security on object S:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.	TSManager	1/08/2018 9:53:55 AM	1372 (0x055C)
Path variable OSDisk converted from C: to ACE832210000F01500000000:	TSManager	1/08/2018 9:53:55 AM	1372 (0x055C)
Updated security on object C:\_SMSTaskSequence.	TSManager	1/08/2018 9:53:55 AM	1372 (0x055C)
Set a global environment variable _SMSTSNextInstructionPointer=7	TSManager	1/08/2018 9:53:55 AM	1372 (0x055C)
Set a TS execution environment variable _SMSTSNextInstructionPointer=7	TSManager	1/08/2018 9:53:55 AM	1372 (0x055C)
Set a global environment variable _SMSTSInstructionStackString=	TSManager	1/08/2018 9:53:55 AM	1372 (0x055C)
Set a TS execution environment variable _SMSTSInstructionStackString=	TSManager	1/08/2018 9:53:55 AM	1372 (0x055C)
Save the current environment block	TSManager	1/08/2018 9:53:55 AM	1372 (0x055C)
Expand a string: %_SMSTSMDataPath%\Logs	TSManager	1/08/2018 9:53:55 AM	1372 (0x055C)

There were a couple of errors / warnings in the log along the way, I am not sure if they a relevant to the issue or not but I thought they were worth mentioning:

ShellExecute ('raserver.exe') failed. 0x80070002.	TSPxe	1/08/2018 9:29:33 AM	1264 (0x04F0)
Failed to open "SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" (0x80070002).	ApplyOperatingSystem	1/08/2018 9:52:47 AM	1780 (0x06F4)
Unsuccessful in releasing BRW0005F. 80070490.	OSDSetupWindows	1/08/2018 9:53:28 AM	1088 (0x0440)

The package ID mentioned above is the is actual OS Image. 

The output from 'All Status Messages for a Specific Deployment at a Specific Site'  was exactly the same as the previous one. 

I'm really scratching my head now.. could it be the image itself causing these issues? They are fairly basic images with a couple of additional small applications installed, nothing complex or really large in size.

Share this post


Link to post
Share on other sites

You could try to redistribute the content for the image.

Otherwise, you can also try to deploy a standard wim file (the original from the Windows DVD).

Share this post


Link to post
Share on other sites

I'll try redistributing the image.

I have deployed other WIMs via other task sequences OK so I know my general setup seems to work, it's just something particular to either this image or this TS?

Share this post


Link to post
Share on other sites

Possibly it is something particular to this image.

You can also try to rebuild the task sequence from scratch to make sure that is the problem. Fortunately there aren't very much steps. 

However, when I search for the error (0x80070002) in your log, it brings me to this site:

https://prajwaldesai.com/task-sequence-failed-error-code-0x80070002/

It states that possibly something is wrong with your NAA (Network Access Account). Perhaps password expired or wrong?

Share this post


Link to post
Share on other sites

I decided to give in and got the image rebuilt. This one works without issue, so I can only assume something was wrong with the previous one?

There were no file system errors, sfc /scannow never complained and all H/W checks from the reference PC passed. So what caused this, I have no idea....... and probably never will!

Thanks for your help, I did learn a few things out of it so it wasn't in vain.

 

Share this post


Link to post
Share on other sites

Good to hear that you've managed to get it working.

Perhaps the image got corrupted due to offline servicing of Windows updates within the image? Something must have touched the image, making it corrupt. 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...