MDT & Deployment

czql5v 221 Reputation points
2020-10-20T06:44:11.497+00:00

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.

Microsoft Configuration Manager Deployment
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Deployment: The process of delivering, assembling, and maintaining a particular version of a software system at a site.
976 questions
Microsoft Configuration Manager
0 comments
Accepted answer
  1. czql5v 221 Reputation points
    2020-10-24T11:07:02.807+00:00

    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?

10 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Gary Blok 1,736 Reputation points
    2020-10-21T19:16:22.197+00:00

    The task sequence log is not on a MP or DP, it's only on the client. You'd have to Press F8 (assuming you enabled F8 support on your boot media) on the Client while in winpe, type cmtrace into the command prompt that opens when you press F8, then go to the log. Or enable TS Debugger which makes it very easy.

    You have to set the variable on the collection you have the client in, or on the client object itself.
    See this, find Option 2, which I find to be the most useful way to do it: https://www.anoopcnair.com/troubleshoot-sccm-task-sequence-debugger/

    The screen shot didn't come through, but my assumption is that you have different boot media assigned to your TS than what you are using to PXE boot, which is why almost right away in the process it is downloading a WIM and trying to reboot.

    It's odd that it isn't reboot to that WIM however.

    I'd also recommend creating a new simple native TS, something that looks like the image in this post: https://docs.recastsoftware.com/ConfigMgr-Docs/TaskSequence/SCCM-TaskSequence-Step-Auto-Apply-Drivers.html

    Keep is very simple, prove that it works, then start adding things in. My assumption is you have a misconfiguration of your assigned boot media, but without looking at your environment and seeing logs, it's hard to really give you a good answer.

    One other thing, if you're not leveraging any of the MDT Options, you should remove it and keep things clean. I have found native functionality to cover anything I once needed MDT for, or have found community tools to replace MDT, so I no longer need to have that installed and kept current.

    0 comments
  2. czql5v 221 Reputation points
    2020-10-22T06:59:42.24+00:00

    Hi Gavin,

    Thanks for the reply.

    Q. The task sequence log is not on a MP or DP, it's only on the client. You'd have to Press F8 (assuming you enabled F8 support on your boot media) on the Client while in winpe, type cmtrace into the command prompt that opens when you press F8, then go to the log.
    A. If I am reading the above correctly I would power up the client that needs to be PXE booted and Press F8 before I PXE booted? Then do the setup? Or would that be after a PXE attempt? Are there instructions on how to enable F8 on boot media.

    Q. Or enable TS Debugger which makes it very easy.
    You have to set the variable on the collection you have the client in, or on the client object itself.
    See this, find Option 2, which I find to be the most useful way to do it: https://www.anoopcnair.com/troubleshoot-sccm-task-sequence-debugger/
    A. I am going to have a go at the TS Debugger today.

    What I don't understand is that every other PXE model boots ok. This is the only model of Dell we are having problems with. I recently (last week) setup and PXE built a Dell 5410 model without any problems. Its just the 5310 that is giving us some serious issues.

    If you have any other ideas I am "All Ears".

    Once again thanks for taking the time out to offer advice.

    0 comments
  3. czql5v 221 Reputation points
    2020-10-22T07:45:42.137+00:00

    Sorry one other thing. Just looking at option 2 the machines need to have the SCCM agent on them before we can use the TS Debugger? We don't have the agent on a PXE built machine until its been PXE built - we are in a catch 22 situation.?

  4. Gary Blok 1,736 Reputation points
    2020-10-23T15:12:42.957+00:00

    Thanks for the screen capture.
    Are you able to press F8 at that point and pull up the logs?

    Do you ever see the box to select the task sequence you want to deploy?

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.