joeman1881 Posted April 8, 2014 Report post Posted April 8, 2014 Recently we started deployment several hundred machines as a start of a 4,000 machine deployment. These machines are all on a child domain of our parent domain that I have been deploying to without issue for months. I want to say that I didn't have issues deploying to the child domain before but for some reason it isn't working now. I have about 120 machines right now that are missing the client. These machines were all imaged using PXE deployments, but for some reason the client didn't install correctly. When I attempt to force the client down from the server, this also fails. It seems the machine attempted to install the client during deployment, and didn't complete correctly, because I can see the folders in the C:\Windows folder. Is there additional configuration I am missing? I will attach the smsts.logs and ccmsetup-ccmeval log I found on an example machine. Thank you in advance! ccmsetup.log ccmsetup-ccmeval.log smsts.log smsts-20140402-132717.log Quote Share this post Link to post Share on other sites More sharing options...
joeman1881 Posted April 9, 2014 Report post Posted April 9, 2014 Please let me know if I'm being too vague. I'm still a rookie so I won't take offense! Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted April 9, 2014 Report post Posted April 9, 2014 The ccmsetup.log shows a successful client installation. What is the exact problem you are seeing? Quote Share this post Link to post Share on other sites More sharing options...
joeman1881 Posted April 9, 2014 Report post Posted April 9, 2014 Yes, this is what I saw as well. When I am looking in the server client, the machines (so far only in the child domain) show as "No" client installed. This issue was reported by our team of level 1 technicians (level 1 means they have some access, but not all). I did a test this morning and here were my results. I created a task sequence in SCCM using my credentials (enterprise admin) and added the machine to the child domain using those same credentials. This allowed the client to install correctly and communicate back to the server so it marked the client as "Yes" installed. I then used the same task sequence in SCCM but edited to use one of my level 1 technicians credentials to add the machine to the child domain. I changed nothing else yet the client again showed as "No" client installed? It's making me think it's permissions related, but how could adding it to the domain with one user vs another cause an issue with the client communicating back to the server? These technicians also are able to successfully install the client and the machines report back as "Yes" installed when deploying to the parent domain. The test I am running now adds the technician 1's security group to the local admin group, THEN installs the client. I probably won't be able to report my findings until the morning. If you have any other feedback please advise. Thank you, -Joe Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted April 10, 2014 Report post Posted April 10, 2014 With their credentials, is the machine joined to the domain? If not, that could very well explain why the client still shows as not installed. Quote Share this post Link to post Share on other sites More sharing options...
joeman1881 Posted April 10, 2014 Report post Posted April 10, 2014 With their credentials, is the machine joined to the domain? If not, that could very well explain why the client still shows as not installed. Yes, the only step in my task sequence that uses credentials is adding to the domain. Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted April 11, 2014 Report post Posted April 11, 2014 But is the machine successfully joined to the domain? Quote Share this post Link to post Share on other sites More sharing options...
joeman1881 Posted April 14, 2014 Report post Posted April 14, 2014 But is the machine successfully joined to the domain? Sorry, I was OOO Friday. Yes it does successfully join the domain. I can ping the machine from SCCM with the FQDN and also the machine to the SCCM Server if that's helpful. Quote Share this post Link to post Share on other sites More sharing options...
joeman1881 Posted April 14, 2014 Report post Posted April 14, 2014 In addition, I noticed that in the "ccmNotificationAgent.log", there are Bgb client agent is disabled, and TCP Listened is disabled notes. These showed up for a few days and not just a repeat of '"Wait 3600 Seconds for event notification". I will dig further into this and see what I can find but I wanted to update the thread in case this is an obvious fix. Update: I also just noticed on these machines that in the Config manager client properties on the suspect machines, the CCM Notifications Agent is Disabled...Hopefully I am getting somewhere now. I just need to figure out how to enable it. Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted April 14, 2014 Report post Posted April 14, 2014 You might want to take a look at ClientIDManagerStartup log file. Quote Share this post Link to post Share on other sites More sharing options...
