WMI Isn’t Working!




Troubleshooting Problems with WMI Scripts and the WMI Service


Before you begin repairing suspected problems with the WMI service it is strongly recommended that you run the new WMI Diagnosis Utility. You should always run this utility before making any changes to the WMI service.

WMI is a resilient piece of software. For example, suppose the WMI service is stopped, yet you still try running a WMI script. What do you think will happen? Will the script fail? Will the computer lock up? Will the very fabric of space and time be ripped apart? Not exactly. Instead, the WMI service will probably just restart itself and run your script. Most likely you will never even know that the service had been stopped.

Is there a lesson in that for script writers? You bet there is: if you are having problems with a WMI script, don’t jump to conclusions and assume that WMI is broken. If you have a script that doesn’t work it’s usually due to a problem with the script and not due to a problem with WMI. Admittedly, you could encounter a catastrophic failure of WMI itself, a failure that requires you to re-register all the WMI components or to rebuild the WMI repository. However, it’s far more likely that any problems you are experiencing are the result of doing something like typing in an incorrect namespace or trying to connect to a remote computer where you do not have local Administrator rights.


MSDN WMI Reference


SMS 2003 Product Documentation


All the documentation you ever wanted to have for implementing/maintaining SMS 2003!

IE 7 Is Coming This Month…Are you Ready?


from: http://blogs.msdn.com/ie/archive/2006/10/06/IE7-Is…

The final release of IE7 is fast approaching … and I mean really fast … and will be delivered to customers via Automatic Updates a few weeks after it’s available for download. We want to ensure that you are ready and the information below will help get you there.

Compatibility with sites, extensions and applications has been a very high priority for us as we develop new features, enhance the existing features and move the platform forward to be more secure and standards compliant.  We are continually listening to feedback from our customers, partners and leaders in the industry to resolve major compatibility issues to ensure our common customers have a great experience with IE7. As we make key improvements in areas such as layout and security, some changes need to be made by site owners to work smoothly with IE7.  We have produced detailed documentation, tools and other resources to assist site, extension and application owners in their testing and development efforts to ensure they are compatible with IE7.  We have also proactively worked with hundreds of companies to resolve issues that were reported through our beta testing to ensure those issues were resolved before IE7 is released.

These efforts have been ongoing since last year and have been extremely successful but we can’t ensure 100% compatibility without your help. We need you to test and ensure your sites, extensions, and applications are ready for IE7. We strongly encourage you to do the following ASAP:

Download, install and test your products with IE7 RC 1 –This is the fastest and best way to test for compatibility issues.
Download the IE7 Readiness Toolkit – This toolkit pulls together a number of important resources to help you prepare for IE7:
Developer and IT Pro readiness check lists,
Detailed documentation on important changes in IE7,
Testing and debugging guidance,
Tools for testing, debugging and investigating issues,
And more…

Download and use the Application Compatibility Toolkit – Helps test browser-based applications to ensure they work with IE7.

Visit the Microsoft Internet Explorer Developer Center – You will find an array of important information for developers.

Use the Information Index for Internet Explorer7 – Think of this as a table of contents linking you to documentation, blog posts, whitepapers and other information on IE7.

Read the IE Team Blog – Use the search feature on the right to find previous posts on almost any topic you can think of with regard to IE7.

What if my organization is not going to be ready for IE7 in time?

Organizations that are using Automatic Updates in their environments can block the AU deployment of IE7.  For more details check out the “Options for Blocking Automatic Delivery” section of our Automatic Delivery of Internet Explorer 7 article.

We hope that you are as ready and excited about IE7 as we are. If you have feedback or encounter any issues, check out the IE7 Support page for FAQs, Release Notes, and feedback options.

Thank you,

Scott Graff
Program Manager – IE7 Compatibility
Microsoft Corporation

Log files created in SMS 2003


All the client and site server components in Microsoft Systems Management Server (SMS) 2003 record process information in individual log files. You can use the information in the client and site server log files to help you troubleshoot issues that may occur in your SMS 2003 hierarchy.



By default, client and server component logging is turned on in SMS 2003. However, the log files differ according to the type of client that is installed. For example, the following rules apply:

The SMS 2003 Legacy Client logs record the same information as the SMS 2.0 client. The Legacy Client log files are located in the %Windir%\MS\SMS\Logs folder on the client computer.

The SMS 2003 Advanced Client uses different log files than the Legacy Client to record information. The Advanced Client logs are located in one of the following locations:

On computers that serve as management points, the Advanced Client logs are located in the SMS_CCM\Logs folder.

