MrWillyWonka Posted November 14, 2014 Report post Posted November 14, 2014 Hi, I work on four independent sites and some time ago I configured SCCM 2012 on all sites (primary site for all). All has been working very well (much better than SCCM 2007) until last week when I did a build of about 20 machines (Windows 8.1 Enterprise x64), the first 15 or so deployed successfully then all of a sudden the last few builds got an error message upon logon: "The User Profile Service Failed the Logon" Now any new builds I do gets the error message after a successful deployment. After a little digging around I found that in the security settings in one of the dirs in system32 a message stated that it could not connect to AD. I reset the DC on server 2012 to no avail, reset the DC on server 2008 and the problem went away. Funnily enough the 2008 server was due for decommissioning earlier this week anyway (and has now been demoted and turned off). but the problem still occurs. The few machines which were fixed by the DC reset are still working as they should. There doesn't seem to be much information about this error but does anyone have any ideas on what is causing this? I have done a manual install of Windows and manually added to the domain and it works fine. Also the message in the security tab about not being able to connect to AD is no longer there. Usually I can fix SCCM issues but this one has me stumped. There is nothing in the error logs too and all SCCM logs come back with no errors. I know there has been some mention of IEAK causing this but we do not use it. We do use McAfee but I have tested an install without McAfee and problem persists. Any help appreciated! Quote Share this post Link to post Share on other sites More sharing options...
MrWillyWonka Posted November 20, 2014 Report post Posted November 20, 2014 I know nobody commented on this post but my problem is resolved. I left the affected machines off over the weekend and when I returned after the weekend they all logged on as normal. I can only suggest that somehow the clients were still trying to access the old DC but they have refreshed their connections. Not very technical but all is well. Quote Share this post Link to post Share on other sites More sharing options...
