Archive

Archive for the ‘OpsMgr2012’ Category

OpsMgr 2012 R2 – how to remove an old management group with VB script

18/04/2014 Leave a comment

Recently I needed a quick solution to a problem during a migration project. the problem was that some agents point to more then 1 management group. I found 2 good starting point to my problem: Manipulating SCOM 2012 agent multihoming options by script & Remove a Management group from a SCOM 2012 agent with script by Bob Cornelissen. System Center 2012 Operations Manager includes an agent configuration library that we can use to add, remove or view management group information using a script. my goal was to add a task to the new Operations Manager installation that in the end will help the customer to remove old management groups whenever he need.

Option Explicit

Dim objMSConfig

Set objMSConfig = CreateObject(“AgentConfigManager.MgmtSvcCfg”)

‘Get all management groups and display the port

Dim collMG

Set collMG = objMSConfig.GetManagementGroups()

if collMG.count > 1 then

   wscript.echo “found ” & collMG.count & ” management groups”

   ‘Enumerate the collection

   Dim mgItem

   For Each mgItem In collMG

       if mgItem.ManagementGroupName <> “<YourMGName>” then

       Call objMSConfig.RemoveManagementGroup (CStr(mgItem.ManagementGroupName))

          wscript.echo CStr(mgItem.ManagementGroupName) & ” removed”

       end if

   Next

end if

‘ enumerate MG again for task info Set collMG = objMSConfig.GetManagementGroups()

For Each mgItem In collMG

    wscript.echo “found ” & collMG.count & ” management group: ” & mgItem.ManagementGroupName

Next

Step taken:

  1. Create a blank MP
  2. Goto authoring pane and right click on tasks
    removeold1
  3. Select “run a script” under agent tasks and point to the blank MP from step 1.
    removeold2
  4. Give the task a name and target the task to “Agents”
    removeold3removeold4
  5. Enter the script name and paste the above script
    removeold5
  6. Click “create”
  7. Goto monitoring pane -> Operations Manager -> agent details -> agent health state
  8. Click an agent or multi select several agents and click on the task
    removeold6
  9. View the task log for success or failures.
    removeold7

link from MSDN:

Agent Configuration Library Overview – Provides an overview of agent configuration scripting.

How to Add and Remove a Management Group – Describes how to add and remove a management group.

How to Display Management Group Information – Describes how to display management group information.

 

 

Hope you will find it helpful.

Categories: OpsMgr, OpsMgr2012

Cool article by Marnix Wolf

04/10/2012 1 comment

A long time since my last post.

today I read the last post of Marnix and I must say that this is exactly the topics that interest me in our field. As always Marnix presents the subject in his unique way.

 

Wow! On my HP Elitebook notebook with an I7 Intel CPU, SSD HD and 16 GBs of RAM I run Windows 8 RTM version with Hyper-V enabled. On the SSD I run all my VMs which – guess what – run some System Center 2012 components like SCOrch and OpsMgr 2012.

On itself it’s already awesome: when I put my notebook into hibernation, the VMs will be set into a saved state, basically meaning when I start my notebook again, the VMs will run from the moment they were paused.

So my VMs are running for more then a few weeks now, without any glitch at all. All the screens which I had opened in all my VMs before hibernating my notebook, are found back in the exact same way after my notebook is on again. Even better, all processes which I started run from where they left off…

And that’s really something very good Microsoft pulled of here. So no more need for any other hyper-visors on my Windows 8 machine! Again, awesome! Respect. This feature on itself is for me enough to migrate ALL my pc’s to Windows 8!”

http://thoughtsonopsmgr.blogspot.com/2012/10/a-story-of-window-8-hp-apple-ipad.html

Categories: OpsMgr2012, Technology

What’s New in SCOM 2012 Network Device Monitoring

25/08/2011 Leave a comment

In the old days Winking smile when we used Operations Manager 2007 R2 to monitor network device we ware limited to network device availability (online or offline). if we wish to know more, we could used the xSNMP management pack .this MP helped us monitor the availability of ports and interfaces and performance related issues. But xSNMP MP covers only few devices like Cisco, HP ProCurve , Juniper etc. moreover discovery of network devices is limited to SNMP V1 & V2 only. if we wish to monitor SNMP V3 we must use third party applications that extend OM2007 (like JalaSoft).

So what changes have been made to network monitoring in OM2012 ?

  • Extended device monitoring
  • Multi vendor support and multi protocol support.
  • Resource pools
  • Discovery
  • Server to network dependency
  • Dashboards and reporting

Extended Device monitoring

Unlike Operations Manager 2007, Operations Manager 2012 is a game-changer with a new network device monitoring engine. OM2012 extend those capabilities to a large number of vendors and devices (provide port monitoring for devices that implement interface MIB (RFC 2863) and MIB-II (RFC 1213) standards.)
OM2012 provides the ability to discover and monitor network routers and switches, including the network interfaces and ports on those devices and the virtual LAN (VLAN) and Hot Standby Router Protocol (HSRP) groups that they participate in. further more, OM2012 can monitor Firewalls and load balancers.

