System Center 2012 R2 Configuration Manager Cumulative Update 4 released

Recently Microsoft released Cumulative Update 4 for System Center 2012 R2 Configuration Manager to solve issues related to:

– Client
– Software distribution and application management
– Network Access Protection
– Operating System Deployment
– Administrator Console
– Site servers and site systems
– Mobile devices
– Migration
– Reporting
– Software updates

additionally CU4 include the changes to the following:

– Windows PowerShell
– Data replication
– Endpoint Protection
– Operating systems other than Windows

The new version of Configuration Manager will be 5.00.7958.1501 and the new version of Endpoint Protection will be 4.6.0305.0.

For more information about what Cumulative Update 4 fix and update, check KB3026739

Abduljalil Abolzahab

Advertisements

CU: Cumulative Update 1 for System Center 2012 R2 Configuration Manager

Summary

On March 28, 2014 Microsoft release Cumulative Update 1 for System Center 2012 R2 Configuration Manager to fix issue related to:

  1. Administrator Console.
  2. Mobile Device Management.
  3. Reporting.
  4. Application Virtualization.
  5. Internet-based clients.
  6. Software Center.
  7. Operating system deployment.
  8. Endpoint Protection.
  9. Supported operating systems.
  10. Site systems.
  11. Windows PowerShell.
  12. Wake-up proxy

The following KB’s are also included in CU1 for System Center 2012 R2 Configuration Manager:

KB2928122 Application contents are duplicated in stand-alone media in System Center 2012 R2 Configuration Manager
KB2905002 An update is available for the “Operating System Deployment” feature of System Center 2012 R2 Configuration Manager
KB2910552 You cannot stage a Windows PE 3.1 boot image to a Windows XP-based computer in System Center 2012 R2 Configuration Manager
KB2907566 Per-computer variables for imported computers are not read in System Center 2012 R2 Configuration Manager
KB2913703 Applications that use dynamic variable lists are not installed in System Center 2012 Configuration Manager SP1
KB2918997 A hotfix is available to update the Software Requirements user interface for the Mac software distribution operating system in System Center 2012 Configuration Manager
KB2932274 Description of Windows PowerShell changes in Cumulative Update 1 for System Center 2012 R2 Configuration Manager

 

Important Note: After this cumulative update is installed on site servers, any operating system boot image should be updated.

To download hotfix and for more information, please refer to the following link from Microsoft:

http://support.microsoft.com/kb/2938441/en-us

 

Abduljalil Abolzahab

ConfigMgr: Client Push Installation issue – Download transfer take long time

SYMPTOMS

We configure Client Push Installation in System Center 2012 R2 Configuration Manager, the installation of Configuration Manager Agent take long time to install on clients.

We also notice that client take long time to download to C:\Windows\ccmsetup folder and I checked ccmsetup.log file I found the following:

File ‘C:\Windows\ccmsetup\WindowsFirewallConfigurationProvider.msi’ does not exist. Discovery failed.

File ‘C:\Windows\ccmsetup\vcredist_x86.exe’ doesn’t exist.

File ‘C:\Windows\ccmsetup\vc50727_x86.exe’ doesn’t exist.

File ‘C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi’ doesn’t exist.

File ‘C:\Windows\ccmsetup\WindowsFirewallConfigurationProvider.msi’ doesn’t exist.

File ‘C:\Windows\ccmsetup\SCEPInstall.exe’ doesn’t exist.

File ‘C:\Windows\ccmsetup\client.msi’ doesn’t exist.

Download Update: 15750351 out of 61961080 bytes transferred.

Download Update: 16050379 out of 61961080 bytes transferred.

Then I found the “successfully download” message in the ccmsetup.log file after one day. And everything is working fine after client installation such as Hardware and Software inventory, Remote Tool, Software Distribution, Software Update, Endpoint Protection, Power Management and other Configuration feature.

