1) Backup your SQL 2005 databases
2) Backup your RMS encryption key
3) Backup your IIS metabase
4) Backup your management packs (unsealed)
5) Backup your files
6) Backup your registry

Step 1) Backup your SQL 2005 databases
First off al we are going to backup the SQL 2005 databases.
- OperationsManager
- ReportServer
- ReportServerTempDB
       

Step 2) Backup your RMS encryption key
The next step is to backup the RMS (Root Management Server) encryption key.
We are going to use the tool SecureStorageBackup.exe, located in the installation directory of SCOM 2007.
       

Step 3) Backup your IIS metabase
The next step is to backup the IIS metabase.
       

Step 4) Backup your management packs (unsealed)
Now we are going to backup the unsealed management packs. The sealed management packs can be downloaded from the vendor’s website again.
       

Step 5) Backup your files
The next step is to backup the SCOM 2007 configuration files. Make sure you backup the following directory.(in my example!!)
- C:\Program Files\System Center Operations Manager
This can also be different, but this is the installation directory of your SCOM 2007 environment.
- C:\Program Files\System Center Management Packs
This is the defualt location of your sealed management packs.

Step 6) Backup your registry
The last step is to backup some registry keys. Make sure you backup the following registry keys.
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager
HKEY_CURRENT_USER\Software\Microsoft\Microsoft Operations Manager
   

In this example i’ve choosen for the “Automaic Computer Discovery”. With the “Advanced Discovery” you’ve some more options to discover you’re clients and servers, for example with a custom LDAP query on your Active Directory to find a specific client or server in your environment.

First off all install the following prerequisites:

- Windows Powershell 1.0
- .NET Framework 3.5 Service Pack 1
- IIS (Internet Information Services
- ASP.NET 2.0
- COM+ components

After this is all done, we can install Microsoft SQL 2005 server for the SCOM database.*
*(Note! When you have more than ten SCOM agents, it’s recommended that you install a dedicated Microsoft SQL 2005 server)

Now Microsoft SQL 2005 server SP2 is installed succesfully, we’re going to prepare our Active Directory for Microsoft System Center Operations Manager 2007.

Create two new user account in your Active Directory. These users can be used for the following tasks:
(OpsMgr-SAA, Server Action Account) to gather operational data from providers, to run responses, and to perform actions such as installing and uninstalling agents on managed comptuers.
Make this user member of the Domain Admins Security Group.
(OpsMgr-SDK, SC Database Server) to logon to the System Center Database Server.
Make this user member of the Local Adminstrators Security Group on the SCOM SQL server*
*(Note! in this example not nessecary because there’s only one server for all the services.)

Create also a Security Group in your Active Directory for managing the System Center Operations Manager Environment.
(OpsMgr-Admins, for managing the SCOM environment)
This group has full permissions to manage within a Management Group.

Now we can install System Center Operations Manager.