Thursday, February 18, 2010

For inboxes information to export to excel for single system complete list

Script for complete Inboxes checks to export the results to Excel file

sStartPath = "\\your sccmservername\SMS_smssitecode\inboxes\"
Set oFSO = CreateObject("Scripting.FileSystemObject")

Set objExcel = CreateObject("Excel.Application")
objExcel.Visible = True
intRow = 2

objExcel.Cells(1, 1).Value = "Directory"
objExcel.Cells(1, 2).Value = "Count"


Sub ListFolders(sPath)
Set oFolder = oFSO.GetFolder(sPath)
objExcel.Cells(intRow, 1).Value = oFolder.Path
objExcel.Cells(intRow, 2).Value = oFolder.Files.Count
intRow = intRow + 1

For Each oFldr In oFolder.SubFolders
ListFolders oFldr.Path
End Sub

Set sStartPath = Nothing
Set objExcel = Nothing

objExcel.Selection.Interior.ColorIndex = 19
objExcel.Selection.Font.ColorIndex = 11
objExcel.Selection.Font.Bold = True

Delete script for bad inboxes files for SMS / SCCM

Delete script for bad inboxes files for SMS / SCCM
save the above as .bat or .cmd file and run it. You need to replace the server name with sccm server name and site code

Jonathan Swift  - "May you live every day of your life."