Given this situation, we don’t need to worry about our SCCM server, it should be running well. And there is no download problem between the SCCM server and the client machines.

Solution

Meanwhile, the download slow issue also can be related with BITS settings. It can occurs if the BITS throttling is enabled on the client machines.

To avoid it, we can use Group Policy to force the client to disable the BITS throttling. To do this, please try:

  1. On Domain Controller Server, open GPMC
  2. Create a new policy and link to the client machines (OU) or the domain.
  3. In the left pane of the Group Policy Management Console (GPMC), expand Computer Configuration, expand Administrative Templates, expand Network, and then click Background Intelligent Transfer Service.
  4. In the Setting pane, double-click Limit the maximum network bandwidth for BITS background transfers.
  5. In the top pane of the dialog box, click Disabled.

After that, please the user reboot the client computer and then logon again. The new polices will be applied to the client computers and the BITS throttling will be disabled.

I check if the BITS configured in SCCM client settings by the following:

  1. Open SCCM 2012 Console
  2. Click Administration, then click Client Settings.
  3. By default, check the Properties if the Default Settings.
  4. Check the settings of the first item “Background Intelligent Transfer
  5. Please make sure the settings “Limit the maximum network bandwidth for BITS background transfers” is configured as: False.
  6. If you have customize client settings, please check the same settings.

After disable Limit the maximum network bandwidth through Group Policy the download of the SCCM setup files become very fast.

Abduljalil Abolzahab

Hotfix: Deployment fails when deploy a task sequence to a Windows XP in System Center 2012 R2 Configuration Manager

SYMPTOMS

When you tried to deploy task sequence with captured image to a Windows XP machine using Operating System Deployment feature in System Center 2012 R2 Configuration Manager, the deployment fails and you may found the following error in smsts.log file:

CreateProcess failed. Code(0x800700C1) TSManager datetime 3048 (0x0BE8)

Command line execution failed (800700C1) TSManager datetime 3048 (0x0BE8)

Failed to install boot image.

is not a valid Win32 application. (Error: 800700C1; Source: Windows) TSManager datetime 3048 (0x0BE8)

Failed to install boot image CCR00004.

is not a valid Win32 application. (Error: 800700C1; Source: Windows) TSManager datetime 3048 (0x0BE8)

Failed to reboot the system. Error 0x(800700c1) TSManager datetime 3048 (0x0BE8)

Failed to initialize a system reboot.

is not a valid Win32 application. (Error: 800700C1; Source: Windows) TSManager datetime 3048 (0x0BE8)

Fatal error is returned in check for reboot request of the action (Restart in Windows PE).

is not a valid Win32 application. (Error: 800700C1; Source: Windows) TSManager datetime 3048 (0x0BE8)

Solution

To solve this issue install HOTFIX from KB2910552 on the following:

  1. Central Administration sites.
  2. Primary sites.
  3. Administrator consoles.
  4. Clients (Client update package will be created after installing hotfix on site system server).

Finally don’t forget to update Windows PE 3.1 boot images.

Abduljalil Abolzahab

KB 2905002 Hotfix Update available for OSD feature of SC 2012 R2 Configuration Manager

SYMPTOMS

Microsoft recently release hotfix to solve issue related to “Operating System Deployment” feature on System Center 2012 R2 Configuration Manager, and this update will solve the following issues:

  1. Windows Deployment Service (WDS) stops after enabling PXE Service Point role or when you select Deploy this boot image from the PXE-enabled distribution point.
  2. The download time take long time when Operating System image and packages downloaded to Configuration Manager 2012 R2 Client.

Solution

You need to install hotfix KB2905002 on Central Administration Site, Primary Site, Administrator Console and Clients. And note the following:

  • When you install hotfix on site server, it will create package for client upgrade.
  • Update all boot images after hotfix applied.
  • Re-create all stand-alone media that used for stand-alone deployment.

Abduljalil Abolzahab