SCOM 2012 beta – new install considerations

July 18, 2011 Leave a comment

A few things to be aware of before you try and install SCOM2012:

SQL needs Full Text Search Service … this is becoming a standard requirement in most System Center products to leverage advanced searching capabilities.

Reporting is no longer a seperate install but is part of the initial installation routine. Therefore, to install SCOM, you MUST install Reporting at the same time.

Operations Manager Administrators Group. You no longer get asked for the Operations Manager Administrators Group. Instead setup automatically assigns the Administrators group on the local computer to the Operations Manager Administrators role. You must be logged on with an account that has local Administrator rights to run Setup on the first management server that you install; this ensures that you can open the Operations console after Setup is completed. Best practice is to create a global OpsMgr Admins Security Group and a local OpsMgr Admins Security Group on each Management Server. Then add users who will have this role to the global group, and then add this global group to the local group. Then in the OpsMgr console, re-assign the OpsMgr Admins role to the local windows OpsMgr Admins security group.

Operations Manager Admin Role

Operations Manager Admin Role

There isn’t a Root Management Server anymore. Well, that might not be 100% true depending on how pendantic you want to be but I’ll go into that in more detail in another article. In SCOM 2012, all Management Servers are created almost equal, similar to the move from NT4 domains to Windows 2000 Forests. But as with that move, we had a PDC emulator. In SCOM 2012 we have an RMS emulator that enables legacy management packs which rely on the RMS to continue to function in SCOM 2012. This role can be moved \ managed using PowerShell – there are new PowerShell cmdlets for this:
– set-scomrmsemulator
– get-scomrmsemulator

RMS Emulator Role

RMS Emulator Role

Resource Pools. We can now create a resource pool for Network Devices and non-Windows Servers for failover.

Note that windows agents do not use resource pools for failover which continues to function exactly the same as in SCOM 2007.

Also that Resource Pools only apply to the “Health Service” functionality at present and not to SDK functionality. So you can’t use Resource Pools for OpsMgr connectors or for Reporting failover.

More also on Resource Pools in a later blog.

System Center Operations Manager 2012 Public beta released

July 18, 2011 Leave a comment

Guess the title says it all – http://www.microsoft.com/download/en/details.aspx?id=26804

I’ll be running through some of the new features and requirements in a series of blogs so keep watching for more info!

Categories: SCOM2012

Operations Manager 2007 R2 on SQL 2008 R2

June 23, 2011 Leave a comment

The official documentation for setting this up is to be found on technet http://support.microsoft.com/kb/2425714

However, Vivia Xing has found a couple of other very useful articles to assist in implementing this configuration:

System Center Orchestrator 2012 : Installation step by step

June 19, 2011 Leave a comment

I was going to run through a step by step install but noticed that Christopher Keyaert, a regular poster on the Operations Manager forums, has already completed an excellent walk through here.

Christopher creates the Orchestrator database and manually assigns the Orchestrator service account db_owner rights part way through the install which gets around the issue mentioned in my post below.

Categories: SCorch 2012

System Center Orchestrator 2012 install error

June 18, 2011 2 comments

If you create the Orchestrator service account as a local windows administrator with log on as a service rights then you might well see the following error at the end of the install:

“Post-install configuration failed: : Threw Exception.Type: System.ServiceProcess.TimeoutException, Exception Error Code: 0x80131906, Exception.Message: Time out has expired and the operation has not been completed.”

If you check in the SQL Server error log you’ll see “login failed” errors for the Orchestrator service account.

This is because the install doesn’t assign any SQL rights to the Orchestrator service account. The database gets created by the user that is logged in and doing the install who will need SQL SysAdmin rights. But the Orchestrator service account still needs rights on SQL to function.

No definitive list of rights is provided yet but after the install (when the Orchestrator database has been created), I created a login to SQL for the Orchestrator service account and made it a db_owner on the Orchestrator database. Then I rebooted the box. This resolved the error and it all seems to work again.

Categories: SCorch 2012

System Center Orchestrator 2012 beta released

June 18, 2011 Leave a comment

Move over Opalis – there is new kid on the block. System Center Orchestrator 2012 beta is now available with some great training videos and documentation.

All the details on the Orchestrator 2012 blog.

Scheduled Maintenance Mode – scalability considerations

June 16, 2011 Leave a comment

Suggested Support numbers are as follows:

  • Up to 20 jobs per management group
  • Up to 10 items (computer, group, other class) in a job. If you would like to schedule 1000 agents you should place them in a group.

There does seem to be an issue with trying to modify jobs that have more than 6 objects – I have found (and others have been able to replicate) that when you try and modify the job details, an error is thrown and the schedule is blank (and can’t be re-added). A fix is in the pipeline so stay tuned if you are affected by this.