All Activity

are you sure that that fqdn was pingable before this step, could the system have dropped the ip address or gone asleep ?

The Applying Image step gets all the way done, and then gives the following errors in smsts.log I opened command prompt and pinged the FQDN as well as the short name, and it resolved without issues. Any ideas? unknown host (gethostbyname failed) TSManager 12/1/2021 10:42:18 AM 4132 (0x1024) hr, HRESULT=80072ee7 (X:\bt\1026714\repo\src\Framework\OSDMessaging\libsmsmessaging.cpp,10078) TSManager 12/1/2021 10:42:18 AM 4132 (0x1024) Sending with winhttp failed; 80072ee7 TSManager 12/1/2021 10:42:18 AM 4132 (0x1024) End of retries TSManager 12/1/2021 10:42:18 AM 4132 (0x1024) Send (pReply, nReplySize), HRESULT=80072ee7 (X:\bt\1026714\repo\src\Framework\OSDMessaging\libsmsmessaging.cpp,2260) TSManager 12/1/2021 10:42:18 AM 4132 (0x1024) failed to send the request. 80072ee7. TSManager 12/1/2021 10:42:18 AM 4132 (0x1024) DoRequest (sReply, false), HRESULT=80072ee7 (X:\bt\1026714\repo\src\Framework\OSDMessaging\libsmsmessaging.cpp,4598) TSManager 12/1/2021 10:42:18 AM 4132 (0x1024) Failed to send status message (80072ee7) TSManager 12/1/2021 10:42:18 AM 4132 (0x1024) smStatusMessage.Send(), HRESULT=80072ee7 (X:\bt\1026714\repo\src\Framework\TSCore\utils.cpp,7317) TSManager 12/1/2021 10:42:18 AM 4132 (0x1024) Error calling message lib Send(). Code 0x80072ee7 TSManager 12/1/2021 10:42:18 AM 4132 (0x1024) Non fatal error 0x80072ee7 in sending task sequence execution status message to Management Point TSManager 12/1/2021 10:42:18 AM 4132 (0x1024) Active power scheme is cbd2463e-9cea-42a7-bdff-7c02f06b18c2 TSManager 12/1/2021 10:42:18 AM 4132 (0x1024) Reverting power plan to the initial setting after it was set to custom performance plan. TSManager 12/1/2021 10:42:18 AM 4132 (0x1024) Set active power scheme to 381b4222-f694-41f0-9685-ff5bb260df2e TSManager 12/1/2021 10:42:18 AM 4132 (0x1024) Deleted power scheme cbd2463E-9cea-42a7-bdff-7c02f06b18c2 TSManager 12/1/2021 10:42:18 AM 4132 (0x1024) Server is no longer in use. Shutting down. TSProgressUI.exe 12/1/2021 10:42:18 AM 4840 (0x12E8)

well spotted, and here's a tip for everyone to help you find out what these codes mean, start CMTrace.exe (available in the C:\Windows\CCM folder), click on Tools and select Error Lookup in the window that appears, paste in your error code and click on Lookup this helps to reveal the reason why something is failing

Hi Find it ( if anyone is interestered ) Windows Setup failed with hexadecimal exit code 0x80070652 (decimal 2147944018). To identify the type of issue, lookup it against the table of known values of Windows Setup errors online. = Another installation is already in progress. Complete that installation before proceeding with this install.

