Friday, November 29, 2013

[OpsMgr 2012 R2] New Powershell Cmdlets ( #OpsMgr2012R2 #Powershell )

Stefan Roth (SCOMFaq) has made a comparison between Cmdlets provided by SCOM 2012 SP1 and the one that comes with SCOM 2012 R2. There is something new since there is 7 more Cmdlets in the R2 version !
Full Article from Stefan >>>>>> Here <<<<<<


Here are the 7 new Cmdlets :



Add-SCAdvisorAgents: adds one or more agent(s) to the group of agents reporting to the Advisor Connector.

Get-SCAdvisorAgents: gets the agents that are reporting to the Advisor Connector.

Get-SCAdvisorProxy: gets the proxy server for connecting to the Advisor Service.

Register-SCAdvisor: registers an Operations Manager management group to a System Center Advisor account.

Remove-SCAdvisorAgents: removes one or more agent(s) from the group of agents reporting to the Advisor Connector.

Set-SCAdvisorProxy: sets the proxy server for connecting to the Advisor Service.

Remove-SCOMUserRole: Remove a SCOM user role


This posting is provided "AS IS" with no warranties.

[OpsMgr 2012] Operation Manager 2012 Toolbox - Override Explorer Updated

To complete the toolbox post created here : OpsMgr Toolbox, here is an article to announce that OverrideExplorer has been updated to Version 3.7 to work with OpsMgr2012 and includes some minor fixes, as well as the capability to Export all overrides to an Excel spreadsheet. It also now shows both Windows and Unix computers in the computers view.



This posting is provided "AS IS" with no warranties.

Thursday, November 28, 2013

[OpsMgr 2012 R2] Microsoft Monitoring Agent 2013 ( #MMA #OpsMgr2012R2 )

Microsoft Monitoring Agent monitors computer infrastructure and application health. It collects diagnostic data, such as performance metrics, event logs, and traces. Microsoft Monitoring Agent can be used as a standalone tool or together with System Center Operations Manager. When monitoring .NET applications, you can direct the agent to save application traces in an IntelliTrace log format.

Microsoft_System_Center_2012_R2_logo_thumbnail
Version:
Date Published:
1.0 9/24/2013
File name:
File size:
MMASetup-AMD64.exe       26.4 MB
MMASetup-i386.exe          21.1 MB






Microsoft Monitoring Agent monitors computer infrastructure and application health. It collects diagnostic data, such as performance metrics, event logs, and traces. Microsoft Monitoring Agent can be used as a standalone tool or together with System Center Operations Manager. When monitoring .NET applications, youMicrosoft Monitoring Agent monitors computer infrastructure and application health. It collects diagnostic data, such as performance metrics, event logs, and traces. Microsoft Monitoring Agent can be used as a standalone tool or together with System Center Operations Manager. When monitoring .NET applications, you can direct the agent to save application traces in an IntelliTrace log format that can be opened in Visual Studio Ultimate. When connected to System Center Operations Manager, the agent calculates the health state of the monitored computers and objects, and then reports back to the management server. The management servers centrally distribute the configuration to agents and store data received from the monitored computers.

Microsoft Monitoring Agent can be used as a standalone tool for collecting application traces locally. You can use PowerShell commands to start and stop monitoring and collect IntelliTrace logs from applications written in Microsoft .NET Framework.

Microsoft Monitoring Agent includes the full functionality of System Center Operations Manager Agent, .NET Application Performance Monitoring, and IntelliTrace Standalone Collector and can be used for monitoring applications that are running in production environments.

Compatibility

  • Visual Studio Ultimate 2013
  • Visual Studio Ultimate 2012 Update 4
  • System Center 2012 R2 Operations Manager
  • System Center 2012 SP1 – Operations Manager )
  • System Center 2012 – Operations Manager

For details about compatibility and upgrade guidance, see Microsoft Monitoring Agent Compatibility (http://go.microsoft.com/fwlink/?LinkId=323495) can direct the agent to save application traces in an IntelliTrace log format.



Service Microsoft Monitoring Agent

Build

September 2013 release

Supported versions of System Center


System Center 2012 R2 Operations Manager
System Center 2012 Service Pack 1 (SP1)
Operations Manager
System Center 2012 – Operations Manager

Supported versions of Visual Studio Microsoft Visual Studio Ultimate 2013
Microsoft Visual Studio Ultimate 2013
Microsoft Visual Studio Ultimate 2012 Update 2

Interoperability information




If you want to use local monitoring with
Application
Performance Monitoring in System Center
2012 SP1, you must be running Update 4.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2012 R2] Why Operations Manager Agent becomes Microsoft Monitoring Agent ? ( #OpsMgr #Opsmgr2012R2 )

Since the release of System Center 2012 R2, we can ask why did Microsoft rename the Operations Manager agent to "Microsoft Monitoring Agent" ?
Microsoft Monitoring Agent is a new agent that replaces the Operations Manager Agent and combines .NET Application Performance Monitoring (APM) in System Center with the full functionality of IntelliTrace Collector in the Microsoft Visual Studio development system for gathering full application-profiling traces.

Microsoft Monitoring Agent can collect traces on demand or can be left running to monitor applications and collect traces.

You can limit the disk space that the agent uses to store collected data. When the amount of data reaches the limit, the agent begins to overwrite the oldest data and store the latest data in its place.

You can use Microsoft Monitoring Agent together with Operations Manager or as a stand-alone tool for monitoring web applications that were written on the Microsoft .NET Framework. In both cases, you can direct the agent to save application traces in an IntelliTrace log format that can be opened in Microsoft Visual Studio Ultimate. The log contains detailed information about application failures and performance issues.
You can use Windows PowerShell commands to start and stop monitoring and collect IntelliTrace logs from web applications that are running on Internet Information Services (IIS). To open IntelliTrace logs that are generated from APM exceptions and APM performance events, you can use Visual Studio. For information about supported versions of IIS and Visual Studio, see Microsoft Monitoring Agent Compatibility.

Source & more information : Technet Site


We can also read this interesting article : Introducing Microsoft Monitoring Agent that explain how to use the Microsoft Monitoring Agent in standalone mode and how to generate and use the IntelliTrace file !


Daniele Muscetta has written too an interesting post explaining Microsoft Monitoring Agent, System Center Operations Manager and Visual Studio Application Insights



This posting is provided "AS IS" with no warranties.

[OpsMgr 2012] How to find a specific rule/monitor/discovery in the console - SQL queries / Powershell command ( #SQL #Powershell #OpsMgr #OpsMgr2012 )


Sometimes in the Operations Manager Event log, we have some event/alert  for script error or WMI query error and all the time, the description give your the exact name of the rule/monitor/discovery that cause the issue. In SCOM console, you cannot find the rule/monitor/discovery by their exact name, only by the display name.



For example, here is an event 5500 we have on one server due to an invalid configuration for a monitor: Microsoft.SystemCenter.Agent.HealthService.PrivateBytesThreshold



Log Name:      Operations Manager
Source:        HealthService
Date:          11/28/2013 3:10:43 PM
Event ID:      5500
Task Category: Health Service
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      MyServer.MyDom.Dom
Description:
Frequent state change requests caused the incoming state change request to be dropped due to it being older than the currently recorded state change for this monitor. This could also be due to an invalid configuration for this monitor. 

Affected monitor: Microsoft.SystemCenter.Agent.HealthService.PrivateBytesThreshold
Instance: MyServer.MyDom.Dom
Instance ID: 293C0099-290F-C53C-340E-A5E710CA5B9F
Management Group: MyMgtGroup

Request generated time: 2013-11-28T15:10:43.1658766+01:00
Requested state: Success

Recorded time: 2013-11-28T15:20:35.7827611+01:00
Recorded state Success


To start investigation, you need to retrieve the display name of the rule/monitor/discovery. You can also execute SQL queries on views in the OpsMgrDB or PowerShell commands connected to your management group :

Rules:

SQL:

select DisplayName from ruleview where name = 'Rule.Name'

Command Shell:

(Get-SCOMRule | Where {$_.name -match 'Rule.Name'}).DisplayName

Monitors:

SQL:


select DisplayName from monitorview where Name = 'Monitor.Name'

Command Shell:

(Get-SCOMMonitor| Where {$_.name -match 'Monitor.Name'}).DisplayName

Discoveries:

SQL:

select DisplayName from DiscoveryView where name = 'Discovery.Name'

Command Shell:

(Get-SCOMDiscovery| Where {$_.name -match 'Discovery.Name'}).DisplayName


In our case, powershell command or SQL query give a display name (replace Monitor.Name by Microsoft.SystemCenter.Agent.HealthService.PrivateBytesThreshold in the line) : Health Service Private Bytes Threshold for monitor Microsoft.SystemCenter.Agent.HealthService.PrivateBytesThreshold

We can now retrieve the monitor in the SCOM console and try to investigate the issue  ! :)



This posting is provided "AS IS" with no warranties.

[SCCM 2012 R2] Windows Intune Company Portal By Microsoft Corporation ( #SCCM2012R2 #Intune #Android #iOS )



Microsoft has just finished the validation and publication of enterprise portal applications for iOS and Android to allow mobile device management via System Center Configuration Manager 2012 R2. These applications are available on the publisher AppStore and Google Play stores:




The Company Portal app helps you search, browse and install apps made available to you by your organization through the Windows Intune online service. Apps can be installed without requiring a connection to your corporate network. You can also add your personal computers and devices to the service and locate contact information for your IT team.

Features
• Company apps – browse, search and install apps made available to you by your company
• Computer/device enrollment – manage enrollment with Windows Intune for your devices, as well as the ability to remote wipe certain device types
• Contact IT – easily locate contact information

IMPORTANT: This software requires your company’s organizational account and connectivity to your company’s valid subscription to Windows Intune™. Updates to the service may be required for proper performance. Some functionality may not be available in all countries. If you have issues with this software or have questions about the use of it (including questions about your company’s privacy policy), please contact your company’s IT Administrator. Do not contact Microsoft, the application store owner, your network operator, or device manufacturer for support.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2012] Using SiteName when deploying gateways to help manage alerts ( #OpsMgr2012 #Opsmgr )

When deploying the Operations Manager gateway role you can tag the gateway with a Site name.   Any alerts coming from an agent reporting to this gateway will now have it's "Site" property populated with the site name you configured when deploying the gateway.  This can be really handy for building specific alert views and sending notifications.




To create a site (without using the SDK) you need to create a gateway, more a site can only be created at gateway approval time, this the command line to create MySite site associated with Gateway.dom.lab gateway:

MICROSOFT.ENTERPRISEMANAGEMENT.GATEWAYAPPROVALTOOL.EXE /ManagementServerName=ms1.dom.lab /GatewayName=Gateway.dom.lab /SiteName=MySite

Sites are slightly changed in OM2012, nothing you can get in the UI, but the code has been reviewed and a new relationship of type Microsoft.SystemCenter.SiteContext has been added to track site memberships.

Be carefull this change has an important implication (probably a bug) : you must avoid orphaned sites. Orphaned sites are sites without any gateway associated with.

You can find more information on this point on the site bellow :



This posting is provided "AS IS" with no warranties.