On all other computers, the Advanced Client log files are located in the %Windir%\System32\CCM\Logs folder.

Back to the top
Back to the top

Legacy Client log files

The following table describes the Legacy Client log files and lists possible issues that apply.

Log file name
Used to help troubleshoot

Installation of the Advertised Programs Agent (APA).
Installation of software distribution components.

Client Configuration Installation Manager (CCIM). Logs routine verification of client components.
Client installation and upgrade problems.

Client core components.
Client installation and upgrade problems.

Activity of the SMS Client service.
SMS Client service problems.

File copy activity to the client access point (CAP).
Inventory data or status data that is not received by the site.

Hardware inventory process.
Hardware inventory problems.

Installation of hardware inventory.
Scenarios where hardware inventory is turned on, but it is not installed on the client.

Installation of software inventory.
Scenarios where software inventory is turned on, but it is not installed on the client.

Records whether users are logged on to the computer.
Scenarios where SMSMON32 does not start, or there are problems with software distribution.

Records the Offer Data Provider (ODP) polling process for advertisements that are based on the computer name.
Scenarios where the client computer does not receive advertisements.

Records the Offer Data Provider (ODP) polling process for advertisements that are based on the user name.
Scenarios where the user does not receive advertisements.

Records the Offer Data Provider (ODP) polling process for advertisements that are based on the user group name.
Scenarios where a user group does not receive advertisements.

Installation of the remote control component.
Scenarios where remote control is turned on, but it is not installed on the client.

Software inventory process.
Scenarios where software inventory does not run.

Logs the processing of advertised programs by the Available Programs Manager (APM).
Scenarios where advertisements fail or do not run.

Logs the start of the Systems Management tool in Control Panel.
Scenarios where the Systems Management tool does not start or does not work correctly.

Logs registry access when the client is installed.
Client installation issues.

Advertised Programs Monitor log.
Advertisement issues.

Records the installation of the software distribution components.
Scenarios where software distribution is turned on, but it is not installed.

Logs the client installation process when the logon script is used.
Client installation issues.

Logs the manual client installation process.
Client installation issues.

Logs the remote “push” installation of the client software.
Client installation issues.

Back to the top
Back to the top

Advanced Client log files

The following table describes the Advanced Client log files and lists possible issues that apply.

Log file name
Used to help troubleshoot

Content Access service. Maintains the local package cache.
Downloaded package issues and “cache out of space” errors. Make sure package content access is completed.

Records activities of the client and the SMS Agent Host service.
Scenarios where the client is corrupted or not functioning. For example, this log applies to a scenario where the client cannot communicate with a management point. Make sure that there are no errors, such as WinHTTP errors, listed.

Maintains certificates for Active Directory directory service and management points.
Scenarios where the client cannot communicate with a management point or with Active Directory.

Creates and maintains the client GUID.
Scenarios where the client changes its GUID after a hardware change or after Windows activation.

Site assignment tasks.
Scenarios where the client is not assigned to a site. Make sure that the client has determined its assigned site.

Schedules the Background Intelligent Transfer Service (BITS) or the server message block (SMB) to download or to access SMS packages.
Package version issues or packages that are not available.

Records all BITS communication for policy or package access.
Download problems from a management point or a distribution point.

Records advertisements that run.
Package errors or packages that are unavailable. Make sure that the program command line has run successfully and that status is generated.

Records all SMB package access tasks.
Problems that occur when you run a package from the distribution point when BITS is not turned on.

Fsinvprovider.log (FileSystemFile.log in SMS Service Pack 1.)
Windows Management Instrumentation (WMI) provider for software inventory and file collection.
File system access or the WMI provider.

This component creates discovery data records (DDRs) and hardware and software inventory records.
Inventory issues or problems where the client cannot access the management point. Make sure that inventory or discovery has finished and that the report is copied to the management point.

Finds management points and distribution points.
Name resolution or scenarios where the client cannot find the management point or distribution point in Active Directory or in WINS. Make sure that the client has identified its default management point in WMI. Additionally, make sure that the resident management point or the proxy management point is identified.

The WMI provider for .MIF files.
Scenarios where MIFs are marked “invalid”.

Monitors all software metering processes.
Scenarios where metering cannot monitor a program or add to WMI. Make sure that the software metering rules were downloaded, and that the programs are matched by the rules.

Requests policies by using the Data Transfer service.
Policy request problems. Make sure that policies were downloaded from the management point.

Records policy changes.
Policy request problems or WMI errors.

Records new policy settings.
Policy override issues. Make sure that the downloaded policies are applied to the local computer.