Multi vendor support and multi protocol support

Microsoft published an Excel spreadsheet that lists the devices, vendors, model names, and versions of network devices that have extended monitoring capability. The Devices worksheet includes processor and memory columns for each device to indicate whether Operations Manager can provide extended monitoring for either or both aspects for each device.

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26831

Resource Pools

Resource Pool is a feature in OM2012 which gives us the ability to monitor non-windows devices in a high availability mode. The concept behind this feature is that we can select management servers and group them in a pool, and then assign network devices to be monitored by the pool. If a server goes down from that pool, it will automatically failover any monitoring that is occurring on that management server to the other members of the pool.

Discovery

The network discovery process is a great change compared to SCOM2007, it allows us to discover multiple devices using discovery rules. the discovery deals with different community names just like run as account and allows us to discover sets of devices and individual network devices in the same rule.
There are 2 types of discovery:
Explicit – OM will discover specific network device that was specified in the rule.
Recursive – OM will discover the devices specified as well devices found in the ARP table of those devices.
I preferred explicit rather then recursive discovery, because recursive will discover devices that we don’t need to monitor and as a result, will increase the administrative workload and the management server workload.

Server to network dependency

Server and network dependency is part of the vicinity dashboard, and it’s actually a dynamic map that show us contextual network map. we can choose whether to display computers that connected to the network devices. the map can be scoped to number of hopes from the selected network node.

Dashboards and reporting

Well, how can one explain this ? I thought that a a picture is worth a thousand words…

Capture

image

clip_image002[4]

clip_image002[6]

image

clip_image002[8]

 

Useful links :

http://blogs.technet.com/b/kevinholman/archive/2011/07/21/opsmgr-2012-discovering-a-network-device.aspx

http://technet.microsoft.com/en-us/library/hh212935.aspx

Categories: OpsMgr2012 Tags: ,

SCOM 2012 Beta installation–Step by Step guide

04/08/2011 2 comments

Although there is very good quick start guide that comes with the Beta version,  I thought to bring my own experience from the field.

first we need to get the Beta version, while downloading I thought that it would be best to start reading the quick start guide and to take notes for prerequisites that I need to take BEFORE I start the setup process.

Prerequisites:

Active Directory:
I created the following users

  • SCOMAction – OM Action Account (I’m Using Domain Admin Member)
  • SCOMSDK – OM Config & Data Access Service Account (must be local admin on the server)
  • SCOMDR – Reporting Read Account
  • SCOMDW – Reporting Write Account
  • SQLSVC – SQL 2008 Service Account
    Server Operating system:
    Windows Server 2008 R2 SP1 (VM hosted on Hyper-V, 2 CPU’s 2Gb Memory.)

The New SCOM 2012 server will include:
Management Server, Web Console, Reporting, Management Console & Databases

Server Roles & Features:

.NET Framework 3.5.1

IIS Role with: (We must install IIS before installing the ASP.Net 4.0)

IIS1iis2

Installation of the web console requires that ISAPI and CGI Restrictions in IIS be enabled for ASP.NET 4. To enable this, select the web server in IIS, and then double-click ISAPI and CGI Restrictions. Select ASP.NET v4.0.30319, and then click Allow.

Install the .NET Framework 4 – Download here

Install Microsoft Report Viewer 2008 SP1 Redistributable Package (Used for OM Console)

Install Hotfix 976898 (Used for OM Console)

SQL 2008 R2:

Install SQL 2008 R2 with: SSRS, Full Text Search and SQL Agent. do not forget to set the SQL Agent to automatic. SQL Agent is required for Application Advisor reports publishing AND only when you select the “Reporting Server” option during setup.

Set the SQL server collation to SQL_Latin1_General_CP1_CI_AS.

Installation Process:

1. run the SCOM2012BETA.EXE.

2

2. when the extract process finished the setup screen appears

3

!!! the Release Notes open the OM2007 R2 release note !!!

3. Click the install link

7

8

select all the check box above

choose the installation folder, I used the default path

9

10

Opps….I missed one of the steps above – Install Hotfix 976898 (Used for OM Console)

enter the SQL server name that will host the OperationsManager DB

14

enter the SQL server name that will host the OperationsManagerDW DB

15

select the SQL server reporting instance, before selecting next I recommend to check if the reports web site is responding. open IE and go to  http://localhost/reports web site.

16

select the web site which will host the web console.

17

select your favorite authentication mode

18

set all OM account

19

choose your preferred settings

20

21

and that’s it.

22

after several minutes, we got the setup complete screen

23

image

Summary:

Microsoft did a great job on the SCOM2012 installer. easier installation process and all prerequisites are checked during install with a very useful information about the problem and how to solve it without leaving the setup process.

Categories: OpsMgr2012 Tags: ,