------ =_0_MIME_Boundary_22211.342fe472.horizonw.ci.in.ameritech.com
Phil:
Phil:

  We were able to do a bare metal restore of NT.  We reinstalled NT to
a different directory then its original one.  We then booted NT from
this directory, installed ADSM and restored everything from ADSM.

  The registry takes a separate ADSM restore after restoring the files.
You don't have to restore the whole registry, only a few hives.  This is
explained in the ADSM bare metal restore redbook.

  After restoring the files and then the registry, we rebooted our
original NT system.  Of course boot.ini gets involved here, but the way
we restored everything with ADSM our reboot to our original system
worked fine because boot.ini was overwritten by our ADSM restore.


  Good Luck

   Ron Heflin
------ =_0_MIME_Boundary_22211.342fe472.horizonw.ci.in.ameritech.com
Phil Chissell wrote:
Phil Chissell wrote:
>
> I am running ADSM Server 2.1.0.13 and Client 2.1.06 on NT.
>
> My problem is:-
>
> - I performed a full backup (including the registry) of an NT server
via ADSM.
>
> - I then trashed the box, re-installed NT and then the ADSM client.
>
> - I restored all the files from the ADSM server.
>
> - I then restored the (full) registry.
>
> - I reboot the machine but it hangs
>
> I have repeated the above procedure many times but I always get the
same
> result.  My initial reaction is that I probably shouldn't be
performing a
> full restore of the registry.  Does anybody know what the procedure is
for
> fully restoring an NT client via ADSM?
>
> Regards
>
> Phil

------ =_0_MIME_Boundary_22211.342fe472.horizonw.ci.in.ameritech.com--
=========================================================================