Jump to content


Gar

Troubleshooting CTM Job Process - Understanding each step in the ContentTransferManager.log

Recommended Posts

So the purpose of this thread is directly related to my issue in TechNet Post

But I justified it deserves a separate post of itself. To summarise the problem, I have extended the scope of our SCCM to cover another domain, of which it has no problems deploying applications/updates to Desktops, but with servers it is only deploying applications but not software updates (although they are detected under UpdatesDeployment.log and UpdatesHandler.log).

 

Before I continue, Boundaries and Boundary Groups are configured and working, as some of the working desktops fall in the same IP Range as the servers that are not working.

For Example

Boundaries IP Range: 10.10.10.1 - 10.10.10.254

Boundary Group: All DPs/MPs

Working Desktop IP: 10.10.10.50

Non-Working Server IP: 10.10.10.200

 

 

Non-Working Client - ContentTransferManager.log

CTM job {339D9C5D-6CB3-45F4-9789-D30018436A4D} entered phase CCM_DOWNLOADSTATUS_WAITING_CONTENTLOCATIONS

Queued location request '{5B8ADECB-DD78-46A2-B6C2-F1E4013F8AB9}' for CTM job '{339D9C5D-6CB3-45F4-9789-D30018436A4D}'.

CCTMJob::UpdateLocations - Received empty location update for CTM Job {339D9C5D-6CB3-45F4-9789-D30018436A4D}

 

Working Client - ContentTransferManager.log

CTM job {EDCAE134-0282-48B6-AF28-7E673DC79A49} entered phase CCM_DOWNLOADSTATUS_WAITING_CONTENTLOCATIONS

Queued location request '{2FDD4693-2C59-4E9E-A467-15F9BBD6BFF8}' for CTM job '{EDCAE134-0282-48B6-AF28-7E673DC79A49}'.

Persisted locations for CTM job {C3E0349C-691D-4FD0-A356-7402098F0AFB}:

              (LOCAL) http://SCCM_SERVER#/SMS_DP_SMSPKG$/d5b73f6c-662f-47c7-a6c6-5e495f0297ef

              (LOCAL) http:// SCCM_SERVER#/NOCERT_SMS_DP_SMSPKG$/d5b73f6c-662f-47c7-a6c6-5e495f0297ef

              (LOCAL) http:// SCCM_SERVER#/SMS_DP_SMSPKG$/d5b73f6c-662f-47c7-a6c6-5e495f0297ef

              (LOCAL) http:// SCCM_SERVER#.SMS_DP_SMSPKG$/d5b73f6c-662f-47c7-a6c6-5e495f0297ef

              (LOCAL) http:// SCCM_SERVER#/SMS_DP_SMSPKG$/d5b73f6c-662f-47c7-a6c6-5e495f0297ef

              (LOCAL) http:// SCCM_SERVER#/SMS_DP_SMSPKG$/d5b73f6c-662f-47c7-a6c6-5e495f0297ef

 

I want to trace each granular step of this entire process to the point where I can see the CTM job {EDCAE134-0282-48B6-AF28-7E673DC79A49} entered phase CCM_DOWNLOADSTATUS_WAITING_CONTENTLOCATIONS job request on the server, and hopefully whatever the server is doing causing it send no DPs back to the client requesting this. I can't seem to find the root cause of this issue and really need to make some progress as it's already behind schedule and Management are waiting on me on this problem.

ContentTransferManager_NotWorking.jpg

ContentTransferManager_Working.jpg

Share this post


Link to post
Share on other sites

1) Please check the settings of IIS & check IIS logs as well for the specific client machine.

2) Please confirm are you able to see the Updates in SC.

3) Ensure there is no CU required for the patch you are deploying on the server itself.

4) Check if there is any other GPO applied on this server e.g (WSUS) or any Third party AV might be blocking.

5) Check the settings are enabled for these server as well in Hierarchy settings to connect device anonymously. 

6) Further you can check the deep dive flow of Steve Rachui on Software deployment on server/client side.

 

Hope this helps :)

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.