Microsoft System Center Configuration Manager 2007 backups may fail if other VSS-aware backup software is scheduled to run concurrently. In this scenario, the Smsbkup.log will show entries similar to the following:
Deleting E:SMSbackupSiteServerSMSServerinboxesauthstatesys.boxincoming, FAILED, Win32 Error = 145
Deleting E:SMSBackupSiteServerSMSServerinboxesauthddm.box, FAILED, Win32 Error = 145
Deleting E:SCCMBackupBackup, FAILED, Win32 Error = 145
Failed to delete the contents of the backup folder. Error Code = 0x0 SMS_SITE_BACKUP
Error: Deleting the existing files in the backup location failed… SMS_SITE_BACKUP
SMS site backup failed. Please see previous errors. SMS_SITE_BACKUP
SMS site backup service is stopping. SMS_SITE_BACKU
These errors can occur if the Volume Shadow Copy Service (VSS) provider is in use by another process. Configuration Manager Backup expects to have exclusive access to these resources when performing a backup.
To prevent these errors, configure Configuration Manager Backup to start at a time outside the window for other backup jobs on the server. The schedule for this can be found in the Configuration Manager Console under Site Management -> Site Code -> Site Settings -> Site Maintenance -> Tasks -> Backup ConfigMgr Site Server.
Microsoft released a hotfix for Asset Inteligence – Hotfix rollup for Asset Intelligence in System Center Configuration Manager 2007 SP2
it optimizers some of the reports, bad detection and incorrect reporting
This hotfix rollup resolves the following issues:
- The query for the Asset Intelligence “License 01A” report does not detect Microsoft SQL Server 2008 licenses.
- The query for the Asset Intelligence “License 01A” report does not detect SQL Server 2008 R2 licenses.
- The query for the Asset Intelligence “License 01A” report does not detect licenses of the SQL Server 2000 editions except of SQL Server 2000 RTM.
- The query for the Asset Intelligence “License 01A” report does not detect Microsoft Exchange Server 2007 licenses.
- The query for the Asset Intelligence “License 01A” report does not detect Microsoft Exchange Server 2010 licenses.
- The query for the Asset Intelligence “License 01A” report incorrectly reports Microsoft Office Personal 2007 as Microsoft Office Small Business 2007.
- The query for the Asset Intelligence “License 06A” and “License 06B” reports does not detect SQL Server 2008 licenses.
- The query for the Asset Intelligence “License 06A” and “License 06B” reports does not detect Exchange Server 2010 licenses.
- The query for the Asset Intelligence “License 01A” report incorrectly reports some editions of Windows Vista, of Windows Server 2008 R2, or of Windows 7 as Windows XP.
- The query for the Asset Intelligence “Software 01A” report reports the instance count of SQL Server 2008 R2 or SQL Server 2008 incorrectly. The reported count is two times the actual count.
- The Asset Intelligence custom labels are limited to 100 custom labels.
Steve Rachui published another great post over on his blog, this time about using the Windows Server 2008 R2 Direct Access feature to manage Internet based clients of System Center Configuration Manager 2007:
“Do you have internet based clients that you want to manage? Does the idea of switching to SCCM native mode to manage those client make you nervous? Do you have Windows 2008 R2 servers in your environment and are the internet systems you want to manage running Windows 7 (Enterprise or Ultimate) or Windows Server 2008 R2? If you said yes to all of these questions then you might just be interested in taking a look at Direct Access (DA).”
To read Steve’s excellent blog post see the following link:
Direct Access – SCCM – Managing internet clients
The Task Sequence fails.
Examining the SMSTS.log reveals the following error:
Installing SMS client OSDSetupHook
Clearing existing client configuration. OSDSetupHook
Cleaning existing client certificates from SMS certificate store OSDSetupHook
Restoring SMS client identity. OSDSetupHook
Could not import certificate to temporary store (0x80092024) OSDSetupHook
Failed to restore client certificates. Code 0x80092024. OSDSetupHook
Failed to restore SMS client identity. Code 0x80092024. OSDSetupHook
Failed to install SMS Client (0x80092024) OSDSetupHook
Failed to execute task sequence (0x80092024) OSDSetupHook
Examining the ccmsetup.log and client.msi.log reveals that the logs either do not exist or have not updated since the ConfigMgr 2007 client was originally installed on the reference image.
For all the details as to the cause and how to resolve it see the following Knowledge Base article:
KB2028442 – System Center Configuration Manager 2007 client may not install during an OSD Task Sequence in a Refresh scenario
On a system that is running Windows 7 x86 (32 bit) the System Center Service Manager 2010 Console fails to launch. Additionally, The following event is logged in the Application log:
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Faulting application Microsoft.EnterpriseManagement.ServiceManager.UI.Console.exe, version version number , faulting module igdumd32.dll, version version number , fault address address.
The system also has one of the following Intel GPU chipsets:
- Intel Q43 Express Chipset
- Intel Q45 Express Chipset
- Mobile Intel 4 Series Express Chipset Family
For the latest status of this issue please see the following Knowledge Base article:
KB2278267 – On a system that is running Windows 7 x86 (32 bit) the System Center Service Manager 2010 Console fails to launch
Microsoft Configuration Manager 2007 setup on Windows Server 2008 may fail to proceed with the following error message:
Web-based Distributed Authoring and Versioning (WebDAV) is required for the management point and distribution point site system roles. If you have selected to install a site role requiring WebDAV, and it is not enabled, this rule will fail. Web-based Distributed Authoring and Versioning (WebDAV) is not enabled and/or IIS 6 WMI compatibility component for IIS7 is not installed on the computer specified for management point installation or setup was unable to verify remote IIS settings because IIS common components were not installed on the site server computer. ConfigMgr requires WebDAV to be installed and enabled in Internet Information Services (IIS) for management point site systems. Setup cannot continue.
This occurs even if the steps from How to Configure Windows Server 2008 for Site Systems article has been followed.
To resolve this issue and allow ConfigMgr 2007 setup to complete follow the steps below:
- Click on Start, click on All Programs, Click on Administrative Tools and then click on Internet Information Services (IIS) Manager.
- Highlight the entry on the left-hand pane for your servername (SERVERNAME (DOMAINuser)).
- Double-click on WebDAV Authoring Rules.
- Delete any rules that appear.
- Highlight your Default Web Site (or ConfigMgr 2007 web site) and edit the WebDAV settings at that level as explained in this article: http://technet.microsoft.com/en-us/library/cc431377.aspx
For all the details and the latest version of this document please see the following new Knowledge Base article:
KB2378924 – System Center Configuration Manager 2007 prerequisites checker reports WebDAV settings are incorrect
This new module allows adminstrators to manage vPro clients programatically very easy! 🙂