OpsMgr 2012: a quickstart deployment guide

re: OpsMgr 2012: a quickstart deployment guide

P&A — Wed, 01 May 2013 04:56:53 GMT

This is excellent. Thanks so much! Just what I needed.

re: OpsMgr 2012: a quickstart deployment guide

Kevin Holman — Mon, 08 Apr 2013 12:19:51 GMT

@William - Active Directory is required.

re: OpsMgr 2012: a quickstart deployment guide

William — Mon, 08 Apr 2013 07:40:07 GMT

Hi Kevin,

I would like to know if SCOM 2012 can be deployed into an environment that has only LDAP? If it is possible, will there be any limitations to what SCOM can do and what is the workaround for an LDAP environment deployment?

Thanks,

William.

re: OpsMgr 2012: a quickstart deployment guide

Matt — Wed, 27 Mar 2013 18:27:05 GMT

What's a typical strategy to roll out agents and management packs into an enterprise environment?

re: OpsMgr 2012: a quickstart deployment guide

Bryan Heath — Fri, 15 Mar 2013 16:05:18 GMT

One other thought In a production environment wouldn't It makes sense to separate a SCOMInfastructureAdmins separate from SCOMAdmins? As the Authoring Console requires Admin rights it would seem as if some SCOM admins would not necessarily need Local Admins on the infrastructure servers. Thanks for taking the time to write this document and field questions.

re: OpsMgr 2012: a quickstart deployment guide

Bryan Heath — Fri, 15 Mar 2013 15:43:02 GMT

Maybe you can help clear up some questions regarding the Required Accounts for me. It is a bit frustrating for me as I try to map out my install using the documentation provided.

Management server action account: This account is used to carry out actions on monitored computers across a network connection. Permissions: To save time, specify a domain-based account. We recommend that you create an account for this purpose that has local administrative credentials. You should not use an account that has domain administrative credentials. - My Comment: This does not really state where the local admin rights should be. It leaves me to assume but it is not clear. It sounds as if it might be needed on all systems being monitored. I am told this is only needed on the MS.

Data Warehouse Write account: and has logon rights for the computers hosting both the operational database and the reporting data warehouse. - My Comment Am I to assume local users group? I have even seen this account given admin rights on the DB server in some posts.

Data Reader Account: and Management Server logon rights. My Comment - Am I to assume local user on all MS?

How is it that the technical documentation can be so ambiguous? Does Microsoft expect me to buy book or rely on the user community? Perhaps they could just CLEARLY state what they are looking for with some examples… I have a link to the original document and a summary of the document. The SQL portion seems failrly clear.

re: OpsMgr 2012: a quickstart deployment guide

Marlon H — Fri, 11 Jan 2013 08:41:00 GMT

Tx, Kevin

Your blog has been a great help for setting up a new testenvironment.

I will present my results to the IT staff

Ciao

re: OpsMgr 2012: a quickstart deployment guide

Kevin Holman — Tue, 08 Jan 2013 14:57:03 GMT

@Marlon -

You are correct - SCOM is not designed as an event collector/aggregator, to collect ALL events in an event log.

HOWEVER - it is possible/feasible to do this - for application and system events - only if they meet some criteria, such as critical, etc. Only you will be able to determine if this is sustainable... based on the number of events. If the number of events per second is low, you should be able to handle this for 200 servers, which is a very small environment.

re: OpsMgr 2012: a quickstart deployment guide

Marlon H — Tue, 08 Jan 2013 14:16:06 GMT

Hi guys,

I am in the final stage of testing SCOM2012 (Evaluation).

My test environment is 1 Management server, 1 server with all the "SCOM" databases, 1 Reporting server including the reporting database and 7 other servers which are monitored.

Everything is working fine.

For me its time to write down my testresults and to present it to the IT staff.

There is one final challenge:

Management wants that all the System logs and Application logs from the Event Viewer from all the Windows Servers must be monitored in SCOM2012.

SCOM2012 must collect all the Event/Application logs in real time

Only the critical and or errors will be collected ofcourse..

I really think that is not the purpose of SCOM , especially when it will be in production for some 200+ servers.

I think this will generate to much traffic and will be difficutl to implement.

So is there anybody out there who also use SCOM to read out the Event Viewer from monitored servers??

Regards,

Marlon

re: OpsMgr 2012: a quickstart deployment guide

bradje — Thu, 01 Nov 2012 02:02:41 GMT

Hi,

Should SQL2008R2 SP2 be used now instead of SP1 ?

Thx,

John Bradshaw