Microsoft Intune

Following the ConfigMgr task sequence bootstrap process

In my previous blog, I talked about how you could have Intune automatically run a ConfigMgr task sequence during a Windows Autopilot deployment.  For those of you who wanted more information on how this works, here’s some additional details.

First, you’ve seen the command line parameters passed into the CCMSETUP.MSI:

CCMSETUPCMD=”/nocrlcheck /UsePKICert /mp:https://CONTOSOCM.CONTOSOCM.COM/CCM_Proxy_MutualAuth/72057594037927953  CCMHOSTNAME=CONTOSOCM.CONTOSOCM.COM/CCM_Proxy_MutualAuth/72057594037927953 SMSSiteCode=PRI PROVISIONTS=PRI20003″

Included in that is the task sequence deployment ID, which will start with the site code and a 2 – in my case the site code is PRI, so the prefix is PRI2.  If the 4th character is something other than a 2, then you have the wrong ID.  If you look in the C:\Windows\ccmsetup\Logs folder, you should find a number of references to this ID:

  • The CCMSETUP*.LOG files should reference the deployment ID and pass it forward to CCMSETUP.EXE, e.g. with something like this:  PROVISIONTS=”PRI20003”
  • Next, that is passed forward to the CLIENT.MSI, so you’ll see that ID referenced in the CLIENT.MSI.LOG:
  • You should then see in the CcmExec.log that it is firing off TSAgent:
  • Then the TSAgent will start the task sequence using TSPLaunch.exe:
  • At that point, the task sequence will start and log to the normal SMSTS.LOG file:

At that point, you should be able to follow the progress through the SMSTS.LOG to see if the policy can be downloaded and the task sequence started and whether it completes successfully, so once you get that far, focus on that file.  Of course my task sequence failed, so that’s where I’ll focus…