Insaf Mohd
New Member
- Messages
- 1
- Reaction score
- 0
- Points
- 1
Hi Prajwal,
I am a newbie here so greetings
I recently discovered your blog series and became an ardent fan of them.
Kudos to your great work that is 100% valuable for all of us!
My issue, when I deploy software updates to a collection it usually works fine as expected and i get decent compliance. My targets are Office 2013, Windows 10, Windows Server 2012 R2 and a few Windows server 2016 servers. But sometimes some deployments seem stuck , in the Unknown <Monitoring
"Client check passed/Active" /#machines
It occurs quite often, then if I reboot some targets they fall to the installation and compliance or never at all where I delete the deployment job and recreate it. I even reboot SCCM host sometimes thinking that might help.
I can assure,
We have a high end single host that's installed with ConfigMgt Roles+ MS SQL+WSUS for SUP
1- Discovery methods, Boundaries (all Subnets), boundary groups all configured - that's why I succeed in deployments most of the time
2- All required ports are open between clients and CM host bidirectionally
2 - CM admin user has local admin access in all the target collections for deployments
3- Clients are properly listed active in the devices list and agent is updated
4 - SUP syncs properly with WSUS, it fetches every updates on release times.
NB: The WSUS in the SCCM host (SUP) is a downstream as there's no internet in this domain at all (security reasons). There's an upstream WSUS in DMZ where I select the products, classifications etc which downloads from internet and the SCCM's WSUS syncs from it via 8530. The clients in the domain are pointed to SCCM host only on same 8530 port. This setup worked fine with us
5 - I delete every expired updates from the packages prior to every deployments
6 - I am not using ADRs and do not prefer it but manual
This issue I noticed only with software updates not app or package deployments. What could be wrong in my setup? Any fine tuning advisable?
Regards
Insaf
I am a newbie here so greetings
I recently discovered your blog series and became an ardent fan of them. Kudos to your great work that is 100% valuable for all of us!
My issue, when I deploy software updates to a collection it usually works fine as expected and i get decent compliance. My targets are Office 2013, Windows 10, Windows Server 2012 R2 and a few Windows server 2016 servers. But sometimes some deployments seem stuck , in the Unknown <Monitoring
"Client check passed/Active" /#machines
It occurs quite often, then if I reboot some targets they fall to the installation and compliance or never at all where I delete the deployment job and recreate it. I even reboot SCCM host sometimes thinking that might help.
I can assure,
We have a high end single host that's installed with ConfigMgt Roles+ MS SQL+WSUS for SUP
1- Discovery methods, Boundaries (all Subnets), boundary groups all configured - that's why I succeed in deployments most of the time
2- All required ports are open between clients and CM host bidirectionally
2 - CM admin user has local admin access in all the target collections for deployments
3- Clients are properly listed active in the devices list and agent is updated
4 - SUP syncs properly with WSUS, it fetches every updates on release times.
NB: The WSUS in the SCCM host (SUP) is a downstream as there's no internet in this domain at all (security reasons). There's an upstream WSUS in DMZ where I select the products, classifications etc which downloads from internet and the SCCM's WSUS syncs from it via 8530. The clients in the domain are pointed to SCCM host only on same 8530 port. This setup worked fine with us
5 - I delete every expired updates from the packages prior to every deployments
6 - I am not using ADRs and do not prefer it but manual
This issue I noticed only with software updates not app or package deployments. What could be wrong in my setup? Any fine tuning advisable?
Regards
Insaf
