We had a machine that showed as "Waiting for Content" for a certain application in the Deployments section of Monitoring in SCCM administration console.
All other machines in the company successfully received the application with successful installation. So this was a one-off.
Troubleshooting Process:
1) Verified SCCM client was installed correctly and completely. This meant 7 tabs across two rows in the client window, 11 client actions listed on the Actions Tab, correct assigned site code, and an "installation succeeded" entry in the C:\Windows\ccmsetup\Logs\ccmsetup.log file.
2) Verified software was seen in Software Center with status as Downloading (0% complete)
3) AppDiscovery.log and AppEnforce.log in C:\Windows\CCM\Logs didn't show anything in particular in regards to the application in question
4) Verified content was available in the SCCM software repository location and was available on the Distribution Point where the computer was located
Resolution:
In the process of seeing what remote site the computer was at to verify the Distribution Point location, I looked at the IP address of the machine. It showed to have an IP address in the new IP address scheme we are starting to slowly roll out to all of our sites.
I then remembered that as we roll out the new IP address scheme, whenever the new data subnet deployed to a site was not added to Active Directory Sites and Services, SCCM content could not be downloaded by client computers.
Sure enough, the new subnet that the computer was in was missing from Active Directory Sites and Services. We added the subnet in, waited a few hours for everything to update, and then checked that the computer began downloading and installing the software.
No comments:
Post a Comment
Give my post a +1 or let me know if you found any of my blog content helpful!