Answering some common deployment questions (Part 1)
Published Feb 14 2019 08:08 PM 1,226 Views
First published on TECHNET on Jan 22, 2008
What level of privileges are required to install the product?<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

Someone recently asked a question regarding what level of privileges are required to install the product and later they asked me why the accounts had to be what they were. I thought I would take some time to write this blogs and explain these accounts in a simple way.

The account doing the install on the server where the SQL server and Root Management Server are going to be installed needs to have local administrator privileges. To run MSI packages users must at a minimum have local admin privileges.  In addition to this account would also require system administrator privileges on the instance of SQL where the Operations manager Database is going to be hosted. This would be required so that the setup can configure the necessary privileges for the SDK and Config service account and assign them the proper roles and rights on the Operations Manager Database as the SDK and the Config services read and write to the database Operations manager DB. The reason why we require the user installing to be an admin is because setup creates services, file/folders. It also creates SQL DB, SQL logins/roles so it needs to have necessary permission in order to do this.

Does the OpsMgr team support SQL 2005 database mirroring functionality?

Database mirroring is something that is OpsMgr team is not supporting at the moment (slight possibility we may support it in the future). But from what we know there should not be any reason why it would not work. SQL Full recovery mode is supported in OpsMgr 2007 and therefore log shipping is also supported. MSIT has built out their OpsMgr infrastructure which is using log shipping for their database; you can read more about their log shipping implementation here .

How do I know on which day the evaluation version of OpsMgr 2007 will expire?

Unfortunately there is no easy way to do this. But the one thing you can do is check the date installed in the registry and the eval expires after 180days (6months).

The registry key is

HKLMSoftwareMicrosoftMicrosoft Operations Manager3.0SetupInstalledOn

Note: Trying to change the registry key to extend the evaluation period or change the license key will not work, all this data is encrypted in the database.

Capacity Planner for OpsMgr 2007 is currently only in Beta how do I plan my customers OpsMgr deployments?

There is an internal alias called OMCAPREQ (OpsMgr 2007 Capacity Planning Requests) where internal MS employees can email information on their customers environment such as number of agents they want to monitor, kind of management packs they are planning to deploy and if they are planning to leverage new features like AEM and ACS and we will give guidance on what hardware is recommended and if we can scale to your customers needs. If you are a customer and want to get your deployment reviewed please get in touch with your TAM or Consultant and ask them to email this alias at Microsoft. In would be helpful if you sent a pictorial diagram of what you think your environment looks like.

Is it supported to install the Gateway role onto a domain controller?

I have tried it out in my Virtual environment and it works. I can't day for sure  we officially support it because I don’t think our test team has actually tested this scenario but if the customer runs into an issue we will help debug it but if there is no resolution to the problem then they will need to put it on a regular server. Just be aware of KB946428 and the likely need to run the HSLockdown tool.

Is MSIT using a three node cluster to host the database and root management server roles? Why is it not supported?

MSIT was at one point in time using the Active-Active-Passive scenario.  However, since it is not a supported scenario by us they redeployed their RMS and SQL systems to two separate two node clusters prior to the RTM release. One of the limitations we have is not being able to monitor instances for SQL running on same cluster. If customer runs different databases on same HW, he would need to proceed with agentless monitoring for those instances.

How do I change the account the OpsMgr Services are running under?

Follow the steps in this KB article:

Satya Vel | Program Manager | System Center |

Version history
Last update:
‎Mar 11 2019 08:00 AM
Updated by: