Very useful report for identifying make and models in your environment

SELECT
Manufacturer0 AS Manufacturer,
Model0 AS Model,
COUNT (Model0) AS Count
FROM v_GS_COMPUTER_SYSTEM
GROUP BY Model0, Manufacturer0
ORDER BY Manufacturer0, Model0

This article describes the prerequisite hotfix for System Center Configuration Manager 2007 R3.

This hotfix is required for the following computers that are running System Center Configuration Manager 2007 Service Pack 2 (SP2):

• Primary and secondary site servers
• Remote administrator console servers
• Remote provider servers
• Client computers

read more: http://support.microsoft.com/default.aspx?scid=kb;en-us;977384&sd=rss&spid=12769

Today we are pleased to announce the release and availability of System Center Configuration Manager 2007 R3! Organizations of all sizes use System Center Configuration Manager for better insight and control of their servers, PCs and devices across physical, virtual and distributed environments. Now, R3 brings a complete set of power management tools for more Green IT, mobile device management capabilities, as well as other enhancements.

Below is a quick summary of what’s new with R3. Go here to download the evaluation software – it will be available at around 2 p.m. Pacific time.

see more at: http://blogs.technet.com/b/systemcenter/archive/2010/10/14/system-center-configuration-manager-2007-r3-unleashed.aspx

wuhu!! 🙂

ConfigMgr Status Message Viewer – The parameter is incorrect

The error appears when trying to view package status and system status

The “Status Messages:SetViewing Period” dialog shows up, but there are no items in “Select Time Zone” and “Select date and time” comboxes and there are label text missing

Solution:

Backup

• SoftwareMicrosoftWindows NTCurrentVersionTime Zones key
• Delete New Zealand
• Try again, if it works re-import the key again and it now works

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

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