stuyd

This is the article I was talking about: Machine Account Password Process - Ask the Directory Services Team - Site Home - TechNet Blogs

Hi sted, As part of our rollout the names of any existing machines were changed by prefixing them with a 3 character suffix, also a large number were replaced with new machines. As we use the machines serial number with the 3 character prefix there is no chance of the names been the same (he says crossing his fingers)… Does anyone know how the machine password process works when it comes to Windows 7 and Server 2003 Ad? I have found an article from 2009 but the Reg. keys that store the current and previous password that are talked about in this article don’t exist in Win 7 (at least not in the same location) and the attributes on the server where they should be stored are empty…

I am having a similar issue. We have recently upgraded around 1200+ machine to Win 7 SP1 using SCCM. Over the last 3 months or so we have been getting jobs logged for trust issues. In most cases the fix is as simple as a reboot but in some we have to do the whole disconnect and re-join the domain.... In most of the cases the issue happens when the user stays logged into their machine overnight . The next morning when the user goes to unlock there machine they get the trust issue. Unplugging the network cable allows the user to unlock the machine and carry on (once the cable is plugged back in that is...). I think the issue started happening when we had DNS scavenging turned on but I can't be sure. I know we do have issues where DNS appears to be slow to replicate so we need up with multiple machines with the same IP. Also the issue isn't happening on the same machine more than once (that we can tell) as of yet so it makes it very hard to troubleshoot. Any thoughts??