Here is my test environment for SCOM
All are VMs and given minimum requirements for Memory, HDD and Processor
Domain Controller – test.com
IP Address: 192.168.100.250
Operations Database (Ops DB): 192.168.100.230
Root Management Server (RMS): 192.168.100.231
Management Server (MS) + Audit Collection Server Collector (ACS C): 192.168.100.232
Audit Collection Server Database (ACS DB): 192.168.100.235
Data ware House (DW): 192.168.100.236
Preparing the Active Directory
To prepare accounts and groups in Active Directory
1. In Active Directory Users and Computers, create five accounts:
|
Account Role |
Account Name |
|
Management Server Action account |
MgtSvrAction |
|
SDK and Configuration Service account |
SDKConfigSvc |
|
Data Reader account |
DataRdr |
|
Data Warehouse Write Action account |
DataWHWrtActn |
|
Operations Manager Administrator account |
OpsMgrAdmn |
Note:
These can all be domain user accounts. No special privileges are required at the domain level.
Select Password never expires for the individual accounts.
2. In Active Directory Domain Services,
Create a Global Security group for the Operations Manager Administrators.
3. Add the Operations Manager Administrator Account to the Operations Manager Administrators Global Security group.
Operations Manager DB Server
To prepare accounts and groups on the Operations Manager server
|
1) On the server that you are going to install Operations Manager on, log on with an account that has local administrator rights. 2) In the Computer Management tool, under Local Users and Groups, open the Administrators group and add the Operations Manager Administrators Global Security group that you created in step 2 of “To prepare accounts and groups in Active Directory.” 3) Also add the accounts that you created to use as the Management Server Action account, the SDK and Config account, the Data Reader account, and the Data Warehouse Write Action account. 4) Log off and then log back on with the Operations Manager Administrator account (for example, OpsMgrAdmn). |
Install SQL Database standard or Enterprise before proceeding to install OPS Manager Database
To check prerequisites for OperationsManager
1. 
Logon to the system with Operations Manager Administrator account credentials.
2. From your Operations Manager 2007 installation media, double-click SetupOM.exe to start the System Center Operations Manager 2007 Setup on the Start page.
3. Under the Prepare heading, click Check Prerequisites to start the Prerequisite Viewer.
4. In the Components box, select the Operational Database
To install the OperationsManager Database
|
1. Log on to OPSDB Server with an account that has administrator rights and is a member of the Operations Manager Administrators group. 2. On your Operations Manager 2007 installation media, start SetupOM.exe 3. On the Operations Manager 2007 Start page, in the Prepare area, click the Check Prerequisites link to open the Prerequisite Viewer. 4. In the Components box, select the Operational Database component and then click Check. 5. A status of Passed should be returned in the lower pane. If a status of Warning or Failed is returned, click More next to the status for information on why the prerequisite returned that status. Resolve the issues that are identified there and then rerun the prerequisite check. Repeat this process until all prerequisites achieve a passed status. Note: By selecting the Operational Database component, the Prerequisite Viewer checks for the presence of Windows Server 2003 Service Pack 1 and Microsoft SQL Server 2005 Service Pack 1. These are minimum requirements; 6. Click Close. 7. On the Start page, in the Install area, click the Install Operations Manager 2007 link. 8. On the Welcome page click Next. 9. On the End User License Agreement (EULA) page, accept the agreement and click Next.
11. On the Custom Setup page, click the Database component and select This component and all dependent components, will be installed on local disk drive. 12. Select the Management Server, User Interfaces, Command Shell, and Web Console component, and set them to This component will not be available. Click Next. 13. On the Management Group Configuration page, type a name for your management group in the Management Group name box.
15. Click Next. 16. On the SQL Server Database Instance page, select the SQL Server instance that you want to install on from the SQL Server database instance drop down box.
18. Click Next. 19. On the Database and Log File Options page, accept the default value of OperationsManager for the SQL database name or change it as wanted. Ensure that the Data file and Log file locations are set to the shared disk that you created for this SQL instance. Accept the default Database size of 1000 MB or type the starting database size that you want. For more information about calculating a starting database size. The minimum starting database size is 500 MB. 21. On the Operations Manager Error Reports page, optionally choose to send error reports to Microsoft and click Next. 22. On the Microsoft Update page, optionally choose whether you want to use Microsoft Updates and click Next. 23. On the Ready to Install the Program page, click Next when you are ready to start the installation. 24. When setup completes successfully click Finish on the Completing the System Center Operations Manager 2007 setup wizard page |
|
To confirm the existence of the OperationsManager database
1. On the owning node, open SQL Server Management Studio. 2. If prompted, log on to your database engine instance and expand the Databases folder. 3. Check for the presence of the OperationsManager database.
|
