Archive | SCOM

Here are the new features in V5.1:

• 24-Hour International Date Time Format –  International customers that use a 24-Hour time clock can now use their native time format.

Here are the new features in V5:

• Monthly Maintenance Mode –  This has been one of the most requested feature as end users often want to schedule maintenance mode on specific days of the month such as patch Tuesday or during their monthly patch windows.

• Set an end date for reoccurring maintenance jobs – Now you can set an end date for daily, weekly and monthly jobs

• More secure code – All executables, dlls and installers are now digitally signed for security

• Fixed Date bug in Manage Page – Fixed issue where date was showing up in US format even when international was selected.

Monthly Maintenance Mode

Set an end date for reoccurring maintenance jobs

More secure code

Fixed Date bug in Manage Page

If upgrading please see the upgrade guide before installing.

https://www.scom2k7.com/maintenance-mode-scheduler-20/v5-upgrade-guide/

**Update**

Microsoft has finally released a new version of Remote Desktop Connection Manager that was once deprecated.

You can download the version 2.81 here:

Download: https://download.sysinternals.com/files/RDCMan.zip

Anyone running lots of remote desktop sessions will want to check out Remote Desktop Connection Manager 2.7

Download: https://www.scom2k7.com//downloads/rdcman.msi

I have been using this build for a few months and it has lots of nice features over 2.2

The feature I use the most is the Reconnect Feature.

Other features include

• Virtual machine connect-to-console support
• Smart groups
• Support for credential encryption with certificates
• Windows 8 remote action support
• Support for Windows 8, Windows 8.1 / Windows Server 2012, Windows Server 2012 R2

Lots of of good fixes in the latest UR.  Especially  if you are using APM then this update rollup  is a must for making this work.   Working with Sensitive Data for .NET Applications

Link:  http://support.microsoft.com/kb/2992020

Issues that are fixed in update rollup 4

Issue 1

It takes many minutes for the Microsoft.Windows.CheckNTServiceStateMonitorType function to determine that the service is down.

Issue 2 

An attempt to apply sensitivity rules fails, and you receive the following error message:

Issue 3

GSM locations are geotagged incorrectly on Map Widget.

Issue 4

The MonitoringHost.exe process issues too many calls to System Center Failover Clustering.

Issue 5

The re-synchronization of all managed entities from Operations Manager to the Operations Manager Data Warehouse database causes duplicate entries, and an exception that resembles the following is thrown:

Issue 6

If data is truncated and is in Terminal status to a workflow, event ID 31551 is logged, and an exception that resembles the following is thrown:

Issue 7

An arithmetic overflow error occurs, and an exception that resembles the following is thrown:

Issue 8
You experience poor performance when Operations Manager searches for attributes. Additionally, when doing more than one search in a row, the cache file (momcache.mdb) keeps increasing.

Issue 9
SCX agent generates lots of warnings in the log file when a user is using Security-Enhanced Linux (SELinux).

Issue 10
By default, the Rpcimap monitor for Red Hat Enterprise Linux 6 is disabled.

Here are the new features in V4:

• Multi-select Computers  This has been the most requested feature as end users often want to schedule multiple computers at a time without having to create groups.

• Multi-select Computers in Integrated dashboard  Now you can select multiple computers in the dashboards without getting an error

• New Search in Computers and Groups  Now instead of scrolling up in down the list you can just start to type in the name of the group or computer and results will be filtered.

• One Click MM now accepts parameters   Some environments One Click MM was not working as the client security was high or there were DNS issues.  Now you can just add the computer as a parameter.

• New Configuration backup tool for easier upgrades  Now you can back your configuration and upgrade to the latest version of SCOM 2012 Maintenance Mode Scheduler with have to reconfigure all of your settings.

Download Free Trial

Multi-select Computers

Now you can select multiple computers at a time for maintenance mode.

Multi-select Computers in Integrated dashboard

New Search in Computers and Groups

One Click MM now accepts parameters

New Configuration backup tool for easier upgrades