Hi I have got same error on several machines when I have done Task Sequences Windows 10 22H2 Upgrade from Windows 10 1903 The error messages is in SMST.log --> "Windows Setup failed with hexadecimal exit code 0x80070652 (decimal 2147944018). To identify the type of issue, lookup it against the table of known values of Windows Setup errors online. OSDUpgradeWindows 04-09-2023 16:10:29 39084 (0x98AC) Failing this task sequence step OSDUpgradeWindows 04-09-2023 16:10:29 39084 (0x98AC) upgrade.Run(), HRESULT=80004005 (K:\dbs\sh\cmgm\1125_114522\cmd\1w\src\client\OsDeployment\UpgradeWindows\upgradewindows.cpp,1881) OSDUpgradeWindows 04-09-2023 16:10:29 39084 (0x98AC) Exiting with code 0x80004005 OSDUpgradeWindows 04-09-2023 16:10:29 39084 (0x98AC) Process completed with exit code 2147500037 TSManager 04-09-2023 16:10:29 42592 (0xA660) TSManager 04-09-2023 16:10:29 42592 (0xA660) Failed to run the action: Upgrade Operating System. Error -2147467259 TSManager 04-09-2023 16:10:29 42592 (0xA660) Not in SSL. TSManager 04-09-2023 16:10:29 42592 (0xA660) Set a global environment variable _SMSTSLastActionRetCode=-2147467259 TSManager 04-09-2023 16:10:29 42592 (0xA660) Set a global environment variable _SMSTSLastActionName=Upgrade Operating System TSManager 04-09-2023 16:10:29 42592 (0xA660) Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 04-09-2023 16:10:29 42592 (0xA660) Clear local default environment TSManager 04-09-2023 16:10:29 42592 (0xA660) Let the parent group (Upgrade the Operating System) decides whether to continue execution TSManager 04-09-2023 16:10:29 42592 (0xA660) The execution of the group (Upgrade the Operating System) has failed and the execution has been aborted. An action failed. Error 0x80004004 TSManager 04-09-2023 16:10:29 42592 (0xA660) Failed to run the last action: Upgrade Operating System. Result -2147467259. Execution of task sequence failed. TSManager 04-09-2023 16:10:29 42592 (0xA660) Not in SSL. TSManager 04-09-2023 16:10:30 42592 (0xA660) Showing task sequence error message after failure in task sequence step of type 'SMS_TaskSequence_UpgradeOperatingSystemAction' TSManager 04-09-2023 16:10:30 42592 (0xA660) Task Sequence Engine failed! Code: enExecutionFail TSManager 04-09-2023 16:25:37 42592 (0xA660) TSManager 04-09-2023 16:25:37 42592 (0xA660) Task sequence execution failed with error code 80004005 TSManager 04-09-2023 16:25:37 42592 (0xA660)" The task sequence manager could not successfully complete execution of the task sequence Error Messages 11170... I have done that : Check the SMSTS.log file for more information about the error. Look for any error messages that may provide more details about the issue. See below Verify that the computer has sufficient disk space to perform the upgrade. Ensure that there is enough free space on the system drive to accommodate the upgrade. 33 GB in C Free Check the network connectivity between the client computer and the Configuration Manager server. Ensure that the client computer can communicate with the server and that there are no network issues. The client can ping the SCCM Server Verify that the user account running the task sequence has the necessary permissions to perform the upgrade. Ensure that the account has administrative privileges on the client computer. Missing Network Access Account in SCCM ( it is needed ? ) Check if any antivirus or firewall software is blocking the upgrade process. Disable any antivirus or firewall software temporarily and try running the task sequence again. The clients is running Windows Defender Ensure that the necessary files and drivers are available on the client computer. Verify that the required drivers and files are present on the client computer and that they are accessible. How will I checked that ? Remotely ?? Please help ! // Sokoban

what happens just before the error ? what server version is it ? which ADK is installed ? is it pure WDS or WDS plus some other functionality ?

Hello guys, I need your help as I'm encountering an issue with the WDS service, which is giving me the following error when trying to deploy an image: '0xc000000f the boot data in your PC.'"

@xerxes2985 great ! I'm glad to hear it !

@anyweb got it working. In my original TS I had extra files to run TSBackground, and winpeshl.ini got stuck in the OSD\bin\x64 folder pointing to an invalid file. I updated it to point to %SYSTEMDRIVE%\sms\bin\x64\TsBootShell.exe and now all is working. Thanks for pointing me to the boot image!

It's set to the same one that I watch as the progress bar before I get to the screen where I should be able to press F8. I'll try hooking up an external keyboard to the laptop.

then something is not right, if you enable f8 command support then it should work, if it is not then you are working on the wrong boot image to the one in the console

Same result. Should I contemplate removing the DP role and recreating the DP?

if you have enabled it on the boot image, then redistribute it to the distribution point(s) and try again

Tried this as well. No luck.

@anyweb unfortunately pressing F8 (even though I have the box checked on my boot image) is not working.

Try a diskpart/select disk 0/ clean Then reboot and try again. I've seen this on a few machines when booting off a USB flash drive and it stumped me. The above disk part resolves it.

on the client, press f8 to bring up a cmd prompt, then click on your available task sequence, browse to x:\windows\temp\smstslog and find and download/attach the smsts.log file here please

Unfortunately no. Each time it PXE boots this is all that shows up in the log. If need be, I can remove/reinstall the DP and any other components.

Just as a note, OU data will get returned to ConfigMgr via Heartbeat discovery. This means by default it will take 7 days or longer for the details to get returned.

the reason for the reboot is it either can't see a task sequence or missing drivers, but we are not seeing that in this log, is there anything further logged in smsts.log ?

I have had this happen before with a collection that still had old members in it. For example, when you move a computer to a different OU (if you have OU based collections), I have experienced where they get stuck, and manually updating the collection membership will remove those old computers.

