Cumulative Update 1 for System Center 2012 R2 Configuration Manager available

SCCM

SCCM

Cumulative Update 1 for System Center 2012 R2 Configuration Manager is now available. The update is available here .

This hotfix seems to touch upon many different areas in SCCM 2012 R2 ranging from console updates, OSD image delivery speed to an update for the wakeup proxy feature. While I have known that this has been out I wasn’t sure if I wanted to apply this to my development environment right away or not. When you submit to receive the download link for this the email says, “WARNING This hotfix has not undergone full testing. Therefore, it is intended only for systems or computers that are experiencing the exact problem that is described in the one or more Microsoft Knowledge Base articles that are listed in “KB Article Numbers” field in the table at the end of this e-mail message.” So am I seeing any problems? Maybe…

When I first saw this CU was available I also saw an interesting article describing how Microsoft is changing release methods and frequency of SCEP updates. this article describes how SCEP updates are now going to be available via Microsoft Updates. In the past these updates were applied to the SCCM site server and then pushed out to clients. In an effort to provide better and quicker support to customers, MS is now providing these updates as Software Updates that will be coming out multiple times a year. Additionally Microsoft is going to try and release CUs for ConfigMgr faster it appears so we will probably be seeing these more often. Seeing how this could cause problems with the dashboard in my environment this made me interested in this CU.

The next issue that I have come across with OSD, specifically slow image download times as detailed in this KB. Operators have been expressing a slower than desired image download times. Searching has shown that this is probably something specific to R2. The other part of this KB, which is also applied via the CU 1, talks about the WDS service shutting down. After I pushed the boot image out, and made it available to PXE DPs, it indeed stopped the WDS service. In order to get this back I had to remove PXE from the DP, manually remove WDS and the REMOTEINSALL folder, and then run through the whole PXE configuration again.

All in all this looks like a pretty solid CU that touches upon many areas that I have seen issues with. I expect to be applying this 85MB update soon!

 

Chadd

 

Leave a Reply