I have a few laptops that are built from MDT and added to the domain.  ConfigMgr will discover the machines but they are not installing the client.  There is no CCM or CCMSetup directory in the C:\Windows.  

What am I missing?

Is there a log I can view to see where the install is throwing errors?

Check the CCM.log file on the CM12 Server. Did you enable Client push Installation and configure the Client push Installation account?

• Edited by dekac99 16 hours 32 minutes ago

Yes I have both of those configured and set.  If we push OSD or even build machines with a disk, they will get a client.  So it seems these are hit and miss deployments.

Thank you for the quick reply, I will check that log and keep you updated.

CCM.log looks good, there are no errors, warnings.

I see these entries in the adsysdis.log:

INFO: discovered object with ADsPath = 'LDAP://PDC-LOC-02.DOMAIN.LOCAL/CN=WIN7-SPARELT4,OU=Loaner Laptops,OU=Information Technology,OU=Computers,OU=Location,DC=Domain,DC=local' SMS_AD_SYSTEM_DISCOVERY_AGENT 4/28/2015 12:02:08 AM 3280 (0x0CD0)
WARN:  Failed to get following optional attributes, userWorkstations,manager,department,displayName, SMS_AD_SYSTEM_DISCOVERY_AGENT 4/28/2015 12:02:08 AM 3280 (0x0CD0)
INFO: DDR was written for system 'WIN7-SPARELT4' - D:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\adsmdt5d.DDR at 4/28/2015 0:0:2. SMS_AD_SYSTEM_DISCOVERY_AGENT 4/28/2015 12:02:08 AM 3280 (0x0CD0)

Discovery has nothing to do with client push.

Looking at logs isn't just about looking for errors or warnings. You need to find the section referencing the client in question and examine exactly what it says, line by line.

I looked for any errors or warnings as well as anything that had the machines name.  The machine was never mentioned.  So I am guessing it isn't getting that far in the process.  Is the CCM.log the next log after the discovery?  

ccm.log is the only log file that lists client push activity. The log wraps quickly though. Often when troubleshooting client push, it's best to initiate a manual push to the client in question and watch the log file explicitly.

Also, for the client in question, does the resource show a site code in the All Systems collection?

There is no Site Code listed for this machine.  I am able to manually push the client without issues, just for some reason it will not install automatically.  Discovery, Client settings and boundaries are set.  Also the machine has the ConfigMgr Cert as well.

Without a site code, the ccm process will not automatically push the client agent to it.

Thus, you need to examine your boundaries and boundary groups enabled for site assignment to ensure the resource is contained within a boundary contained within one of these boundary groups.

Check the CCM.log file on the CM12 Server. Did you enable Client push Installation and configure the Client push Installation account?

• Edited by dekac99 Tuesday, April 28, 2015 3:13 PM

I have double and triple checked my boundaries and boundary groups.  I guess I will have to get Microsoft on the line and check as well.  Not sure what I am missing.  I will update once I get this running.  

Thank you again Jason.

What kind of boundaries are you using?

I use the IP Address Range that match in AD Sites.

Also I just got off with Microsoft and we found some residual nodes from our previous Site Server in the ADUC > System > System Management OU, and a _tcp entry for the old site as well in DNS.  

Cleaned those up and things are running better now.