SMS 2003 - Troubleshooting - MP Control Manager Related Issues (IIS)

I had spent some time yesterday researching and correcting an IIS-related issue with my MP on a particular Site Server. Another issue was present on which I had found some information, but had not found a resolution. Again, within the Application Event log on the Site Server, the following errors were showing:

Event_ID: 47

WMI ADAP was unable to retrieve data from the PerfLib subkey: SYSTEM\CurrentControlSet\Services\mssindex\Performance\Library, error code: 0x80041009

Event_ID: 47

WMI ADAP was unable to retrieve data from the PerfLib subkey: SYSTEM\CurrentControlSet\Services\MSSGTHRSVC\Performance\Library, error code: 0x80041009


Event_ID: 47

WMI ADAP was unable to retrieve data from the PerfLib subkey: SYSTEM\CurrentControlSet\Services\MSSGatherer\Performance\Library, error code: 0x80041009


Event_ID: 47

WMI ADAP was unable to retrieve data from the PerfLib subkey: SYSTEM\CurrentControlSet\Services\MSSEARCH\Performance\Library, error code: 0x80041009


Event_ID: 47

WMI ADAP was unable to retrieve data from the PerfLib subkey: SYSTEM\CurrentControlSet\Services\Autocat\Performance\Library, error code: 0x80041009


The research I performed indicated there were some additional permissions which needed to be made - and these were already present when I checked the various areas listed. But, to my surprise, these errors disappeared after my re-installation of IIS yesterday. All Event Logs were clear of the problems reported yesterday.

I will still research this, but for the time being, I'm going to attribute yesterday's problems to a corrupt IIS installation. If anyone has had these issues and found an alternate solution, please post a comment.

SMS 2003 - Troubleshooting - MP Control Manager detected MPsetup has failed to create the CCM_Incoming Virtual Directory

This morning greeted me with an error message I had not seen in quite a while. As I was going through my normal "morning check" of our various SMS sites, I noticed one particular site was lit up like a Christmas tree. Both the OS Application Event log and the SMS_MP_CONTROL_MANAGER had multiple errors displaying:

SMS_MP_CONTROL_MANAGER:

Message ID: 1020

SMS Site Component Manager failed to reinstall this component on this site system.

Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager will automatically retry the reinstallation in 60 minutes. To force SMS Site Component Manager to immediately retry the reinstallation, stop and restart SMS Site Component Manager using the SMS Service Manager.

Message ID: 4963

MP Control Manager detected MPsetup has failed to create the CCM_Incoming Virtual Directory.

Possible cause: The IIS IWAM account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IWAM account. (i.e.: “net user IWAMMachineName)
Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use “net user” to modify the account properties.

Possible cause: The IIS IUSR account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IUSR account. (i.e.: “net user IWAMMachineName)
Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use “net user” to modify the account properties.

Possible cause: The Default Web Site is disabled in IIS.
Solution: Verify that the Default Web Site is enabled, and functioning properly.


Application Event Log:

Event_ID: 10005

Product: SMS Management Point -- Error 25006. Setup was unable to create the Internet virtual directory CCM_System
The error code is 80020009


MPSetup.log: (at the tail end of the MP installation log)

<05-02-2007 09:57:45> Setup was unable to create the Internet virtual directory CCM_System
The error code is 80020009
<05-02-2007 09:58:00> MP.MSI exited with return code: 1603
<05-02-2007 09:58:00> Backing up MPMSI.log to E:\SMS\logs\MPMSI.log.LastError
<05-02-2007 09:58:00> Fatal MSI Error - MP.MSI could not be installed.


I've had this error before, generally after a site reset required after an upgrade. In the past I've tried recommended fixes of starting and stopping services, rebooting, etc., etc. But, none of these methods ever worked consistently from one time to the next. Following is how I solve this problem and it has worked for me 100% of the time:

- Remove the MP role from the Site Server. Watch the MPSetup.log to ensure that the removal is complete.
- Uninstall the IIS component from the OS of the Site Server.
- Reboot the Site Server.
- Run ccmdelcert.exe from the SMS Toolkit.
- Reinstall the IIS component (with BITS) on the OS of the Site Server.
- Go into the IIS manager and allow WebDav.
- Add the MP role to the Site Server. Watch the MPSetup.log to ensure that the installation completes correctly.

