PENDING SCCM Windows 10 1903 Upgrade Stuck 0% Downloading

[dprd7]

For the past few weeks I have been updating my clients to Windows 10 1903 and everything was working ok until this week. All of a sudden with no changes being done I can no longer upgrade. The client keep saying 0% downloading and on the console said it says waiting for content. Please help.

 

[Prajwal Desai]

Can you also tell us what procedure are you following to upgrade your windows 10 computers to 1903.
To start with, confirm that the software has been distributed to your distribution point and that the boundary that your client is in, is associated with the correct distribution point.

Check the following log files - CAS.log, ContentTransferManager.log, DataTransferService.log

 

[dprd7]

I was using the guide you had but the only difference is I am doing a required install with times to be available and expiration times. My first couple deployments worked but out of nowhere now it is not. The software has been sent and the computer is in the boundary group but using active directory since we can't use IP Ranges.

I also did a test last night with your guide completely and when I try to install through software center it says "The software could not be found on any server at this time which is odd".

I will look at those logs but I am kinda a newbie with reading the logs. lol

I wanted to say by the way I love the site and the guides. It is an amazing resource.

 

[dprd7]

I am curious about the boundary groups. I have it set the domain level and all the computer are in that domain but I did notice one thing in the logs which is weird.

This is from the locationServices log

Client is not in any boundary group and ConfigMgr is no longer managing WindowsDO GPO. Set WindowsDO GPO to default values. Mode = LAN. GroupID = empty LocationServices 12/6/2019 12:14:13 PM 8800 (0x2260)

 

[dprd7]

Update. I just noticed that my clients are saying the wrong Active Directory Site when you look at the general info for the client which is why they seem to be outside the boundary group. Anyone have any idea how this happened and how to fix it since I made no changes to my SCCM and the boundary and boundary groups are correct. Before Thanksgiving everything was fine. I could push the client and the AD site would be correct but after break if I push the client it says the wrong AD site. Please help

 

[joe_v]

Do you have Computers in a specific OU in Active Directory? Is that OU used in discovery? If you try to remote to the client system, do you see the site code that was assigned to the SCCM showing up in Configuration Management Client (under the site tab) ? Are you able to ping the client? Do you have firewall settings that might be blocking ICMP or ping?

 

[dprd7]

My boundary is set at the top and my discovery is set to specific OUs which are within the boundary and are being discovered there. The clients have the correct Site code. I can ping them and there has been no firewall changes.

 

[joe_v]

Alright... If you do these 2 things, on one machine please try to uninstall SCCM client manually through command prompt (run as admin) by changing directory to C:\windows\ccmsetup (this is seen only if the client was installed previously on the computer) then typing ccmsetup /uninstall. Waiting for the ccmsetup in processes to complete ( in taskmanager). Then try to install in again manually.

From another machine, could you try to post the recent client.msi.log and ccmsetup.log from the C:\windows\ccmsetup.

 

[joe_v]

Also for the one where you would be doing the manual install for the sccm client on the host machine, please check the site code to see if it is showing as the right one or if it is empty. If it is empty, use the find site button and wait to see if it brings the right site code.

 

[dprd7]

Will do that when I get a chance. Is there a way to push out software if the machine lives outside the boundary group?

 

[joe_v]

Technically, the boundary helps the client to see where to get the software from. Otherwise it won't know where to look for the software. Please try the things i told earlier and we can try to see what the problem is.