There is a bug in Silects MP Author SP2 tool.  If you select a 32-Bit registry key for discovery.

When you save the MP it will automatically remove the Wow6432Node

Most 32-Bit applications don’t write to multiple locations so It won’t discover anything.

**As pointed out by Kevin Holman there is an XML element called <registryview>32bit</registryview> that will accomplish the same thing but will work with 32-bit servers and 64-bit servers.**

Open up the XML and add the <registryview>32bit</registryview>

My XML would look like this.

<RegistryAttributeDefinition>
<AttributeName>ConfigProductCode</AttributeName>
<Path>SOFTWARE\Research In Motion\BlackBerry Enterprise Server\Setup\ConfigProductCode</Path>
<PathType>1</PathType>
<AttributeType>0</AttributeType>
<RegistryView>32bit</RegistryView>
</RegistryAttributeDefinition>

More info on this can be found here.  http://michielw.blogspot.ca/2010/01/scom-registry-discovery-on-64-bit-os.html

The following workaround will work as well, but is not perfect as you might have apps installed on both 32-bit and 64-bit servers.

Open up the XML and edit it back to what it should be.

I have reported this to Silect.  Hopefully they will fix it in the next version.

Creating a Process Monitoring Recovery Task to stop a process that has been running too long.

I already created the monitor using the Process Monitoring template.

To create the recovery task.

I right click on the process monitor I created.

Choose View Management Pack Objects, Monitors.

The I expand down ProcessFiles, Entity Health, Availability.

I right click on Process Running Time Monitor and click Properties

I choose the Diagnostic and Recovery Tab.

Then under Configure recovery tasks.  I choose Recovery for critical health state.

I click Run Command

Give it a Recovery Name

Full path to file:

%windir%\system32\taskkill.exe

Parameters:

/F /IM processfiles.exe

Click Create

If you like me you want to check out the new preview but don’t want to spend too much time installing and configuring it, as they will likely change.

You can download the System Center Technical Preview VHDs here:

System Center: Data Protection Manager

System Center: Operations Manager

System Center: Orchestrator

System Center: Service Manager

System Center: Virtual Machine Manager

I go to a lot of customers where when I launch the Operations Manager Shell (PowerShell Interface for SCOM) the shortcut is broken.

This is often caused by a user installing SCOM to a drive other then the C drive.  I’m sure there a many other possible reasons but lets just focus on fixing it.

First I Open up a new PowerShell Command Prompt as administrator.

Then I run $env:PSModulePath

Then I run the same command on my SCOM Management Server that I know that the Operations Manager Shell works.

I notice a big difference in the modules listed for my PowerShell environment.

I can manually fix the Environment Variable by going to the Advanced System Settings

**Note you will have to reboot after fixing this as its not the running config**

Just like there is no crying in football there is no GUIs in PowerShell so I wrote this PowerShell script to fix it..

Here is the script I wrote to fix it with comments

#Get the Current Environment Variable PSModulePath Path
$current = [Environment]::GetEnvironmentVariable("PSModulePath", "Machine")
$current

#Set the Missing Paths  **Note** This may be a different drive or location depending on where you installed SCOM 
$path1 = "C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Powershell\;"
$path2 = "C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\PowerShell\;"
$path3 = "C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Powershell\"

#Combine the Missing Paths with the Current PSModulePath Path
$FixedPath = $current + ";" + $path1 + $path2 + $path3
$FixedPath

#Set the new Environment Variable Path for PSModulePath
[Environment]::SetEnvironmentVariable("PSModulePath", $FixedPath, "Machine")

#Set the current running PSModulePath to the stored path  **Note** You can also just reboot
$env:PSModulePath = [Environment]::GetEnvironmentVariable("PSModulePath", "Machine")

Now when I run the shell it works.

You can download the script here.  https://www.scom2k7.com/downloads/FixOMShell.txt

In a previous post I showed how to install the SCOM 2012 Visio Dashboards on SharePoint 2010.

To install the Visio Dashboards on SharePoint 2013 it’s a little more tricky.

Part 1 – Installing SharePoint 2013 Integration Components

First I install the Operations Manager 2012 R2 console on my SharePoint Server

Next I verify that the SharePoint 2013 Enterprise with Visio Services are enabled.

On my SharePoint server I go to the SharePoint Central Administration Page.

I click Configuration Wizards

I click Launch Farm Configuration Wizard

I scroll down and verify that the Visio Graphics Service is Enabled.

It appears to be already enabled so I click Cancel.

I verify that Microsoft .NET Framework 3.5 Features are enabled.

Ok now I am ready.

First I need to install the Visio Services Data Provider.

I log on to my SharePoint server as the Farm Administrator so I have all the permissions I need.

Now I copy the Server folder over to my SharePoint 2013 server in the C:\temp\ directory from the Extensions I downloaded earlier.

Then I run setup.exe.  Click Next, Next, Close.

On my SharePoint server, I open the SharePoint 2013 Management Shell as an Administrator

In the Command shell I change directories to

C:\Program Files\Visio Services Data Provider for System Center 2012 – Operations Manager

Now I type in

.\InstallOpsMgrDataModule.ps1

I get an error because I am running SharePoint 2013.  I don’t worry about it as I will fix it later.

I run

get-spsolution

I see that it says that opsmgrdatamodule.wsp is Deployed so I am good.

I also see that another one listed called microsoft.enterprisemanagem…  This is from when I installed the SCOM Dashboard Integration
https://www.scom2k7.com/how-to-view-scom-2012-dashboards-in-sharepoint-2010/  and is not required to make the Visio integration work.

I go back to the SharePoint Central Administration Console and Click Manage service applications

I Click New, Visio Graphics Service.

I type in Visio Graphics.

Then I select Create a new application pool and type in VisioGraphicsAppPool and click OK

Note: It may take a little while to complete

Now I Select the Visio Graphics I just created.

I Select Trusted Data Providers

Click Add a new Trusted Data Provider

For Trusted Provider ID I type in:

Microsoft.Office.Visio.Server.OperationsManagerModule.OperationsManagerDataModule, Microsoft.Office.Visio.Server.OperationsManager, Version=1.0.0.1122, Culture=neutral, PublicKeyToken=31bf3856ad364e35

For Trusted Data Provider I Type in: 6

For Trusted Data Provider Description I Type in: SCOM 2012 R2

I Click OK

Back on the SharePoint Central Administration Console and I Click Manage Services on server

I click Start the Visio Graphics Service

Part 2 – Configuring SharePoint 2010 Integration Components

I open the SharePoint Central Administration Console.  I click Configure service accounts from the Security Section

From the dropdown I pick Service Application Pool – SharePoint Web Services System

I need to grant the SCOM2K12\max (or whatever your account listed here is) access to read SCOM.  I open the SCOM 2012 console double click on the Operations Manager Read-Only Operators and add my SharePoint service account to the Operations Manager Read-Only Operations user role.

Part 3 – Adding your Visio Dashboard to SharePoint 2013

I get my SCOM Dashboard Visio document from my previous post.  https://www.scom2k7.com/creating-scom-2012-dashboards-using-visio-2010-or-visio-2013/

I open up the diagram document in Visio 2013

I click Configure to make sure my connection is correct.

I click File, Save As a Visio 2010 Web Drawing

Note: You might get a warning about some Compatibility issue.  Just click Continue.

I now go to my SharePoint page and click Shared Documents and upload the Visio file.

Now I select the document just uploaded

I click on my Visio Document and it comes up in a web console.

I click Allow Refresh

Part 4 – Configuring SharePoint 2013 to show your Visio Dashboard as a web part.

From my site I Add a page

Then I add a Web Part.  Under Business Data I select Visio Web Access

Then I select Click here to open the tool pane

I select the Document from my shared Documents where I stored it earlier.

Then I set the Automatic Refresh interval to 10 and uncheck Show Open in Visio

Then I Click Apply then OK

Now I check out my finished product.