SC Operations Manager 2007 - The Basics of Deploying the Agent

We have a number of improved methods for deploying the SC OM2k7 Agent (Agent Managed Agent) when contrasted with Deploying the Agent in MOM2k5 SP1.  In the following Screen Captures I will offer one method and comments specific to many of the new options offered along the way.

<Click the Image to Enlarge in a Color Window>


I begin this process by selecting the 'Administration Pane' and then invoking the 'Discovery Wizard' by Right-Mouse Clicking the 'Administration' Object. 



We now begin the see the granular options for Deploying the SC OM2k7 Agent to Servers or Workstations.  Here, I have selected the 'Advanced Discovery' toggle but could have invoked an 'Automatic Discovery'.  Automatic Discovery does not mean the Agent is automatically deployed - just that there is an option provided to select 'discovered' Servers and Workstations.



In this example since I had only 3 targeted Servers I manually input them (or Browsed by NetBIOS Name) into the Computer and Device Management Wizard.  In larger Environments I typically input a specific Statement into the 'Scan Active Directory' toggle and 'Configure' button. 



We now have the ability to define a User ID with the Security Context to correctly 'install' the SC OM2k7 Agent on the respective Server/Workstation.  In large environments there are typically many differed Local Administrators based upon the Server Role (Web Server, Messaging Server, SQL Application Server, etc.) that require many different Accounts (User IDs) to be specified.  We would simply repeat this process for each Group of Servers overseen by each respective Local Administrator.



In this step of the Computer and Device Management Wizard we can select several different options.  The initial option is to select Servers we are targeting for Agent or Agentless Deployment.  Agent Deployment means installing an Agent on the respective Server that 'reports back' data to the Management Server(s).  Agentless Deployment means forgoing installation of a Local Agent and using the Management Server's Processing/Disk Capacity to function as the Agent.



These 3 targeted Servers will be 'Agent Managed' Servers.



After defining the Volume and Agent Application File Path we then specify the Security Context the Agent will function under.  In our example we use the Local System User Context. 



Success!  (Did your really expect me to show when it didn't work?)  The Agent is now deployed to these 3 Servers.  We can begin the work of defining Overrides and adding Alerts, Rules and Monitors to understand each Servers Health.  Operations Management - you gotta love this stuff!



Our 3 Servers show up in the 'State and Alerts' dialogue windows from the Main Management Console page.



Now we begin to see some of the many 'Views' available to Agent Monitored Servers in SC OM2k7.  In this example it is the 'Computers View' indicating the general Health is good! 

Lynn Lunik
Independent Security Consultant
Windows(R) Platform
IT Pro Secure Corporation
and
exchangesummit.net
http://itprosecure.com and http://www.exchangesummit.net
blog <at> itprosecure.com