SCSM – Exchange Connector 3.0 RTM

Recently Microsoft released the System Center Service Manager Exchange Connector 3.0. This  release is compatible with and requires Service Manager 2012 SP1 Update Rollup 2 and later. It is fully supported by Microsoft. Exchange Connector 3.0 contains bug fixes and the initial set of features, which includes the following capabilities:

•    Create incidents and service requests from email.
•    Update incidents, problems, service-request action log from email.
•    Resolve or close incidents from email.
•    Approve or reject change requests from email.
•    Mark a manual activity as completed from email.
•    Add an email file attachment to a work item as an attachment.

Important Note – Remove every previous version of the Exchange Connector prior to the installation of this version

The Send Email solution is no longer included in the Exchange Connector package. Microsoft moved it to the TechNet Gallery.  Send Email solution is still not a supported solution. 

You can find the download location here. The guide walks through the details of deploying, configuring and using the connector.

SCOM 2012 Quick Tip: Monitoring UNIX or Linux

Whenever I suggest monitoring UNIX and Linux monitoring with SCOM, every IT Manager says “yes”,  but when I need to discuss the technical installations with the UNIX SysAdmin the conversation turns;

Nevertheless I have made a collection with very useful links for Monitoring UNIX or Linux machines with SCOM 2012;

• Install Agent on Windows Using the Discovery Wizard [click]
• Install Agent and Certificate on UNIX and Linux Computers Using the Command Line [click]
• Configuring sudo Elevation for UNIX and Linux Monitoring with SCOM 2012 [click]
• Troubleshooting UNIX/Linux Agent Discovery in SCOM 2012 [click]

Recently I had an issue the verification of the UNIX/Linux Agent after a manual installation, the error message was

“The SSL Certificate could not be checked for revocation”

But searching the Technet Library, I found the following article [click] and I found ouy that the Linux server was not correct configured. If all is done well, you can see the result in the SCOM Console

Upgrading SCOM 2012 to SP1

On 20.12.2012 Microsoft released SP1 for the System Center 2012 Suite, for all TechNet and MSDN subscribers. This release makes it possible to upgrade our LAB environment.

In this blog I want to describe my experience with upgrading from System Center 2012, Operating Manager RTM to SP1 in our LAB environment. As like any upgrade in the past [CU, SP or 2007R2 to 2012], keep in mind to

– Backup your servers;
– Backup your SQL databases;
– Backup your unsealed Management Packs;
– Backup your encryption key;

In my opinion this should be done on a regular basis, but especially when making changes on your environment. Also make sure your installation is meets the required hardware and software for System Center 2012 SP1 – Operations Manager. Click on the following TechNet article for more information. [http://technet.microsoft.com/en-US/library/jj656654.aspx]

Accept the License Terms, Confirm the installation location.

System Center 2012 – Operations Manager supported SQL 2008 R2, not any additional SP was required on SQL Server, but System Center 2012 SP1 only supports SQL Server 2008 R2 SP1 and SP2. In my case I needed to update my SQL Server first.

Within our LAB environment I didn’t stumble upon any errors. And SP1 installed succesfully.

**Remember the following when upgrading your existing SCOM 2012 environment **

– Make sure all your components of your System Center 2012 SP1, Operations Manager environment are upgraded with SP1. The Network Summary Dashboard doesn’t function, if you are trying to connect to a SP1 upgraded Management Server, with a RTM Console. 

Microsoft updated the Release Notes after the release of SP1 BETA with 9 more known issues. Click on the following TechNet article for more information. [http://technet.microsoft.com/en-us/library/jj656651.aspx]

System Center 2012 Suite SP1 released

On 20.12.2012 Microsoft released SP1 for the System Center 2012 Suite, for all TechNet and MSDN subscribers. This release makes it possible to upgrade our LAB environment.

Exciting new features are being introduced. Microsoft made a summary of all new features, this summary can be found here.

.. This will be promising for 2013..

SCOM 2012 – Installation MS could not find database

When installing an additional Management Server within an existing management group at one of my customers. I encountered the following issue. When I entered the correct MS-SQL Server and the correct SQL Server Port, there was no database found. The DBList in the wizard was empty.

After double checking all the known and common issues; sufficient permissions on the database, firewall and DNS settings. I checked the OpsMgrSetup.log for more information

[13:50:35]: Info: :Adding to DBList
[13:50:35]: Info: :Key: OperationsManager OMDB: False Empty:False
[13:50:35]: Info: :Key: OperationsManagerDW OMDB: False Empty:False

Why is the wizard not adding the database to the list? I already removed the SCOM 2012 Agent from the server because the installation of the Management Server doesn’t liked it one bit. The solution is to also remove the server (as agent) from the SCOM Console, the installation of the Management Server role runs successfully.

I also check the OpsMgrSetup.log for more information

[14:02:21]: Info: :Adding to DBList
[14:02:21]: Info: :Key: OperationsManager OMDB: True Empty:False
[14:02:21]: Info: :Adding OperationsManager

You can see that the database is added to the DBList.