Configuration Manager Site Supported Configurations

 

 

Primary Site Server

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Enterprise Edition SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Secondary Site Server

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Management Point

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

State Migration Point

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Distribution Point

Windows Server 2003 Web Edition SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter and Storage Server Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Distribution Point - Branch DP Role Only

Windows XP Professional Service Pack 2

Windows XP Professional for 64-bit Systems

Windows Vista Business, Enterprise and Ultimate Editions

 

Reporting Point

Windows Server 2003 Standard Edition SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Server Locator Point

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Site Database Server

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Software Update Point

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Fallback status point

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

PXE service point

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Configuration Manager Console

Windows XP Professional Service Pack 2

Windows XP Professional x64

Windows Vista Business, Enterprise and Ultimate Editions

Windows Server 2003 Web Edition SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter and Storage Server Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

SCCM 2007 Mobile Device Clients Supported

SCCM 2007 Clients as Mobile Device Client's

 

 

Windows CE 4.2 (ARM processor only)

Windows CE 5.0 (ARM and x86 processors)

Windows Mobile 5.0 Smartphone

Windows Mobile 6 Classic

Windows Mobile 6 Professional

Windows Mobile 6 Standard

Windows Mobile for Pocket PC 2003

Windows Mobile for Pocket PC 2003 Second Edition

Windows Mobile for Pocket PC 5.0

Windows Mobile for Pocket PC Phone Edition 2003

Windows Mobile for Pocket PC Phone Edition 2003 Second Edition

Windows Mobile for Pocket PC Phone Edition 5.0

Windows Mobile Smartphone 2003

Let play a Game with SCCM 2007; Quize on SCCM 2007 ; SCCM 2007 Games

Here is the Microsoft Link...

 

 

http://www.microsoft.com/downloads/details.aspx?familyid=B9FB478A-EC98-47F2-B31E-57443A8AE88F&displaylang=en

 

 

The following quizzes are available:

Configuration Manager 2007 Client Installation Quiz
Configuration Manager 2007 Client Management Quiz
Configuration Manager 2007 Client Site Assignment Quiz
Configuration Manager 2007 Desired Configuration Management Quiz
Configuration Manager 2007 Internet-Based Client Management Quiz
Configuration Manager 2007 Native Mode Quiz
Configuration Manager 2007 Network Access Protection Quiz
Configuration Manager 2007 Wake On LAN Quiz
New! - Configuration Manager 2007 Software Updates Operations Quiz
New! - Configuration Manager 2007 OSDeployment Quiz
New! - Configuration Manager 2007 What's New Quiz
New! - Configuration Manager 2007 Software Updates Configuration Quiz
New! - Configuration Manager 2007 Mobile Device Management Quiz
New! - Configuration Manager 2007 Fundamentals Quiz
New! - Configuration Manager 2007 Client Roaming Quiz
New! - Configuration Manager 2007 Software Updates Interop Quiz
New! - Configuration Manager 2007 Setup Quiz
New! - Configuration Manager 2007 Software Distribution Quiz

 

 

Enjoy,

Paddy

Management Point (MP) Logs

 

 

MP_Ddr	Records the conversion of XML.ddr records from clients, and copies them to the site server.
MP_GetAuth	Records the status of the site management points.
MP_GetPolicy	Records policy information.
MP_Hinv	Converts XML hardware inventory records from clients and copies the files to the site server.
MP_Location	Records location manager tasks.
MP_Policy	Records policy communication.
MP_Relay	Copies files that are collected from the client.
MP_Retry	Records the hardware inventory retry processes.
MP_Sinv	Converts XML hardware inventory records from clients and copies them to the site server.
MP_Status	Converts XML.svf status message files from clients and copies them to the site server.

SCCM 2007 Client To Site Communication Ports

 

 

 

 

Service	Port	Description
Client Request-HTTP (TCP)	80	(default) Client Requests-HTTP (TCP)
Client Request-HTTPS (TCP)	443	(default) Client Requests-HTTPS (TCP)

 

 

By default the HTTP port is set to Port 80 and the HTTPS port is set to Port 443 and as mentioned above can be modified or changed to reflect your infrastructures needs.

 

The ports can also be modified using the PortSwitch VBS script included on the installation media in the Tools\PortConfiguration directory folder using the following syntax to change the HTTP Port number:

 

 

The following g Registry key holds the information for the HTTP and HTTPS ports:

 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM

HttpPort=dword:Decimal Value

HttpsPort=dword:Decimal Value

SCCM Ports are configurable & some are not

 

 

Configurable Ports

 

Client to internet (as proxy server settings)

Client to reporting point

Client to site system

Software update point to internet (Proxy server settings)

Software update point to WSUS server

 

UnConfigurable Ports

 

Configuration Manager 2007 console to SMS Provider

Configuration Manager 2007 console to the Internet

Site server to site database server

Site server to site system

Site system to site database server

Site to site (Primary-to-primary or primary-to-secondary)

SQL Query To Find Unhealthy Machines

SQL Query:

 

Select Distinct

Name 'Machine Name',

LastUser 'Last Logged On User',

WasOnline,

LastPingResult State,

Classification Status

From ClientHealthResults

 

Where LastPingResult Is Not Null

And Classification = 'UnHealthy'

RoboCopy VBS Script

VBS script with source and destination folder input dialog boxes as well as hard coding the RoboCopy command line switches opposed to issuing the commands from the command prompt

 

 

 

Set objShell = CreateObject("Wscript.Shell")

 

objSource = InputBox("Enter Source")

objDestination = InputBox("Enter Destination")

 

objCommand = "RoboCopy.Exe " & Chr(34) & objSource & Chr(34) & " " & Chr(34) & objDestination & Chr(34) & " /e /r:1 /w:2"

objShell.Run(objCommand)

 

MsgBox "Done"

What's New in Configuration Manager 2007

Some aspects of Configuration Manager 2007 have changed very little since SMS 2003, while some have changed a lot. Also, several new features have been added and some features have been removed.

The following features are new to Configuration Manager 2007:

• Desired configuration management
  
• Network Access Protection for Configuration Manager
  
• Wake On LAN
  

The following features were previously available only in Feature Packs but are now incorporated into the core product:

• Mobile device management
  
• Operating system deployment
  
• Transfer site settings wizard
  
• Manage site accounts tool (MSAC)
  
• Asset Intelligence
  

The following features have changed significantly from SMS 2003:

• Backup and recovery
  
• Software updates
  

The following features have been improved but still function very much as they did in SMS 2003:

• The administrator console
  
• Collections
  
• Software distribution
  
• Software metering
  
• Remote tools
  

The following features either have not changed or have minor changes:

• Discovery
  
• Inventory
  
• Queries
  
• Reporting
  

