"replication failures" Of AD? I would fix that first before I fix the sysprep issue.
From: [email protected] [mailto:[email protected]] On Behalf Of Bill Songstad Sent: Thursday, June 20, 2013 3:12 PM To: [email protected] Subject: Re: [NTSysADM] Trust relationships failing Most of the common culprits are in place unfortunately. DNS problems, DHCP issues, improper syspreps, replication failures a veritable smorgasboard of problem causers. The domain is W2K3 the clients are a mix of WXP and up including windows server 2008r2. There are 15 DCs across various "sites" but all have connectivity to about 4 DCs at HQ. So the concept of sites is a little more isolated than reality since connectivity back to HQ is stable and 100-500 MB/s. My most recent problem child was a W2K8R2 server at HQ and it really made me start wondering if this was out of the ordinary. The tenured folks all consider part of mix. The problem on this one seems to be caused by a password mismatch. ADSIEDIT showed the password was a couple of months old and set at a time when the server was offline for a few days. Probably not the same cause as the various workstations of the past episodes. But I can't say for sure since this is the first time I've looked deeply into one of these. Nothing has been imaged in months though. Why a steady trickle of these and not a bunch after 30-60 days? -Bill On Thu, Jun 20, 2013 at 11:49 AM, Erik Goldoff <[email protected]<mailto:[email protected]>> wrote: duplicate machine names, duplicate SIDs, DNS db problems, AD db problems ? On Thu, Jun 20, 2013 at 2:27 PM, Bill Songstad <[email protected]<mailto:[email protected]>> wrote: I've recently moved from a small (50 node) network to a 3500 node network. In my last gig, I never had a single machine lose its trust relationship and have to be rejoined to the domain in 14 years. In my new gig I get 2-3 of these a month. Is that normal? Anybody with a large domain never seeing this? Thanks for any insight, Bill
