Jaybone Posted December 24, 2015 Report post Posted December 24, 2015 Hi, all. Hoping someone can point out what I'm missing, here. Task sequences to reimage a system are working fine. What we've never done is automatically join the domain - always just did that manually. I copied a TS, added one extra step to the end to join the domain. Testing that TS, what I've found is that systems which already exist in the domain/config manager appear to be completely unable to ever get a working client install. Systems unknown to Config Manager have no problem. The TS with all the exact same steps except the auto-domain-join, client is fine after manually joining the system to the domain. Tried adding a reboot step at the end of the TS after the auto-join. Didn't help. Uninstalling with ccmsetup /uninstall and pushing a new client doesn't help; client push works and installs, but it never hooks up. Forceful uninstall by manually deleting services and ccm/ccmsetup/ccmcache; same as regular uninstall. GUID of the client never shows up in Config Manager - the computer object still has the old GUID from before the reimage, and searching for the new GUID comes up empty. Tail end of the ccmsetup.log has a couple odd entries: Anyone know what I'm missing, here? Quote Share this post Link to post Share on other sites More sharing options...
Jaybone Posted December 24, 2015 Report post Posted December 24, 2015 I should've said before - if I delete an existing computer and reimage with the TS that includes the auto-join, all is well. And that bit of logfile is from an attempted reinstall of the client on one of the affected systems, not the initial install that happens during the TS and before the domain join. Nothing jumped out at me from the logs right after the reimage, but I'll reimage an affected one again and copy off the logs before messing with anything and post em when I can. Quote Share this post Link to post Share on other sites More sharing options...
YPCC Posted December 27, 2015 Report post Posted December 27, 2015 not sure why a client re-install wouldnt work but rather than having domain join at the end of a task sequence, add it BEFORE the sccm agent is installed as normally this is when it occurs. I cant remember off the top of my head exactly where it falls but the step is called "Apply Network Setting" and comes after Apply Operating System but BEFORE "setup windows and configmgr" Do a google image search for: "sccm task sequence network settings" to determine where you should place your domain join step. Domain join is a very routine step that rarely causes issues as you have described. Maybe adding it to the end is causing an issue somewhere. Quote Share this post Link to post Share on other sites More sharing options...
cubspsycho85 Posted February 16, 2016 Report post Posted February 16, 2016 Jaybone, I know this is an older topic, but I'm now experiencing this issue as well after upgrading to 2012 R2 SP1 CU2. Did you figure anything out for this? Quote Share this post Link to post Share on other sites More sharing options...
