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

http://support.microsoft.com/?id=2263826

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.

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

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:

1. Click on Start, click on All Programs, Click on Administrative Tools and then click on Internet Information Services (IIS) Manager.
2. Highlight the entry on the left-hand pane for your servername (SERVERNAME (DOMAINuser)).
3. Double-click on WebDAV Authoring Rules.
4. Delete any rules that appear.
5. 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

Common Daily Maintenance Tasks

Some common daily maintenance tasks are listed below:

• Verify that predefined maintenance tasks scheduled to run daily are running successfully.
• Check Configuration Manager 2007 site database status.
• Check site server status.
• Check Configuration Manager 2007 site system inboxes for backlogs.
• Check site systems status.
• Check client status.
• Check the operating system event logs on site systems.
• Check the SQL Server error log.
• Check system performance.

Common Weekly Maintenance Tasks

Some common weekly maintenance tasks are listed below:

• Verify that predefined maintenance tasks scheduled to run weekly are running successfully.
• Delete unnecessary files from site systems.
• Produce and distribute end-user reports if required.
• Back up application, security, and system event logs and clear them.
• Check the site database size and verify that there is enough available disk space on the site database server to allow the site database to grow.
• Perform SQL Server database maintenance on the site database according to your SQL Server maintenance plan.
• Check available disk space on all site systems.
• Run disk defragmentation tools on all site systems.

Common Periodic Maintenance Tasks

Some common periodic maintenance tasks are listed below:

• Review the security plan for any needed changes.
• Change accounts and passwords if necessary according to your security plan.
• Review the maintenance plan to verify that scheduled maintenance tasks are scheduled properly and effectively depending on configured site settings.
• Review the Configuration Manager 2007 hierarchy design for any needed changes.
• Check network performance to ensure changes have not been made that affect site operations.
• Verify Active Directory settings affecting site operations have not changed. For example, you should ensure that subnets assigned to Active Directory sites used as boundaries for a Configuration Manager 2007 site have not changed.
• Review the disaster recovery plan for any needed changes.
• Perform a site recovery according to the disaster recovery plan in a test lab using a backup copy of the most recent backup snapshot created by the Backup ConfigMgr Site Server maintenance task.
• Check hardware for any errors or hardware updates available.
• Check overall health of site.

Delete all packages? This should do it.

(replace MyLABServer) with site servername, and LAB with site code (in powershell 2.0):

$pkgs = gwmi sms_package -computer MyLabServer -namespace rootsmssite_LAB

$pkgs | % {$_.Delete()}

This does all classic packages.  If you want to do others, you’ll have to change the class – sms_DriverPackage, sms_ImagePackage, etc…