Jump to content

Scott46517

Members
 View Profile  See their activity

  • Posts

    4

  • Joined

  • Last visited

Reputation

0 Neutral

About Scott46517

Personal Information

  • Occupation
    Systems Administrator
  • Location
    Colorado

Employer (optional)

  • Company Represented
    Englewood
  1. Scott46517
    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.
  2. Scott46517
    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?
  3. Scott46517
    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.
  4. 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.
×
×
  • Create New...