PENDING Received empty location update for CTM Job

[Jameel]

Hi, When first setup and configured in October 2018 all Windows updates and packages download and install with no issues, this has suddenly stopped working, where all clients have window updates advertised but sit at downloading at 0%, All Software packages advertise and install with no problems so this is not a Boundary Group problem. All logs have been checked on client and can only see the following in contenttransfermanager.log -[CCTMJob::UpdateLocations - Received empty location update for CTM Job and in the Updatesstore.log -Queried Update (2d7c26b9-83c6-4312-bda5-4e34ced7a661): Status=Missing, Title=Update for Microsoft Excel 2016 (KB4462212) 32-Bit Edition, BulletinID.
Any help would be appreciated

 

[Garth]

the empty location suggests that your boundaries are not right. exactly what type of boundaries are you using?

 

[Jameel]

Hi, we are using IP Subnets only, if it was a Boundary Issue it doesn't explain how all the Application packages work fine but willing to try anything as at the moment we have making no progress in resolving this - Thanks

 

[Garth]

ip subnet are generally no recommended you should use ip ranges only.

 

[Jameel]

Hi sorry we use IP ranges on the LAN and IP Subnets on VPN, the issue we see is from both and am currently testing on LAN which uses IP ranges

 

[Garth]

IP ranges should be used everywhere, particularly on VPNs.

Are you sure that a regular package works correctly on your problem client? I would double check it.

 

[Jameel]

Hi - Yes all software packages work fine from LAN or VPN, I found that the IP ranges wouldn't work on VPN only as they would do a similar thing to the Windows updates in that they advertise but do not download and sit on 0%, once I changed the VPN boundaries to IP subnets they started to download fine

 

[Garth]

IP ranges will always work as the subnet mask is always assumed to be 255.255.255.255, where as IP subnet will only work if, and only if, the subnet mask matches, what should subnet mask. AKA If a computer has 192.168.1.25 with a subnet mask of 255.255.255.255, it will NEVER fall into the subnet of 192.168.1.0, 255.255.255.0.

Now back to your problem. I'm sure that you have check this but...

• Confirm that the exact SU is deployed to all of your DP.
• Refresh the deployment to your DP.
• On a working computer determine URL to the SU, take that URL and see if you have download from a problem computer.
• Compare a working computer to a non-working computer. What is different?

 

[Jameel]

Hi, yes the DP and SUP are all looking fine, I have just re created the ADR's which we have done a few times before where it made no difference but now most clients are now installing all the updates??, there are a few just sat with waiting to install but never do, so not convinced its fully working but have made progress, even though we had a already tried new ADR's it never made a difference, its seems SCCM is a bit flakey for distributing windows updates from our experience and think this issue isn't full resolved

 

[Nav4339]

I am having having the exact same issue, and unable to resolve

Verified my boundary groups, content on DP, created new ADR, created new boundary groups. I even went to the extent of setting up a brand new DP. Still got the same result with my CTM logs. If I add my MP to my boundary everything works fine - but it is defeating the purpose as my MP is sitting at a remote site.

 

[mdc111]

Anyone resolve this? Having the same issues, checked the same stuff. I have 143 devices compliant, and 6000+ sitting in unknown status, active/passed.

 

[mdc111]

Had a similar issue, Added the SUP server to the default-boundary-group. That solved it for me. I still see that message in the client logs, but not as much as before.
I currently have an issue with a AV product on the DP server interferring with client getting updates. I'm waiting for the av product to be removed, and then will recheck the clients.