[windows2000] Re: Trust problem

  • From: "Sullivan, Glenn" <GSullivan@xxxxxxxxxxxxxx>
  • To: <windows2000@xxxxxxxxxxxxx>
  • Date: Tue, 8 Jun 2004 15:22:07 -0400

Did you create computer accounts in the AD for the new names?
 
I have never had luck getting a ghosted machine to join the domain
cleanly... a RIS'ed machine, sure.  A ghosted syspreped machine... sure.
A ghosted member, using SidWalker or NEWSid, never.
 
Frankly though, I have found that it is better to spend the time getting
your software to deploy via GPO, and using the CD-based RIS install with
an answer file.  Then you will almost never have incompatible image
problems, as the install is a regular cd-based install, not some sort of
clone.
 
My $.02... but I'll spend 5 hours scripting something to save 5 minutes
per task...

Glenn Sullivan, MCSE+I  MCDBA
David Clark Company Inc. 

 

________________________________

From: windows2000-bounce@xxxxxxxxxxxxx
[mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of Bill Beckett
Posted At: Tuesday, June 08, 2004 1:27 PM
Posted To: Windows 2000
Conversation: [windows2000] Trust problem 
Subject: [windows2000] Trust problem 



First time ghosting an XP Pro workstation so maybe I'm missing something
here. In a 2000 domain environment, I've put together an XP pro
workstation as a prototype. First one works fine, no problems. I ghosted
it then went it and ran sysinternals NEWSID changing the computer name
as well as the SID. However, when trying to log into the domain, it
still tells me (The workstation) " The trust relationship between the
workstation and primary domain controller failed". What am I missing? 

Other related posts: