+++++++++++++++++++++++++++++
Consumer Warning: This information applies to restoring USER PROFILES on
Win2K PRO systems.
It does not normally apply to Win2K SERVER. Unless you know what a USER
PROFILE IS, and you are interested in Win2K PRO bare metal restores, don't
read it, it will just give you a headache....
+++++++++++++++++++++++++++++
Hi Tim,
We just tested a bare-metal restore for WIn2k Pro with the 4.1.2 client.
We ran the registry (system object) backup manually. We found that the
logged on user profile is indeed saved in a subdirectory of adsm.sys, and
called NTUSER.DAT, as you said.
We were able to recover the profile by just dragging NTUSER.DAT from
adsm.sys to the appropriate place for that user's profile in Documents and
Settings/userxx subdirectory.
There is one trick to it, though:
You must copy the NTUSER.DAT from adsm.sys to the Documents and
Settings\userxx directory BEFORE that user ever logs on again after the bare
metal restore.
If there is not an NTUSER.DAT file in that directory, then WIn2K creates a
NEW profile when the user logs on, which will be the directory called
"userxx.domainname" or "userxx.domainname.00n", and it will be a copy of the
default profile.
(There may not be an NTUSER.DAT in that directory if the user always backed
up while logged on; or it may be an old copy if the user backed up some time
previously while logged off. Personally I would compare the time stamps and
don't try to recreate the profile if there is a recent NTUSER.DAT copy in
Documents and Settings.)
If you get a new profile created under "userxx.domainname", you either have
to log on again as administrator and copy the NTUSER.DAT file from adsm.sys
to the NEW directory (AND copy the user's shortcuts from the old DESKTOP
directory, plus other stuff like that). Or it is actually easier, In my
opinion, to go into the registry and point the user's profile back to the
old profile directory.
Anyway, the way to do it right is (1) do the bare-metal restore while logged
on as Administrator, not as userxx, and (2) after the bare-metal restore,
copy NTUSER.DAT from adsm.sys to the Documents and Settings directory BEFORE
you ever log on again as userxx. If you DON"T get the right profile when
userxx logs on, look in Documents and Settings to see if you have gotten a
bogus new profile created instead, and work at cleaning it up.
None of the above will make much sense to someone else util they sit down
and LOOK at what is in adsm.sys and in the Documents and Settings directory.
MANY THANKS, Tim, for spotting this conflict in the Redpiece, you saved us a
BUNCH of time and confusion...
************************************************************************
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: Rushforth, Tim [SMTP:TRushfor AT CITY.WINNIPEG.MB DOT CA]
> Sent: Thursday, January 25, 2001 11:23 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Windows 2000 Client RedPiece available
>
> The RedPiece states:
>
> "Backups taken while a user is logged on locally at the system console
> will
> fail
> for the user profile file ntuser.dat for the current logged on user.
> Restoration
> of the user's profile from that backup session will not be possible."
>
> If the system ojbect is backed up when a user is logged on locally, the
> user's ntuser.dat (and usrclass.dat) is placed in the staging directory.
> Can we not copy this file manually as was recommeneded in the NT4 Redbook?
>
> Also, the restore procedure recommended here is:
> - restore the boot/system partition
> - restore system object
> - reboot
> - restore other drives
> - reboot
>
> Is there any reason why the other drives should not be restored along with
> the boot/system partition? This not only saves one reboot, but also may
> prevent the same tape(s) from being mounted and searched again.
>
>
> Thanks,
>
> Tim Rushforth
> City of Winnipeg
>
> -----Original Message-----
> From: Jim Smith [mailto:Jim_Smith AT TIVOLI DOT COM]
> Sent: Wednesday, January 24, 2001 4:12 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Windows 2000 Client RedPiece available
>
>
> The RedPiece "Deploying the Tivoli Storage Manager Client for Windows
> 2000"
> (SG24-6141-00) is now available at http://www.redbooks.ibm.com
>
> - Jim
>
> J.P. (Jim) Smith
> Tivoli Storage Manager - Software Development
|
