Archive for category ConfigMgr 2007
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.
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:
- On Domain Controller Server, open GPMC
- Create a new policy and link to the client machines (OU) or the domain.
- 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.
- In the Setting pane, double-click Limit the maximum network bandwidth for BITS background transfers.
- 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:
- Open SCCM 2012 Console
- Click Administration, then click Client Settings.
- By default, check the Properties if the Default Settings.
- Check the settings of the first item “Background Intelligent Transfer“
- Please make sure the settings “Limit the maximum network bandwidth for BITS background transfers” is configured as: False.
- 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.
We are using Microsoft System Center Configuration Manager 2007 Service Pack 2 – Operating System Deployment feature. We create task sequence to deploy Windows 7 and install software updates. In my scenario tasks sequence will install more than 60 software updates.
Deployment start and task sequence hang and stop responding when Downloading 1 of 75 Updates (0% Complete) in Install Software Updates action.
According to Microsoft Support KB2509007 This issue occurs because a deadlock occurs when the task sequence retrieves content locations for the updates.
In other scenario this issue may occur when large numbers of software updates are applied via Install Software Update action in task sequence.
To resolve this issue install hotfix from KB2509007 and follow instructions that explain how to install the KB2509007 hotfix during a ConfigMgr 2007 OSD task sequence.
In other scenario you can solve this issue by reduce number of software updates applied via Install Software Update action.
HOTFIX: You cannot distribute large packages in a System Center Configuration Manager 2007 site that uses slow network links
Consider the following scenario:
- You have a Branch Distribution Point (BDP) in a Microsoft System Center 2007 Configuration Manager site that uses slow network links.
- You try to distribute a large package (for example, a 5.7 gigabyte package) or several packages.
In this scenario, the package replication job is automatically canceled on the BDP after seven days. Additionally, the job remains in the System Center Configuration Manager Package replication queue. When this occurs, you do not receive a notification that the replication job is not running.
To resolve this issue install hotfix from KB2679776 on the affected System Center Configuration Manager 2007 Service Pack 2 (SP2) primary site server.
When configure PXE Service Point in Microsoft System Center Configuration Manager 2007, booting may fail with the following errors:
PXE-T04: Access Violation
PXE-E36: Error Received from TFTP Server
PXE-M-F Exiting PXE Rom
You also may notice missing entries in the SMSPXE.log
This can occur because of wrong DHCP configuration.
You may need to configure IP helper (BOOTP) settings on the routers OR configure DHCP scope options in case you have Cisco DHCP instead of Microsoft DHCP.
To Configure DHCP Scope on Cisco Routers, add the following to DHCP Scope:
next-server ‘IP Address of PXE Service Point’