This guide assumes the selection of Server 2008\2008 R2 in 32 bit or 64 bit mode and the type of installation was Windows and not Core. It also assumes that the server is also a standalone domain server and that the installation of the operating system is the only action that has been taken so far.
Whether you are a programmer or an administrator, your goal is to install SCOM 2007 R2 on a 2008\2008 R2 operating system.
If you have selected a 32 bit installation, you have one to three machines available to you and you don’t care much about performance or the fact that you can’t use memory beyond 3 gigabytes.
You may want to create a standalone domain server, install SQL Server and SCOM on separate machines or on the same machine and then have the other machines join that domain. You may have one machine for developing and have others you can use to install agents on for testing.
On the other hand, you may have selected a 64 bit installation and you’ve got lots of memory available and plan on using the memory resources available. You may a machine dedicated to becoming standalone domain server, one for SQL Server and another for SCOM.
You may have additional machines you can use to join the domain. You may have one machine for designing, developing and testing management packs and others for installing agents on it or one or more of the machines that you’ve joined to that domain
Or, everything will be installed on the same machine and additional machines will join that domain and work with the available resources.
The point is for whatever reason, your here and you want to install SCOM 2007 R2.
Assume this is a standalone server and it will act as a domain server as well. Before you turn it into a domain server, you need to perform the following tasks:
You begin by going to Start\Administrative Tools\Server Manager.
Double clicking this option brings us to the next window.
Double click on roles.
Notice that all of the requirements for being able to install and run SCOM 2007 R2 have already been met. If you are having problems reading them, the installed services are:
1. Active Directory Services
2. Application Server
3. DNS Server
4. IIS Server
Active Directory Services automatically installs DNS Server and there really is no preference with respect to the order of the install sequence of these services. When I was first installing SCOM 2007 SP1, Application Server and IIS Server were the first two roles that were installed.
After that, SQL Server 2005 was installed along with SQL Server 2005 SP1 and then SQL Server 2005 SP2. After that, the Active Directory Services role was installed and then SCOM 2007 SP1 was added to the server.
Over time, however, I discovered that SCOM reporting services had issues with this. Consequently, past SCOM 2007 SP1, I installed Active Directory Services – which installed DNS Server automatically – and then installed SQL Server.
SCOM 2007 R2 requires SQL Server 2008 and SQL Server 2008 SP1to be installed along with the AJAX 1.0 Extensions. Beyond those two external requirements, everything else needed to make SCOM 2007 R2 work is just a matter of selecting roles and features built into Server 2008/2008 R2.
ADDING THE ROLES
Because we are starting with a fresh installation of Server 2008, none of the above services have been installed just yet. With that said, the primary concern here is with how to add a service.
After the Server Manager goes through the process of initializing, you can select roles on the left side and should see a blank screen as above but with a summary of the amount of roles available and that 0 have been installed.
Also, the Add Roles option on the right side should be enabled. The image above shows it disabled. Once enabled, click that option. Click next. You may want to check the checkbox so you don’t have to click next beyond this point.
Once clicked, the list of available rules will be shown as in the image below.
At this point, while the image shows these roles you’ll want to add already installed and disabled, your view will show them unchecked and enabled. Check Active Directory Domain Services and continue along until the software is installed and enabled.
Once installed, click the link for DCPROMO. You can either add the server to an existing forest or create a new domain. Again, once you’ve made your selection continue through the prompts and check to box to automatically reboot once the program completes.
JOINING A DOMAIN
The below image will show you where to go to join a domain.
After you have double clicked on the properties option another window will be created and it looks like this:
Where Computer name, domain, and workgroup settings section of the window is located, you will see a change settings link. Click that.
Now, you have the option to change the existing settings. Click on change.
Notice that since my computer already is a domain server, the options to change the server to a Domain or Workgroup is grayed out. Because your machine is not a domain server, these will not be grayed out and you will have the ability to add the domain.
Depending on how sophisticated your Domain is, you may have to join with specific credentials. And if you do and if you have not done this originally, you’ll want to create a user account on your machine with the same credentials and include that user as part of the administrators group.
You may also have to include IP and DNS information if dedicated IP addressing and DNS lookup are required. Otherwise, your computer may not be able to resolve the Domain name.
Keeping it simple and assuming the DNS resolves, you’ll be prompted to log in with the correct credentials and joining the domain will be complete after reboot.
Either way you have to profile your server, once you’re done, the next step is to add the necessary services and software to install SCOM 2007 R2 on the machine.
ADDING APPLICATION SERVER AND IIS SERVER
When you select Application Server you will also have the option to install IIS. So, you don’t have to install them separately. Once you have included Application Server and IIS Server, you will have the options to choose features you want to include. I have discovered that you can select them all and then tweak them later if they are not necessary.
Certificates, if needed, can be added or you can choose the option to create one automatically. Once completed, you’re ready to install features.
Without going into everything that’s needed, the following five images of what features needed are displayed in those five images.
At this point, you are ready to install SQL Server 2008 and SQL Server 2008 SP1. Please see the detailed how to on this for installation instructions.
As for the AJAX 1.0 install, simply follow this link:
There are three accounts that should be addressed before installing SCOM. Please take a look at the following link:
After this, you are ready to install SCOM 2007 R2.
The exe will ask you where you want to install the image. You may want to have the folder placed on your desktop. The choice is entirely yours. After you have completed this task, go to the folder and look for the installer icon named SetupOM and click it.
This will create a window that will provide you with the option to Install Operationms Manager 2007 R2
Once clicked on, a program will begin that will guide you through the rest of the process.
The next screen will look like this:
If you don’t accept the Licensing Terms, you only have the cancel and back options. Once the radio button is chosen for acceptance, the next button will be enabled.
The next screen allows you to add User Name and Organization.
By default the correct installation options are set for installing SCOM and creating the Operations Manager database:
At this point SCOM performs a test to determine if you have installed everything needed. As it is with my single machine installation, SCOM doesn’t like being installed on my domain server. So it passes but with warnings.
Now I have to provide the wizard with a Management Group Name. The name can be anything you want it to be. I generally use my first name for the group but you can call it anything you want. (Keep your boss happy and name it for the company the Service is going to serve.)
Below this is the option to provide SCOM with the correct group that has permissions to configure Operations Manager.
Now, you can point SCOM to the correct SQL Server database instance and port number. The next screen defines the name of the Operations Manager database as well as its size:
Once you’ve completed this and click next, your next option window involves the Management Server Action Account.
If you are part of a forest, the top level Domain Administrator account would be the most logical choice. If a local account is good enough, select the local system account and click next. By default, the local system account is used to run the SDK:
Again, if you have created an account for this, simply switch to that option and select the account you want to use. Once you click next, you have the choice to decide what kind of authentication you want to use for your web console.
By default it is set for Windows Authentication.
If you want to send error reports to Microsoft, check the checkbox. Click next.
If you want to participate in the Customer Experience Program, select that radio button. Click next.
If you’re ready, click install. Assuming everything installs without issue, you should see this:
It is a good idea to back up the encryption key as if you have to reinstall SCOM or worse, the entire machine, you can save the .mdf and .ldf files along with the encryption key and replace the new files with the old ones and continue to use the database.