Operations Manager 2007 SP1 is supported on Windows Server 2008. Both Windows Server 2008 and Operations Manager 2007 SP1 hot fixes are required. Official supported scenarios with the required hot fixes can be found at: http://go.microsoft..../?LinkId=119299 Operations Manager 2007 is supported on Windows Server 2008, no hot fixes are required.
Download and install the following 4 hotfixes on your SCOM server and on any Windows 2008 Server that will be monitored by SCOM.
Below are the X86 hotfixes:
Below are the X64 hotfixes:
Once they are all installed, reboot.
Download the System Center Operations Manager DVD from Technet or MSDN. The file I used here for this guide is the Service pack 1 version of SCOM 2007 called en_system_center_operations_manager_2007_with_service_pack_1_x86_dvd_x14-05942.iso, once downloaded, burn to DVD or mount with daemon tools or similar.
Note: Microsoft offers a 180 day Evaluation of SCOM 2007 SP1 here.
Step 1. Install SCOM 2007 sp1
Login to the SCOM server as a member of the OpsMgrAdmins Security Group.
Double click on SetupOM.exe from the OpsMgr 2007 installation media.
In the System Center Operations Managager 2007 Setup window, click Install Operations Manager 2007
When the Welcome to the System Center Operations Manager 2007 Setup Wizard screen appears, click Next
On the End User License Agreement screen, select the I accept the terms in the license agreement option, and then click Next.
Enter your product registration values and key and then click Next.
On the Custom Setup screen, verify that all options are set to This component, and all dependant components, will be installed on the local disk drive and change the default installation location to D:\Program Files\System Center Operations Manager 2007\, and then click Next.
The installer will now do a Prerequisites check and if you forgot any component such as .NET or Powershell then it will fail, however you may also get a warning if the amount of RAM present is less than 2GB (as in my case, I have 512 on this virtual machine for the lab).
You can view the log or click next to continue.
Note: If you have failed the Prerequisites check you cannot continue until you resolve the failures.
Enter SCOMMGMTGRP as the Management Group name and change the default Administrator by clicking Browse and point to the OpsMgrAdmins Security Group we created in AD
click Next to continue
Leave the Database Instance and Port settings as they are, click next
On the management server Action Account page, accept the default Domain or Local Computer Account option, enter the credentials of the management server Action account (SA-OpsMgrMSAA), and then click Next.
Leave the Database and Log file locations as they are, in a production environment you would want to separate the Log and DB files to separate SAN drives, but this is only a lab so it's fine like this, in addition, in production with 10 or so Management Packs you'd want to increase the size of the DB to 5000mb, the default 1000mb is fine for lab.
For Management Server Action Account enter the credentials of the management server Action account (OpsMgrMSAA) that we created in Part 1, and then click Next.
For the SDK and Config Service Account screen, select the Domain or Local Account option and enter the credentials for the SDK and Config service account (OpsMgrSDK) that we created in Part 1, and then click Next.
For web console Authentication configuration leave it as default,
For the Customer Experience Improvement Program screen, make your choice and then click Next.
and for the Microsoft Update screen, make your choice and then click Next.
finally on the Install the Program screen click Install.
after a long while, you'll see the completing System Center Operations Manager screen, leave both options checked.
the console will open up and you can now start using System Center Operations Manager 2007 SP1. Congratulations !!