SCOM 2012 R2 – SQL Server 2014 / Report Viewer 2014 Support

Microsoft announced few month ago SCOM 2012 R2 offers support for SQL Server 2014…

image

And if we go to the TechNet article it also clearly says, SCOM 2012 R2 is supported on SQL Server 2014 here described

image

There is even a perfect table which explains everything clearly…

image

From my point of view, this let’s us assume, that we can just pick SQL Server 2014 and used it for a clean installation of SCOM 2012 R2. In this TechNet article we find even this sentence…

Use this information to evaluate if your SQL Server environment is ready to support the installation of or upgrade to System Center 2012 R2. Use this information whether you are deploying one or multiple components of System Center.

(Source)

So there is no doubt, that it is fully supported to install a clean installation of SCOM 2012 R2 on SQL Server 2014.

Continue reading

SCOM 2012 R2 Technical Preview – A Box of Chocolates?

image

I was asked few times during my engagements what has changed in the System Center Operations Manager Technical Preview. Microsoft released few weeks ago a first technical preview of Windows 10, Windows Server and System Center. You can download Windows 10 here , for Windows Server and System Center you need to have a MSDN subscription to download the sources or test it in Microsoft Azure. But what has changed in SCOM 2012 R2 Technical Preview? Is it like a box of chocolates, a box filled with many sweet things and surprises? Well, not really.

Continue reading

Quick Post – Documenting Setups & Installations Smartly

I am a big fan of smart solutions and approaches. Today I had one of these moments which I really liked. I was going to update a SCOM 2012 environment to SCOM 2012 SP1. Because the customer only had Thin Clients, which basically only provide an RDP client, it was somewhat limited with tools available. SCOM 2012 management server was installed on Windows Server 2008 R2. The customer asked me to document the steps I am doing. Well, not really easy having this kind of setup because usually I use the Snipping Tool or other tools which can create screenshots. Luckily, the customer had a very smart idea, why not use the Problem Steps Recorder to document the SP1 installation :).

Problem Steps Recorder is a small utility which is normally used for a user to document problems on his computer. This utility is a built-in tool since Windows 7 and Windows Server 2008 R2. It is even available in Windows 8 and Windows Server 2012(R2). So, how does it work and what do you get? Let’s see…

Continue reading

SCOM 2012 Veeam MP for VMware 6.0 – Part 2 FAQ

Few month ago I had written about the installation respectively upgrade of the Veeam management pack from version 5.7 to 6.0. You will find this post on my blog called SCOM 2012 Veeam MP for VMware 6.0 – Part 1 Upgrade.
Alec King, who is the “father” of the Veeam MP, attended System Center Universe DACH and because of that he was staying in Switzerland for a few days. Veeam took that chance and has organized a workshop for partners and customers at a steakhouse in Mettmenstetten.

Here a picture of the Veeam MP, the Veeam Meat Packs…oh sorry steaks…

WP_20130919_054

Because I am not much interested into marketing slides only in hard facts, this event was just perfect for me. In this post I would like to summarize the most important topics which came up during the workshop.

Continue reading

SCOM 2012 SP1 – Configure Web Console HTTPS “500 – Internal server error”

Yesterday, I bumped into an issue while configuring https for the SCOM web console. As this is a IIS hosted website there is no magic configuring it. Well, I was taught something else. The SCOM environment was running on Windows Server 2012 and the SCOM 2012 SP1 had UR1 installed. Everything was running fine and smoothly even the web console was running fine over http. The customer requested to have the web console communicating over https.

If you have the web console configured to use http you have two choices. Either you reinstall the web console and select https when you are prompted or you modify the settings manually. I wanted to configure the https settings manually.

I requested the SSL certificate (internal), installed it on the web server and configured the bindings to use this certificate for https requests (port 443). In addition you need to configure the web.config file to use https. The file is located at C:\Program Files\System Center 2012\Operations Manager\WebConsole\WebHost\web.config. I changed the following parameters in the file itself…

  • <serviceMetadata httpGetEnabled=”false”/> (is set to true if you use http)
  • <endpoint address=”” binding=”customBinding” contract=”Microsoft.EnterpriseManagement.Presentation.Security.Services.ILogonService” bindingConfiguration=”DefaultHttpsBinding“/> (is set to DefaultHttpBinding if you use http)
  • <endpoint address=”” binding=”customBinding” contract=”Microsoft.EnterpriseManagement.Presentation.DataAccess.Server.IDataAccessService” bindingConfiguration=”DefaultHttpsBinding“/> (is set to DefaultHttpBinding if you use http)
  • In IIS Manager select the OperationsManager virtual directory, then SSL Settings and check “Require SSL” option and “Ignore” for the Client Certificates.

After that configuration changes, I restarted IIS to load the new settings.  I could open and login into the web console, but as soon I clicked onto a view I received the following error…

image

Continue reading

SCOM 2012 SP1 – Upgrading Linux Agent From SCOM 2007 R2

This week I was working for an international customer. The customer had a SCOM 2007 R2 CU5 infrastructure installed on Windows 2008 R2 SP1 servers with ~800 Windows agents and ~250 Unix based agents which they were going to migrate to SCOM 2012 SP1 UR2 installed on Windows Server 2012 in a side-by-side scenario.

Because of the amount of Unix agents, we were looking to upgrade those agents from the new management group. Therefore we tried to discover the Linux agents using the SCOM 2012 SP1 discovery wizard and ran into the following error…

The WinRM client received an HTTP status code of 501 from the remote WS-Mangement service.

image 

Continue reading