We are unable to deliver software packages, nor push SCCM client to any device that connects via our WIFI network. What would be some key points to look at / troubleshoot to identify what maybe the cause of this issue? Larry W. Wilks

For client push check the ccm.log file, it could be a firewall issue. For software packages, check the boundaries and advertisment settings. It's always a client that will connect to the MP not the other way around.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

Are your wifi networks included in your boundaries?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

In ADSS I have two sites configured "SiteA" and SiteB", within Subnets I have our Wifi Subnets ("x.x.23.0/24 x.x.24.0/24 which is superscoped) and the Wifi subnets are associated to "SiteA". Wifi devices can ping my SCCM server and ping the wifi device from the SCCM server. However, the wifi device will not "Pull" the Client Install, nor can we "Push" the Client Install to these devices... The General settings for the SCCM Boundary is using Active Directory site, "SiteA". Network Connection is set to FAST.. Larry W. Wilks

What troubleshooting have you done (besides pinging)? When trying to push the client, have you reviewed the ccm.log on the site server? When trying to pull the client, what method are you using? Have you reviewed ccmsetup.log on the client?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Is the subnet exactly the same in ADSS as the ConfigMGR client sees? If you have X.X.23.0/24 in your ADSS and your client ipconfig shows X.X.23.X/32 it's not the same boundry. They have to match, otherwise it's out of bourdy.MCITP Server Administrator Blog: http://www.nixadmins.net

Looking at DHCP and ADSS both areas are configured /24. The "SuperScope" was created on the DHCP server combining the two subnets, instead of a true superscope using /23. SCCM Boundary appears to only look at the Sites in ADSS and is using the subnet configurations in ADSS Sites. Strange part is I had one laptop that SCCM installed Advanced Client to over copper, and I later added laptop to collection. User then began using wifi and it successfully deployed application package to laptop yesterday. Had exact same model laptop next to it, that would not get the Advanced Client over copper or wifi. Believe we maybe opening a case with MS. Larry W. Wilks