The basic site infrastructure has not changed. You still have primary sites and secondary sites, although the new feature for software distribution called the branch distribution point might remove the need to create some child sites in your hierarchy. Site-to-site communication is still configured using senders and addresses; however, in Configuration Manager 2007 senders can be installed only on primary or secondary site server systems. Configuration Manager 2007 now supports hosting the site database on a clustered SQL Server virtual instance as well as SQL Server 2005 named instances. Several new server roles have been added to support new features.

In SMS 2003 you had two types of clients, but in Configuration Manager 2007 you have only one client type, which is similar to the SMS 2003 Advanced Client. Some of the client deployment methods have changed and some methods have been removed. A new method, software update point client installation, allows you to leverage your software update infrastructure to deploy Configuration Manager 2007 clients.

In SMS 2003 you had two security modes, but in Configuration Manager 2007 you have the equivalent of SMS 2003 advanced security. However, you now have two site modes: Configuration Manager 2007 native mode and Configuration Manager 2007 mixed mode. Although site modes are not at all related to the SMS 2003 security modes, they do involve the security of your Configuration Manager 2007 environment. Native mode is a requirement to support Internet-based client management, a new feature that allows you to manage clients that do not have a direct connection to your site.

In SMS 2003, the site server's local subnet is automatically used as the site boundary for the site during setup. In Configuration Manager 2007, there is no default boundary created during setup, and you must manually create the boundary for a site when setup has completed. In SMS 2003, there are site boundaries and roaming boundaries, but in Configuration Manager 2007, there is only one type of boundary and it is equivalent to SMS 2003 roaming boundaries. Computers are assigned as clients to Configuration Manager 2007 sites according to the site boundaries you configure in the Configuration Manager console. Boundaries can now be defined by IP subnets, Active Directory site names, IPv6 Prefix, or IP ranges.

In SMS 2003, roaming boundaries were either local or remote roaming boundaries. When creating Configuration Manager 2007 boundaries, you instead decide whether the boundary will be used for either a slow or unreliable or a fast (LAN) network connection. During upgrade, any existing remote roaming boundaries will become slow boundaries and any local roaming boundaries will become fast (LAN) boundaries.

In SMS 2003, you could not upgrade from the evaluation version of the product to the full version. Configuration Manager 2007 now supports upgrading from the evaluation version. When upgrading an evaluation version, whether it is SMS 2003 or Configuration Manager 2007, an entire setup process must be completed using the new installation source files.

In SMS 2003, the client push installation method properties used when installing clients have the default site code set to Auto. In Configuration Manager 2007, the default site code used when installing clients using the client push installation method is set to the site code of the primary site.

In Configuration Manager 2007, state messages are sent by Configuration Manager 2007 clients using a new messaging system built into the product that allows clients to send "checkpoints" of important changes of state. State messages are not the same as status messages; whereas status messages provide information about component behavior and data flow, state messages provide a snapshot of the state of a process at a specific time.

Configuration Manager 2007 also includes support for fully qualified domain names (FQDNs) and IPv6.

 

can be find more from.....http://technet.microsoft.com/hi-in/library/bb680807(en-us).aspx

Thanks,

Pavan Kumar

Status Check for Wake On Lan

On Error Resume Next

Const wbemFlagReturnImmediately = &h10
Const wbemFlagForwardOnly = &h20

arrComputers = Array("ComputerName")
For Each strComputer In arrComputers
   WScript.Echo
   WScript.Echo "=========================================="
   WScript.Echo "Computer: " & strComputer
   WScript.Echo "=========================================="

   Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\WMI")
   Set colItems = objWMIService.ExecQuery("SELECT * FROM MSNdis_DeviceWakeOnMagicPacketOnly", "WQL", _
                                          wbemFlagReturnImmediately + wbemFlagForwardOnly)

   For Each objItem In colItems
      WScript.Echo "Active: " & objItem.Active
      WScript.Echo "EnableWakeOnMagicPacketOnly: " & objItem.EnableWakeOnMagicPacketOnly
      WScript.Echo "InstanceName: " & objItem.InstanceName
      ''WScript.Echo   " **Computer" & strComputer & "  WOL Settings Failed to Retrive"
     
   Next
Next

Dell recommend using SMS WOL BIOS Settings remote Enable

Dell recommend using SMS and Dell OpenManage Client Instrumentation (OMCI).  However, this requires WMI scripting which may be prevented if security lockdown settings prevent such scripts from running.

Pros: Exposes the Dell BIOS to WMI and therefore enables almost any modification to be made by running VB script.  It also means SMS hardware inventory can then report upon  BIOS settings by extending the SMS_DEF.MOF.

Cons: Requires agent software to be run on the client.

The Dell Client Configuration Utility (DCCU) can be used as an alternative to the OMCI client to create stand-alone executables that can output configuration settings ('Get Values') to an XML file and/or configure BIOS settings ('Set Values'), including enabling WOL.

Pros: Leaves not footprint on the client

Cons: An executable file needs to be created for every action you want to perform against the BIOS; meaning heavier network utilization.

BiosConfigUtility.exe

HP provides a number of tools based on HP Client Management Interface (CMI).  The exception is HP System Software Manager (SSM) which includes a bundled utility called BiosConfigUtility.exe that modifies BIOS settings through a text-based file format, which can be used independently of SSM.   HP says a future version of HP SSM will leverage HP CMI on 32-bit and 64-bit platforms.

Modify the DNS Server Search Order for a Network Adapter

Modify the DNS Server Search Order for a Network Adapter

Configures a TCP/IP-bound network adapter to use two DNS servers: 192.168.1.100 and 192.168.1.200. Note that even if a computer only uses one DNS server, the IP address of that server must still be passed to the SetDNSServerSearchOrder method as an array (in that case, an array with only one element).  and more Scripts can be found here