Again, in my experience, I've never had this method fail, nor hork up any other process on the Site Server. Other experiences may vary, but I can only speak to my own. I hope this helps someone out there.

SMS 2003 - Updates - SP3 is LIVE

I'm not sure about the rest of you, but for me, this is a very exciting day. I've had SP3 in the test lab for a while now, and I do like the extra features it offers. Here is the Microsoft summary and the link.

<<>>
Overview
Microsoft Systems Management Server (SMS) 2003 with Service Pack 3 (SP3) brings full Vista support to your organization beyond just OS Deployment, which is already available through the OS Deployment Feature Pack. Now, full lifecycle support of Microsoft’s latest platform including software distribution, update services as well as inventory are available to the Vista Client. In addition, SP3 introduces X64 architecture support for your high performance platforms. SMS 2003 SP3 provides an option to augment existing SMS inventory capabilities with deeper asset intelligence, bringing knowledge driven management with over 400,000 software titles in the library.

Install the “SMS 2003 Device Management Feature Pack” to correct the device file collection issue after applying SMS 2003 SP3. Please reference KB 934206 for more details (http://support.microsoft.com/kb/934206/ )
<<>>


SMS 2003 Service Pack 3 Home Page

SMS 2003 - Troubleshooting - 4918 Errors in SMS_SITE_COMPONENT_MANAGER

If you've recently upgraded your SMS infrastructure to SP2, you may have encountered repeating 4918 errors within the SMS_SITE_COMPONENT_MANAGER component. Here is a brief of how the error would read:

<<>>
Message ID: 4918

Systems Management Server cannot update the dNSHostName property for the existing object "cn=SMS-MP-Z13-LWSMSLWPRIM" in Active Directory. This property is used to publish fully qualified host names in Active Directory.

Possible cause: The Active Directory schema has not been extended with latest version of the SMS Active Directory classes and attributes.
Solution: Ensure the schema has been extended with the latest version of the SMS Active Directory classes and attributes. The schema can be extended with the tool "extadsch.exe" from the SMS directory on the SMS Site server that reported this message.
<<>>

The resolution presented is correct in this situation. SP2 for SMS 2003 has an added feature of utilizing the Site Server FQDN's within Active Directory. To use this function, you must extend the Active Directory Schema. The tools you need are provided with the SP2 upgrade files. You can extend the schema using extadsh.exe or with the provided LDIF file using ldifde.exe. I've provided links to explanations for both methods, but I prefer using extadsh.exe.

*** It should be noted that it is NOT necessary to extend the schema for SP2 if you do not plan on taking advantaged of the extended features. These errors are not malicious and will not affect the operation of your site.

Blogcast For EXTADSH.EXE

Technical Document for Using LDIFDE.EXE

SMS 2003 - Reports - Computer Model Reports

Recently I was asked to provide some SMS web reports for upcoming budget planning sessions. Specifically, managers wanted computer model reports for machine refresh expenditures. I created a few reports, but these two were well-received by managers. Perhaps some of you may find these reports useful. I have included the MOF code for importing. There are two reports supplied here. (The MOF code does not always import correctly so I have provided a link to the file on MyITForum, where I posted the original article 2/5/2007)

http://www.myitforum.com/inc/arts/11649reports.zip



// *********************************************************************************
//
// Created by SMS Export object wizard
//
// Friday, February 02, 2007 created
//
// File Name: models_by_selection.MOF
//
// Comments :
//
// Displays workstations of a selected model: (Machine Name, Serial Number, Mfg, Mo
// del, and OS)
//
// *********************************************************************************


// ***** Class : SMS_Report *****
[SecurityVerbs(140551)]
instance of SMS_Report
{
Category = "Hardware - General";
Comment = "";
GraphXCol = 1;
GraphYCol = 2;
MachineDetail = FALSE;
MachineSource = FALSE;
Name = "Count Computer Models by Selection (Show All)";
NumPrompts = 1;
RefreshInterval = 0;

ReportParams = {
instance of SMS_ReportParameter
{
AllowEmpty = FALSE;
DefaultValue = "";
PromptText = "Enter Computer Model";
SampleValueSQL = "SELECT DISTINCT Model0 FROM v_GS_COMPUTER_SYSTEM
\nORDER BY Model0";
VariableName = "variable";
}};
SecurityKey = "";
SQLQuery = "SELECT v_R_System.Name0, v_GS_PC_BIOS.SerialNumber0, v_GS_COMPUTER_SYSTEM.Manufacturer0, v_GS_COMPUTER_SYSTEM.Model0,
\n v_R_System.Operating_System_Name_and0
\nFROM v_R_System INNER JOIN
\n v_GS_COMPUTER_SYSTEM ON v_R_System.ResourceID = v_GS_COMPUTER_SYSTEM.ResourceID INNER JOIN
\n v_GS_PC_BIOS ON v_R_System.ResourceID = v_GS_PC_BIOS.ResourceID
\nWHERE (v_GS_COMPUTER_SYSTEM.Model0 = @variable)
\nORDER BY v_R_System.Name0";
StatusMessageDetailSource = FALSE;
};
// ***** End *****


// *********************************************************************************
//
// Created by SMS Export object wizard
//
// Friday, February 02, 2007 created
//
// File Name: models_by_ADSite.MOF
//
// Comments :
//
// Displays a summary count of all computer models in a particular Site. (selected
// by AD Site)
//
// *********************************************************************************


// ***** Class : SMS_Report *****
[SecurityVerbs(140551)]
instance of SMS_Report
{
Category = "Hardware - General";
Comment = "";
GraphCaption = "";
GraphType = 0;
GraphXCol = 2;
GraphYCol = 3;
MachineDetail = FALSE;
MachineSource = FALSE;
Name = "Count Computer Models by Site (AD Boundaries Only)";
NumPrompts = 1;
RefreshInterval = 0;

ReportParams = {
instance of SMS_ReportParameter
{
AllowEmpty = FALSE;
DefaultValue = "";
PromptText = "Enter Site Name";
SampleValueSQL = "SELECT SiteCode, v_Site.SiteName FROM v_Site";
VariableName = "variable";
}};
SecurityKey = "";
SQLQuery = "SELECT v_SiteBoundary_ADSite.SiteCode, v_GS_COMPUTER_SYSTEM.Model0, COUNT(DISTINCT v_GS_COMPUTER_SYSTEM.ResourceID) AS Count
\nFROM v_GS_COMPUTER_SYSTEM INNER JOIN
\n v_R_System ON v_GS_COMPUTER_SYSTEM.ResourceID = v_R_System.ResourceID INNER JOIN
\n v_SiteBoundary_ADSite ON v_R_System.AD_Site_Name0 = v_SiteBoundary_ADSite.ADSiteName
\nWHERE (v_SiteBoundary_ADSite.SiteCode LIKE @variable)
\nGROUP BY v_SiteBoundary_ADSite.SiteCode, v_GS_COMPUTER_SYSTEM.Model0";
StatusMessageDetailSource = FALSE;
XColLabel = "";
YColLabel = "";
};
// ***** End *****

SMS 2003 - Log Files - The CAS.log Revealed - Part 1

When encountering software distribution problems, the SMS client log files are key in the troubleshooting process. Four client log files come to mind when thinking about how to go about resolving software distribution problems: LocationServices.log, CAS.log, Execmgr.log and ContentTransferManager.log. Each has its own purpose and contains information valuable to tracking down the source of a software distribution problem. In this article, I'm going to focus on the CAS.log and review some details about the information which it contains.

The CAS.log (Content Access Service) is typically used to find the status of the local package cache. It shows the success, or lack thereof, of the client's attempts at accessing content on its Distribution Point. Containing valuable distribution information, the CAS.log can be an asset to SMS sdministrators attempting to deduce various software distribution problems.

Let's take a look at a CAS.log containing the successful access of a software package which has been advertised to a client. This particular advertisement is set to run from the distribution point. I have omitted time stamp information from the log displayed here to save space.

Requesting content Z00000FD.1, size(KB) 1164, under context System
LS job {78C2DCAB-26A0-43BF-A1A1-11263440625B} submitted to get DP locations for content Z00000FD.1
Successfully created location request {EA8DD5F0-964D-4B0D-B116-8BC84EDD4F42} for content Z00000FD.1
Location update from LS for content Z00000FD.1 and location request {EA8DD5F0-964D-4B0D-B116-8BC84EDD4F42}
Matching DP Location found 0 - \\IOWACSMSPRIM01\Z20_DP_SHARE$\SMSPKG\Z00000FD\
Canceling LS Job {78C2DCAB-26A0-43BF-A1A1-11263440625B} for content Z00000FD.1

You can follow the process in the log and see the subsequent successful location of the content on a reachable DP. Considering this is not a "download and run" advertisement, the logging for this content ends a the job cancellation. You can pick up the rest of the process in other client logs which will be discussed in future articles.

Now let's look at the CAS.log of the same package advertised to a client where there is no available Distribution Point containing the package.

Requesting content Z00000FD.1, size(KB) 1164, under context System
LS job {5B0BBB9F-89A1-45E2-AC50-02C0921F4B47} submitted to get DP locations for content Z00000FD.1
Successfully created location request {837B5728-D4CB-4C25-BD35-A39ECBAC5110} for content Z00000FD.1
Location update from LS for content Z00000FD.1 and location request {837B5728-D4CB-4C25-BD35-A39ECBAC5110}
No matching DP Location found
Location update from LS for content Z00000FD.1 and location request {837B5728-D4CB-4C25-BD35-A39ECBAC5110}
No matching DP Location found

(These last two message repeat until a failure is determined at which time the following messages occur.)

Failed to get DP locations from LS for content Z00000FD.1 and location request {837B5728-D4CB-4C25-BD35-A39ECBAC5110}
Releasing content request {837B5728-D4CB-4C25-BD35-A39ECBAC5110}
Canceling LS Job {00000000-0000-0000-0000-000000000000} for content Z00000FD.1
CancelLocationRequestfailed

The failure notifications will be easy to locate in the CAS.log using SMS Trace as the "Failed to get DP location..." message will be in yellow and the "CancelLocationRequestfailed" message will be flagged in red.

Hopefully this will help some with the visual on how the CAS.log works with non-downloaded content. In a future article I will discuss and demonstrate the workings of the CAS.log in reference to downloaded content. There are differences between the logging of the two types of content requests which are significant enough to document and demonstrate.

SMS 2003 - Reporting Site - Increasing the ASP script timeout value

If you have ever run a particularly time-consuming SMS Web Report, you have probably run into the problem where IIS times out during the report. The error indicates that the ASP script has timed out.

The default timeout value is set to 90 seconds. You can increase this value within IIS Manager:

• Open IIS Manager
• Expand Web Sites
• Right-click on SMSReporting_SiteCode and select Properties
• Within the Virtual Directory tab, click on the Configuration button
• Within the Options tab, enter the desired timeout value in the ASP Script Timeou field (shown in seconds)
• Click OK, Click OK, then close the IIS Manager

This may take a few configurations to get the timing correct for your report, but it's well-worth the few seconds it takes to change it.

Security Vulnerabilities - Broadcom and Centrino Wireless

Some of you may have had the recent surprise of the Broadcom and Centrino Wireless vulnerabilities and have wondered how to tackle the problem. Here's what we did to pinpoint the machines.

1. Within (Site Settings in the console) Client Agents > Software Inventory Client Agent > Properties
2. Add a new file type *.sys
3. Set the Path to a “Variable or path name” = %windir%\system32\drivers\ and Search subdirectories
4. Make sure all Excludes are unchecked
5. Make sure File details and Product details are checked
6. Refresh machine policies on all sites where changes are made
7. Initiate Software Inventory on all sites where change are made
8. Wait for the data to flow up to your reporting sites
9. Within (Reporting Website) Software – Files > Computers with a specific file
10. Enter the filename for which you are searching. (i.e. for Broadcom wireless – BCMWL5.sys
11. When the report is produced, sort by file version and export this report to an Excel spreadsheet
12. Eliminate all rows which have a version which is compliant with the new standards
13. Create a text file with the list of machine names and eliminate all spaces (reports tend to put spaces in strange places)
14. Create a collection with the tool “Collection Adder” with the test file you just created
15. Deploy your update to this collection. (each different driver will require a separate collection and deployment of course.)

I hope this helps others trying to tackle this problem.