It’s time to plan for some maintenance, Microsoft just release updates for your System Center Products.
If you still run System Center 2012 RTM (without SP1) – Update Rollup 5 For System Center 2012 RTM Is Available
If you run the latest and greatest System Center SP1 – Update Rollup 2 For System Center 2012 SP1 Is Available
An important update has been released by Microsoft – CU5. Below you find what’s updated since CU4 (note that CU5 included all fixes so you don’t need to install any other CU’s):
- Restart of non-Operations Manager services when the agent is updated.
- Updated ACS reports.
- TCP Port Probe incorrectly reports negative ping latency.
- MissingEvent Manual Reset Monitor does not work as expected.
- Drill-through fails due to rsParameterTypeMismatch in the EnterpriseManagementChartControl.
- ACS – Event log message is truncated or corrupted in SCDW.
- UI hang caused by SDK locking.
- ACS Filter fails for certain wildcard queries.
- Edit Schedule button is disabled with SQL Server 2008 R2.
- Web console is timing out while opening the left navigation tree.
- Scheduled Reports view for Windows Server 2003 and SQL SRS 2005 SP3 CU9 – returns System.IndexOutOfRangeException: Index was outside the bounds of the array.
- Signed MPs cannot be imported when new attributes are added to existing classes.
Download CU5 from Microsoft
Good post about CU5 from Kevin Holman
In the last weeks Microsoft released a couple of good and important hotfixes for all of you that uses SCCM 2007 R2.
- If you installed the 2212600 update that lets you import the same driver multiple times and you use driver categories you might have noticed that the category information is overwritten. To fix this Microsoft released the below update:
- If you use SCUP and have a SCCM multi site infrastructure, and you try to publish updates with "metadata only" they will not be replicated to the WSUS hierarchy servers.
Note that the above updates are identical and you should only install one of them (not sure why the WSUS team released two)
- If you have a Task sequence that installs many updates (more then 80) you might have noticed that the TS might stop responding. To fix this Microsoft released the below update:
- If you have a Task sequence that installs a lot of Software (more then 100) you might have noticed that the TS might stop responding. To fix this Microsoft released the below update: