I have new machines that have been added to my domain. SCCM client is not being installed on these machines. I see these machines in the All Systems collection, but no client installed, and some don't show the Site Code. What I've checked: 1) The new machines are within one of the boundaries. 2) There is no ccmsetup folder or log on the client machine. 3) There is no reference to the client machine in the ccm.log file on the SCCM server. 4) The account being used for pushing the client software is a Domain Admin, so shouldn't be having an issue on the client. Anyone have any other tips that I can try to figure this issue out?

What install method are you using? John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

Sorry, forgot those details: I'm using client push installation, using a service account, which is a Domain Admin.

Do the resources actually show as assigned to the site in the console?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

They are all showing No in the Assigned column, as well as having nothing showing in the Site Code column.

So here's a new fact, and maybe you guys can help me figure out why it worked this way: I logged into one of the clients as the service account that I use to push the SCCM client software. I browsed to \\Site_Server\SMS_Sitecode\client and ran the ccmsetup.exe. This was successful in installing the client software to this machine, and this machine now shows as installed when I look at it in my SCCM console. It now shows the site code, Yes under Client, Approved, etc. There shouldn't be a firewall issue between these machines, as the Window's Firewall is completely shut off on the clients, and on the Site Server, only the Public profile is turned on.

When you run the client push wizard select Always install or repair and deslect the option to install install clients in assigned sites. Monitor activity in the ccm.log file.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

Because if the system is not assigned, then by default client push will not attempt to push the client setup to that system. (That's why I was asking the question). It's not that the client can't be assigned, it's just that the default setting says ignore non-assigned clients. One of the checkboxes on the manual push wizard addresses this.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Ok, so that tells me how to "fix" a manual push. But, the original issue I brought up was that the automatic push is not happening. SCCM is discovering the client machines, but nothing is being installed on them.

Ok, so why aren't the machines being assigned? Previously, everything was done automatically; previously being within the last couple of months. One sidenote, the All Systems collection was deleted a month or so ago, and I used a script I found, here I think, to recreate it, and assign the proper collection code to it. Could my issues be stemming from that incident?

Assignment is based upon your boundaries at the time that discovery runs. Without knwoing the configuration details of both of these in your environment, no one can tell you why your systems aren't being assigned. No, deleting a collection has nothing to do with resources.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Same answer here. If they are not assigned, ConfigMgr won't push to them.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

And you can have multiple boundaries, as long as the machine falls into one of them, right?

Correct. What kind of boundaries are you using. If you're suing anything but IP Address range boundaries, stop and change them. Both IP Subnet and AD Site boundaries have design flaws.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Ahh, I am currently using AD Site for a few boundaries. I'll change those. Thanks for all the help Jason.