With UR5 there is a bug in the UI that does not show SMB file shares when you try to deploy HA VM or do storage migration to SMB share. Functionality was still working when you use PowerShell. Continue reading “Install SMB Share SCVMM 2012 R2 UR5 UI Hotfix”
There is a nasty issue with the SCSM console that when it is maximized it can consume a lot of CPU. This issue has been around since SCSM 2012 and it can be annoying in environments with Terminal Servers. As I’ve reported this issue a couple of times and pushed hard to be fixed I am proud to announce that this will happen very soon for SCSM 2012 SP1 and SCSM 2012 R2. This will happen in the next rollup updates for System Center 2012 SP1 and R2 and you can read more about here along with many other improvements and fixes. I hope you will be glad that this issue is fixed and that it will bring you on new perspective about the SCSM console performance.
Consider the following situation:
- You install VMM 2012 R2 Preview
- You install manually Windows Server 2012 Hyper-V Host/s
- You install manually Windows Server 2012 R2 Preview Hyper-V Host/s
- You add the Hyper-V 2012 and 2012 R2 hosts to VMM 2012 R2
- You create Port Profile for teaming with Dynamic algorithm
- You create Logical Switch to which you add the created Port Profile
- You open the properties of Hyper-V 2012 host and in Virtual Switches tab you’ve try to add Logical Switch. Immediately the VMM 2012 R2 Preview console crashes with the following error:
Dynamic algorithm for NIC Teaming is available only on Hyper-v 2012 R2 hosts. Even if you create a port profile with a supported by Hyper-V 2012 NIC Teaming algorithm and assign it to different logical switch you still might get the error.
Change the port profile with Dynamic algorithm to use Host Default that way when the Hyper-V host is 2012 Hyper-V Port algorithm will be used and for 2012 R2 Host Dynamic algorithm will be used. The console will not crash on trying to add logical switch on Hyper-V 2012 host.
Recently I’ve encountered a bug in the VMM console. It is nothing major but I’ve decided to share it. If you are configuring SCOM-VMM integration and more specifically SQL Server Analysis Services for SCOM-VMM integration you may experience VMM console restart if you enter backlash “\” character in the filed for SSAS server or SSAS instance. I’ve experienced this bug with VMM 2012 SP1 UR2. This bug is not big deal as this operation is done only once and backlash character should not be used as there are separate fields for SQL server and SQL instance.
I’ve ran into an issue where I couldn’t install SCOM 2012 SP1 agent on a server. I was getting the following error:
The System Center 2012 – Operations Manager agent cannot be installed on a computer on which the Operations Manager management server, gateway server, Operations console, operational database, web console, System Center Essentials, or System Center Service Manager is already installed.
The server had OpsMgr and SCSM consoles installed because it was Orchestrator server. To resolve my issue I had to remove both consoles in order to be able to install the OpsMgr agent. I’ve removed both consoles installed the agent and than installed the consoles again.
I cannot remember having this issue with SCOM 2007 R2 but definitely had it with MOM agent 2005 and MOM 2005 Consoles. It will be better if such dependencies are removed in System Center vNext.