Sunday, November 25, 2007

Operating Systems: Recovering from bad app installations

You are preparing to install an application on a user's computer, which is running Windows XP Professional.
How can you ensure that you can restore the system to its current state if the application does not work correctly after it is installed?

1. Use Last Known Good Configuration.
2. Create an Automated System Recovery (ASR) backup.
3. Save a copy of the Registry to a separate location.
4. >>Create a restore point.

Explanation : You should use System Restore to create a restore point. A restore point is a non-destructive way to revert a computer to a particular configuration state. Although some installation programs create a restore point, not all of them do. Therefore, to be safe, you should manually create a restore point before installing the application.

Creating an ASR backup will not meet the requirements. An ASR recovery is a destructive recovery that will reformat the hard disk and require you to reinstall all data files.

Saving a copy of the Registry to a separate location is not the best way to manage recovery. The Registry cannot be replaced manually while you are running Windows XP. Also, it is possible that all configuration changes made by the application will not be saved to the Registry. For example, a .NET Framework application might install a component in the Global Assembly Cache.

Last Known Good Configuration cannot be used to meet the requirements because it is likely you would not know the application is not working until the Last Known Good Configuration has been replaced by a new one. Last Known Good Configuration is updated each time you log on successfully

Objective: Operating Systems