SCCM 2012 is not pushing FEP to all Devices

[Scott46517]

I'm having a problem with SCCM 2012 not pushing out FEP to all machines in the Devices column. It seems just like the local machines in same IP address range as the server are getting the FEP. Any answers? I'm new with SCCM. Thank you.

[FN-GM]

Have you setup your boundary's correctly? Do they have the SCCM client installed?

[Scott46517]

Have you setup your boundary's correctly? Do they have the SCCM client installed?

Yes. I even have the IP range set. The client won't install either. Seems like it's only installing on the computers with the same subnet as the server (e.g 192.168.1.xx). Anything else without the 192.168.1.xx will not install client or FEP. Could it be a certificate issue? I have given all the permissions in AD and the AD Discovery went through without a hitch. I also have the firewall turned off as well.

[FN-GM]

I doubt its certificates. Are 100% sure your boundaries and boundary groups are correct?

[TheScarfedOne]

Check your Client Settings, as in Big changes in Configuration Manager 2012: Client settings | TechRepublic. You should create a new Settings option, and ensure that you have activated the option for FEP.

[FN-GM]

Check your Client Settings, as in Big changes in Configuration Manager 2012: Client settings | TechRepublic. You should create a new Settings option, and ensure that you have activated the option for FEP.

The client isnt even installed on these machines...

[Scott46517]

The client isnt even installed on these machines...

12.png

The IP address range covers the complete scope and also has the AD site. The computers from 192.168.1.0 to 192.168.1.254 have the client and FEP installed and running. All IP from 192.168.2.0 to 192.168.255.254 have no client or FEP. Very puzzled. Is there something I am doing wrong?

[sonofsanta]

Can config manager even see the computers to state that they're unmanaged?

Looking at your settings above, I would try adding your problematic ranges as subnets, in the same way as 192.168.1.x is. FWIW all my VLANs are added as individual IP address ranges - although mine are out of date, as they were set before one /24 range was split into two /25s, so the top range should have worked for you anyway.

Are all the ranges added into the boundary group?

May not be relevant, but if you have AD discovery on, are all your VLAN subnets listed correctly under AD Sites & Services on your DC?

EDIT: looking back at it, I think my address ranges were created automatically based on my AD Sites > Subnets entries, so try updating the info there.

If you're VLANned (and hence the different subnets), are you sure it's not a more fundamental routing issue?

[FN-GM]

Try deleteing a few of the machines and rediscovering them. I just remeber this fixed an issue i had when i first installed SCCM 2012

[Scott46517]

Try deleteing a few of the machines and rediscovering them. I just remeber this fixed an issue i had when i first installed SCCM 2012

I found out what it was. Group Policy. Had to allow WMI traffic to go through the whole network. It's working great and I want to thank all of those who helped and let everyone know that this forum definitely helped me.