Records schedule tasks for all client operations.
WMI access errors or scenarios where tasks do not start.

Records usage of the Systems Management tool in Control Panel.
The Systems Management tool in Control Panel.

Logs status messages that are created by the client components.
Scenarios where the client cannot send status to the management point.

Generates a usage data report that is collected by the metering agent. (This data is logged in Mtrmgr.log.)
Scenarios where the client cannot send a software metering report to the management point. Make sure that the client can generate a usage report and send it to the management point.

Logs when the remote control component (WUSER32) starts.
Scenarios where you try to control the client remotely.

You may see repeated log entries in the SMS 2003 Advanced Client log when the client reports inventory. The log entries indicate any problems that occur when the inventory is reported. For example, you may see the following log entry:

Inventory: Successfully sent report. Destination:mp:MP_SinvEndpoint, ID: {AAEE97B0-271B-42F5-A946-B996592A2539}, Timeout: 10080 minutes

In this example, the destination is defined as a MP_xxxxEndpoint, where xxxx is the SINV component in this example.

Back to the top
Back to the top

Site server log files

The SMS 2003 site server log files are located in the SMS\LOGS folder. Because SMS 2003 relies heavily on Microsoft Internet Information Services (IIS), you can review the IIS log file for additional errors that relate to client access to the IIS server. The IIS log file is located in the %Windir%\System32\logfiles\W3SVC1 folder on the IIS server. The following table describes the site server log files and lists possible issues that apply.

Log file name
Used to help troubleshoot

Records the local SMS Administrator Console tasks when you connect to SMS sites.
Connectivity errors to site servers or to site databases.

Client Configuration Manager tasks.
Scenarios where the site cannot connect to computers because of permissions or name resolution. Make sure that the site server can connect to the Admin$ share on the client computer.

Records changes to the client settings by the Client Install Data Manager (CIDM).
Scenarios where the site is not updating CLIDATA.SRC files. Make sure that the correct files are copied to the SMS\Inboxes\Clicomp.src folder.

Logs when collections are created, changed, and deleted by the Collection Evaluator.
Problems with collections. Make sure that collections are created and updated successfully.

Records Component Status Summarizer tasks.
Scenarios that occur when the status system does not update component tallies.

Records Courier Sender confirmation service tasks.
Courier Sender errors.

Processes Management Information Format (MIF) files and hardware inventory in the SMS database.
Communications errors in the SMS database or “bad” hardware inventory files. Make sure that the delta MIF file was processed to the SMS site database.

Saves DDR information to the SMS database by the Discovery Data Manager.
Communicating errors with Microsoft SQL Server or “bad” discovery records.

Records incoming site-to-site communication transfers.
Corrupted files or when the Despooler component cannot decompress packages.

Records package creation, compression, delta replication, and information updates.
Package source version issues or package update issues.

Records site configuration changes and publishes site information in Active Directory.
Site control serial number or delta serial number issues, or scenarios where the site cannot publish site information to Active Directory. Make sure that *.CT2 files are processed and that child sites attach correctly. Make sure that the site code and roaming boundaries are published to the Active Directory.

Records files that are moved from the CAP to the corresponding SMS\INBOXES folder.
Problems with site server permissions or scenarios where the registry is corrupted.

Records CAP file maintenance.
Problems with permissions or scenarios where the registry is corrupted.

Records the processing of delta MIF files for the SMS Dataloader component from client inventory files.
Problems with file corruption. Make sure that .nhm files are processed to .mif files.

Records the registration of the management point with WINS. Records the availability of the management point every ten minutes.
Possible IIS issues if the management point is unavailable. Review this log for other IIS communication issues and WINS registration issues.

Management point component that moves client files to the corresponding SMS\INBOXES folder.
Problems with file permissions.

Management point .msi installation log.
Management point installation errors. Search for “return value 3” errors.

Records the management point installation wrapper process.
Scenarios where you cannot run Mp.msi or management point installation is not completed. Make sure that Mp.msi was started.

SMS server discovery.
Problems with SMS site systems discovery.

Records advertisement updates.
File corruption or scenarios where notification and advertisement changes do not occur.

Records summarization of advertisement status messages.
Status message miscounts or scenarios where summarization files are not created.

Records updates to the Advanced Client policies to reflect changes to client settings or advertisements.
Scenarios where policy updates do not occur after you make changes to advertisements or to client settings.

Records the replication of files between the site server components and the Scheduler component.
A backlog of files in the INBOXES\Schedulr.box\tosend folder or file permission issues. Make sure that outgoing requests are changed to minijobs for the Scheduler component and that incoming files are moved to the correct component.

