The following
step-by-step walkthrough, will go through all the steps to have a fully working
Veeam nworks MP for VMware with SCOM 2012 setup.
Parts in this
series:
Part 1 -
Preliminaries
1.1 Download
software’s from Veeam - specifically we need the files from the ZIPs below:
VMwareOMMP_5.7.9.1054.zip
·
Nworks.VMware.VEM.mp
·
nworksEMS.exe
·
nworksUI.exe
·
nworksVIC.exe
mp_resource_kit_5.7.1054.zip
·
nworks.VMware.2007R2RequiredOverrides.xml
nworks.vmware.bpac.zip
·
nworks.VMware.BPAC.xml
1.2 Lab Setup
·
2 x Windows 2008 R2 (with SP1) Enterprise member
servers - new builds (1 will be the Enterprise Manager Server and Enterprise
Manager UI, the other will be collector)
·
Existing System Center 2012 Operations Manager
server
1.3 Deployment
of OpsMgr Agents
·
On servers dedicated to be Collector servers
·
On vCenter server (recommended)
·
On the nworks Enterprise Manager Server
(recommended)
1.4 How to Deploy
OpsMgr agents
Launch the System Center 2012 Operations Manager DVD/ISO,
and click on the Local agent option under Optional Installations
Welcome to the System Center 2012 - Operations Manager
Agent Setup wizard, Next >
Destination Folder: Accept/Change… the install location
and Next >
Management Group Configuration: Here we will leave the
‘Specify Management Group information’ box checked and Next >
Management Group Configuration: Enter SCOM Management
Group Name, Server FQDN and port; and Next >
Agent Action Account: For the demo lab we’re going to use
the domain administrator account and Next >
Microsft Update: Select to use Microsoft Update or not -
as desired, and Next >
Ready to Install: Install
Completing the System Center 2012 - Operations Manager
Agent Setup wizard: Finish
Note 1: In the
System Center 2012 Operations Console, you will need to approve manually
installed agents if the setting to automatically approve is unchecked. See:
Operations Console > Administration > Settings > Type: Server >
Security
Agents pending
management will appear in the Administration > Device Management >
Pending Management view
Note 2: Collector
servers must have their OM Agent configured to “Allow this agent to act as a
proxy and discover managed objects on other computers”. See: Operations Console
> Administration > Device Management > Agent Managed > Right-Click
the Collector Server and select Properties > Security tab > check the box
> OK
Comments
Post a Comment