On Error Resume Next  strComputer = "." Set objWMIService = GetObject("winmgmts:" _     & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")  Set colNetCards = objWMIService.ExecQuery _     ("Select * From Win32_NetworkAdapterConfiguration Where IPEnabled = True")  For Each objNetCard in colNetCards     arrDNSServers = Array("192.168.1.100", "192.168.1.200")     objNetCard.SetDNSServerSearchOrder(arrDNSServers) Next 

SCCM Agent Related Exe file

SCCM Agent Related Exe file

 

 

 

 

ccmdump.exe
CcmExec.exe
ccmrepair.exe
CcmRestart.exe
OSDBitLocker.exe
OSDDiskPart.exe
OSDJoin.exe
OsdMigrateUserState.exe
OSDNetSettings.exe
OSDPrepareOS.exe
OSDPrepareSmsClient.exe
OSDSetupWindows.exe
OSDSmpClient.exe
OSDWinSettings.exe
SCCMNativeModeReadiness.exe
smsboot.exe
SMSCliUI.exe
SmsClrHost.exe
smsnetuse.exe
smsswd.exe
tsenv.exe
TSInstallSWUpdate.exe
TSLauncher.exe
TSManager.exe
TSMBootstrap.exe
TsProgressUI.exe
VAppLauncher.exe
VAppCollector.exe
RCLaunch.exe-Remote Control launch
RCServer.exe-Remote Control Server
clicore.exe

What's new in Windows Vista Service Pack 1 (SP1)

Improvements in reliability

Windows Vista SP1 includes improvements that address many of the most common reasons for which Windows stops responding. Many of the reliability improvements in SP1 are in response to issues that customers reported by using the Windows Error Reporting tool.

Other reliability improvements in Windows Vista SP1 include improvements in wireless computer-to-computer (ad hoc) connections, better peer-to-peer connections, such as using Windows Meeting Space, and many more.

Top of page

Improvements in performance

Windows Vista SP1 includes many changes that can improve your computer's speed and performance. Here are some of the areas that are improved:

•	Faster copying or extracting files from a compressed mode.
•	Better use of network bandwidth when browsing file shares over a network.
•	Improved performance from Windows ReadyBoost in reducing the time it takes for Windows to wake up from Hibernate and Standby power modes.
•	Better power consumption when your computer screen is idle for a long time.
•	Improved logon experience when using a corporate computer, such as a laptop, outside of the corporate network.
•	Faster opening of large image files.

 

Improvements in security

You can now use BitLocker to encrypt multiple partitions on your computer's hard disk, rather than just a single partition. Note that BitLocker is only available in Windows Vista Enterprise and Windows Vista Ultimate.

 

Changes to search

SP1 includes an important change to the way desktop search works in Windows Vista. You can now select a default desktop search service, similar to the way you can select a default search service for web browsers and media players. With SP1, you can now get to your preferred search results from within the Start menu and Windows Explorer.

 

Changes in memory (RAM) reporting

SP1 also changes how the random access memory (RAM) that is installed in your computer is reported. Before SP1, the amount of memory reported was equal to the amount of memory that Windows was able to use. In SP1, the amount of memory reported is the amount of memory that is actually installed on your computer. If you have 4 gigabytes (GB) of memory installed, you'll now see 4 GB of memory reported by features such as System or Performance Information and Tools in Control Panel. This change can only happen if your computer's basic input/output system (BIOS) is capable of displaying that much RAM.

 

Advanced information

If you are an IT professional or an advanced user and want additional detailed information about SP1, you can find the release notes, the SP1 deployment guide, and other information at the Windows Vista Service Pack 1 Resources page on the Microsoft TechNet website.

Query Criterion Values

String Values

You must specify the exact string that the query will use to evaluate the expression — do not use quotation marks unless they are part of the string. For relational operators that perform LIKE comparisons ("is like" or "is not like"), you can use wildcard characters within the string. You can use the following wildcards.

Wildcard	Description
%	Any string of zero or more characters
_ (underscore)	Any single character
[]	Any single character within the range or set (for example [a-f] or [abcdef])
[^]	Any single character not within the specified range (for example [^a-f] or [^abcdef])

Date and Time Values

You must enter a date that the query can use to evaluate the expression. This value must be entered according to the units that are specified by the date and time operator. For example, if you use the "year is after" operator, you would enter the year by using four digits (for example, 2002).

When you write queries by using Configuration Manager 2007 Query Builder, you can express the date and time in any valid SQL format. For more information, see the SQL Server documentation.

Prerequisites for Asset Intelligence :- SMS_def.mof 9 Modification Prerequisites for Asset Intelligence

Prerequisites for Asset Intelligence

 

The Asset Intelligence feature in Configuration Manager 2007 has both external dependencies and dependencies within the product that should be considered when implementing Asset Intelligence or attempting to view Asset Intelligence report information.

The prerequisites for Asset Intelligence in Configuration Manager 2007 include the following:

• Client agent prerequisites
  
• Hardware inventory file modification prerequisites
  
• Site maintenance task prerequisites
  
• Windows event log setting prerequisites
  

Client Agent Prerequisites

The Asset Intelligence reports depend on client information obtained through client hardware and software inventory reports.

To obtain the information necessary for all Asset Intelligence reports, the following client agents must be enabled:

• Hardware inventory client agent
  
• Software metering client agent
  

Hardware Inventory Client Agent Dependencies

To collect inventory data required for some Asset Intelligence reports, the hardware inventory client agent must be enabled. In addition, some hardware inventory reporting classes must be enabled in the SMS_DEF.mof file on the primary site server computer.

For information about enabling the Hardware Inventory Client Agent, see How to Configure Hardware Inventory for a Site.

Software Metering Client Agent Dependencies

A number of Asset Intelligence software reports depend on the software metering client agent for data. For information about enabling the software metering client agent, see How to Configure Software Inventory for a Site.

The following Asset Intelligence reports depend on the software metering client agent to provide data:

• Software 07A - Recently Used Executables by Number of Computers
  
• Software 07B - Computers that Recently Used a Specified Executable
  
• Software 07C - Recently Used Executables on a Specific Computer
  
• Software 08A - Recently Used Executables by Number of Users
  
• Software 08B - Users that Recently Used a Specified Executable
  
• Software 08C - Recently Used Executables by a Specified User
  

Hardware Inventory File Modification Prerequisites

Important file modification prerequisites apply to the Configuration.mof file and to the SMS_def.mof file.

For more information about the Configuration.mof file, see About MOF Files Used by Hardware Inventory.

For more information about editing the Configuration.mof file, see How to Extend Hardware Inventory Using the Configuration.mof File.

Configuration.mof File Modification Prerequisites

Client Access License (CAL) data collection must be enabled in the Configuration.mof hardware inventory data class file to provide data for the Asset Intelligence Client Access License reports. To enable CAL data collection, the Configuration.mof file must be edited and associated maintenance tasks must be enabled. In addition, computer security policies must be configured to audit Success logon events. For more information about enabling success event logging, see How to Enable Success Logon Event Logging.

For more information about Asset Intelligence CAL data reports, see About Client Access License Reports .

For more information about the maintenance tasks that must be enabled to support the Asset Intelligence CAL reports, see the "Site Maintenance Task Prerequisites" section in this topic.

To enable data collection for CAL data, the CCM_CALTrackConfig WMI data class must be edited in the Configuration.mof file to configure the following required settings.

Note
The Configuration.mof file is located on the primary site server computer in the <ConfigMgr installation directory> \ Inboxes \ clifiles.src \ hinv directory.

CALCollectionType

The CALCollectionType parameter controls whether CALs are tracked for devices, users, or both. To enable CAL data collection, the CALCollectionType parameter value must be changed from the default value of 0 to a value that specifies the type of data to be collected. The CALCollectionType parameter can be set to one of the values described in the following table.

Parameter Setting	Setting Description
0	Data collection disabled
1	User CAL collection only
2	Device CAL collection only
3	All CAL collection enabled

Note
If you want to enable CAL data collection on more than one Configuration Manager 2007 or Configuration Manager 2007 SP1 primary site, the Configuration.mof file for each site must be edited.

CALCollectionFrequencyDays

A single server can be accessed regularly by thousands of users and devices. Creating a record in the Configuration Manager site database for each connection could result in high network bandwidth usage. Polling for which users or devices access the server on a weekly basis is adequate for tracking CAL usage. The CALCollectionFrequencyDays parameter value controls the frequency, in days, of CAL data collection. The default value is 7 days, but a value between 0 and 90 days can be specified. Setting this parameter to 0 causes polling to be run based on the CALCollectionFrequencyMinutes parameter.

CALCollectionFrequencyMinutes

When the CALCollectionFrequencyDays parameter setting is set to 0, polling occurs based on the CALCollectionFrequencyMinutes parameter setting. The CALCollectionFrequencyMinutes parameter setting controls the frequency, in minutes, of CAL data collection. A value between 1 and 1,440 minutes can be specified.

Note
Polling for CAL information too frequently in large sites can result in a significant network impact.

CALCollectionTimeWindow

Current Microsoft licensing models allow for CALs to be reassigned every 90 days. The CALCollectionTimeWindow parameter reflects this licensing model. If the model is changed, this parameter can be adjusted to agree with the new licensing model. The default is 90 days, but a value between 1 and 365 days can be specified.

CALSupportedWindowsVersions

To limit polling to servers, this parameter lists the operating system versions that are polled for client access information. This parameter setting should not be modified. Modification of this setting will result in inaccurate CAL counts. The default value is "5.0,5.2,6.0."

SMS_def.mof Modification Prerequisites

The following hardware inventory reporting classes in the SMS_def.mof file can be enabled to support Asset Intelligence reporting requirements:

Note
The SMS_def.mof file is located on the primary site server computer at <ConfigMgr installation directory> \ Inboxes \ clifiles.src \ hinv directory.

1. SMS_SystemConsoleUsage
2. SMS_SystemConsoleUser
   
3. SMS_InstalledSoftware
   
4. SMS_AutoStartSoftware
   
5. SMS_BrowserHelperObject
   
6. SMS_InstalledExecutable
   
7. SMS_SoftwareShortcut
   
8. SoftwareLicensingService
   
9. SoftwareLicensingProduct
   
   
   For more information about hardware inventory reporting classes used by Asset Intelligence, see Hardware Inventory Reporting Classes Required for Asset Intelligence Reports.

Site Maintenance Task Prerequisites

Two site maintenance tasks are associated with CAL information stored in the site database:

• Delete Aged Client Access License Data Properties
  
• Summarize Client Access License Weekly Usage Data
  

For information about enabling and scheduling site maintenance tasks, see How To Schedule a Site Maintenance Task

Delete Aged Client Access License Data

The Delete Aged Client Access License Data maintenance task is not necessary for data collection, but it should be enabled to prevent the accumulation of unnecessary data stored in the site database. The purpose of this task is to periodically delete aged CAL data from the site database that is no longer needed.

For more information, see Delete Aged Client Access License Data Task Overview.

Summarize Client Access License Weekly Usage Data

The Summarize Client Access License Weekly Usage Data task establishes summaries of usage over time and directly supports the Asset Intelligence license management report: License 11A - Historical Client Access License (CAL) Utilization.

The CAL data that is collected from client hardware inventory reports represents a single computer at a single point in time. To have meaningful reports, it is necessary to periodically gather these points together into summaries that are stored and used for the purpose of tracking usage trends over time.

For more information, see Summarize Client Access License Weekly Usage Data Task Overview.

Windows Event Log Setting Prerequisites

Four Asset Intelligence reports display information gathered from the Windows security event logs on client computers. If the security event log settings are not set correctly, these reports will contain no data, even if the appropriate hardware inventory reporting class is enabled.

The following Asset Intelligence reports rely on collected Windows security event log information:

• Hardware 3A - Primary Computer Users
  
• Hardware 3B - Computers for a Specific Primary Console User
  
• Hardware 4A - Shared (Multi-user) Computers
  
• Hardware 5A - Console Users on a Specific Computer
  

To enable the hardware inventory client agent to inventory the information required to support these reports, you must first modify the Windows security event log settings on clients to log all Success logon events, as well as enable the SMS_SystemConsoleUser SMS_def.mof reporting class. For more information about modifying security event log settings to log all Success logon events, see How to Enable Success Logon Event Logging.

Note
The SMS_SystemConsoleUser SMS_def.mof reporting class will retain successful logon data for only the previous 90 days of the security event log, regardless of the length of the log. If the security event log has fewer than 90 days of data, the entire log is read.

Disk Space Threshold Registry Key

Disk SpaceThreshold

By default Windows sends an administrative alert when the amount of free space remaining on a hard disk drive falls below 10 percent. This percentage can be configured using this setting.

Open your registry and find the key below.

Create a new DWORD value called "DiskSpaceThreshold" and set it to the percentage of free disk space remaining before an alert is sent.

Restart Windows for the change to take effect.

 

Registry Settings
System Key: [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\
Parameters]
Value Name: DiskSpaceThreshold
Data Type: REG_DWORD (DWORD Value)
Value Data: 0 - 99 percent (Default is 10)

 

Configuring SLP / MP in WINS

Configuring SLP in WINS

To manually configure the SMS 2003 Server Locator Point (SLP) server in WINS, type the following from a command prompt:

C:\>netsh <enter>
NETSH>wins <enter>
WINS>server <enter>
WINS SERVER>add name Name=SMS_SLP endchar=1A rectype=0 ip={xxx.xxx.xxx.xxx}
(NOTE: Replace x's with IP address of server acting as SLP)

Command completed successfully.
(This will appear if you used the proper syntax.)

This can also be configured in one simple command (all on one line) as follows:
wins server \\SERVERNAME add name Name=SMS_SLP endchar=1a rectype=0 ip={xxx.xxx.xxx.xxx}

To verify the SLP entry in WINS:

WINS SERVER>show name Name=SMS_SLP endchar=1A

Name : SMS_SLP [1Ah]
NodeType : 1
State : ACTIVE
Expiration Date : Infinite
Type of Rec : UNIQUE
Version No : 0 1bc1
RecordType : STATIC
IP Address : xxx.xxx.xxx.xxx
Command completed successfully.

Configuring MP in WINS
To manually configure the SMS 2003 Management Point (MP) in WINS, type:

WINS SERVER>add name Name=SMS_MP endchar=1A rectype=0 ip={xxx.xxx.xxx.xxx}
(NOTE: Replace x's with IP address of server acting as SLP)

Command completed successfully.
(This will appear if you used the proper syntax.)

To verify the MP entry in WINS:
WINS SERVER>show name Name=SMS_MP endchar=1A

Name : SMS_MP [1Ah]
NodeType : 1
State : ACTIVE
Expiration Date : Infinite
Type of Rec : UNIQUE
Version No : 0 1bc2
RecordType : STATIC
IP Address : xxx.xxx.xxx.xxx
Command completed successfully.

When finished, type:
WINS SERVER> exit <enter>
C:\>

Everything was going really well with the newest version of SMS 2003, including an average software distribution success rate of more than 95%. About a month later, when hardware became available, another primary site was configured at our Disaster Recovery location, including a separate server to act as a Central Site for both primary sites.

Problems Arise
From this point, strange things began to happen. Some of our SMS 2003 Advanced Clients were not even receiving configured advertisements and our success rate dipped as low as 60% successful.

Thanks to Michael Niehaus's expertise, the syntax for configuring a Management Point in WINS is slightly different if all the SMS sites in the hierarchy share the same WINS database!!!

Configure Multiple MPs in one WINS Database
To configure multiple SMS 2003 Management Points (MP) in WINS that share the same database, follow this syntax:

add name Name=MP_<sitecode> endchar=1A rectype=0 ip={xxx.xxx.xxx.xxx}
(NOTE: Replace x's with IP address of server acting as SLP)

To verify the MP entry in WINS:

show name Name=MP_<sitecode> endchar=1A

Enjoy,

Paddy

WScript.Echo "Computer connecting error: " & strComputer

WScript.Echo "Computer connecting error: " & strComputer

 

This is the code to get the output in vbscript with computername

Play with Script for Windows Firewall

Scripting for Windows Firewall

 

Add an Authorized Application

Adds Freecell.exe to the list of authorized applications in the current Windows Firewall profile.

Set objFirewall = CreateObject("HNetCfg.FwMgr") Set objPolicy = objFirewall.LocalPolicy.CurrentProfile  Set objApplication = CreateObject("HNetCfg.FwAuthorizedApplication") objApplication.Name = "Free Cell" objApplication.IPVersion = 2 objApplication.ProcessImageFileName = "c:\windows\system32\freecell.exe" objApplication.RemoteAddresses = "*" objApplication.Scope = 0 objApplication.Enabled = True  Set colApplications = objPolicy.AuthorizedApplications colApplications.Add(objApplication) 	 

Add an Application to the Standard Profile

Adds Freecell.exe to the list of authorized applications in the Windows Firewall standard profile.

Set objFirewall = CreateObject("HNetCfg.FwMgr") Set objPolicy = objFirewall.LocalPolicy Set objProfile = objPolicy.GetProfileByType(1)  Set objApplication = CreateObject("HNetCfg.FwAuthorizedApplication") objApplication.Name = "Free Cell" objApplication.IPVersion = 2 objApplication.ProcessImageFileName = "c:\windows\system32\freecell.exe" objApplication.RemoteAddresses = "*" objApplication.Scope = 0 objApplication.Enabled = True  Set colApplications = objProfile.AuthorizedApplications colApplications.Add(objApplication) 	 

Create a New Port

Opens port 9999 in the Windows Firewall current profile.

Set objFirewall = CreateObject("HNetCfg.FwMgr") Set objPolicy = objFirewall.LocalPolicy.CurrentProfile  Set objPort = CreateObject("HNetCfg.FwOpenPort") objPort.Port = 9999 objPort.Name = "Test Port" objPort.Enabled = FALSE Set colPorts = objPolicy.GloballyOpenPorts  errReturn = colPorts.Add(objPort) 	 

Delete an Authorized Application

Deletes Freecell.exe from the list of authorized applications in the Windows Firewall current profile.

Set objFirewall = CreateObject("HNetCfg.FwMgr") Set objPolicy = objFirewall.LocalPolicy.CurrentProfile  Set colApplications = objPolicy.AuthorizedApplications  errReturn = colApplications.Remove("c:\windows\system32\freecell.exe") 	 

Disable the Firewall

Disables the Windows Firewall for the current profile.

Set objFirewall = CreateObject("HNetCfg.FwMgr") Set objPolicy = objFirewall.LocalPolicy.CurrentProfile  objPolicy.FirewallEnabled = FALSE 	 

Delete an Open Port

Closes port 9999 in the Windows Firewall current profile.

Set objFirewall = CreateObject("HNetCfg.FwMgr") Set objPolicy = objFirewall.LocalPolicy.CurrentProfile  Set colPorts = objPolicy.GloballyOpenPorts errReturn = colPorts.Remove(9999,6) 	 

Disable Remote Administration

Disable Windows Firewall remote administration.

Set objFirewall = CreateObject("HNetCfg.FwMgr") Set objPolicy = objFirewall.LocalPolicy.CurrentProfile  Set objAdminSettings = objPolicy.RemoteAdminSettings objAdminSettings.Enabled = FALSE 	 

Enable the Firewall

Enables Windows Firewall for the current profile.

Set objFirewall = CreateObject("HNetCfg.FwMgr") Set objPolicy = objFirewall.LocalPolicy.CurrentProfile  objPolicy.FirewallEnabled = TRUE 	 

Enable File and Printer Sharing Through Windows Firewall

Enables File and Printer Sharing on a computer running Windows XP Service Pack 2.

Set objFirewall = CreateObject("HNetCfg.FwMgr") Set objPolicy = objFirewall.LocalPolicy.CurrentProfile  Set colServices = objPolicy.Services Set objService = colServices.Item(0) objService.Enabled = TRUE 	 

Enable Remote Administration

Enables remote administration of Windows Firewall fro the current profile.

Set objFirewall = CreateObject("HNetCfg.FwMgr") Set objPolicy = objFirewall.LocalPolicy.CurrentProfile  Set objAdminSettings = objPolicy.RemoteAdminSettings objAdminSettings.Enabled = TRUE 	 

List Authorized Applications

Lists all authorized applications for the Windows Firewall current profile.

Set objFirewall = CreateObject("HNetCfg.FwMgr") Set objPolicy = objFirewall.LocalPolicy.CurrentProfile  Set colApplications = objPolicy.AuthorizedApplications  For Each objApplication in colApplications     Wscript.Echo "Authorized application: " & objApplication.Name     Wscript.Echo "Application enabled: " & objApplication.Enabled     Wscript.Echo "Application IP version: " & objApplication.IPVersion     Wscript.Echo "Application process image file name: " & _         objApplication.ProcessImageFileName     Wscript.Echo "Application remote addresses: " & _         objApplication.RemoteAddresses     Wscript.Echo "Application scope: " & objApplication.Scope     Wscript.Echo Next 	 

List Authorized Applications in the Standard Profile

Lists all authorized applications for the Windows Firewall standard profile.

Set objFirewall = CreateObject("HNetCfg.FwMgr") Set objPolicy = objFirewall.LocalPolicy  Set objProfile = objPolicy.GetProfileByType(1) Set colApplications = objProfile.AuthorizedApplications  For Each objApplication in colApplications     Wscript.Echo "Authorized application: " & objApplication.Name     Wscript.Echo "Application enabled: " & objApplication.Enabled     Wscript.Echo "Application IP version: " & objApplication.IPVersion     Wscript.Echo "Application process image file name: " & _         objApplication.ProcessImageFileName     Wscript.Echo "Application remote addresses: " & _         objApplication.RemoteAddresses     Wscript.Echo "Application scope: " & objApplication.Scope     Wscript.Echo Next 	 

List All Globally-Open Ports

Lists all globally-open ports for the Windows Firewall current profile.

Set objFirewall = CreateObject("HNetCfg.FwMgr") Set objPolicy = objFirewall.LocalPolicy.CurrentProfile  Set colPorts = objPolicy.GloballyOpenPorts  For Each objPort in colPorts     Wscript.Echo "Port name: " & objPort.Name     Wscript.Echo "Port number: " & objPort.Port     Wscript.Echo "Port IP version: " & objPort.IPVersion     Wscript.Echo "Port protocol: " & objPort.Protocol     Wscript.Echo "Port scope: " & objPort.Scope     Wscript.Echo "Port remote addresses: " & objPort.RemoteAddresses     Wscript.Echo "Port enabled: " & objPort.Enabled     Wscript.Echo "Port built-in: " & objPort.Builtin Next 	 

List Firewall Properties

Lists Windows Firewall properties for the current profile.

Set objFirewall = CreateObject("HNetCfg.FwMgr") Set objPolicy = objFirewall.LocalPolicy.CurrentProfile Wscript.Echo "Current profile type: " & objFirewall.CurrentProfileType  Wscript.Echo "Firewall enabled: " & objPolicy.FirewallEnabled Wscript.Echo "Exceptions not allowed: " & objPolicy.ExceptionsNotAllowed Wscript.Echo "Notifications disabled: " & objPolicy.NotificationsDisabled Wscript.Echo "Unicast responses to multicast broadcast disabled: " & _     objPolicy.UnicastResponsestoMulticastBroadcastDisabled 	 

List Firewall Service Properties

Lists service properties for the Windows Firewall current profile.

Set objFirewall = CreateObject("HNetCfg.FwMgr") Set objPolicy = objFirewall.LocalPolicy.CurrentProfile  Set colServices = objPolicy.Services  For Each objService in colServices     Wscript.Echo "Service name: " & objService.Name     Wscript.Echo "Service enabled: " & objService.Enabled     Wscript.Echo "Service type: " & objService.Type     Wscript.Echo "Service IP version: " & objService.IPVersion     Wscript.Echo "Service scope: " & objService.Scope     Wscript.Echo "Service remote addresses: " & objService.RemoteAddresses     Wscript.Echo "Service customized: " & objService.Customized     Set colPorts = objService.GloballyOpenPorts     For Each objPort in colPorts         Wscript.Echo "Port name: " & objPort.Name         Wscript.Echo "Port number: " & objPort.Port         Wscript.Echo "Port enabled: " & objPort.Enabled         Wscript.Echo "Port built-in: " & objPort.BuiltIn         Wscript.Echo "Port IP version: " & objPort.IPVersion         Wscript.Echo "Port protocol: " & objPort.Protocol         Wscript.Echo "Port remote addresses: " & objPort.RemoteAddresses         Wscript.Echo "Port scope: " & objPort.Scope     Next     Wscript.Echo Next 	 

List ICMP Settings

Lists ICMP settings for the Windows Firewall current profile.

Set objFirewall = CreateObject("HNetCfg.FwMgr") Set objPolicy = objFirewall.LocalPolicy.CurrentProfile  Set objICMPSettings = objPolicy.ICMPSettings  Wscript.Echo "Allow inbound echo request: " & _     objICMPSettings.AllowInboundEchoRequest Wscript.Echo "Allow inbound mask request: " & _     objICMPSettings.AllowInboundMaskRequest Wscript.Echo "Allow inbound router request: " & _     objICMPSettings.AllowInboundRouterRequest Wscript.Echo "Allow inbound timestamp request: " & _     objICMPSettings.AllowInboundTimestampRequest Wscript.Echo "Allow outbound destination unreachable: " & _     objICMPSettings.AllowOutboundDestinationUnreachable Wscript.Echo "Allow outbound packet too big: " & _     objICMPSettings.AllowOutboundPacketTooBig Wscript.Echo "Allow outbound parameter problem: " & _     objICMPSettings.AllowOutboundParameterProblem Wscript.Echo "Allow outbound source quench: " & _     objICMPSettings.AllowOutboundSourceQuench Wscript.Echo "Allow outbound time exceeded: " & _     objICMPSettings.AllowOutboundTimeExceeded Wscript.Echo "Allow redirect: " & objICMPSettings.AllowRedirect 	 

List Remote Administration Settings

Lists remote administration settings for the Windows Firewall current profile.

Set objFirewall = CreateObject("HNetCfg.FwMgr") Set objPolicy = objFirewall.LocalPolicy.CurrentProfile  Set objAdminSettings = objPolicy.RemoteAdminSettings Wscript.Echo "Remote administration settings enabled: " & _     objAdminSettings.Enabled Wscript.Echo "Remote administration addresses: " & _     objAdminSettings.RemoteAddresses Wscript.Echo "Remote administration scope: " & objAdminSettings.Scope Wscript.Echo "Remote administration IP version: " & objAdminSettings.IPVersion 	 

List Standard Profile Properties

Demonstration script that connects to and returns information about the Windows Firewall standard profile.

Set objFirewall = CreateObject("HNetCfg.FwMgr") Set objPolicy = objFirewall.LocalPolicy Set objProfile = objPolicy.GetProfileByType(1)  Wscript.Echo "Firewall enabled: " & objProfile.FirewallEnabled Wscript.Echo "Exceptions not allowed: " & objProfile.ExceptionsNotAllowed Wscript.Echo "Notifications disabled: " & objProfile.NotificationsDisabled Wscript.Echo "Unicast responses to multicast broadcast disabled: " & -     objProfile.UnicastResponsestoMulticastBroadcastDisabled 	 

Modify an ICMP Setting

Demonstration script that modifies a Windows Firewall ICMP setting for the current profile.

Set objFirewall = CreateObject("HNetCfg.FwMgr") Set objPolicy = objFirewall.LocalPolicy.CurrentProfile  Set objICMPSettings = objPolicy.ICMPSettings objICMPSettings.AllowRedirect = TRUE 	 

Modify a Firewall Property

Demonstration script that modifies Windows Firewall properties for the current profile.

Set objFirewall = CreateObject("HNetCfg.FwMgr") Set objPolicy = objFirewall.LocalPolicy.CurrentProfile  objPolicy.ExceptionsNotAllowed = TRUE objPolicy.NotificationsDisabled = TRUE objPolicy.UnicastResponsestoMulticastBroadcastDisabled = TRUE 	 

Open a Closed Port

Opens closed port 9999 for the Windows Firewall current profile.

Set objFirewall = CreateObject("HNetCfg.FwMgr") Set objPolicy = objFirewall.LocalPolicy.CurrentProfile Set colPorts = objPolicy.GloballyOpenPorts  Set objPort = colPorts.Item(9999,6) objPort.Enabled = TRUE 	 

Restore the Default Settings

Restore the Windows Firewall default settings.

Set objFirewall = CreateObject("HNetCfg.FwMgr") objFirewall.RestoreDefaults()

 

Enjoy

Paddy

DTS-------> SMS data transfer service

DTS-------> SMS Data Transfer Service

These are the reports available in SCCM for Patch Management

These are the reports available in SCCM for Patch Management

 

Software Updates - A. Compliance

Software Updates - B. Deployment Management

Software Updates - C. Deployment States

Software Updates - D. Scan

Software Updates - E. Troubleshooting

Software Updates - F. Distribution Status

 

Enjoy,
Paddy

SCCM 2007 Software Updates Reports

Software Updates Reports

Software Updates - A. Compliance

The reports in the Software Updates - A. Compliance category provide the scan results for software update compliance on client computers. More specifically, these reports provide information about what software updates are required, installed, or not required on clients. The following software updates reports are in this category:

• Compliance 1 - Overall Compliance
  This report returns the overall compliance for the set of software updates in a specific update list and collection. The Collection ID and Update List ID are required parameters. You can drill into report "Compliance 8 - Computers in a specific compliance state for an update list <secondary>" to view the computers in the compliance state.
  
• Compliance 2 - Specific software update
  This report returns the overall compliance data for a specified software update. The Collection ID and Update Title, Bulletin ID, or Article ID are required parameters. You can drill into report "Compliance 7 - Specific software update states <secondary>" to view the count and percentage of computers in each state for the update.
  
• Compliance 3 - Update list (per update)
  This report returns the overall compliance data for software updates defined in an Update List. The Update List ID and Collection ID parameters are required. You can drill into report "Compliance 7 - Specific software update states <secondary>" to view the count and percentage of computers in each state for the update.
  
• Compliance 4 - Deployment (per update)
  This report returns the overall compliance data for software updates defined in a deployment. The Deployment ID and Collection ID parameters are required. You can drill into report "Compliance 7 - Specific software update states <secondary>" to view the count and percentage of computers in each state for the update.
  
• Compliance 5 -Updates by vendor/month/year
  This report returns the compliance data for software updates released by a vendor during a specific month and year. The Collection ID, Vendor, and Year parameters are required. To limit the amount of information returned, you can filter on the Update Class, Product, or Month parameters. You can drill into report "Compliance 7 - Specific software update states <secondary>" to view the count and percentage of computers in each state for the update.
  
• Compliance 6 - Specific computer
  This report returns the software update compliance data for a specific computer. The Computer Name parameter is required. To limit the amount of information returned, you can filter on the Vendor and Update Class parameters.
  
• Compliance 7 - Specific software update states <secondary>
  This report returns the count and percentage of computers in each compliance state for the specified software update. For best results, start with a compliance 2 - 5 report, and then drill into this report to return the count of computers in each compliance state. You can drill into report "Compliance 9 - Computers in a specific compliance state for an update <secondary>" to view the computers in the specific state for the update.
  
• Compliance 8 - Computers in a specific compliance state for an update list <secondary>
  This report returns all computers that have a specific compliance state for the set of software updates in an update list. For best results, start with "Compliance 1 - Overall Compliance" to return the count of computers in each compliance state, and then drill into this report to return the computers in the selected compliance state. You can drill into report "Compliance 6 - Specific computer" to view the compliance data for the computer.
  
• Compliance 9 - Computers in a specific compliance state for an update
  This report returns all computers in a specific compliance state for a software update. For best results, start with a compliance 2 - 5 report, drill into "Compliance 7 - Specific software update states <secondary>" to return the count of computers in each compliance state, and then drill into this report to return the computers in the selected compliance state. You can drill into report "Compliance 6 - Specific computer" to view the compliance data for the computer.
  

Software Updates - B. Deployment Management

The reports in the Software Updates - B. Deployment Management category provide information about the software update deployments. The following software updates reports are in this category:

• Management 1 - Updates required but not deployed
  This report returns all vendor-specific software updates that have been detected as required on clients but that have not been deployed to a specific collection. The Collection ID and Vendor parameters are required. To limit the amount of information returned, you can specify the software update class.
  
• Management 2 - Updates in a deployment
  This report returns the software updates that are contained in a specific deployment. The Deployment ID parameter is required. For each software update, you can drill down to report "States 5 - States for an update in a deployment <secondary>" to view the states for the specific software update.
  
• Management 3 - Deployments that target a collection
  This report returns the deployments that have targeted a specific collection. The Collection ID parameter is required. You can drill down to report "Management 2 - Updates in a deployment" to view the software updates in the selected deployment.
  
• Management 4 - Deployments that target a computer
  This report returns the deployments that have targeted a specific computer. The Computer Name parameter is required. You can drill down to report "Management 2 - Updates in a deployment" to view the software updates in the selected deployment.
  
• Management 5 - Deployments that contain a specific update
  This report returns the deployments that contain a specific software update. The Update parameter is required. You can drill down to report "Management 2 - Updates in a deployment" to view the software updates in the selected deployment.
  
• Management 6 - Deployments that contain an update list
  This report returns the deployments that were created using a specific update list. The Update List ID parameter is required. You can drill down to report "Management 2 - Updates in a deployment" to view the software updates in the selected deployment.
  
• Management 7 - Updates in a deployment missing content
  This report returns the software updates in a specified deployment that do not have all the associated content retrieved, preventing clients from installing the update and achieving 100% compliance for the deployment. The Deployment ID parameter is required. You can drill down to report "Management 8 - Computers missing content <secondary>" to view the computers that require the software update files.
  
• Management 8 - Computers missing content <secondary>
  This report returns all computers that require a specific software update contained in a specific deployment that is not provisioned on a distribution point. For best results, start with "Management 7 - Updates in a deployment missing content" to return all software updates in the deployment that do not have all the associated content retrieved, and then drill into this report to return all computers that require the software update.
  

Software Updates - C. Deployment States

The reports in the Software Updates - C. Deployment States category provide information about the evaluation and enforcement states on client computers for software update deployments. The following software updates reports are in this category:

• States 1 - Enforcement states for a deployment
  This report returns the enforcement states for a specific software update deployment, which is typically the second phase of a deployment assessment. For the overall progress of the software update installation, use this report in conjunction with "States 2 - Evaluation states for a deployment." The Deployment ID parameter is required. You can drill down to report "States 4 - Computers in a specific state for a deployment <secondary>" to view all computers in the state.
  
• States 2 - Evaluation states for a deployment
  This report returns the evaluation state for a specific software update deployment, which is typically the first phase of a deployment assessment. For the overall progress of the software update installation, use this report in conjunction with "States 1 - Enforcement states for a deployment." The Deployment ID parameter is required. You can drill down to report "States 4 - Computers in a specific state for a deployment <secondary>" to view all computers in the state.
  
• States 3 - States for a deployment and computer
  This report returns the states for all software updates in the specified deployment for a specified computer. The Deployment ID and Computer Name parameters are required. You can drill into the Status Message Details page for any software update that contains an Error Record ID value.
  
• States 4 - Computers in a specific state for a deployment <secondary>
  This report returns all computers in a specific state for a software update deployment. For best results, start with "States 1 - Enforcement states for a deployment " or "States 2 - Evaluation states for a deployment" to identify the states for the deployment, and then drill into this report to return all computers in the specific state. You can drill down to report "States 7 - Error status messages for a computer <secondary>" to view the status messages for the computer.
  
• States 5 - States for an update in a deployment <secondary>
  This report returns a summary of states for a specific software update targeted by a specific deployment. For best results, start with "Management 2 - Updates in a deployment" to return the software updates contained in a specific deployment, and then drill into this report to return the state for the selected software update. You can drill down to report "States 6 - Computers in a specific enforcement state for an update <secondary>" to list the computers in the state.
  
• States 6 - Computers in a specific enforcement state for an update <secondary>
  This report returns all computers in a specific enforcement state for a specific software update. For best results, start with " Management 2 - Updates in a deployment" to return the software updates contained in a specific deployment, drill into "States 5 - States for an update in a deployment <secondary>" to return the states for the selected software update, and then drill into this report to return all computers in the selected state.
  
• States 7 - Error status messages for a computer <secondary>
  This report returns all status messages for a given Update or Deployment on a specific computer for a given status message. For best results, start with "States 1 - Enforcement states for a deployment" or "States 2 - Evaluation states for a deployment" to identify the states for the deployment, drill into "States 4 - Computers in a specific state for a deployment <secondary>" to return all computers in the specific state, and then drill into this report.
  

Software Updates - D. Scan

The reports in the Software Updates - D. Scan category provide information about computers in a specific scan state.

Note
Scan reports do not contain any information from clients that have not submitted any scan status. To see client computers that have not submitted scan status, see the report States 2 - Evaluation states for a deployment.

Note

If an SMS 2003 client sends scan results through hardware inventory, the client will appear as an SMS 2003 client in a separate section of these reports. To see the detail information about scan status for these SMS 2003 clients, go to the Software Distribution - Advertisement report category and check run a report that will show the status of the advertisement you use for your Inventory Tool for Microsoft Updates scanning.

The following software updates reports are in this category:

• Scan 1 - Last scan states by collection
  This report returns the count of computers in each of the compliance scan states returned by client computers in a specific collection during their last scan for software updates compliance. The Update Source ID and Collection ID parameters are required. You can drill down to report "Scan 3 - Clients of a collection reporting a specific state <secondary>" to view the computers in a specific state.
  
• Scan 2 - Last scan states by site
  This report returns the count of computers in each of the compliance scan states returned by client computers assigned to a specific site during their last scan for software updates compliance. The Update Source ID and Site Code parameters are required. You can drill down to report "Scan 4 - Clients of a site reporting a specific state <secondary>" to view the computers in a specific state.
  
• Scan 3 - Clients of a collection reporting a specific state <secondary>
  This report returns the computers in a specific collection that returned a specific state during their last scan for software updates compliance. For best results, start with "Scan 1 - Last scan states by collection" to return the count of computers in each scan state, and then drill into this report. You can drill down to report "States 7 - Error status messages for a computer <secondary>" to view the status messages for the computer.
  
• Scan 4 - Clients of a site reporting a specific state <secondary>
  This report returns the computers assigned to a specific site that returned a specific state during their last scan for software updates compliance. For best results, start with "Scan 2 - Last scan states by site" to return the count of computers in each scan state, and then drill into this report. You can drill down to report "States 7 - Error status messages for a computer <secondary>" to view the status messages for the computer.
  

Software Updates - E. Troubleshooting

The reports in the Software Updates - E. Troubleshooting category provide information about scan and deployment errors that occur on client computers. The following software updates reports are in this category:

• Troubleshooting 1 - Scan errors
  This report returns the count of computers for each error that occurred during the last scan for software update compliance on client computers. The Update Source ID and Collection ID parameters are required. You can drill down to report "Troubleshooting 3 - Computers failing with a specific scan error <secondary>" to view a list of computers that returned the specific scan error.
  
• Troubleshooting 2 - Deployment errors
  This report returns the count of computers for each deployment error that occurred on client computers. The Deployment ID parameter is required. You can drill down to report "Troubleshooting 4 - Computers failing with a specific deployment error <secondary>" to view a list of computers that returned the specific deployment error.
  
• Troubleshooting 3 - Computers failing with a specific scan error <secondary>
  This report returns all computers that have returned a specific scan error. For best results, start with "Troubleshooting 1 - Scan errors" to return the count of computers for each error that occurred during the last scan for software update compliance, and then drill into this report and then drill into this report.
  
• Troubleshooting 4 - Computers failing with a specific deployment error <secondary>
  This report returns all computers that have returned a specific deployment error. For best results, start with "Troubleshooting 2 - Deployment errors" to return the count of computers for each deployment, and then drill into this report.
  

Software Updates - F. Distribution Status

The reports in the Software Updates - F. Distribution Status category provide distribution status data for SMS 2003 clients that are targeted in a software updates deployment. The following software updates reports are in this category:

• Distribution 1 - Advertisement Status for SMS 2003 clients
  This report lists all software distribution advertisements for the selected update. For each advertisement, it also shows the advertisement state and count of machines in that state. This report also covers additional advertisement states available for software update advertisements. The Type and Update Title, Bulletin ID, or Article ID parameters are required. You can drill down to report "Distribution 2 - SMS 2003 clients with a specific update advertisement state" to view the computers in the state.
  
• Distribution 2 - SMS 2003 clients with a specific update advertisement state
  This report shows a list of computers that are in a specific state of an advertisement. This report also covers additional advertisement states available for software update advertisements. The Advertisement ID and Distribution Status parameters are required. You can limit the results by specifying a value for the Update Distribution Status parameter. You can drill down to report "Advertisement status messages for a particular client and advertisement" to shows the status messages reported for the computer and advertisement.Enjoy,
  
  Enjoy,
  Paddy