I was unsuccessful before in uploading these procedures as a WORD doc, so this attachemnt is a .txt version. I suggest you copy and paste the text into WORD instead of trying to print from Notepad; WORD will wrap the txt for you before printing. 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 Prof Part 1.txt>>
TSM Bare Metal Recovery for Win2K Professional Part 1 Requirements PLEASE READ THESE INSTRUCTIONS CAREFULLY. The instructions below are very detailed, but the procedures themselves are actually pretty simple. However they WILL NOT WORK unless you execute them exactly as stated, in the right order. These procedures have been tested for a Win2K system built from the install media. They will NOT work for a system that was converted in place from NT 4.0. In addition: * The machine being rebuilt must be the same one that failed, or one with identical hardware. (The reason is that the registry contains hardware-specific information, and the registry will be restored as one of the last recovery steps.) * Current TSM (or ADSM) backups of user data, software, and the registry must be available. * The restore must be run using TSM client software at version 3.7.2.01 or later. * When the instructions in this document say to reboot, you MUST shut down and restart Windows. Just logging off and logging back on again will NOT accomplish what is required (and in fact will make it more difficult to recover the user profile.) If you have problems with any of these instructions, please go to the Troubleshooting section. . Preparing the Disk for Recovery There are three things you have to do before starting the TSM restore of the disk. Step 1: Install a new copy of Windows 2000 and recustomize TCP/IP Step 2: Reset the client's password on the TSM server. Step 3: Reinstall the TSM client code Step 1 The first thing to do is install a bootable copy of Win2K on the disk to be recovered. You can reinstall from the media, or recreate it with GHOST. The objective is to get a minimal bootable Win2K system that can communicate with the TSM server via TCP/IP, and nothing else. When building the new disk: * Do NOT install the standard apps (Office, Exchange, etc.) * Do NOT create any user accounts other than administrator. * Do NOT add the workstation to the Windows network domain. The system being recovered should not communicate at all with the Windows domain controller until AFTER all the recovery is complete. * DO give the new machine exactly the same Windows network id as the machine being recovered. * DO recustomize the network TCP/IP connections so that the machine is capable of pinging the TSM server. Step 2 Reset the client's TSM password on the TSM server to something you know. You can do this by starting IE on the system you have just rebuilt, or by starting IE or the ADSM admin GUI on your own PC, or by having another TSM administrator do it for you. Do not skip this step, even if you think you know what the password is. This is to make sure the TSM client code on the machine to be restored (such as the TSM Central Scheduler and adsmreg.bat) cannot run without prompting you for the password first. Step 3 Install the TSM Client code You must install the TSM client version 3.7.02.1 or later. Here are instructions for installing from the distribution copy on the server: * Open My Network Places * Go to: \\servername\adsm\ClientCode (you will be prompted to enter your network password) * Look for the directory for Win32.TSM 3.7.2.01. (or later) * Drill down through the subdirectories to the DISK1 subdirectory. * Click on SETUP.EXE to start INSTALLSHIELD. * Take ALL defaults. Keep clicking NEXT/Finish until the install is complete. * TSM will automatically open the README file and the TSM Client Configuration Wizard. * Choose "Help me configure the TSM Backup Archive Client" (Next) * Choose "Create a new options file" (Next) * Fill in the TSM client NODENAME (Next) * Choose TCP/IP (Next) * Fill in the TSM Server address: ADSMSRV1 * Fill in the Port: 1500 * (Next) * Skip the include/exclude lists; must select (Next) * Click FINISH * If TSM complains about any errors, click the BACK button and correct them. * When the Configuration Wizard finishes, it will start the client and prompt for the NEW TSM password that you set in step 2 above. Running the TSM RESTORE You should be logged on to Win2K locally as administrator, with the TSM GUI client started. Step 1: Restore the C: drive * On the primary TSM window, click the RESTORE tab * The top level of the tree should show the ADSM name of the machine to be restored. Click the grey box to the left of the drive to be restored. * Click the plus sign to expand "File Level". * Click the gray check box to the left of the drive to be restored. * Click the OPTIONS button (the unlabeled icon next to the ESTIMATE button). This opens the "Modify Restore and Collision Options" window. * Pull down the Action for Files that Exist option; select Replace. * Now check the Replace even if Read Only/Locked option. * Leave the other options in the window at defaults. * Click the OK button. * Now click the RESTORE button at the top. This brings up the "select destination" window. * Select "Restore to original location". * Now click the RESTORE button. * You can optionally click the white icon in the RESTORING FILES window to get a more detailed description of what is going on. You should get NO errors and NO prompts during the restore. If you do, go to the Troubleshooting section on P. 6 of this document. If you still get prompted, or if you get errors, please click the VIEW button to get a detailed list of the errors and let me know what they are. Step 2: Restore the event logs (optional step - most people don't care about their event logs) * Close the TSM RESTORE window by clicking the X in the upper right hand corner of the inner window. Go back to the TSM initial window with the BACKUP/RESTORE/ARCHIVE/RETRIEVE tabs. * Click the RESTORE tab again. * Expand the System Objects branch of the file tree. * Click the gray box next to Event Logs. * Click the RESTORE button. * Select "Restore to original location". * Click the RESTORE button again. * There should be no errors during this part of the restore. Step 3: Restore the registry * Go back to the main TSM window with the BACKUP/RESTORE/ARCHIVE?RETRIEVE tabs. * Select the RESTORE tab. * Expand the System Objects branch of the file tree. * Click the gray box next to Registry * Click the RESTORE button. * Reply YES when prompted to Activate Registry Key. * You should get a message saying "machine must be rebooted". Before you reboot, do the next section, Determine Whether to Restore the User Profile. If you see any errors during the registry restore, please go to the Troubleshooting section.. Determine Whether to Restore the User Profile The Windows user profile contains all the customization the user has done on the desktop (fonts, icons, etc.), Control Panel changes, wallpaper, and customization for many applications, such as Outlook. It may be necessary to restore the user profile, in addition to restoring the registry (which you did in the last step) to get the customization back. This section and the next one contain the instructions needed to restore the user profile. * Go back to the TSM main window with the BACKUP/RESTORE/ARCHIVE/RETRIEVE tabs. * Click the RESTORE tab. * In the TSM RESTORE window, click the plus sign to expand "File Level". * Click on the plus sign to expand the C: drive. * Expand the adsm.sys directory. * Drill down through Registry, then (machine name), then Users. You should see a directory matching the userid, ex: user23 * Click the yellow icon to see the backups in this directory. * There should be a file whose name looks something like this: S-1-5-nn-xxxxxxx-yyyyyyyy-zzzzzzzzz-qqqq This is the backup of the user's desktop customization taken from the Registry. Make a note of the backup date for this file. (If you can't find a file by this name, go to the Troubleshooting section of this document, P. 6.) * Now in the TSM RESTORE file tree, expand the Documents and Settings directory. * Expand the subdirectory that matches the userid, ex. user23. * Look for the file called ntuser.dat. This file also contains the user desktop customization information. Make a note of the backup date for this file. Now compare the two backup dates you wrote down. * If the ntuser.dat file is newer (has a more current backup date/time) than the file in adsm.sys, you do not need to restore the user profile. Skip the next section of this document and go to the CLEANUP section on Page 6. * If the ntuser.dat file is older than the file in adsm.sys, you should do the following section, Restoring the User Profile. Restoring the User Profile * REBOOT. * Log on to the Windows network as the user whose profile you are trying to restore. (You will need the user's network password. If you cannot log on the network, go to the Troubleshooting section on Page 6 of this document.) When the system starts up, you may see the TSM window pop up for adsmreg.bat. It will prompt you for the TSM password again. DO NOT RESPOND to this prompt at this time; just close the window. Note: At the point, the desktop customization you see is taken from the ntuser.dat file. * Start the TSM Backup Client GUI. * Click the RESTORE tab. * Expand the System Objects tree. * Expand Registry. * Expand HKEY_USERS. * Check the gray box for Current User registry key. * Click the RESTORE button. * Reply YES to the prompt to activate the registry key. * Go on to the next step, CLEANUP. Cleanup * REBOOT. * Log on to the network as the user whose profile you restored. (If you see a white background with an error message about Active Desktop, go to the Troubleshooting section on P. 6.) * The adsmreg.bat window will pop up again, and ask for the TSM password. Type the password and press ENTER. At this point, you should see the restored user profile/desktop customization in effect. * Go to Start, Settings, Control Panel, Admin Tools, Services. * Stop the TSM Central Scheduler, then restart it (this is necessary to pick up the new password.) You're done.
