Preparing for a computer rebuild or replacement

Preparing for a computer rebuild or replacement

Document number: 69074

A rebuild involves completely wiping all data from the computer and then installing a standard configuration of the operating system and software. This document is intended to help you prepare for most rebuild or machine replacement situations, e.g. conversion of your system from Windows NT to Windows 2000, getting a replacement machine or submitting the machine for repair, or the need to for a fresh build due to persistent errors, system lockups or performance problems.

The exact software that will be installed on the machine depends upon the "build profile." Your "build profile" depends upon your job function. If you don't know what your build profile should be then check with your manager. If you don't supply a specific build profile when you submit your machine for rebuild, your machine will be built with a standard profile. In most cases you can add any additional software after your machine is returned to you.

This checklist assumes that you can do some tasks on your computer. Do what you can do. Be sure to explain to the technician any problems you had as well as what you were able to complete successfully. Ordinarily it is the user's responsibility to properly backup data and to restore that data.

In the instructions below click this icon to see a screen shot or graphic.

	Remove all documents from the desktop and place them in folders under c:\user.
	Review what files and folders will be backed up! Make sure you have everything that is important.
	Backup your files.
	Get a printout of your Connected TLM (Connected Backup) account number and encryption key.
	Copy down the information on your drive and printer mappings and schedule changes so that you can recreate these settings when you get your machine back.
	Take a screen shot of your desktop so you can restore your familiar work environment.
	Make a list of the software that you will need to reinstall.

	Collect the information you will need to submit with the machine.

The information below provides details on recording your work environment and backing up your files. Read as much or as little of it as you like. It is provided to help you through the rebuild process.

Backup

Make sure that you have Connected TLM (Connected Backup) installed.

Look for the Connected TLM (Connected Backup) icon in the system tray. Double-click to launch Connected.
If you don't see the icon in the system tray then look in your Start menu. On the Start menu, select Programs, then Connected, then Connected TLM. (Don't forget, if you are using Windows 2000, click on the expand menu arrows).
If you can't find Connected on the machine you can add it from the software library. For installation instructions see Eureka! document 15223 — How to install Connected TLM (Connected Backup).
If you have not used Connected TLM (Connected Backup) within the last sixty days any account you had will have expired. You will see the message " The requested logon account is not active". If you get that message follow the instructions in Eureka! document 21053 — ERROR: The requested logon account is not active.
Do not create a new account unless the old one has expired.

Review your file storage habits.
Be sure you know what folders you are storing your files in so that you can be sure they are backed up. Check your list of recently accessed documents as a double-check to your file storage habits. Remove all documents from the desktop and place them in folders under c:\user. This is especially critical when you are changing from Windows NT to Windows 2000.
Verify that all the files you need to be backed up will get backed up. See Eureka! document 15221 — How to see which files are being backed up in Connected TLM (Connected Backup). Connected TLM (Connected Backup) does not and should not copy everything on your hard drive. Its function is to backup and restore data.

You must not backup applications. It is a waste of space, often violates licensing agreements, and in most cases results in an application that doesn't work at all or is very unstable.
You should not use it to restore application configurations because the risk of corruption, fatal conflicts and errors is very high.
If you created the file or document then it is probably data that should be backup up.
If you merely made some selections to change the behavior of an application that is usually a configuration file, and in most cases should not be backed up. There are a few known exceptions; they are in the list of files backed up by default.
Review Eureka! document 15293 — Files backed by default in Connected TLM (Connected Backup). Compare that list with where you are storing your files. Decide if you will need to make changes to back up your important data files. See Eureka! document 11224 — How to select files for backup by Connected TLM (Connected Backup).
Review Eureka! document 11262 — Important files to back up. Important! Note that the locations of some files change between Windows NT and Windows 2000. You will want to keep that in mind when you restore the files. The changes will affect many shortcuts so you won't be restoring those.

Back up your files. See Eureka! document 11225 — How to do a manual backup.
Get your Connected TLM (Connected Backup) account number and encryption key. For more information, see Eureka! document 15222 — How to get your Connected TLM (Connected Backup) account number and encryption key. Save the information as a draft email or print it out. You may need this information to restore your data after your machine is returned.
You will want to make a record of your personalized settings:
Your drive mapping (network servers you use and their drive letters).
Your printer mapping.
Any changes you have made to the schedules for certain regular tasks like Norton Speed Disk, AntiVirus software, or Connected TLM (Connected Backup), etc.
The arrangement of your desktop icons
The location of the Office Bar (Quick Launch bar in Windows 2000)

Make sure you copy down the information on your drive and printer mappings and schedule changes so that you can recreate these settings when you get your machine back. Take a screen shot of your desktop if you want to try to recreate your familiar work environment. A screen shot of your drive mappings wouldn't hurt. Either print these out or save them as a draft document in Lotus Notes.
Also, note that you will lose certain information that is cached based on your prior accesses such as:
Server names that aren't currently mapped but were mapped in the past.
Run entries on the Start menu (programs, print servers, file servers).
The current AT schedule (if you are using the AT command to schedule miscellaneous tasks on NT).

For most users this is not an important issue, but possibly a minor annoyance.
List any software that you will have to reinstall after the rebuild or replacement. Check to see that each is in the Software library or you have the install disks.
Make sure you have provide the required login and files for the network and restoration of Lotus Notes to the extent these are available to you.

You should receive an email asking for:
Make sure that your machine is expected before you take a trip to the repair/rebuild location. The technicians may need to leave the office to resolve some problems so let them know when you are on your way.
Unless instructed otherwise take only the computer itself. Leave cords and accessories in your office.

The above steps will allow you the best opportunity to recover quickly after your machine is rebuilt or replaced.

Did you open Connected TLM (Connected Backup), look in the files and folders where your important files are stored, and verify that there is a green check mark indicating that the files will be included in the backup?

Did you copy down your drive and printer mappings so you can recreate them later?

See Eureka! document 69075 — Recovering from a Computer Rebuild for restoring your files and work environment.