Let’s understand the workflow of ConfigMgr Client Deployment Using Intune. In this post, we will analyze the sequence of events that occur in the back-end when we deploy the ConfigMgr client from Intune. Understanding this workflow may help in troubleshooting ConfigMgr client deployment using CMG.
In autopilot deployments, Windows 10 devices are managed by Intune. But I have seen many customers still need ConfigMgr for many reasons. As we all know that Intune can deploy the ConfigMgr client via CMG.
- Win 10 provisioned via Windows Autopilot process.
- Windows 10 enrolled to Intune.
- Intune deploy the ConfigMgr client via CMG
- The ConfigMgr agent communicates with the ConfigMgr server via CMG
- Computer becomes co-managed ( ConfigMgr + Intune )
To implement the above scenario, you need a CMG infrastructure, Autopilot, and ConfigMgr Bootstrap executable deployed from Intune.
- Refer here, for more details on how to configure CMG
- Refer here, for more details on how to configure ConfigMgr client deployment in Intune console
Flow Diagram – Client Deployment Using Intune
The below diagrams describe the sequence of events after triggering ConfigMgr agent installation via CMG. The sequence of events is numbered and described in detail.
The following are the steps that help you to understand the ConfigMgr Client Deployment Using Intune process.
- Create CCMSetup Service
- 1. Intune Deploy ConfigMgr bootstrap to create CCMsetup installation service
- Authenticate to get ConfigMgr agent binary
- 2. Win 10 Request AAD token validation to Azure AD
- 3. Win 10 Request CCM token to CMG
- 4. CMG connection point receive the CCM Token request from CMG
- 5. CMG connection point redirect CCM Token request to Management Point
- ConfigMgr agent download and install
- 6. Win 10 receives CCM token and then request for ConfigMgr client binary
- 7. ConfigMgr agent binary download from Azure Blog and install on Win 10
- ConfigMgr client registration and policy download
- 8. The ConfigMgr client sent an AAD token validation request to Azure AD
- 9. Management point register the ConfigMgr client after validating AAD Token
- 10. The ConfigMgr client sent CCM token request to CMG
- 11. CMG connection point receive CCM Token request from CMG
- 12. CMG connection point redirect CCM Token validation request to Management point
- 13. ConfigMgr client receive CCM token and cache locally
- The ConfigMgr client is now co-managed and functional to receive ConfigMgr Policies and apps
In the above workflow, you can see the importance of authentication (Token). CMG will allow communication with ConfigMgr servers only for devices with a valid Token.
Based on your scenario, please make sure your Windows 10 have the necessary Token /certificates like User AD discovery, Root certificate, Client auth certificate, and Device Token.
Let us go through the sequence.
Step 1. Intune Deploy ConfigMgr bootstrap and create CCMsetup installation service
The CCMsetup.exe bootstrap process creates the CCMsetup service as shown below. This is a temporary service that starts the ConfigMgr client install and registration process.
- We can verify the CCMSetup service created from ccmsetup.log.
- The installation command line is constructed based on what you have configured in Intune. CCMSetup.log helps to verify whether the command line is proper
CMG also acts as Cloud DP which provides ConfigMgr client binaries to win 10. CMG and your internal ConfigMgr servers communicate with Win 10 which has a valid Auth token.
Let us discuss the sequence of events required to authenticate and download the ConfigMgr agent.
Step 2. Win 10 Request AAD token validation to Azure AD
The CCMsetup bootstrap service requests an Azure AD device token. An alternate option is the Azure AD user token. In my scenario, win 10 was the Azure AD joined device. This means I have a valid Azure AD Device token. Let us discuss how this AAD token gets validated next
Windows 10 communicate with CMG cloud for Authentication via the Server App Resource URL. This URL is created automatically as part of the CMG configuration.
Note: if there is any issue in Getting the AAD (device) token, then you will see some error in the after below entry.
Only the AAD token is not enough to download the ConfigMgr binaries. CCM token is also required. Let us discuss the CCM token validation process next.
Step 3. Win 10 Request CCM token to ConfigMgr via CMG
After validating the AAD token, next Win 10 will request for ConfigMgr client (CCM) token. As shown below, the Windows 10 device requests a CCM token to CMG via the Security Token Service communication channel (CCM_STS).
You can confirm this request event from Ccmsetup.log (ConfigMgr client logs).
Getting CCM Token from https://cochii.cloudapp.net/CCM_Proxy_ServerAuth/72057594037927951/CCM_STS
Step 4. CMG connection point receive the CCM Token request from CMG
CMG receives CCM token requests and redirects to the ConfigMgr CMG connection point. CMG acts as a proxy or mediator between Win 10 device and ConfigMgr server.
You can verify this event from CMGService.log (CMG Azure server: E:\approot\logs).
ConfigMgr server receives the CCM Token validation requests from CMG. Below log in ConfigMgr server logs these events.
RequestUri: /CCM_PROXY_SERVERAUTH/72057594037927951/CCM_STS RequestCount: 1 RequestSize: 1893 Bytes ResponseCount: 1 ResponseSize: 1567 Bytes AverageElapsedTime: 390 ms
- Below log indicate the communication between your CMG and ConfigMgr server (CMG connection point server).
- SMS_CLOUD_PROXYCONNECTOR.log (CMG connection point server)
Step 5. CMG connection point redirect CCM Token request to Management Point
CMG connection point transforms CCM Token request to management point client request. Management Point to issue CCM token.
From the below log, you can see an incoming request to Management Point. AAD token validated first. If the AAD token is valid, then MP verifies in the ConfigMgr database. If all goes well then you should MP issues CCM token to Win 10 (Via CMG). It seems Microsoft still uses the term “ SCCM” … J
CCM_STS.log ( CMG connection point server)
- Now Windows 10 devices got the valid CCM token to download ConfigMgr client binaries!!!!
Let’s proceed to the next events…
Step 6. Win 10 received CCM token and request for ConfigMgr client content
Win 10 append this CCM token to its request header and request ConfigMgr binary from CMG.
Win 10 gets the reply from CMG with details like ConfigMgr site, Boundary, and ConfigMgr agent content location.
Now win 10 have a valid AAD + CCM token + ConfigMgr Site details to download the agent. 😊.
Let’s proceed to the next events…
Step 7. Azure Blob provides ConfigMgr agent binary download and installs
As seen below, CMG (Content service) respond to the Win 10 request. Then Win 10 starts downloading ConfigMgr agent.
CMG act as Cloud DP as well. Cloud DP response logged in CMGContentService.log (E:\approot\logs)
ConfigMgr agent downloads from Azure DP (Blob storage) using BITS
Once the download completes, the agent install in the below folder path
Now win 10 got ConfigMgr agent installed 😊. But this does not mean the ConfigMgr client is functional to receive policy and apps. ConfigMgr client needs to authenticate and register with the ConfigMgr server.
This is required, irrespective of any scenario. Let us discuss this sequence of events to get the ConfigMgr client registered.
Step 8. ConfigMgr client sent AAD token request to Azure AD
ConfigMgr Client request for AAD token. You can see below the AAD token retrieved and cached. In my scenario, I have enabled Azure AD user discovery enabled.
Step 9. Management Point registers the ConfigMgr client after validating AAD Token
The configMgr agent communicates with MP via CMG. MP registers the client after successful AAD Auth token validation.
ClientIDManager.log indicate registration and approval status as shown below.
MP_RegistrationManager log is useful while troubleshooting. This log helps to track a ConfigMgr client using its GUID. This log also shows the DDR creation and device registration process.
After a few minutes, you can see a new DDR record in the SCCM console.
Now ConfigMgr client registered. We are halfway through now. Next Win 10 needs a CCM token to get Policy and apps. Let’s discuss those events next.
Step 10. ConfigMgr client sent CCM token request to CMG
ConfigMgr agent installed and CCM token requested via STS channel to CMG.
ClientLocation.log ( ConfigMgr agent-client logs )
Step 11. CMG connection point receive CCM Token request from CMG
CMG receives the CCM token request and redirects the request to the CMG connection point. You can verify these events from the CMGService log (CMG server).
Step 12. CMG connection point redirects CCM Token validation request to Management Point
Management point validates AAD token in ConfigMgr site database first and then issues CCM token.
Step 13. ConfigMgr clients receive CCM tokens and cache locally
Win 10 will receive the CCM token and will cache. ConfigMgr clients use this token to communicate with the ConfigMgr server and download policies, apps, etc. This token is valid only for 8 hr. ConfigMgr client will renew the CCM token.
ClientIDManagerStartup.log ( ConfigMgr client logs )
You can see the token renewal from ClientMangerStartup and ccmmessaging logs.
Step 14. The ConfigMgr client is co-managed and ready to receive ConfigMgr Policies and apps
Finally, we got the ConfigMgr client registered and trusted by the ConfigMgr server. Now you can start seeing ConfigMgr clients getting policies or deployments.