Unleash the power of System Center for vSphere and Hyper-V | Veeam Task Manager for Hyper-V
Post Reply
mike.bosco@dcsg.com
Lurker
Posts: 2
Liked: never
Joined: Feb 09, 2011 5:03 pm
Full Name: Mike Bosco
Contact:

SCOM DEV management group

Post by mike.bosco@dcsg.com » Feb 09, 2011 5:31 pm

I currently have 4 collectors with SCOM agents that all point to a SCOM PROD management goup. I need a way to test new Veeam management pack configurations and versions using a SCOM DEV management group prior to implementing in a SCOM PROD management group. Is there a best practice for this from a nworks perspective? Generally speaking it is a relatively common practice for a SCOM agent to point to both SCOM DEV and SCOM PROD management groups. Any issue with this for nworks Collectors? Would it be better to dedicate a Collector and point this to SCOM DEV only.

vBPav
Expert
Posts: 181
Liked: 13 times
Joined: Jan 13, 2010 6:08 pm
Full Name: Brian Pavnick
Contact:

Re: SCOM DEV management group

Post by vBPav » Feb 10, 2011 2:57 am

Hello Mike!

Typically, organizations will dedicate nworks Collectors to the Development Environment. It simplifies the Infrastructure and is super easy to accomplish by utilizing Failover Groups within the nworks EMS. Some environment will go as far as to deploy their own nworks EMS/Collectors for a development environment. This enables them to upgrade the development nworks Infrastructure independant of the production nworks Infrastructure when new product releases come out.

I'm not aware of any issues multi-homing nworks Collector agents for two different SCOM Management Groups.

Hope this helps!


-Brian
Brian Pavnick | Cireson| Solutions Architect

- Follow me on Twitter @ vbpav
- Reach me on e-mail @ brian.pavnick@cireson.com

Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests