> -----Original Message-----
> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On
> Behalf Of MIchael Leone
> Sent: Friday, March 13, 2009 3:09 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: [Networker] Disaster recovery of a Windows client question
> 
> So I am practicing recovering a Windows 2003 member server in a D/R
> situation.  And the manual is telling me to re-install Windows first,
> using the same computer name as before, and (unless I am
> mis-understanding) it says to join this computer to my AD domain.
> 
> Which is impossible, as the SID (Security Identifier) of the client is
now
> different, and won't match the one in AD. So I wouldn't be able to
join to
> the AD, much less proceed to the next step of running a full Networker
> recover of the System State.
> 
> Which clue am I missing here?
> 
> I use NetWorker 7.4 SP2.
> 

Hello - 

Although I have not tested this myself (yet), I would assume that it
updates the computer account in AD to reflect the old SID at some point
during the restore - I have some experience with this using VMWare View
(VDI), as it creates desktops "on the fly" from a single base image that
is already joined to AD, and then it quickly syspreps and "fixes" the AD
computer account/SID to be unique but "tied together" when the desktop
comes online for usage after the final reboot if that makes sense... 

Have you tried it yet?

Regards,
jamie

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER