Brandon Linton - System Center and OS Deployment Blog

The Do's, Don'ts and what did i do's of System Center and OS Deployment...

Cumulative Update 2 for System Center 2012 Configuration Manager Service Pack 1 Now Available!

Cumulative Update 2 for System Center 2012 Configuration Manager Service Pack 1 Now Available!

  • Comments 3
  • Likes

Cumulative Update 2 for System Center 2012 Configuration Manager Service Pack 1 has shipped!  Key feature to this update aside from bug fixes etc... for OS Deployment is the ability for you to add a WinPE 3.1 boot image to a ConfigMgr 2012 SP1 CU2 Site which will give you support now for VMware Workstation and ESX Servers where WinPE 4 wasn't supported!!!

http://support.microsoft.com/kb/2854009

Administrator Console

•The Add Site Server Roles Wizard incorrectly blocks adding a site server when the first word of the server's fully qualified domain name is longer than 15 characters.

•Multiple nodes and property sheets in the Administrator Console can now be announced correctly by screen reader software.

 Application Virtualization

•Virtual Application packages that are saved on a Distributed File System (DFS) share may not migrate from Configuration Manager 2007 to Configuration Manager 2012. Errors that resemble the following are logged in the MIGMCTRL.log file:

 Failed to connect to share \\production\dfs\Virtual Applications\App Source : Error 0x80070520

Impersonation is reverted.

Set the status of the entity Virtual Application 1 to Failed.

 Set the status of the job entity Virtual Application 1 to Failed.

Microsoft.ConfigurationManagement.Migration.MigrationException: Failed to connect to share \\production\dfs\Virtual Applications\App Source : Error 0x80070520

 •Nonalphanumeric characters in the CertificateIssuers string cause site assignments not to work

 

in a System Center 2012 Configuration Manager Site environment.

 Operating system deployment

•Task Sequences may ignore the Multicast Only flag when downloads are performed within the full operating system instead of Windows PE.

•A task sequence that has multiple "Install Application" steps may fail. Additionally, the following error message is logged in the SMSTS.log file:

 Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

 •Clients may not download a new operating system image when custom ports are defined for the site server. The SMSTS.log file will contain error messages that resemble the following:

 WinHttpQueryHeaders() returns status code 404 (Not Found)

SendWinHttpRequest failed. 80190194.

DownloadFile failed. 80190194.

Error downloading file from http://siteserver.contonso.com:80/SMS_DP_SMSPKG$/CAS0000A/sccm?/install_ipremote.cmd to C:\_SMSTaskSequence\Packages\CAS0000A\install_ipremote.cmd

DownloadFiles failed. 80190194.

  

•Cumulative Update 2 offers limited support for deployment of Windows PE 3.1-based images. These images must be completed before they are added to the site server. If later changes are needed, they can be made by using the Deployment Image Servicing and Management (DISM) tool. Any Distribution Points that have the old image must be updated.

 The following optional components have to be installed beforehand:◦WinPE-Scripting.cab

◦WinPE-WMI.cab

◦WinPE-WDS-TOOLS.cab

 The following operations are not supported:◦Installing additional optional component through Configuration Manager

◦Adding drivers

◦Setting scratch space

◦Configuring prestart command

◦Configuring background image file

◦Enabling and disabling command prompt support (debug mode)

 Asset Intelligence

•"Software 09B - Computers with infrequently used software installed" reports do not contain accurate data for Windows Installer-based applications that are updated.

 Mobile device management

•Windows Mobile 6.5 devices no longer receive application policies after the site server is upgraded from the release version of Configuration Manager 2012 to Configuration Manager 2012 Service Pack 1.

 

Software distribution

•The content status of a package is stuck in the "In progress - Waiting for Content" status

 in System Center 2012 Configuration Manager SP1.

•Content status may show a state of "Unknown" when a distribution point on a Configuration Manager 2007 Secondary Site is upgraded to Configuration Manager 2012.

•Status messages from pull-distribution points are now routed through management points instead of directly to site servers. This decreases the site server performance effect of having multiple pull-distribution points.

 Updated list of supported Linux and UNIX clients

•The list of supported UNIX and Linux platforms is updated to include x86 and x64 versions of the following:◦Ubuntu 12.04

◦Ubuntu 10.04

◦Oracle Linux 5

◦Oracle Linux 6

◦CentOS 5

◦CentOS 6

◦Debian 5

◦Debian 6

 Site systems

•Status Manager may not process changes to built-in Status Filter Rules on localized Configuration Manager installations. Entries similar to the following may be logged in the STATMGR.log file:

 ERROR: The component item for SMS_STATUS_MANAGER in the master site control file does not contain property list items for a status filter named "SMS_STATUS_MANAGER", or those property lists are corrupt or badly formatted.

 •Installation of the Client Notification component (bgbisapi.msi) will fail on sites that have custom websites (SMSWEB) or custom ports that are defined. The BGBSetup.log will contain the following errors messages:

 bgbisapi.msi exited with return code: 1603

Backing up X:\Program Files\Microsoft Configuration Manager\logs\bgbisapiMSI.log to X:\Program Files\Microsoft Configuration Manager\logs\bgbisapiMSI.log.LastError

Fatal MSI Error - bgbisapi.msi could not be installed

 The bgbisapiMSI.log will also contain errors that resemble the following:

 ERROR: Failed to configure sms ports '0x80020009'.

ERROR: Failed to process port information.

@@ERR:25011

Product: BGB http proxy -- Internal Error 25011. 80020009

Internal Error 25011. 80020009

CustomAction CcmCreateIISVirtualDirectories returned actual error code 1603

 •Active Directory User and Group Discovery methods may not update group relationship data when the "Enable delta discovery" option is selected.

 Configuration Manager SDK

•The CPApplet.CPAppletMgr Automation object returns error 0x80040154 when you use the object on a 64-bit operating system that has Configuration Manager Compatibility Shims (32BitCompat.msi) installed.

 

Client

•Automatic client updates are unsuccessful for Configuration Manager 2007 clients

 in System Center 2012 Configuration Manager Service Pack 1

 Cumulative Update Setup Wrapper (Installer)

•The installer can now be run again on the same site server to create or to re-create deployment assistance items (packages and programs).

•The installer can update the Administrator Console directly when the installer is run on a site server or on a workstation where the console is installed. Earlier versions of the installer only copied the Administrator Console update (.msp) to the file system, and the console update had to be installed separately. The previous installation method of installing the update manually is still supported.

•The logging format is improved to increase detail for tracking progress or for troubleshooting installation failures.

Comments
  • Hi, I'm having an issues where a lot of my DP's Packages went from Success to Error after installing CU2.  Have you experienced this?

  • The mentioned fix in CU2 (site systems) “internal server error 25011″ is not fixed. In a lab environment, i installed a SCCM SP1 server with CU3!! (CU3 replaces CU2). The MP is configured in HTTPS and working. Also installed a MP and DP in an untrusted forest with HTTPS (and working). After installing the Application Catalog Website point (on the untrusted forest), the "internal server error 25011"  and "failed to configure sms ports 0x8004005" is reported in the portalwebMSI.log on the site system of the untrusted forest.

  • Hi Erwin,

    This issue was resolved in CU2 and yes CU3 is cumulative so it does include the fix in CU3 i would suppose you might be hitting a different issue possibly.  If you are still able to repro i would open a case you will not be charged if it is indeed a bug.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment