In the spirit of Linux, which is teaching us all that more brains working on
a problem give you better results, and as a Thank You for all the people on
this list who have provided me with tons of help, I am posting a copy of my
Bare Metal Restore procedures for Win2K Professional. Due to size
constraints, it is broken into 2 WORD documents. The first is attached
here, the second will be in the next post.
Many thanks to Daniel Thompson, who got me started with the basic steps.
PLEASE READ the caveats below BEFORE you try these procedures, then use at
your own risk:
* These instructions are for Win2K PROFESSIONAL, not Win2K server.
Please don't ask me questions about Win2K server, I don't know.
* These instructions are for a Win2K system created fresh from the
Win2K install media, NOT a Win2K system that was upgraded in place from
WinNT. (While I'm pretty sure the procedure is similar for an upgraded
system, they are different and I haven't tried it yet.)
* If you don't follow these instructions EXACTLY, they won't work,
exactly.
* If you need clarification on my instructions, you can email me
directly and I will at least attempt an answer, if I know the answer.
Please do NOT send me back replies of the form "I tried this and it didn't
work". There are MANY things you can do to make it NOT work, and since I
can't see your client machine directories I won't be able to help you. The
idea is for other people to use these instructions as a base, figure out how
to apply them to other situations, and post THAT information back to the
list!
* I have used these instructions successfully in testing many times
and once for a real bare-metal restore. They have worked at server levels
ADSM 3.1.2.42 and TSM 3.7.2 (AIX). Client backups were run from 3.1.0.6,
3.1.0.7, or TSM 3.7.2.01 clients. The bare metal restore was run with the
TSM 3.7.2.01 client code; I was unable to get the RESTORE itself to work at
any earlier client level.
* You should expect to make some changes to customize these procedures
for your own system/network. Plan to do a lot of testing BEFORE you need
these instructions for real.
* These instructions are set up for Win2K Professional machines in a
MICROSOFT network, so that when a user boots, he normally logs into the
Microsoft domain with a network id. When you see the word DOMAIN in the
text, it is referring to the Microsoft WinNT network DOMAIN, not the
ADSM/TSM DOMAIN. If your WIn2K Proff machine is not in a network, just
ignore all those references in the instructions. If you are in a NOVELL
network, you will probably have to modify the instructions somewhat.
* You will find these instructions are written in FAR TOO MUCH DETAIL
for most TSM administrators! For TSM heavies, you will find they boil down
to a list you can scibble on the back of your hand. I know you guys don't
need instructions for every mouse click; my target audience was our desktop
support staff, some of whom don't get much experience with ADSM/TSM before
they get the panic call to rebuild a WIndows machine.
* You will see references in the document to something called
"adsmreg.bat". This is a .bat file in the user's Win2K startup group that
runs the command "dsmc regback user curuser" when the user logs on. This
bat file is necessary in SOME environments to insure a backup of the user
profile at client levels 3.1.0.6 and below. If you are one of the sites
that use it, you know it. If you don't use it, ignore it in the
instructions.
* There are many references to the "User Profile". In fact, these
instructions would boil down to about half a page except that we really want
to be sure the User Profile comes back correctly. If at all possible, dig
out your Win2K or WinNT book and learn something about user profiles BEFORE
you try this at home, it will help you understand what is going on. In
general User Profiles are only an issue for WInNT Workstation or Win2K
Professional, because the profile retains most of the desktop customization.
Profiles exist on Win2K and WinNT servers, but usually nobody cares about
restoring them because little customization is done for administrative ids
that log on to the Windows server console.
I hope this helps somebody as much as you guys have helped me.
Wanda Prather
"My opinions, and nobody else's...."
<<ADSM-L Bare Metal Recovery for Win2K Professional.ONE.doc>>
|