Reporting point setup log.
Installation errors.

Records site-to-site job and package replication.
A backlog of files that are caused by sender errors or by package corruption.

Records files that are sent to other child and parent sites.
Permissions problems for the INBOXES\DESPOOLR.BOX\RECEIVE sending site folder or an incorrect site address. Make sure that the site can connect to the SMS_Site share on the destination site and that data was transferred.

Records client software inventory data processing to the SMS site database in SQL Server.
Problems with corrupted files or access to SQL Server.

Records maintenance of the installed site components.
Upgrade issues, registry or file system permission issues, or scenarios where the site cannot publish site information to Active Directory.

Records site setting changes to the Sitectrl.ct0 file.
Site control file or database corruption. Make sure that the Sitectrl.ct0 file is updated.

Records the monitoring process of all site systems.
Scenarios where the site cannot access remote site systems to generate status information for available drive space or available database space.

Records database changes.
Possible corruption of the registry triggers or a scenario where the site cannot access SQL Server.

Records processing of all site server component threads.
Problems with possible site corruption or a scenario where the component services do not start.

Records WMI provider access to the SMS database.
Possible WMI corruption or permissions issues with the WMI provider. This file also logs the WMI and SQL queries that are used to access the SMS database.

Records the Reporting Point installation. This component starts the installation tasks and processes configuration changes.
Reporting Point installation.

Records the maintenance of accounts when the site uses standard security.
Scenarios where accounts are removed or changed.

This component writes all status messages to the database.
Scenarios where status messages do not appear, or they appear corrupted.

This component processes metering files and maintains settings.
Scenarios where software metering information does not appear or appears corrupted.

If management points are installed in the site hierarchy, management point log files are stored in the SMS_CCM\LOGS folder on the management point computer. The following table describes the management point log files and lists possible issues that apply.

Log file name
Used to help troubleshoot

Records the conversion of XML.ddr records from clients and copies them to the site server.
File corruption or access to the SMS\MP\OUTBOXES\DDR.BOX folder.

Records the status of the site management points.
IIS access errors.

Records policy information.
WMI access problems.

This component converts XML hardware inventory records from clients and copies the files to the site server.
File corruption or access to the SMS\MP\OUTBOXES\HINV.BOX folder. Make sure hardware inventory data is converted from XML to NHM file format.

Records location manager tasks.
IIS and WMI access problems.

Records policy communication.
SQL Server access problems.

This component copies files that are collected from the client.
File corruption issues.

Records the hardware inventory retry processes.
Corrupted hardware inventory files.

This component converts XML hardware inventory records from clients and then copies them to the site server.
File corruption or access to the SMS\MP\OUTBOXES\SINV.BOX folder. Make sure that software inventory data is converted from XML to SIC or SID file format.

This component converts XML.svf status message files from clients and copies them to the site server.
File corruption or access to the SMS\MP\OUTBOXES\STAT.BOX folder. Make sure that the status message data is converted from XML to SVF file format.

Back to the top
Back to the top

To turn off logging

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
You can manually turn on or turn off logging of the SMS components on the SMS 2003 site server. To turn on logging for the site components, follow these steps:

Click Start, click Run, type regedit, and then click OK.

Locate the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Tracing subkey.

Double-click the Enabled value.

Type 1 in the Value data text box, and then click OK. To turn off logging, use 0 as the Value data. If you want turn off component logging, skip steps 6 and 7.

Click Start, point to Administrative Tools, and then click Services.

Stop and then restart the SMS_EXECUTIVE and SMS_SITE_COMPONENT_MANAGER services.

Back to the top
Back to the top

The SMS Trace utility

You can use the SMS Trace utility (Trace32.exe) to view the SMS log files in real time. When you use the SMS Trace utility, the log view automatically updates to show new entries. The SMS 2003 SMS Trace utility is included in SMS 2003 Toolkit 1. For more information about SMS 2003 Toolkit 1, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyID=8a652974-852f-4845-af9f-c61f3f912540&DisplayLang=en (http://www.microsoft.com/downloads/details.aspx?FamilyID=8a652974-852f-4845-af9f-c61f3f912540&DisplayLang=en)

The SMS 2003 version of the SMS Trace utility includes specific improvements to help you identify error messages and read log files that are generated by IIS.
The SMS 2003 SMS Trace utility has the following feature enhancements:

You can view IIS, Unicode, and MSI logs.

You can select errors.

You can search error codes.

You can use a new information pane to see additional data that is contained in the log entry.