They won't be written over, which is the problem.
ADSM cannot update dll's that are in use and locked by NT.

If your backed up NT had maintenance installed (service packs), and the
install media you use is from an earlier NT level, your restored system will
NOT be the right because of those dll's that ADSM cannot replace on restore.

The correct way to do a bare-metal restore of NT, is to reinstall NT into a
recovery directory.  (Call it WinNTR instead of WinNT, for example.  Then
reboot, then do your ADSM restore.

ADSM will restore NT into the old directory, and there will be no conflict
with files it cannot restore.
After you reboot on the old directory, you will be able to delete the extra
recovery directory.

There are also steps you must take with ADSM to get the NT registry restored
properly.
READ THE REDBOOK (or rather the WinNT section of the redbook) before you try
this, or you are just wasting your time!

***************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
***************************************************************



> -----Original Message-----
> From: Sean Stecker [SMTP:Stecker.Sean AT ORBITAL-LSG DOT COM]
> Sent: Tuesday, February 09, 1999 11:26 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Bare Metal Restore on NT
>
> I've just been informed that this afternoon, we will be blowing away one
> of our
> servers and doing a ground up restore from ADSM.  Just wondering if anyone
> has
> any tips or tricks that you may have found while performing this
> operation.  I
> know it's best to learn from your own mistakes, but I'm willing to make an
> exception if anyone has any red flags to alert me to.  My biggest question
> is
> that after we install NT Server and ADSM, what are the consequences of any
> of
> those files being overwritten once we start the restore?
>
> Thanks for your help!!
>
> Sean Stecker
> stecker.sean AT orbital-lsg DOT com