Cumulative Update 2 for System Center 2012 Configuration Manager Service Pack 2 and System Center 2012 R2 Configuration Manager Service Pack 1

Microsoft released on 11/10/2015 Cumulative Update 2 for System Center 2012 Configuration Manager Service Pack 2 and System Center 2012 R2 Configuration Manager Service Pack 1 and solve some issues related to:

– Administrator Console
– Configuration Manager client
– Site systems
– Operating system deployment
– Software distribution and content management
– Microsoft Intune and mobile device management
– Software update management

Plus the some changes that are included in this update for Endpoint Protection, Software distribution/content management, and Microsoft Intune and mobile device management,

For more information and to download the hotfix, check the following link:
https://support.microsoft.com/en-us/kb/3100144?utm_content=bufferfedd3&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer

Abdul Jalil Abou Alzahab

Blog: http://abduljalil.mscloudsolution.net
My Twitter: http://twitter.com/aabolzahab
Linked-In: http://qa.linkedin.com/in/aabolzahab
Facebook: https://www.facebook.com/Abduljalil.Abolzahab/

Advertisements

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

What’s New in System Center 2012 R2

Microsoft announce the release of “R2 Preview ” for Windows Server 2012 and System Center 2012.

Check the below links to check what new on each product:

Abduljalil Abolzahab

ConfigMgr 2012 Client installation Error: Some of the selected resources are not assigned to any site

SYMPTOMS

You have System Center 2012 Configuration Manager deployed in your organization, after you configure boundaries and discovery you found that none of discovered desktops/laptops/servers got ConfigMgr client installed and no site code assign to clients.

When you tried to push clients from site system, you received the following error:

Error: Some of the selected resources are not assigned to any site

Number of resources that are not in any site’s boundaries and will not be installed: xx

CAUSE

This issue may occur if boundary groups are not configured to use assigned site.

RESLOUTION

To solve this issue, make sure that you configured boundary groups to use site assignment as shown in the below figure:

Abduljalil Abolzahab

Configuration Manager 2012 SP1 Client Installation error 0x800b0101

SYMPTOMS

Failed to install System Center 2012 Configuration Manager Service Pack 1 and receive the following error in ccmsetup.log
file.

Error Message

Couldn’t verify ‘C:\WINDOWS\ccmsetup\MicrosoftPolicyPlatformSetup.msi’ authenticode signature. Return code 0x800b0101

Note: You’ll not receive this error If you install System Center 2012 Configuration Manager Service Pack 1 by using media that you obtained on or after January 25, 2013

CAUSE

This issue occurs because the MicrosoftPolicyPlatformSetup.msi file is signed with a digital certificate that does not have the proper timestamp attributes. Microsoft Security Advisory 2749665 has more information on this certificate issue.

RESLOUTION

Method 1

Install Hotfix in kb2801987 before installing System Center 2012 Configuration Manager Service Pack 1 client.

Method 2

Run Microsoft Windows Update and make sure that you install the following updates before install System Center 2012 Configuration Manager Service Pack 1 client:

  1. Update 2756872 for Windows 8 and Windows Server 2012.
  2. Update 2749655 for Windows that are earlier than Windows 8 and Windows Server 2012.

Abduljalil Abolzahab