This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 51%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
Hi All,
I wonder if someone is able to help and off advise on how to resolve this issue we are getting.
Basically, when I kick off an SCCM task sequence to build a Dell Latitude 5310 the task stops at the MDT splash screen and does not do anything else. After around 2 minutes it will attempt to reboot itself but it always ends up back at the same MDT splash screen with a blank white screen.
The task sequence works on works on every other Dell Latitude and HP laptops without any problems. I have checked the WMIC setup in the task sequence and the query is correct I.E. SELECT * FROM Win32_ComputerSystem WHERE Model LIKE "%Latitude 5310%" or Model LIKE "%Latitude 5310%" . I have run a test against this query and the syntax is correct. I have distributed the new drivers for the Latitude to the DP's etc.
Can someone please help I need to build at least 10 new laptops and am unable to do so in the present state. Is there a log that I am able to look at for troubleshooting further, has anyone else had a similar problem.
Any help or information would be greatly appreciated.
Hi Gary,
I have not tried to press F8 at that particular point. I haven't been able to setup the TS Debugger. To start with unable to turn on the Task Sequence Debugger. Do we need to have that set up to see the logs after pressing F8?
TSDebugger is a very recent addition and has no connection to being able to use F8 to launch the command prompt.
You can confirm you've setup the ability to use F8 to launch command prompt here: https://docs.recastsoftware.com/ConfigMgr-Docs/TaskSequence/ModifyBootImages.html
Is the 5310 the newest Dell you have, is this a new model you just started testing? Or do you have other newer models that work with your task sequence, when this one doesn't?
Hi Gary,
We had two Dell laptops recently added to our catalog. They were the 5410, and 5310. We have tested the 5410 and we did not have this problem. We only get the problem when we attempt to PXE the 5310. We have deleted all the drivers packages the we downloaded for 5310 reinstalled then distributed the latest drivers but to no avail.
Thanks for taking the time out to post.
My Assumptions. You're using Configuration Manager Current Branch, with MDT Integrated.
For OSD using ConfigMgr, the log is SMSTS.log
If you're wanting to confirm it runs that step, the SMSTS.log would tell you.
You get to the CM Boot Menu, you pick your TS, the MDT Integrated TS in ConfigMgr starts running, after a few steps you hit the MDT Front End Splash Screen where you can enter machine names, but you can't get further?
Can you better explain what is happening? It would appear that it never gets close to running your Apply Drivers step.
Uploading the SMSTS.log would help greatly to troubleshoot.
You can also enable the TS Debugger, which is very helpful to figure out these options. Set a variable on the device object to run the debugger.
https://video2.skills-academy.com/en-us/mem/configmgr/osd/deploy-use/debug-task-sequence
Hi Gary,
First of all thanks very much for taking the time out to post and help me with this situation.
You are correct in saying we are on Current Branch with MDT integrated. I will check with the SMSTS.log for some indication of what could be the problem.
Basically, to answer your reply - we F12 the new 5310 and it locates the IP address of where the PXE service is located, after that it downloads the .wim file. after it has downloaded we get to the MDT splash screen where it freezes and reboots numerous times to the same screen. We do not get as far as entering any details of machine names etc.
As for the smsts.log I see its location in c:\windows\ccm\logs\ on the management SCCM server but it appears the last updated entry is on the 16.07.20. We have carried out tens if not hundreds of PXE builds since then. I cant seem to find another log with any entries.
I hope this information goes some way to explaining my predicament.
Regards.
Hi,
Thanks for posting in Microsoft MECM Q&A forum.
Duplicated thread here: SCCM - MDT stuck
Please help check the smsts.log on the problematic client. If possible, please share the error screenshot and task sequence screenshot.
Thanks for your time.
Best regards,
Simon
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
If the issue is happening while the machine is in WinPE, the log would be in %temp%\SMSTSLog\smsts.log
I'd highly recommend enabling the task sequence debugger, which will easily let you launch the log file, as well as walk through each step to determine exactly where your issue is.
From your description, it is still too difficult to offer any advice as to why it's happening.
When you say "downloads the wim file", I assume that means you reach the "Apply Operating System Step" in the Task Sequence. The first reboot of the machine will happen on the "Setup Windows and ConfigMgr" Step.
What functionality are you using in MDT that you're using an MDT Integrated TS instead of a native ConfigMgr TS?
If you're not leveraging anything, you can greatly simplify your TS and your troubleshooting by starting over and not using and MDT integrated TS.
I just had a thought, is the reboot happening very quickly in the process? Does the Assigned Boot media on your TS match your PXE media?
Hi Gary,
Hope you are well...
Q. If the issue is happening while the machine is in WinPE, the log would be in %temp%\SMSTSLog\smsts.log.
A. I cannot see any logs in the above location on the management server or on the DP where the TS is failing.
Q. I'd highly recommend enabling the task sequence debugger, which will easily let you launch the log file, as well as walk through each step to determine exactly where your issue is.
A. I am having some issues in trying to understand how to enable this feature. Further reading is necessary.
Q. When you say "downloads the wim file", I assume that means you reach the "Apply Operating System Step" in the Task Sequence. The first reboot of the machine will happen on the "Setup Windows and ConfigMgr" Step.
A. Basically, after setting the Bios and pressing F12, out TS downloads a .wim file from the relevant distribution point. After this is loaded it stops at the MDT screen (see attached). ![33969-capture.jpg][1]
Q. What functionality are you using in MDT that you're using an MDT Integrated TS instead of a native ConfigMgr TS?
If you're not leveraging anything, you can greatly simplify your TS and your troubleshooting by starting over and not using and MDT integrated TS.
A. The MDT integrated into TS was configured by a company that Setup and configured our SCCM infrastructure.
Q. I just had a thought, is the reboot happening very quickly in the process? Does the Assigned Boot media on your TS match your PXE media?
A. After .wim file installation and when we get to the splash screen after around 1 minute or so it will reboot itself and try the PXE once more.
With the lack of SMSTS logs to troubleshoot would me taking a snip of the Task Sequence for you help in resolving the problem.?
Thank you very much for your continued support.