A few months ago, Netapp upgraded, renamed and grouped their Microsoft System Center management pack and Microsoft PowerShell command-lets into one new product, the OnCommand Plug-in for Microsoft.

This new version of this tool includes also new functionalities like:

· Opalis Integration Packs
· Discovery Agent for Hyper-V host
· Complete documentation for all these functionalities.

Here we will focus only on the Microsoft Operations Manager management pack. This application has to be installed on a management server, if possible, avoid installing it on the root management server.

Copy the file, OnCommand-PlugIn-Microsoft_3.0_x64_NetApp.exe, on the root management server and let’s start the installation by double clicking on it. Unfortunately, we don’t have the choice here, it must run from the RMS.

If a previous version of the management pack is installed, like the Data Ontap Appliance Watch PRO 2.1, it will be automatically uninstalled it.

Click on Yes to continue.

Click on Next to continue.

Click on Next to continue.

Specify the destination folder and Click on Next to continue.

As we are only interested by the SCOM Management Pack, we will not install other component.

NetApp OnCommand needs to run a Web Service. Create a Service Account that will be local admin of the server on which you install the software. Set the credentials and click on Next.

Click on Install to continue.

The installation is now in progress, it will install the application, but it will also automatically import/upgrade the NetApp management packs to the Operations Manager Infrastructure.

And finally, click on Finish.

Start the SCOM Console, the installation process automatically installed the new the NetApp Management packs. /! If you were previously using the Netapp management pack, extract your custom management pack because the upgrade will simply remove it, which could be really frustrating. After the upgrade, you are able to reinstall it. It seems that NetApp changed some class, be sure to check that your overrides are well targeting the right classes./!

The next step is to add the Netapp Controllers as Network device. Go to Administration > Network Devices > Discovery Wizard. Specified the IP range and start the discovery.

Discovery is in progress.

The controllers have been discovered as SNMP devices. Select all the controllers and click Finish.

Go to Monitoring > Data ONTAP > Storage Systems > Management Server, choose the root management server that will monitor your Netapp infrastructure and run the Data ONTAP : Run Discovery Task.

After a few moments, the Netapp Controllers will automatically appear in the Data Ontap > Storage Systems > Controllers view.

Extend the actions pane and click on Data ONTAP : Manage Controller Credentials task.

This will start the Netapp Credentials Manager, where we have to specify the credentials for all the NetApp Controllers.

When done, go back to the SCOM console, Go to the Authoring section > Management Pack Objects > Rules and search for the Data ONTAP: Discovery Rule.

This is the principal discovery rule for all Data ONTAP storage systems. Once you use the SNMP network device Discovery wizard in System Center Operations Manager to discover your Data ONTAP storage controllers, this rule contacts each storage controller and discovers all of its physical and logical storage elements.

This rule is disabled by default. You should enable the rule, via an override, for the management server that will monitor your Data ONTAP storage controllers.

After a few moments, the entire infrastructure will be discovered and all the views will be populated.

Regards
Christopher KEYAERT

operations manager · opsmgr · Scom

Dear All,

Yesterday, I moved some agentless monitored servers from a Windows Server 2003 R2 SP2 management server to a Windows Server 2008 R2 SP1 management server. Since I did that, I received the following alert for all my Windows server 2003 agentless servers :

There are no more endpoints available from the endpoint mapper

In the management server event log, the following event was recorded:

The Windows Event Log Provider is still unable to open the System event log on computer ‘xxx.xxx.com’. The Provider has been unable to open the System event log for 336240 seconds.

Most recent error details: There are no more endpoints available from the endpoint mapper.
One or more workflows were affected by this. 
Workflow name: many
Instance name: many
Instance ID: many
Management group: OM2007

I checked the firewall settings, DNS settings, …. everything was fine. Finally I moved back an agentless monitored server to a Windows Server 2003 R2 SP2 management server and the error disappeared.

The Microsoft Premier Support confirmed it me, a Windows Server 2003 agentless server must be monitored by a Windows Server 2003 server watcher node. Same idea for a Windows Server 2008 agentless server, it must be monitored by a Windows Server 2008 server.

Now, an agentless watcher node could be a management server, or any other agent monitored server of you infrastructure. If you choose an agent monitored server as watcher node, don’t forget to set change the run as account of the agent to an account which has the necessary access right to the agentless monitored server.

Regards
Christopher KEYAERT

Uncategorized

Dear all,

We invite you to join us on the sixth edition of Community Day 2012. On Thursday, June 21st 2012, 17 user groups are working together to bring you a full day of sessions for both the developer and IT-Pro community! Just like last year, the event will take place in Utopolis Mechelen, Belgium.

