Les_Grossman

So by manual push, I mean right clicking on the system in the devices or all systems collection and installing the client. Push is automatic site wide client installation. My goal is to get the client installed on systems after discovery and the automatic site wide client installation feature is enabled. The ccm.log is not showing any activity after I see that the client system has been discovered. I suspect a boundary issue as the "CN=SMS-Site-CEN -> mSSMSRoamingBoundaries" in the system management folder in theSystems container in AD only has two of my boundaries listed by Active Directory Site name. I assume it's supposed to have all my boundaries listed? The other problem is if I try to manually edit "CN=SMS-Site-CEN -> mSSMSRoamingBoundaries" and put in an Active Directory site, the sites I add disappear. Does this make any sense?

The Subnet on this boundary is 10.129.40.0/24 The client IP is 10.129.40.147/24

Our boundary groups cover different offices in the enterprise. In those boundary groups,the boundary defined is the AD site. There is also one boundary group called site assignment that has all our IP ranges in it. IP Subnets aren't used anywhere as far as I can tell.

First, let me thank all of you for an excellent site and these forums. Been very helpful as I have been thrust into taking over our SCCM environment. I have one primary site that I upgraded to R2 SP1 last weekend. I am not able to get the client pushed to any Windows 10 clients. At first, I seemed to be having a problem with all push installs until I realized something was up with the push account. I have since corrected this, but am still unable to get Windows 10 clients installed through push. Manual installation through the console goes fine. My boundary groups haven't changed and I can confirm I see the client machine in the console under all systems. The way the former admin had our BGs set up was that he had one Site Assignment Boundary Group setup with all our IP ranges. I have since deleted the ranges for my current office that I'm testing in and have added them to the Office Boundary Group and ensured the "Use this boundary group for site assignment is checked" I am using HTTP only, so I don't have any PKI certificates to worry about, but when I look at the client machine in the console it's not showing the self signed certificate either. I'm not seeing any activity for my test VMs in ccm.log and nothing is being generated on the client side so I'm really at a loss at this point. Any advice?