I would stop using ad boundaries and use ip ranges only.
Have you reviewed the logs to see what is going on?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Sorry Very new to SCCM here. So bare with me.
I have simple software packages that I create and push out to my computers. Normally patches & updates for Adobe Reader, MS Edge, Firefox.
When I schedule these to go out there are always 30-40 random computers that will not get the package installed out of 130. The only way the software gets installed is if someone logs in to them. Then it will start installing automatically. I get frustrated and just use PSEXEC to push out the software to the remaining systems. But I really need to figure out why this is happening every time. Been fighting this for over 6 months now.
Looks like I'm running version 2103. Mostly likely not up to date. I'm in a closed environment with NO Internet access so an update is not happening anytime soon. Packages are set to install whether or not someone is logged on. I can schedule to run everyday for a week and won't matter.
Boundry is setup to use Active Directory Site. Some packages have install logs but they are not even getting created as they never start to run. I'd say about 99% of computers are listed as Active for Client Activity. I also notice that when I remote into these computer Software Center is not updated until after about 30-45 seconds then it updates itself (with updated software listing) and then software starts to install.
I would stop using ad boundaries and use ip ranges only.
Have you reviewed the logs to see what is going on?
Hi @Bruno Frisan,
1, Are these clients all in the same collection?
2, Please navigate to Monitoring> Distribution Status> Content Status> Package Name to monitor the deployment status after you deploy the package. What is the status about these clients?
3, We can trace the package deployment from execmgr.log and CAS.log based on package ID. These logs located on Client>C:\Windows\ccmsetup\logs...
Looking forward to your reply.
Best regards,
Cherry
Here is my guess; and it's an easy one to try / test.
Next time, when you say it's a required application, and the deadline is "ASAP", don't use ASAP.
Say that the 'available' date/time is 12 hours ago, and that the required time is 3 hours in the future (or something like that) local to the client, not UTC time.
I've seen it, over and over again, where a client sees the "ASAP" designation and for whatever reason... just doesn't know what 'ASAP' means. But if you give it an absolute available and start/deadline time, the client gets it, and acts on it.
Since you said it's 30+ devices out of 120 or so, this is an easy one to try 'next time' ; just to see if that's all it is.