This year, we offer you 6 parallel tracks, over 40 deep-technical sessions delivered by community members and partners and great networking opportunities. It’s your free ticket to get up to speed with all the new releases including Windows 8, SQL Server 2012, System Center 2012, Visual Studio 11, C# 5 and much more.

This year, I will have the honor to present a session about : How to automate your server provisioning with System Center Technologies.

Want to be there? Register your free spot now.

The Community Day 2012 is brought to you by Azug, BeCPP, Besug, Biwug, IT-Talks, Pro-Exchange, SCUG, SQLUG, VBIB, Visug, WinSec, XNA-BUG, CLUG, MyTIC, Wiphug, TechNine and DotNetHub. We look forward to seeing you then!

Click here to download the Outlook Calendar file (*.ics) to save the date in your agenda!

Events

Dear [IT Professional],

This is your personal invitation to one of the two major technical
conferences we will be holding on June 7th 2012: The Best of
Microsoft Management Summit and Experience Windows Server 2012.

During The Best of Microsoft Management Summit (MMS 2012), we
will provide you with the best possible opportunity to learn
about what’s new in System Center 2012. Led by experts who
attended MMS 2012 in Las Vegas, you can expect in-depth sessions
on infrastructure management, service delivery & automation,
application management, desktop & device management.

Discover the full program
http://www.microsoft.com/belux/nl/enterprise/experiencedays/demo-mms.html

At Experience Windows Server 2012 day you will discover how
Windows Server is going beyond virtualization by scaling and
securing workload, how it will enable the modern work style by
giving people access to information and data regardless of the
infrastructure, network, device or application they use to
access it.
And you will discover the power of many servers with the
simplicity of one by efficiently managing infrastructure while
maximizing uptime and minimizing failures and downtime.

Join us and learn more about:

- New Hyper-V Virtualization Platform
- What’s new in Active Directory
- Storage and Management Improvements
- Clustering Improvements
- Plus much more…
   
Discover the full program
http://www.microsoft.com/belux/nl/enterprise/experiencedays/demo-windows-server.html

Places are limited, so register now for:

- The Best of Microsoft Management Summit 
   http://www.microsoft.com/belux/nl/enterprise/experiencedays/demo-mms.html

- Experience Windows Server 2012 
   http://www.microsoft.com/belux/nl/enterprise/experiencedays/demo-windows-server.html

Add to your Outlook calendar:

- The Best of Microsoft Management Summit 
  http://www.microsoft.com/belux/nl/enterprise/experiencedays/agenda-mms.ics

- Experience Windows Server 2012 
  http://www.microsoft.com/belux/nl/enterprise/experiencedays/agenda-experience-windows-server.ics]

These events are part of the Microsoft Experience Days
that take place on 6 and 7 June 2012.

Regards
Christopher KEYAERT

Uncategorized

Hello All,

This morning, I had one agent managed server which stop to work correctly. The server appears as Not Monitored (Note : That’s could apply for some server in grey state) in the Console Computers view.

I checked in the Console Agent Managed view, and there, the server is not present at all.

In the agent managed server, we have the following event :

Event Type:    Warning
Event Source:    OpsMgr Connector
Event Category:    None
Event ID:    21034
Date:        5/10/2012
Time:        8:41:00 PM
User:        N/A
Computer:    TYOBKP002
Description:
The Management Group XXXXX has no configured parents and most monitoring tasks cannot be performed.  This can happen if a management group in Active Directory does not have any server SCPs or if the agent does not have access to any server SCPs.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

The first step is to check if the Management Group Name and the Management server are well configured.

Before going further, be sure to have a good backup of your SCOM DBs. Log on to the OperationsDB database server and run the following query :

SELECT * FROM dbo.[BasemanagedEntity] where FullName Like ‘%Windows.Computer%’ and Name Like ‘%AGENTMANAGEDSERVERFQDN%‘

if the IsDeleted value is set to 0, run the following query :

UPDATE dbo.[BasemanagedEntity] SET IsDeleted = 1 where FullName Like ‘%Windows.Computer%’ and Name Like ‘%AGENTMANAGEDSERVERFQDN%‘

You could now close the Microsoft SQL console, and go back to the Agent Managed server and stop the System Center Management service.

Go to the SCOM Agent Installation folder and delete the Health Service State folder.

Start the the System Center Management service.

After a few seconds, in the event viewer, you will see that event, don’t worry, this is normal.

After a few minutes, the server will reappear as Not Monitored in the Console Agent Managed view.

In the event log, we could see that agent has returned to communicating with the management server.

And after some minutes, it could take up to 30 minutes, the agent will go back to Healthy in the Console Agent Managed view.

Regards
Christopher KEYAERT

Uncategorized