date /t >>"D:\SCCM Team\Daily_checks_archive_Reports\INBOXES\BACKLOGS.txt"
ECHO dc1 >>"D:\SCCM Team\Daily_checks_archive_Reports\INBOXES\BACKLOGS.txt"
diruse /* /m "\\MYSCCMSERVERNAME\d$\Program Files (x86)\Microsoft Configuration Manager\inboxes" >>"D:\SCCM Team\Daily_checks_archive_Reports\INBOXES\BACKLOGS.txt"

date /t >>"D:\SCCM Team\Daily_checks_archive_Reports\INBOXES\BACKLOGS.txt"
ECHO P01 >>"D:\SCCM Team\Daily_checks_archive_Reports\INBOXES\BACKLOGS.txt"
diruse /* /m "\\MYSCCMSERVERNAME2\d$\Program Files (x86)\Microsoft Configuration Manager\inboxes" >>"D:\SCCM Team\Daily_checks_archive_Reports\INBOXES\BACKLOGS.txt"
date /t >>"D:\SCCM Team\Daily_checks_archive_Reports\INBOXES\BACKLOGS.txt"
ECHO P02 >>"D:\SCCM Team\Daily_checks_archive_Reports\INBOXES\BACKLOGS.txt"
diruse /* /m "\\MYSCCMSERVERNAME3\d$\Program Files (x86)\Microsoft Configuration Manager\inboxes" >>"D:\SCCM Team\Daily_checks_archive_Reports\INBOXES\BACKLOGS.txt"
date /t >>"D:\SCCM Team\Daily_checks_archive_Reports\INBOXES\BACKLOGS.txt"
ECHO P03 >>"D:\SCCM Team\Daily_checks_archive_Reports\INBOXES\BACKLOGS.txt"
diruse /* /m "\\MYSCCMSERVERNAME4\d$\Program Files (x86)\Microsoft Configuration Manager\inboxes" >>"D:\SCCM Team\Daily_checks_archive_Reports\INBOXES\BACKLOGS.txt"

date /t >>"D:\SCCM Team\Daily_checks_archive_Reports\INBOXES\BACKLOGS.txt"
ECHO P04 >>"D:\SCCM Team\Daily_checks_archive_Reports\INBOXES\BACKLOGS.txt"
diruse /* /m "\\MYSCCMSERVERNAME5\d$\Program Files (x86)\Microsoft Configuration Manager\inboxes" >>"D:\SCCM Team\Daily_checks_archive_Reports\INBOXES\BACKLOGS.txt"
You need to download the DIRUSE.exe file or get it from 2k3 support tools

Pablo Picasso  - "Computers are useless. They can only give you answers."

For Windows 2003 Server Event viewer archive script

For Windows 2003 Server Event viewer archive script, FYI! in 2k8 you can set archive option but not in 2k3 or below 2k8 servers
strArchiveFolder = "C:\BckEvt"
ServerName = "."
Set WS = CreateObject("Wscript.Shell")
Set FSO = CreateObject("Scripting.FileSystemObject")
DateString = CurrentDate()
Purge = True
on error resume next
StartTime = Now
Output "---------------------------------"
OutPut "Started at: " & CStr(Now)
Output ""
Set System = GetObject("winmgmts:{(Backup,Security)}\\" & ServerName & _
If Err.Number = 0 Then
Set colLogs = System.ExecQuery("select * from Win32_NTEventLogFile",,48)
For Each refLog In colLogs
LogName = ServerName& "_" & LogFileName(refLog.LogFileName) & _
"_" & DateString
If FSO.FileExists(strArchiveFolder & "\" & LogName & ".evt") Then _
FSO.DeleteFile(strArchiveFolder & "\" & LogName & ".evt")
If Purge Then
RetVal = reflog.ClearEventlog(strArchiveFolder & "\" & LogName & ".evt")
RetVal = reflog.BackupEventlog(strArchiveFolder & "\" & LogName & ".evt")
End If
If RetVal = 0 Then
Output vbTab & "Log was archived in .evt format: " & LogName & ".evt"
If Purge Then Output vbTab & "All events were cleared from the log"
Output vbTab & "Error while archiving in .evt format."
End If
Output vbTab & "Failed connect to the server"
End If
Set colLogs = Nothing
Set refLogs = Nothing
Set System = Nothing
Output "----------------------------------------"
OutPut "Finished at: " & CStr(Now)
Output ""
Output ""
Set WS = Nothing
' FullLog.Close ???FullLog=unknown
Set FullLog = Nothing
Set FSO = Nothing
Function CurrentDate
Today = Date
If Month(Today) < 10 Then
CurrentDate = "0" & CStr(Month(Today))
CurrentDate = CStr(Month(Today))
End If
If Day(Today) < 10 Then
CurrentDate = CurrentDate & "0" & CStr(Day(Today))
CurrentDate = CurrentDate & CStr(Day(Today))
End If
CurrentDate = CurrentDate & CStr(Year(Today))
If Hour(Time) < 10 Then
CurrentDate = CurrentDate & "0" & CStr(Hour(Time))
CurrentDate = CurrentDate & CStr(Hour(Time))
End If
End Function
Function LogFileName(LogName)
Select Case LogName
Case "Application"
LogFileName = "app"
Case "Directory Service"
LogFileName = "dir"
Case "DNS Server"
LogFileName = "dns"
Case "File Replication Service"
LogFileName = "rep"
Case "Security"
LogFileName = "sec"
Case "System"
LogFileName = "sys"
End Select
End Function
Sub Output(Text)
' wscript.echo text
' FullLog.writeline text ???FullLog=unknown
End Sub


Mike Ditka  - "If God had wanted man to play soccer, he wouldn't have given us arms."

Wednesday, February 17, 2010

Tool to create MOF file

Tool to create MOF file

Mark Cochrane (System Center Configuration Manager MVP) released an excellent tool to assist with your custom MOF snippet creations, RegkeyToMof.  Grab it from here:

To use it, Run regkeytomof on a box which has the regkeys you want to gather, and browse in the top window to the Regkey Location, until you see the keys & values you want on the right.  Then below in the middle-right, give it a ClassGroup (like CUSTOM) and a ClassName (this must be unique for each custom mof edit you do--but the ClassGroup of CUSTOM can always be CUSTOM) then just copy & paste the results for configuration mof & sms_def.mof
If there are values that you don't want to see in your database, before you save sms_def.mof, just change those from TRUE to FALSE.  (Leave them defined, but change to FALSE, it needs to be consistent)

For example, I've been meaning to make up a Microsoft Forefront client mof edit, similar to the ones available for McAfee and Symantec, for client AV signature info.  Mark's tool made it much easier.  If you look at the below screenshot, I just browsed until I found the regkeys I wanted (in Software\Microsoft\Microsoft Forefront\Client Security\1.0\AM\Signature Updates.  On the right, I could see there were entries for AVSignatureVersion and ASSignatureVersion.  Looks like just what I wanted!

In the middle, I changed the Classgroup to CUSTOM.  I always use CUSTOM for my custom edits.  That helps me to differentiate anything I've done from a 'real' mof snippet from Microsoft.  If you like, you could use any name; but I would keep it short and consistent, and no spaces.  i.e., if you work for ACME Corporation, use something like ACMECorp.  For ClassName, this must be unique for each custom edit you make.  For example, let's say that one day there will be a Microsoft Forefront version 2.0, and that clients' info goes into a completely different area of the registry.  But for a time, I might need to gather both 1.0 keys and 2.0 keys.  So I couldn't call both of the ClassNames "MSForefront".  That's why in my sample I called it MSForefront1, anticipating that one day there will be a MSForeFront2 I'll want to have.  Also, for the ClassName, no spaces.  And don't use _ i.e., don't use MS_ForeFront_1.0.  I think you *can* use them, but in some places within your database tables/views, you might end up with double _; that just feels messy to me.  So avoid the whole thing and don't use spaces or underscores.  AND keep it short. 

So, cool; I've got my edits.  I'm using Configuration Manager, so I need the results from the SCCM Configuration.mof and SCCM sms_def.mof.  Now, to check them.  Hm... do I really need AVSignatureApplied?  I could, I suppose.. but if I *do* want them, if I actually go look at the registry, those binary values are multi binary, not just 1 entry for binary of 0 vs 1.  It's hard to programmatically see that with regkeytomof, so it's not already set to be multi; but if I DID want to gather that info, I just need to add the [] to those entries.  But actually... those values don't really mean much to me.  They aren't in any kind of calendar date format that makes sense to me.  So I would likely just change those from TRUE to FALSE anyway.  So I'd end up with this.  And it only took me about 10 minutes to get that edit together, and make decisions about TRUE vs. FALSE.  Easy!

// configuration.mof for MS Forefront 1.0 Client Signatures
#pragma namespace ("\\\\.\\root\\cimv2")
#pragma deleteclass("MSForeFront1", NOFAIL)
Class MSForeFront1
[key] string KeyName;
String EngineVersion;
String AVSignatureVersion;
String ASSignatureVersion;
Boolean ASSignatureApplied[];
Boolean AVSignatureApplied[];
String SignatureLocation;
Instance of MSForeFront1
[PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Microsoft Forefront\\Client Security\\1.0\\AM\\Signature Updates|EngineVersion"),Dynamic,Provider("RegPropProv")] EngineVersion;
[PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Microsoft Forefront\\Client Security\\1.0\\AM\\Signature Updates|AVSignatureVersion"),Dynamic,Provider("RegPropProv")] AVSignatureVersion;
[PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Microsoft Forefront\\Client Security\\1.0\\AM\\Signature Updates|ASSignatureVersion"),Dynamic,Provider("RegPropProv")] ASSignatureVersion;
[PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Microsoft Forefront\\Client Security\\1.0\\AM\\Signature Updates|ASSignatureApplied"),Dynamic,Provider("RegPropProv")] ASSignatureApplied;
[PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Microsoft Forefront\\Client Security\\1.0\\AM\\Signature Updates|AVSignatureApplied"),Dynamic,Provider("RegPropProv")] AVSignatureApplied;
[PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Microsoft Forefront\\Client Security\\1.0\\AM\\Signature Updates|SignatureLocation"),Dynamic,Provider("RegPropProv")] SignatureLocation;

//sms_def.mof for MS Forefront 1.0 Client Signatures
#pragma namespace ("\\\\.\\root\\cimv2\\SMS")
#pragma deleteclass("MSForeFront1", NOFAIL)
Class MSForeFront1: SMS_Class_Template
[SMS_Report(TRUE),key] string KeyName;
[SMS_Report(TRUE)] String EngineVersion;
[SMS_Report(TRUE)] String AVSignatureVersion;
[SMS_Report(TRUE)] String ASSignatureVersion;
[SMS_Report(FALSE)] Boolean ASSignatureApplied[];
[SMS_Report(FALSE)] Boolean AVSignatureApplied[];
[SMS_Report(FALSE)] String SignatureLocation;



Tools and Utilities for ConfigMgr / SCCM 2007 Including beta's


  • SccmAutoDoc Kim Oppalfens, who is a SCCM MVP, has released a neat utility called SccmAutoDoc. SccmAutoDoc is a command line utility that automatically documents an SCCM site into a human-readable form with minimal user input. Only the useful information is included, as opposed to items that are largely used internally.

  • SMSNotify SMSNotify, by myITforum member Dan Thompson, presents the user with an informative screen that lets them know a package will install at a scheduled time and allows the user to postpone the installation for a future time. Many, many other features and options.

  • ENGL Zwlancfg - ENGL. ENGL Zwlancfg is a tool that simplifies the unattended deployment of Microsoft wireless network settings to Windows XP and Vista machines. Profiles can be created, deleted, exported and imported. Zwlancfg can be run from the command line or from the Microsoft System Center Configuration Manager (SCCM) Task Sequence Plugin.

  • ConfigMgr Branch DP Add - ddelgado1 on CodePlex. BDPAdd is a tool that will bulk add protected branch distribution points to a ConfigMgr 2007 (SCCM) hierarchy. There is currently not a way, in the ConfigMgr console, to add multiple protected Branch distribution points at once. This tools attempts to address that problem. (Note: The tool could be easily modified, if needed, to add unprotected branch DPs. I needed protected Branch DPs though, so that's what I wrote this for.

  • ConfigMgr Site Bound Tool - ddelgado1 on CodePlex. SiteBound is a tool that allows bulk addition of boundaries to ConfigMgr (SCCM ) sites. Adding boundaries through the ConfigMgr console can be tedious if adding more than a handful. Previously for SMS 2003 there was the Siteboun.exe tool which solved this problem, however, to my knowledge there is not a version of this tool available for ConfigMgr 2007. If there is, then oh well I still learned something.

  • Coretech SCCM Manager - Freeware- Coretech A/S
    Formerly known as "Coretech Application Creator for SCCM" This utility is developed based on many years of experience with Microsoft System Management Server now System Center Configuration Manager. Our mission is to streamline every aspect of the package creation process thus making the daily administration of the system smarter. In the latest version you'll also find functionality to prestage computers and configure variables used in the image deployment process.

  • ConfigMgr MP Policy Checker - Vincent Dipippo - I have written a tool that will allow you to select a policy and then check that policy via HTTP pulls to all of the MPs. The tool is multi-threaded for performance and works well in large environment.

  • 1E Migration Tool - This tool is designed to allow an SMS Administrator to Migrate all or selected packages and programs from his SMS environment into a System Center Configuration Management (ConfigMgr) environment. The tool has the following features: The Migration of Package and Program details along with source files; Renaming of Package and Program names during migration; Direct transfer of packages from your SMS site to ConfigMgr; Export to flat file structure from SMS site and Import into ConfigMgr from flat file; Exporting of SMSNomad command line settings to new ConfigMgr Nomad tab settings.

  • ConfigMgr Collection Query Rule Embedded Reference Checker - The tool enumerates all existing site codes, collections, and query rules on that server. It then uses regular expressions to detect probable collection references (i.e. any site code followed by 5 hex digits). There is also a special case for the built-in collections, which do not correspond to a site code (starting instead with SMS) and do not conform to the strict standard for user-created collections (e.g. SMSDM001, SMS000GS, etc.) Finally, it cross-references those collection IDs to the actual list of collections and includes them by ID and name for review. Any collection ID that is found in a rule but not in the collections enumerated from the server is reported as "**** Unknown ****". You can search the output for this to identify bad references.

  • ConfigMgr Package Distribution Health Browser - While the console is quite functional in checking the distribution status of packages in general, I wrote a tool that helps administrators zero in on package replication issues much more quickly. First, it accesses the associated views in the database directly, which makes it much faster to get at this information than the console, which is a front-end to the ConfigMgr WMI provider. Second, it offers some sorting and filtering options that highlight the replication issues much more efficiently than reviewing the total status for every package individually.

  • 1E's Service Window Provides a graphical interface that allows an administrative user to view, add, edit and delete maintenance windows (service windows) on a selected target computer. Maintenance windows define times during which Microsoft System Center Configuration Manager 2007(ConfigMgr) can apply advertisements and software update deployments to the specified computer. If no windows are specified then the computer can receive advertisements at any time. Administrators may assign advertisements outside any maintenance windows irrespective of what has been set.

  • Collection Commander 1.3.1 by Roger Zander

    Initiate SMS 2003 advanced client actions on a collection: Ping,WakeUp,HW/SW Inventory,ReRun Advertisements,Show logged on user,Download/Refresh Policy,Repair SMS Agents,Import Clients to the Collection.

  • SMS Server Tools 0 2 2 - By Bernard White

    Suite of 7 tools including: 1. Management Point Ping (mpping.exe), 2. Site Information (siteinfo.exe), 3. Package Information (pkginfo.exe), 4. Distribution Point Mod (dpmod.exe), 5. Site Control File Check (scfcheck.exe), 6. Site Services (sitesvc.exe), 7. Collection Membership (cmember.exe). For more info see:

  • SCCM 2007 GUID assistant by Greg Ramsey

    Use this utility on a TEST SCCM 2007 site to help you identify the desired GUID required to extend the SCCM 2007 console.

  • SMS Site Status SideBar Gadget by fmerizalde130

    This is the first of several Windows Vista SideBar Gadgets for providing SMS\SCCM information. This gadget, once configured will provide SMS Site Status.

  • Program files application Blocker by rtruss

    A small util to add blank files to the program files dir and remove permissions for local administrators, everyone and users groups and then add domain admins and whatever group you would like to add as well.

  • Dell Client Configuration Utility (DCCU)

    Dell Client Configuration Utility (DCCU) is an application that you can use to obtain or configure BIOS settings. You can also restart or shut down the system or flash the BIOS with DCCU.

  • SMSMap

    Create Visio drawings of any combination of ConfigMgr 2007 and SMS 2003 Site Servers. Source: Tondware

  • Enhanced System Discovery 2007 by System Center Tools

    Provides a number of capabilities to improve your level of integration and synchronization with Active Directory.

  • InventoryManager 2007 by Dudeworks

    Inventory Manager (INVMAN) allows administrators to easily extend, customize and edit asset inventory for System Center Configuration Manager 2007 and SMS 2003.

  • ConfigMgr Branch Distribution Point Bulk Add Tool CodePlex Project

    BDPAdd is a tool that will bulk add protected branch distribution points to a ConfigMgr 2007 (SCCM) hierarchy. There is currently not a way, in the ConfigMgr console, to add multiple protected Branch distribution points at once. This tools attempts to address that problem.

  • SMS/SCCM Peer2Peer AddOn by Roger Zander

    SMSTorrent is a Peer2Peer AddOn for SMS2003/SCCM2007 Clients. SMS/SCCM Clients are able to share the local Package cache with other Clients using the BitTorrent filesharing protocol.

  • MIFCheck - MIFChecker allows you to verify a .MIF file (SMS 2.0 inventory file) for errors.

  • Right-click Collection Listing by Matt Hudson

    Right click on a computer or user and see what collection that resource is in as well as what maintanence window is associated with it.

  • SCAP Conversion Tool for Desired Configuration Manager Microsoft

    The SCAP Conversion Tool for DCM converts Security Content Automation Protocol (SCAP) files into DCM Configuration Packs and indicates gaps in a log file that can result from the conversion process. Use the Configuration Packs in combination with the desired configuration management (DCM) feature in Microsoft System Center Configuration Manager 2007 to monitor compliance with the SCAP baseline.

  • WQL Analyzer - Browse classes, properties, qualifiers; run WQL queries (locally or remotely); save results as XML or HTML; connect to remote computer; export class description to XML or HTML; automatically generate the "SELECT" query (double click on class name).


  • Verify AMT certificates - Steve Rachui's Manageability blog. The CertValidator.vbs utility is designed to run on Windows 2003 and Windows 2008 servers.



Configuration Packs


  • SCCM 2007 Capacity Planner

    Here is an updated Capacity Planner to work with SCCM 2007. This is not fully completed as it is a work in progress. But it has updated terminology and hardware recommendations which may be helpful to some people. The bandwidth used calculations are not updated although you can manipulate the data to give an estimation.

Ron Crumbaker Web Remote Tools 3.21 Customizations or Additional buttons

add your own right click option / extend the SCCM Tools Right click tools

This guide will show you how you can extend the SCCM Tools avavable from here:

If you don´t have this toolkit installed. Download it and install it before continuing.

This is how they look by default:
Attached Image

The actions with this package are not stored within the regestry anymore. Instead they are stored in xml files instead.
These are located on this path: <SCCM Console install directory>\AdminUI\XmlStorage\Extensions\Actions\7ba8bf44-2344-4035-bdb4-16630291dcf6\
Attached Image

Begin with backing up all of these xml files to a diffrent location. just in case you ever wan´t to go back to the originals.

Now lets say we wan´t to add a custom action below the client actions node:
Attached Image

Then open Client Actions.xml with notepad
Attached Image

Scroll to the bottom of the script an input a new "chunk" of code. You can just code one of the above chunks and then edit.
Resized to 99% (was 1371 x 712) - Click image to enlargeAttached Image

As you can see i have pasted in a new chunk of code (marked in blue) and edited the name.

This will give me another option for evaluating the user policy...
Attached Image

But i could also customize this to work with other scripts to make my custom action do something else..
To do this just edit the <FilePath> and <Parameters> values.

If you need to edit any of the other categories just open the xml file for this category (all stored within "<SCCM Console install directory>\AdminUI\XmlStorage\Extensions\Actions\7ba8bf44-2344-4035-bdb4-16630291dcf6")

Enjoy! B)


Troubleshooting:Add Trace32.exe to BOOT File "boot.wim" to read the logs in trace32

This tip is great for incorporating Trace32.exe to your boot.wim for troubleshooting.

Create folders and populate with file(s)

Create a folder on your SCCM server called Extrafiles, put two blank folders in there called windows\system32

copy the trace32.exe file to the system32 folder you just created above (you can copy more than this if you wish, but for this tip this is sufficient)

Attached Image

Create a new boot image

In Operating System Deployment, right click on boot images, and choose create boot image using microsoft deployment.

Attached Image

Point the Package Source to blank shared folder on your network.

Attached Image

Fill in the General Settings

Attached Image

For Image Options, use the Extrafiles folder you created above as 'extra' directories to add

Attached Image

click next and the boot image will be created (takes some time).

Note: if you get this error "Error while importing Microsoft Deployment Toolkit task sequence. Details: the ConfigMgr reported an error" then grant SYSTEM account full permissions on your network share that you are creating the boot.wim file in.

Attached Image

Using the new boot image

Dont forget to add network drivers to your boot.wim and finally dont forget to create a new Distribution Point and update it.

When you are troubleshooting image deployment you can switch to this debug boot.wim by right clicking on a Task Sequence and choose properties, click on the Advanced tab and change the boot image to the one you've just created.

Resized to 98% (was 833 x 506) - Click image to enlargeAttached Image

Now when you press F8 to troubleshoot you can bring Trace32 up to read the logs right there in your deployment.


Troubleshooting:Ride of PXE Boot aborted

Troubleshooting:Ride of Pxeabord message

The first approch would be ....Cleare the PXE advertisement from the collection or by selecting the computer " Clear Last PXE Advertisement"

If you still get the abort message like below then...

Downloaded WDSNBP

Architecture: x64

The details below show the information relating to the PXE boot request for this computer. Please provide these details to your Windows Deployment Services Administrator so that this request can be approved.

Pending Request ID: 45

Contacting Server:

TFTP Download: smsboot\x64\

PXE Boot aborted. Booting to next device...

Deleting the advertisement and re-advertising it
Restarting WDS and DHCP service
Restarting SCCM server
if not reimport the information to the colllection by direct membership method or computer association option

-Hope this help you


yep now Microsoft(R) System Center Configuration Manager 2007 Dashboard


SMS reports
added Asset and other reports to the collections
SCCM reports added
SQL Server Reporting services added to enchance the reports and now what???
yep now Microsoft® System Center Configuration Manager 2007 Dashboard

About the Configuration Manager Dashboard

IT Challenges

IT administrators and IT support staff need easier access to key information about software and operating system deployments, client health, and compliance with regulations.  They must ensure that their systems and software meet the configuration requirements established for the organization.  And they need the ability to track this information without having access to a System Center Configuration Manager console.


The Microsoft System Center Configuration Manager 2007 Dashboard lets customers track application and operating system deployments, security updates, the health status of computers, and IT compliance with key regulations—with an easy to use, customizable Web interface.  Because the Dashboard is built on Windows® SharePoint® Services, IT staff can access information without using the Configuration Manager console. The Dashboard is a free Solution Accelerator, and fully supported by Microsoft.

Key features of the Dashboard include:

  • Easy access to key information without using the Configuration Manager console  
  • Centralized view of Configuration Manager data sets
  • Data can be viewed in graph, table, or Dundas gauge formats
  • You can create custom dashboards for different departments, based on site user's group membership.

Join the Beta Program for the Dashboard

The Configuration Manager Dashboard is now in Beta release (English only).  Click here to join the beta.

Link: SCD-BGMB-FK9M&SiteID=14

How the Dashboard Works

The Configuration Manager Dashboard is designed to work with an existing Configuration Manager 2007 infrastructure. The Dashboard queries the Configuration Manager site database and uses the resulting data set to present key infrastructure metrics in a graphical format.

The Configuration Manager Dashboard uses SharePoint Web parts to manage and display data sets:

  • Microsoft Dashboard Configuration Web Part. Use this Web part to create and modify the SQL queries that produce the data sets and the other properties that govern how the Dashboard displays the data sets.
  • Microsoft Dashboard Viewer Web Part. Use this Web part to display the data sets. A Dashboard Viewer Web Part displays one data set at a time. The Configuration Manager Dashboard can contain multiple copies of the Dashboard Viewer Web Part at once, each copy displaying a different data set.

The following figure shows how users can interact with the Web parts to retrieve and display data.


Figure 1. Configuration Manager Dashboard Process Flow

The Configuration Manager Dashboard process flow involves the following sequence of activities:

  1. An IT Service Manager requests a new data set.
  2. The IT Administrator uses the Dashboard Configuration Web Part to define the new data set.
  3. The IT Administrator stores the configuration information for the new data set (the information is saved in the Windows SharePoint Services Content database).
  4. The IT Administrator adds a new copy of the Dashboard Viewer Web Part to the default Configuration Manager Dashboard and then modifies the Web part to display the new data set.
  5. The IT Service Manager browses to the Configuration Manager Dashboard site.
  6. Windows SharePoint Services queries the Configuration Manager site database as specified by the data set configuration.
  7. Windows SharePoint Services renders the new data set using the Dashboard Viewer Web Part.

Requirements for the Configuration Manager Dashboard

The Configuration Manager Dashboard integrates with an already functioning deployment of System Center Configuration Manager 2007 and has no additional infrastructure requirements. It is assumed that Configuration Manager 2007 and the Configuration Manager site database are configured in accordance with Microsoft installation guidance.

The following table lists software requirements for the Configuration Manager Dashboard.

Table 1. Configuration Manager Dashboard Software Requirements



Operating System

  • See requirements for Configuration Manager 2007


  • Configuration Manager 2007 R2 or SP2
  • Windows SharePoint Services 3.0 SP2

    Note   Microsoft Office SharePoint Server 2007 SP2 is supported as an alternative to Windows SharePoint Services 3.0.

  • Microsoft SQL Server® 2008
  • Microsoft .NET Framework 3.5


  • Microsoft Internet Explorer® 7.0 or Internet Explorer 8.0.

Note   For more information about the software requirements for the Configuration Manager Dashboard, see the appropriate sections in the System Center Configuration Manager 2007 Dashboard: User Guide or the System Center Configuration Manager 2007 Dashboard release notes.