System Center 2012 SP1 Woes, Gotchas, and Workarounds

Microsoft System Center 2012 SP1 adds a bunch of new features to the Suite of products. However, there are a ton of reports coming in that SP1 is causing some frustrating issues in those companies that have decided to deploy it already.  This Wiki post serves to capture the issues in a central location to ensure everyone is aware of them and their potential workarounds until Microsoft releases fixes.

As a member of myITforum and a member of this group you can modify this live document to include issues that you have encountered.

NOTE:  February 20, 2013 – Configuration Manager 2012 SP1 specific information has been moved to it’s own document here:  Configuration Manager 2012 SP1 Issues and Resolutions.  As we begin work with the other product groups within Microsoft concerning the issues around the other Suite products, we will move those issues to their own product-related doc, too.

 

OpsMgr: Missing db pieces after installation

OpsMgr: Web Console issue immediately after upgrade to SP1

* OpsMgr: Errors: Invalid column name ‘ProgressValue’ and Invalid column name “MPResourceElementId” after installation

* OpsMgr: Data Warehouse Database Gets Funny Names & Placement – related: SCOM 2012 SP1 – “Unable to Proceed” Troubleshooting Upgrade Error

* Orchestrator: Runbooks and Folders in the Orchestrator Console are available to users without proper rights

DPM: Virtual machine enters a paused state or a CSV volume goes offline when you try to create a backup of the virtual machine on a Windows Server 2012-based failover cluster and Article ID: 2799728

* DPM: VSS_E_SNAPSHOT_SET_IN_PROGRESS error when you try to back up a virtual machine in Windows Server 2012

* VMM: Suse Linux Enterprise Server 11 is missing from the Linux OS list in System Center 2012 Virtual Machine Manager

* VMM: System Center 2012 – Virtual Machine Manager SP1 setup silently fails

* VMM: System Center 2012 SP1 Update Rollup 1 breaks Service Provider Foundation connectivity in Windows Azure for Windows Server

* Service Manager: Custom PowerShell commands stop working after Service Manager 2012 SP1 upgrade

* Service Manager: OpsMgr agent fails, requires reinstall of Service Manager management server