Not sure what occurred, PXE boot is successful. However, the Microsoft Configuration Manager background loads... sits for a couple seconds.. then the system reboots. I have attached part of the SMSPXE.log from the most recent attempt: I have X'd out the IPs and what not. ============> Received from client: SMSPXE 8/24/2023 1:36:34 PM 4524 (0x11AC) Operation: BootRequest (1) Addr type: 1 Addr Len: 6 Hop Count: 0 ID: 0001E240 Sec Since Boot: 65535 Client IP: x.x.x.x Your IP: 000.000.000.000 Server IP: x.x.x.x Relay Agent IP: 000.000.000.000 Addr: a4:4c:c8:19:2e:40: Magic Cookie: 63538263 Options: Type=93 Client Arch: EFI BC Type=97 UUID: 0044454c4c5a0010338054c8c04f424832 Type=53 Msg Type: 3=Request Type=60 ClassId: PXEClient Type=55 Param Request List: 3c8081828384858687 Type=250 0c01010d020800010200070e010105040000000aff SMSPXE 8/24/2023 1:36:34 PM 4524 (0x11AC) Looking for bootImage LIB003F7 SMSPXE 8/24/2023 1:36:34 PM 8596 (0x2194) Prioritizing local MP https://servername. SMSPXE 8/24/2023 1:36:34 PM 8596 (0x2194) Using Management Point: https://servername SMSPXE 8/24/2023 1:36:34 PM 8596 (0x2194) SSL, using authenticator in request. SMSPXE 8/24/2023 1:36:34 PM 8596 (0x2194) In SSL, but with no client cert. SMSPXE 8/24/2023 1:36:34 PM 8596 (0x2194) SSL, using authenticator in request. SMSPXE 8/24/2023 1:36:34 PM 8596 (0x2194) In SSL, but with no client cert. SMSPXE 8/24/2023 1:36:34 PM 8596 (0x2194) ============> REQUEST Reply to client ([x.x.x.x:68]) Len:447 SMSPXE 8/24/2023 1:36:34 PM 8596 (0x2194) Operation: BootReply (2) Addr type: 1 Addr Len: 6 Hop Count: 0 ID: 0001E240 Sec Since Boot: 65535 Client IP: x.x.x.x Your IP: 000.000.000.000 Server IP: x.x.x.x Relay Agent IP: 000.000.000.000 Addr: a4:4c:c8:19:2e:40: BootFile: smsboot\x64\bootmgfw.efi Magic Cookie: 63538263 Options: Type=53 Msg Type: 5=Ask Type=54 Svr id: x.x.x.x Type=97 UUID: 0044454c4c5a0010338054c8c04f424832 Type=60 ClassId: PXEClient Type=243 01515c534d5354656d705c323032332e30382e32342e31332e33312e30392e303030342e7b35353838433132432d333241452d344638352d423633322d3539433637353937313139367d2e626f6f742e766172 Type=252 5c534d5354656d705c323032332e30382e32342e31332e33312e30382e30392e7b35353838433132432d333241452d344638352d423633322d3539433637353937313139367d2e626f6f742e62636400 SMSPXE 8/24/2023 1:36:34 PM 8596 (0x2194) <============ REQUEST Reply (end) SMSPXE 8/24/2023 1:36:34 PM 8596 (0x2194) Things I have already done: Rebuilt boot image and made it available to PXE distribution. Restarted server Restarted WDS Ensured task sequence is advertised to a collection that the computer is a member of. No luck and I can't seem to find any errors.

Hello, I have issue with installation of our new computers Dell OptiPlex 7000 Tower. I tried to deploy OS from task sequence which created my previous colleague especially due to deploying to notebooks Dell Latitude 5430. For Latitude 5430 it works great. The task sequence is created using Build and Capture. In case of deploy to OptiPlex 7000 Tower process was stoped at step 48 which is "Setup Windows and Configuration Manager" according to Asset Message window in Monitoring section in SCCM console. I looked at smsts.log and ccmexec.log. But unfortunately I have no idea where can be issue. In smsts.log is red line: Timed out (Timeout=1800 sec) waiting for CcmExec service to be fully operational. OSDSetupHook 8/4/2023 3:39:22 PM 4056 (0x0FD8) And: Failed to wait for CcmExec service to be fully operational (0x80004005) OSDSetupHook 8/4/2023 3:39:22 PM 4056 (0x0FD8) and by yellow colour: RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram OSDSetupHook 8/4/2023 3:39:23 PM 4056 (0x0FD8) GetTsRegValue() is unsuccessful. 0x80070002. OSDSetupHook 8/4/2023 3:39:23 PM 4056 (0x0FD8) I attached smsts.log and ccmexec.log to this thread. If necessary, I can also attach other necessary logs, screen shots, etc. Thank You Very Much for Your Help! smsts.log CcmExec.log

great job, and thanks for posting your resolution to the problem

Managed to figure out what was wrong, the SQL database was the cause, it turned out to be a problem with the spn. The spn was registered with service account and I was getting SSPI error Reset the SPNs and set the SQL startup account to Local System and it had worked