Thursday, January 17, 2013

List of System Center 2012 SP1 issues still growing

System Center 2012 SP1 is Generally Available, but contains a lot of bugs. Otherwise you can say that additional configuration is needed to let function ConfigMgr well again. Here's a list of ConfigMgr issues known. The list mentioned is still growing everyday. I installed SP1 at customer locations already, and have indeed additional configuration to make it functional again. Let's have a look:
  1. ConfigMgr 2012 USMT Migration Fails After SP1 Applied
  2. Active Replica Error after the SP1 upgrade for ConfigMgr 2012
  3. Server 2012 OSD Issues in ConfigMgr 2012 SP1
  4. System Center 2012 Configuration Manager Application Catalog does not refresh on F5 in Windows 8 or Windows Internet Explorer 10
  5. Site replication degraded then a minute later, changes back to active
  6. Beware when installing ConfigMgr SP1 when still using vSphere 4 or running other platforms not supporting Windows 8
  7. ConfigMgr 2012 SP1 client installation error with MicrosoftPolicyPlatformSetup.msi - Hotfix Available! or utilize the new SP1 bits
  8. Changes to built-in collections are overwritten when you upgrade to System Center 2012 Configuration Manager SP1
  9. Antimalware Policies issue, a workaround, and a forgotten Beta message with ConfigMgr 2012 SP1
  10. Service Pack 1 for MS ConfigMgr 2012 Resets the SUP Port to 80 and Why does WSUS not sync anymore in ConfigMgr 2012 SP1?
  11. MAC client fails to register in System Center 2012 Configuration Manager SP1
  12. Editing reports in Configuration Manager may fail when Internet Explorer is not the default browser
  13. System Center 2012 Configuration Manager Application Catalog requires Compatibility Mode in Internet Explorer 10
  14. Configmgr SP1 : Windows 7 deployment is not supported anymore from the setup.exe
  15. Application Catalog link breaks if you change the regional settings decimal separator in Software Center in System Center 2012 Configuration Manager
  16. Client push fails with Authenticode Signature error
  17. Virtual Application Fails to Install with Event ID 1008 in the Windows Applications and Services Logs
There are issues reported also on other System Center products, but ConfigMgr has the most by far. The whole list can be found HERE. Let's hope that the list not becomes any longer.. 

Update 21-1-2013: New issues added to the list
Update 30-1-2013: New issues added to the list again

No comments:

Post a Comment