troubleshooting sccm

Troubleshooting SCCM..Part I (Client Push Installation)

Client Installation

Once you are through with the installation of the SCCM server and the configuration then the next major task is client or agent installation. There are various methods to accomplish this task. Please check this link for more details. http://technet.microsoft.com/en-us/library/bb633063.aspx e,

Whatever be the method used, the logic remains the same. The ccmsetup.exe is downloaded to the system and is executed. The ccmsetup.exe reads the manifest file and fetches the remaining files to continue the client installation.

When ccmsetup.exe runs from the source specified in the command or from the MP it will download the other necessary files required for installation and trigger the client installation on the local system installation and trigger the client installation on the local system

The important log in case of client installation in the agent is the ccmsetup.log and clientmsi.log these logs are present in the location C:\windows\System32\ccmsetup

Troubleshooting Client Push Installation

When we start troubleshooting client push installation the first log we need to check is ccm.log in the server logs 1[1] .If you look at the ccm.log you can see the start of the request made to the client and you can verify if the ccmsetup.exe service was able to successfully run on the targeted client machine.

èCCM.log

Received request: "HIQMYRJC" for machine name: "SQL" on queue: "Incoming". SMS_CLIENT_CONFIG_MANAGER 4/16/2010 9:31:37 AM 1908 (0x0774)

Stored request "HIQMYRJC", machine name "SQL", in queue "Processing". SMS_CLIENT_CONFIG_MANAGER 4/16/2010 9:31:37 AM 1908 (0x0774)

======>Begin Processing request: "HIQMYRJC", machine name: "SQL" SMS_CLIENT_CONFIG_MANAGER 4/16/2010 9:31:40 AM 3196 (0x0C7C)

---> Attempting to connect to administrative share '\\SQL.MYLAB.IN\admin$' using account 'mylab\administrator' SMS_CLIENT_CONFIG_MANAGER4/16/2010 9:31:40 AM 3196 (0x0C7C)

---> Connected to administrative share on machine SQL.MYLAB.IN using account 'mylab\administrator' SMS_CLIENT_CONFIG_MANAGER 4/16/2010 9:31:43 AM3196 (0x0C7C)

---> Attempting to make IPC connection to share <\\SQL.MYLAB.IN\IPC$> SMS_CLIENT_CONFIG_MANAGER 4/16/2010 9:31:43 AM 3196 (0x0C7C)

1[1] Server logs <Drive>:\Program Files\Microsoft Configuration Manager\Logs or <Drive>\SMS\Logs

---> Searching for SMSClientInstall.* under '\\SQL.MYLAB.IN\admin$\' SMS_CLIENT_CONFIG_MANAGER 4/16/2010 9:31:43 AM 3196 (0x0C7C)

---> Service Pack version from machine "SQL" is 2 SMS_CLIENT_CONFIG_MANAGER 4/16/2010 9:31:49 AM 3196 (0x0C7C)

---> Creating \ VerifyingCopying exsistance of destination directory \\SQL\admin$\system32\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 4/16/2010 9:31:50 AM3196 (0x0C7C)

---> Copying client files to \\SQL\admin$\system32\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 4/16/2010 9:31:50 AM 3196 (0x0C7C)

---> Copying file "C:\Program Files\Microsoft Configuration Manager\bin\I386\MobileClient.tcf" to "\\SQL\admin$\system32\ccmsetup\MobileClient.tcf"SMS_CLIENT_CONFIG_MANAGER 4/16/2010 9:31:50 AM 3196 (0x0C7C)

---> Copying file "C:\Program Files\Microsoft Configuration Manager\bin\I386\ccmsetup.exe" to "\\SQL\admin$\system32\ccmsetup\ccmsetup.exe"SMS_CLIENT_CONFIG_MANAGER 4/16/2010 9:31:50 AM 3196 (0x0C7C)

---> Created service "ccmsetup" on machine "SQL". SMS_CLIENT_CONFIG_MANAGER 4/16/2010 9:31:55 AM 3196 (0x0C7C)

---> Started service "ccmsetup" on machine "SQL". SMS_CLIENT_CONFIG_MANAGER 4/16/2010 9:32:02 AM 3196 (0x0C7C)

---> Deleting SMS Client Install Lock File '\\SQL.MYLAB.IN\admin$\SMSClientInstall.LAB' SMS_CLIENT_CONFIG_MANAGER 4/16/2010 9:32:02 AM3196 (0x0C7C)

---> Completed request "HIQMYRJC", machine name "SQL". SMS_CLIENT_CONFIG_MANAGER 4/16/2010 9:32:02 AM 3196 (0x0C7C)

Deleted request "HIQMYRJC", machine name "SQL" SMS_CLIENT_CONFIG_MANAGER 4/16/2010 9:32:02 AM 3196 (0x0C7C)

<======End request: "HIQMYRJC", machine name: "SQL". SMS_CLIENT_CONFIG_MANAGER 4/16/2010 9:32:02 AM 3196 (0x0C7C)

If you are able to see that the ccmsetup.exe service is created then it clearly informs us that the server has completed its request to the client and the client has started installing. From here on you need to check the client for troubleshooting.

In case you don’t see “started service” in ccm.log then that means that the requirements are not met. See the points below for the Client Push installation pre-requisites

At least one Client Push Installation account must be defined in the Accounts tab of the Client Push Installation Properties dialog box. This account must be a member of the local Administrators group.

The computer to which you are targeting the client installation must have been discovered by at least one Configuration Manager 2007 discovery method.

The computer has an ADMIN$ share and able to connect from the SCCM server with the account used for Client push installation (You can check if you can access \\<Clientname>\ADMIN$ from the sccm server)

In case this fails make sure that ADMIN$ is enabled in the client From the server to the client there are no DNS issue

Firewall is not blocking the SMB traffic Account Specified for client push is correct and have permission to connect to

the share

The WMI connection also should be possible from the SCCM server to the client with the account used for Client push installation (You can use WbemTest and try connecting to \\<Clientname>\root\cimv2 and make sure you are able to remotely connect to client WMI)

Make sure that there are no DNS issues Check the properties of the WMI and make sure remote connectivity is allowed Make sure the RPC port 135 and the Dynamic port range is opened in any

firewall between the client and the server including the windows firewall.

Enable client push installation to assigned resources must be selected in the Client Push Installation Properties dialog box if you want to automatically push the Configuration Manager 2007 client to discovered resources.

The client computer must be able to contact a management point in order to download supporting files.

The ports used when you are doing a client push is

Description UDP TCP

Server Message Block (SMB) between the site server and client computer.

-- 445

RPC endpoint mapper between the site server and the client computer.

135 135

RPC dynamic ports between the site server and the client computer.

-- DYNAMIC

Hypertext Transfer Protocol (HTTP) from the client computer to a mixed mode management point.

-- 80 (See note 1, Alternate Port Available)

Secure Hypertext Transfer Protocol (HTTPS) from the client computer to a native mode management point.

-- 443 (See note 1, Alternate Port Available)

In order to successfully use client push to install the Configuration Manager 2007 client, you must add the following as exceptions to the Windows Firewall:

File and Printer Sharing Windows Management Instrumentation (WMI)

The following links will give more details

http://technet.microsoft.com/en-us/library/bb680537.aspx

http://technet.microsoft.com/en-us/library/ff189805.aspx


Client side troubleshooting

Once the ccmsetup service is started in the client then you need to check the client logs. If you look at the ccmsetup.log you should find that from the source or the MP the required files are downloaded. If you find any error pertaining to download please check the following

1) There is no DNS issue in the client and that client is able to resolve the SCCM server NetBIOS as well as FQDN without any issues.

2) Make sure that the MP link is accessible from the client

http://<SCCM_SERVER/SMS_MP/.sms_aut?mplist

http://<SCCM_SERVER/SMS_MP/.sms_aut?mpcert

If the above test fails make sure that MP is working fine. You can check mpcontrol.log on the server to find the error and make sure that the same works.

3) Make sure that the firewall allows the download of the required files.

è CCMSETUP.log

==========[ ccmsetup started in process 5780 ]========== ccmsetup 1/31/2010 8:55:52 AM 5100 (0x13EC)

Version: 4.0.6487.2000 ccmsetup 1/31/2010 8:55:52 AM 5100 (0x13EC)

Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 1/31/2010 8:55:52 AM5100 (0x13EC)

Command line: "C:\WINDOWS\system32\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf ccmsetup 1/31/2010 8:55:52 AM 5100 (0x13EC)

CCMHTTPPORT: 80 ccmsetup 1/31/2010 8:55:52 AM 5100 (0x13EC)

CCMHTTPSPORT: 443 ccmsetup 1/31/2010 8:55:52 AM 5100 (0x13EC)

CCMHTTPSSTATE: 0 ccmsetup 1/31/2010 8:55:52 AM 5100 (0x13EC)

CCMHTTPSCERTNAME: ccmsetup 1/31/2010 8:55:52 AM 5100 (0x13EC)

FSP: ccmsetup 1/31/2010 8:55:52 AM 5100 (0x13EC)

CCMFIRSTCERT: 0 ccmsetup 1/31/2010 8:55:52 AM 5100 (0x13EC)

Config file: C:\WINDOWS\system32\ccmsetup\MobileClient.tcf ccmsetup 1/31/2010 8:55:52 AM 5100 (0x13EC)

Retry time: 10 minute(s) ccmsetup 1/31/2010 8:55:52 AM 5100 (0x13EC)

MSI log file: ccmsetup 1/31/2010 8:55:52 AM 5100 (0x13EC)

MSI properties: INSTALL="ALL" SMSSITECODE="LAB" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" CCMFIRSTCERT="0"ccmsetup 1/31/2010 8:55:52 AM 5100 (0x13EC)

Source List: ccmsetup 1/31/2010 8:55:52 AM 5100 (0x13EC)

\\SCCM.MYLAB.IN\SMSClient ccmsetup 1/31/2010 8:55:52 AM 5100 (0x13EC)

\\SCCM\SMSClient ccmsetup 1/31/2010 8:55:52 AM 5100 (0x13EC)

MPs: ccmsetup 1/31/2010 8:55:52 AM 5100 (0x13EC)

SCCM.MYLAB.IN ccmsetup 1/31/2010 8:55:52 AM 5100 (0x13EC)

Updated security on object C:\WINDOWS\system32\ccmsetup\. ccmsetup 1/31/2010 8:55:52 AM 5100 (0x13EC)

A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent. ccmsetup 1/31/2010 8:55:52 AM 5100 (0x13EC)

Running as user "SYSTEM" ccmsetup 1/31/2010 8:55:52 AM 4928 (0x1340)

Detected 2442 MB free disk space on system drive. ccmsetup 1/31/2010 8:55:52 AM 4928 (0x1340)

DetectWindowsEmbeddedFBWF() Detecting OS Version ccmsetup 1/31/2010 8:55:52 AM 4928 (0x1340)

Client OS Version is 5.2, Service Pack Version 2 ccmsetup 1/31/2010 8:55:52 AM 4928 (0x1340)

Client OS is not a supported Windows Embedded Platform ccmsetup 1/31/2010 8:55:52 AM 4928 (0x1340)

IsFileMicrosoftTrusted Verified file 'C:\WINDOWS\system32\ccmsetup\WindowsServer2003-KB923845-x86-ENU.exe' is MS signed. ccmsetup1/31/2010 8:56:32 AM 4928 (0x1340)

Installing file 'C:\WINDOWS\system32\ccmsetup\WindowsServer2003-KB923845-x86-ENU.exe' with options '/norestart /quiet /log:C:\WINDOWS\system32\ccmsetup\WindowsServer2003-KB923845-x86-ENU.exe.log'. ccmsetup 1/31/2010 8:56:32 AM 4928 (0x1340)

File 'C:\WINDOWS\system32\ccmsetup\WindowsServer2003-KB923845-x86-ENU.exe' returned exit code 3010. ccmsetup 1/31/2010 8:58:18 AM4928 (0x1340)

Finished installing file 'C:\WINDOWS\system32\ccmsetup\WindowsServer2003-KB923845-x86-ENU.exe'. ccmsetup 1/31/2010 8:58:18 AM 4928 (0x1340)

Successfully ran BITS check. ccmsetup 1/31/2010 8:58:18 AM 4928 (0x1340)

IsFileMicrosoftTrusted Verified file 'C:\WINDOWS\system32\ccmsetup\ccmsetup.cab' is MS signed. ccmsetup 1/31/2010 8:58:48 AM 4928 (0x1340)

Successfully extracted manifest file C:\WINDOWS\system32\ccmsetup\ccmsetup.xml from file C:\WINDOWS\system32\ccmsetup\ccmsetup.cab.ccmsetup 1/31/2010 8:58:48 AM 4928 (0x1340)

Loading manifest file: C:\WINDOWS\system32\ccmsetup\ccmsetup.xml ccmsetup 1/31/2010 8:58:48 AM 4928 (0x1340)

Successfully loaded ccmsetup manifest file. ccmsetup 1/31/2010 8:58:48 AM 4928 (0x1340)

Once the download is over the MSI action starts and the client installation proceeds so further error shown you need to check the client.msi.log to see if there is issue.

èClient.msi.log

=== Verbose logging started: 4/16/2010 9:36:44 Build type: SHIP UNICODE 3.01.4000.3959 Calling process: C:\WINDOWS\system32\ccmsetup\ccmsetup.exe ===

MSI (c) (8C:48) [09:36:45:817]: Resetting cached policy values

MSI (c) (8C:48) [09:36:45:817]: Machine policy value 'Debug' is 0

MSI (c) (8C:48) [09:36:45:817]: ******* RunEngine:

******* Product: C:\WINDOWS\system32\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\client.msi

******* Action:

******* CommandLine: **********

MSI (c) (8C:48) [09:36:45:927]: Client-side and UI is none or basic: Running entire install on the server.

MSI (c) (8C:48) [09:36:45:927]: Grabbed execution mutex.

MSI (c) (8C:48) [09:36:45:957]: Cloaking enabled.

MSI (c) (8C:48) [09:36:45:957]: Attempting to enable all disabled priveleges before calling Install on Server

MSI (c) (8C:48) [09:36:45:957]: Incrementing counter to disable shutdown. Counter after increment: 0

………………… (Proceeds………………)

……………………..

Property(S): PrimaryVolumePath = C:

MSI (s) (78:74) [10:05:05:310]: Note: 1: 1728

MSI (s) (78:74) [10:05:05:350]: Product: Configuration Manager Client -- Configuration completed successfully.

MSI (s) (78:74) [10:05:05:530]: Cleaning up uninstalled install packages, if any exist

MSI (s) (78:74) [10:05:05:530]: MainEngineThread is returning 0

MSI (s) (78:74) [10:05:05:630]: Destroying RemoteAPI object.

MSI (s) (78:C8) [10:05:05:670]: Custom Action Manager thread ending.

=== Logging stopped: 4/16/2010 10:05:05 ===

MSI (c) (8C:48) [10:05:06:321]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1

MSI (c) (8C:48) [10:05:06:391]: MainEngineThread is returning 0

=== Verbose logging stopped: 4/16/2010 10:05:06 ===

Common issue found at this phase is the WMI issues of the client. You can try rebuilding the WMI or can fix that before you retry the installation. More details on this you can check the client reporting troubleshooting.

Note: Rebuilding WMI might lead to some application which were working on the system not to work so make sure you don’t perform this on servers but can be done on client OS where you can reinstall the application not working after the rebuild.

Once successfully completed you should find

èCCMSETUP.LOG

MSI: Action 9:50:05: RollbackCleanup. Removing backup files ccmsetup 4/16/2010 9:50:05 AM 5336 (0x14D8)

MSI: Action 9:50:08: RemoveExistingProducts. Removing applications ccmsetup 4/16/2010 9:50:08 AM 5336 (0x14D8)

Installation succeeded. Windows Installer has requested a reboot. ccmsetup 4/16/2010 9:50:08 AM 5336 (0x14D8)

Successfully deleted the ccmsetup service ccmsetup 4/16/2010 9:50:15 AM 5336 (0x14D8)

A Fallback Status Point has not been specified. Message with STATEID='401' will not be sent. ccmsetup 4/16/2010 9:50:15 AM 5336 (0x14D8)

Deleted file C:\WINDOWS\system32\ccmsetup\WindowsServer2003-KB923845-x86-ENU.exe ccmsetup 4/16/2010 9:50:15 AM 2032 (0x07F0)

Deleted file C:\WINDOWS\system32\ccmsetup\ccmsetup.cab ccmsetup 4/16/2010 9:50:15 AM 2032 (0x07F0)

Deleted file C:\WINDOWS\system32\ccmsetup\ccmsetup.xml ccmsetup 4/16/2010 9:50:15 AM 2032 (0x07F0)

Deleted file C:\WINDOWS\system32\ccmsetup\client.msi ccmsetup 4/16/2010 9:50:15 AM 2032 (0x07F0)

If you are using the Software Update Point client installation you can check the windowsupdate.log on %systemdrive%\windows\. On checking this log you will be able to find that the installation request is forward as a mandatory update and this triggers the ccmsetup.log

If you are using the logon script or group policy you need to make sure that the group policy is applied successfully to that system and after that you need to check the usual ccmsetup.log and client.msi.log

For manual installation you can check the same log and see the process ccmsetup.log and client.msi.log

Few Related links which will be of help.

Data Flows for Configuration Manager Client Deployment : http://technet.microsoft.com/en-us/library/bb680591.aspx

Troubleshooting Configuration Manager Client Deployment: http://technet.microsoft.com/en-us/library/bb693607.aspx

Planning for Configuration Manager Client Deployment : http://technet.microsoft.com/en-us/library/bb693966.aspx

Configuring Configuration Manager Client Deployment : http://technet.microsoft.com/en-us/library/bb680326.aspx

Tasks for Configuration Manager Client Deployment : http://technet.microsoft.com/en-us/library/bb680606.aspx

Technical Reference for Configuration Manager Client Deployment : http://technet.microsoft.com/en-us/library/bb694109.aspx

Client Reporting

Sometimes the most challenging part of the Configuration Manager 2007/SMS 2003 deployment phase can be ensuring that the client successfully reports to the site server. We occasionally see these issues here in support, typically either as cases for clients not reporting after the client installation, or maybe where it’s noticed that the client count is decreasing from the collection.

When we look at the SMS/SCCM console collection, there is an entry for the client status that indicates either Yes or No. Assuming everything is installed and configured properly, a client installed on a system should automatically report as Yes, but sometimes that does not turn out to be the case. The reason could be that the client has not yet reported to the SCCM\SMS server, or it was reporting previously but has now stopped. Managing the client in the collection is a continuous task and for a healthy environment the client should be continuously reporting to the SMS\SCCM server.

Troubleshooting issues where clients are not reporting

You can have a look at this blog for more details

http://blogs.technet.com/configurationmgr/archive/2009/08/10/troubleshooting-issues-where-clients-are-not-reporting.aspx

Troubleshooting issues where clients are not reporting:

Sometimes the most challenging part of the Configuration Manager 2007/SMS 2003 deployment phase can be ensuring that the client successfully reports to the site server. We occasionally see these issues here in support, typically either as cases for clients not reporting after the client installation, or maybe where it’s noticed that the client count is decreasing from the collection.

When we look at the SMS/SCCM console collection, there is an entry for the client status that indicates either Yes or No. Assuming everything is installed and configured properly, a client installed on a system should automatically report as Yes, but sometimes that does not turn out to be the case. The reason could be that the client has not yet reported to the SCCM\SMS server, or it was reporting previously but has now stopped. Managing the client in the collection is a continuous task and for a healthy environment the client should be continuously reporting to the SMS\SCCM server.

There are various reasons why a client may not be able to report to even if the SMS\SCCM agent is installed on a machine. A few of these reasons are discussed below:

The first thing to check is whether the client is on the network, and if it’s not on the network, does the system even exist? It’s possible that represents a stale record from AD.

Systems NOT on the network: If the system is not actually on the network, check if it is shutdown, and if so if it’s been shut down for long time. If yes then first restart the system and then initiate the discovery cycle from the control panel agent properties action TAB.

Stale Entries: When you use AD discovery, the DDRs are created for the computers that reside in the AD container that we have requested to be queried by the discovery process. If that container has the stale records for the resources, then client records may be created for systems that don’t actually exist, thus they will never report.

There is a Maintenance task that will clear the inactive records but if the discovery process runs again and the AD container still has these entries then they will simply show up again.

Resolution: For the stale records you need to make sure that the AD container is cleared of these stale records and scavenging is done for the computers container in AD regularly. Once this is done you can either make use of the maintenance task or you can create a collection for the NON SMS CLIENTS and then do a delete special to the collection so that the entries will be removed permanently from the SMS\SCCM database. Then a discovery can be run which will bring back only the active systems in the collection.

Once the agent is available on the network and the client is installed, the client goes through the following actions as part of the reporting process:

1. Client location services identify the site code and the MP it is supposed to connect to. 2. The client connects to the Management Point and downloads the policies. 3. Once the policies are downloaded it sends the heartbeat record to the server. 4. Once the server receives this heartbeat record these are converted in to DDR and processed.

This will set the client flag to 1 which will make the client status display as Yes in the console. 5. On a regular basis the agent will send the heartbeat and if no heart beat or inventory shows up

for a length of time then the client flag will be marked as 0 by the client flag maintenance task, setting the client status to No.

So only if this process is completed and it continues to happen will the client remain reporting to the server. This is why I said earlier that client management is a continuous task. There can be a variety of reasons why this process might fail, and I’ve outlined a couple of them below:

The Boundaries of the Agent are not specified in the site server

http://technet.microsoft.com/en-us/configmgr/default.aspx

If the client is not assigned in the console or the client is unable to discover the site code, make sure that the AD site or the IP subnet is added in the boundary list. The server will only allow those clients within its boundary to download the polices, so if you have not specified the boundaries the client will not be authorized and the policies will not get downloaded. For boundary issues you can use this as a reference:

http://blogs.technet.com/kevinsul_blog/archive/2006/01/25/418088.aspx.

For the case of overlapping boundaries see http://blogs.technet.com/smsandmom/archive/2007/11/30/sms-2003-finding-overlapping-boundaries.aspx

In the client if you check the location services.log (log location: C:\Windows\System32\CCM\Logs), you can get the information of the site assigned to it as well as the MP it is reporting to. If it is not able to report properly, you need to make sure that the agent can communicate over the network to the site server successfully.

Unable to get the site code

If the client is not able to get the site code, you need to check first the boundaries as above, and also verify that the site information is published in the AD. You can check the last part of the sitecomp.log after you start the site component manager which will say that the components like the MP, SLP etc successfully published or updated. If you are unable to see that and you get access denied errors, make sure that the computer account has read\write permission to the system container in AD. Make sure the permission is flowing to the objects within and the objects below. If you are not publishing the information in AD then you need to make sure that the SLP is configured and working.

For more information you can check Post-installation phase in the link:

http://support.microsoft.com/kb/925282

The client itself is not installed in the Agent

You can take a look at this article http://support.microsoft.com/kb/925282 which will give you a detailed explanation of how you can make sure that the client is installed and reporting successfully.

There is a name resolution issue in the Client.

Make sure that the client is able to communicate to the SMS\SCCM server using the FQDN as well as the NetBIOS name. Use Nslookup or ping to check the name resolution. If you can’t ping the server using the FQDN then you will have problems.

The client is behind a firewall

If clients are behind a firewall, it may be restricting it from contacting the SMS site server. Check if the necessary ports are opened. You can check http://support.microsoft.com/kb/826852 to understand the port requirements.

There are systems in the collection that have multiple GUIDs.

If you suspect your clients may have multiple GUIDs refer to https://technet.microsoft.com/en-us/library/cc917513.aspx for information on how to resolve the issue.

MP not working as a result of which the policies are not getting downloaded

You first need to check to see whether the MP is working. For that you will need to check the mpcontol .log (Log location: \SMS\logs in SMS and \program files\Microsoft Configuration Manager\logs in SCCM).

If it is showing a 200 OK status code then that means the MP is working. For information on troubleshooting the MP you can use the Troubleshooting management point issues section at http://support.microsoft.com/kb/925282 or http://technet.microsoft.com/en-us/library/bb932118.aspx.

If the MP is working fine and the client is unable to contact and download polices, you will have an error on download in the policyagent.log file on the agent (Log location: C:\Windows\System32\CCM\Logs). Before checking this though, check if the locationservices.log has the correct MP information. If it doesn’t then check the resolution mentioned in the topic under Site Code and Boundaries above. If it does have the correct MP information, make sure that the BITS service is started on the client. You can try the following URLs to verify that this is working:

/sms_mp/.sms_aut?mplist">/sms_mp/.sms_aut?mplist">/sms_mp/.sms_aut?mplist">http://<servername>/sms_mp/.sms_aut?mplist

and

/sms_mp/.sms_aut?mpcert">/sms_mp/.sms_aut?mpcert">/sms_mp/.sms_aut?mpcert">http://<servername>/sms_mp/.sms_aut?mpcert

Client is unable to download policy

You may also have issues downloading policies if the client agent has WMI corruption. If you suspect this to be the cause of your issue, if it is a XP client then follow these steps:

1. Uninstall the SMS/SCCM client agent. Use the ccmclean /all (Available in the SMS tool kit) command for SMS and cmsetup /uninstall for SCCM.

2. Troubleshoot or rebuild WMI. For troubleshooting WMI you can reference:

http://support.microsoft.com/kb/875605 http://technet.microsoft.com/en-us/library/cc180763.aspx http://blogs.msdn.com/wmi/archive/2009/03/13/let-s-troubleshoot-wmi-part-1-remoting-and-security.aspx

3. Restart the system and install the agent.

Note: If the SMS\SCCM agent is installed on an exchange server or the DC, or any other application server, please contact Microsoft support to fix the WMI issue as rebuilding can create additional issues with other applications if not done correctly.

Server unable to process DDR

Once you find that the client is able to send the heartbeat data to the server, you next need to check on the server to see if these are getting processed successfully. Here are a few links relating to DDR processing errors:

http://support.microsoft.com/kb/886124 http://support.microsoft.com/kb/891584 http://support.microsoft.com/kb/960634

Clients going to NO after it had reported

The first reason for this is that the heartbeat discovery is enabled and that the DDRs are not reaching the server. The second is that Clear Install Flag is running. The following link will give you more information on this task:


Troubleshooting SCCM ..Part II (Hardware Inventory):

Hardware Inventory

Hardware inventory is a feature in itself and functions independent to the other features of SCCM, but it closely depends on a successful deployment.

SCCM Setup has to complete successfully. The Hardware inventory feature on the server side solely depends on setup and successful SQL install. All the tables from the default sms_def.mof should get correctly created in SQL with the right credentials.

Similarly, for the hardware inventory agent to function as per requirements on the Advanced client, the client setup should have completed successfully and the client should have access to the MP for the Advanced client. On the Advanced client the Inventory agent’s functionality is dependent on the running of the SMS Agent Host service (ccmexec).

The entire hardware inventory feature is dependent on the sms_def.mof file present in the clifiles.src\hinv folder on the SiteServer. If that file is deleted or made corrupt, hardware inventory feature on the clients would not report any valid hardware inventory data.

Client Side

For any inventory to start it has to be scheduled. This is downloaded during the initial policy download.

èInventoryAgent.Log

Inventory: Message type is InventoryActionInventory: Temp directory = C:\SMS_CCM\Inventory\Temp\Inventory: Clearing old collected files.Inventory: Opening store for action {00000000-0000-0000-0000-000000000001}

We can also manually trigger via the Configuration Manger Control Panel Applet or can be triggered using sendsched.vbs.

The Client then checks the policy and determines if it needs to initiate a Full, Delta or Re-Sync. First scan will always be a Full Scan all subsequent scans are Deltas. Re-Sync request is sent by the server if no existing client record exists for the delta sent by a client.

If there is issue in receiving the policy you can check the communication between the client and the MP. Use the steps mentioned in the client reporting troubleshooting.

èInventoryagent.log

Inventory: Delta report without a previous Full report; will do a Full report.Inventory: Action=Hardware ReportType=Full

Once the scan type (Full, Re-Sync, or Delta) has been determined, the Hardware Inventory Client Agent must now determine precisely what to inventory:

Based on the rules and scan type, configuration manager scans WMI and the registry. Results of scan are stored in WMI. Once compiled into WMI, the client generates an XML file. Advanced Client converts XML file to message file and are send to MP. These are as shown in the verbose Inventoryagent.log

Invetoryagent.log

Inventory: Message type is InventoryAction InventoryAgent 1/31/2010 9:39:10 AM 384 (0x0180)Inventory: Temp directory = C:\WINDOWS\system32\CCM\Inventory\Temp\ InventoryAgent 1/31/2010 9:39:10 AM 384 (0x0180)Inventory: Clearing old collected files. InventoryAgent 1/31/2010 9:39:10 AM 384 (0x0180)Inventory: Opening store for action {00000000-0000-0000-0000-000000000001} ...InventoryAgent 1/31/2010 9:39:10 AM 384 (0x0180)Inventory: Delta report without a previous Full report; will do a Full report. InventoryAgent 1/31/2010 9:39:10 AM 384 (0x0180)Inventory: Action=Hardware ReportType=Full InventoryAgent 1/31/2010 9:39:10 AM 384 (0x0180)Inventory: Initialization completed in 0.020 seconds InventoryAgent 1/31/2010 9:39:10 AM 384 (0x0180)Collection: Namespace = \\.\root\ccm\invagt; Query = SELECT __CLASS, __PATH, __RELPATH, Name, SMSID, Domain, SystemRole, SystemType, LocalDateTime FROM CCM_System; Timeout = 600 secs. InventoryAgent 1/31/2010 9:39:10 AM 384 (0x0180)Inventory: Message [Type=InventoryAction, ActionID={00000000-0000-0000-0000-000000000003}, Report=Full] already in queue. Message ignored.

InventoryAgent 1/31/2010 9:39:10 AM 2452 (0x0994)…………….………………………………… Collection: Class "Win32_TSLicenseKeyPack" does not exist out. InventoryAgent 1/31/2010 9:40:08 AM 384 (0x0180)Collection: Namespace = \\.\root\cimv2; Query = SELECT __CLASS, __PATH, __RELPATH, Availability, Description, DeviceID, Manufacturer, Name, Status FROM Win32_IDEController; Timeout = 600 secs. InventoryAgent 1/31/2010 9:40:08 AM 384 (0x0180)Collection: 34/51 inventory data items successfully inventoried. InventoryAgent 1/31/2010 9:40:08 AM 384 (0x0180)Inventory: Collection Task completed in 57.953 seconds InventoryAgent 1/31/2010 9:40:08 AM 384 (0x0180)Inventory: 17 Collection Task(s) failed. InventoryAgent 1/31/2010 9:40:08 AM 384 (0x0180)Inventory: Temp report = C:\WINDOWS\system32\CCM\Inventory\Temp\96dbb66b-b57d-4812-95a6-cf21d7c7c44b.xml InventoryAgent

1/31/2010 9:40:08 AM 384 (0x0180)Inventory: Starting reporting task. InventoryAgent 1/31/2010 9:40:08 AM 384 (0x0180)Reporting: 330 report entries created. InventoryAgent 1/31/2010 9:40:08 AM 384 (0x0180)Inventory: Reporting Task completed in 0.411 seconds InventoryAgent 1/31/2010 9:40:08 AM 384 (0x0180)Inventory: Successfully sent report. Destination:mp:MP_HinvEndpoint, ID: {9DAA9999-4535-4E5C-A6CB-CAD2D11BA960}, Timeout: 80640 minutes MsgMode: Signed, Not Encrypted InventoryAgent 1/31/2010 9:40:09 AM 384 (0x0180)Inventory: Cycle completed in 62.961 seconds InventoryAgent 1/31/2010 9:40:13 AM 384 (0x0180)Inventory: Action completed. InventoryAgent 1/31/2010 9:40:13 AM 384 (0x0180)

If inventory fails, to correct it you can check reinstalling the client and also check for any WMI issues. Follow the steps in WMI troubleshooting in the client reporting part for any WMI issues

This is the end of client side troubleshooting. Now once this is over you need to check the rest of the process in the server side.

Server Side

In the server the CCMExec on the MP processes the message and generates the XML file. File is stored in <ServerDir>2[1] \MP\Outboxes\Hinv.box

2[1] SERVERDIR :\Program Files\Microsoft Configuration Manager\ or <Drive>\SMS\

You can view this information from

MP_Hinv.Log

Hinv Retry: ******************* Start of Task ********************* MP_HinvEndpoint 4/21/2010 10:39:15 AM 4360 (0x1108)Hinv Sax: loading C:\Program Files\Microsoft Configuration Manager\inboxes\auth\dataldr.box\HinvAttachmentY3ZGIYW8.xml MP_HinvEndpoint

4/21/2010 10:39:15 AM 4360 (0x1108)Delta report from client SQL, action description = Hardware MP_HinvEndpoint 4/21/2010 10:39:15 AM 4360 (0x1108)Hinv Task: Translate report attachment to file "C:\Program Files\Microsoft Configuration Manager\inboxes\auth\dataldr.box\HQG4Q6EI.MIF" returned 0

MP_HinvEndpoint 4/21/2010 10:39:15 AM 4360 (0x1108)Hinv Retry: ******************* End of Task ********************* MP_HinvEndpoint 4/21/2010 10:39:15 AM 4360 (0x1108)

XML file is then parsed and used to create a .MIF file. This process can be monitored in the MP_Hinv.log

.MIF file is stored in the <ServerDIR>3[2]\MP\Outboxes\Hinv.box

MP_Hinv.log

Hinv Retry: ******************* Start of Task ********************* MP_HinvEndpoint 1/31/2010 9:32:23 AM 2580 (0x0A14)Hinv Sax: loading C:\Program Files\Microsoft Configuration Manager\inboxes\auth\dataldr.box\HinvAttachmentXM1YR1Q7.xml MP_HinvEndpoint

1/31/2010 9:32:23 AM 2580 (0x0A14)Full report from client DC, action description = Hardware MP_HinvEndpoint 1/31/2010 9:32:23 AM 2580 (0x0A14)Hinv Task: Translate report attachment to file "C:\Program Files\Microsoft Configuration Manager\inboxes\auth\dataldr.box\H8TADQ8W.MIF" returned 0 MP_HinvEndpoint 1/31/2010 9:32:23 AM 2580 (0x0A14)Hinv Retry: ******************* End of Task ********************* MP_HinvEndpoint 1/31/2010 9:32:23 AM 2580 (0x0A14)

Management Point File Dispatch Manager copies the file from SMS\MP\Outboxes\Hinv.box to SMS\Inboxes\Dataldr.box . This process can be monitored in the MPFDM.log

MIF file is parsed and determines type of data to be inserted into the database. View dataldr.log to monitor progress, sql tracing can be enabled for detailed output and to further troubleshoot if MIF data is not processed and inserted to the database properly.

If the file is not received at this point need to check the communication between the server and the agent.

Dataldr.log

>> Add 1 files to process directory ... SMS_INVENTORY_DATA_LOADER 4/21/2010 2:44:25 PM 804 (0x0324)Moving MIF file C:\Program Files\Microsoft Configuration Manager\inboxes\auth\dataldr.box\HIZAHGPO.MIF to C:\Program Files\Microsoft Configuration Manager\inboxes\auth\dataldr.box\process\HIZAHGPO.MIF SMS_INVENTORY_DATA_LOADER 4/21/2010 2:44:25 PM 804 (0x0324)Started the machine MIF processing thread, thread ID = AF4 SMS_INVENTORY_DATA_LOADER 4/21/2010 2:44:25 PM 804 (0x0324)Worker thread 2612 starting execution. SMS_INVENTORY_DATA_LOADER 4/21/2010 2:44:25 PM 2612 (0x0A34)Done with job queueing. SMS_INVENTORY_DATA_LOADER 4/21/2010 2:44:26 PM 2804 (0x0AF4)Blocking until completion. SMS_INVENTORY_DATA_LOADER 4/21/2010 2:44:26 PM 2804 (0x0AF4)Thread: 0 is using GUID SMS_INVENTORY_DATA_LOADER 4/21/2010 2:44:27 PM 2612 (0x0A34)

3[2] SERVERDIR :\Program Files\Microsoft Configuration Manager\ or <Drive>\SMS\

Thread: 2612 will use GUID GUID:76B6D180-F0B6-4689-B294-6CCE9033D7EB SMS_INVENTORY_DATA_LOADER 4/21/2010 2:44:27 PM 2612 (0x0A34)Processing Inventory for Machine: SQL Version 1.5 Generated: 04/21/2010 14:44:19 SMS_INVENTORY_DATA_LOADER 4/21/2010 2:44:27 PM

2612 (0x0A34)Begin transaction: Machine=SQL(GUID:76B6D180-F0B6-4689-B294-6CCE9033D7EB) SMS_INVENTORY_DATA_LOADER 4/21/2010 2:44:28 PM

2612 (0x0A34)Commit transaction: Machine=SQL(GUID:76B6D180-F0B6-4689-B294-6CCE9033D7EB) SMS_INVENTORY_DATA_LOADER 4/21/2010 2:44:30 PM

2612 (0x0A34)Done: Machine=SQL(GUID:76B6D180-F0B6-4689-B294-6CCE9033D7EB) code=0 (16 stored procs in XHIZAHGPO.MIF) SMS_INVENTORY_DATA_LOADER

4/21/2010 2:44:30 PM 2612 (0x0A34)Done blocking until completion. SMS_INVENTORY_DATA_LOADER 4/21/2010 2:44:30 PM 2804 (0x0AF4)No more machine MIFs to be processed, terminating thread SMS_INVENTORY_DATA_LOADER 4/21/2010 2:44:30 PM 2804 (0x0AF4)Shutting down Machine Writer. SMS_INVENTORY_DATA_LOADER 4/21/2010 2:44:30 PM 2804 (0x0AF4)Worker thread 2612 halting execution. SMS_INVENTORY_DATA_LOADER 4/21/2010 2:44:31 PM 2612 (0x0A34)Finished processing 1 MIFs SMS_INVENTORY_DATA_LOADER 4/21/2010 2:44:35 PM 2804 (0x0AF4)

Once this is completed we should be able to see the data in the resource explorer. If there is some failure at this point we can enable SQL logging and check the insertion of data. Also if you have issue with the component SMS_INVENTORY_DATA_LOADER then a site reset can also help.

Troubleshooting SCCM Part III ...Software Updates:

Software UpdatesProviding updates to software and maintaining managed resources is a reality of networked, distributed computing. An effective software update management process is necessary to maintain operational efficiency, overcome security issues, and maintain the stability of the network infrastructure. However, because of the changing nature of technology and the continual appearance of new security threats, the task of effective software update management can be challenging.

The Microsoft System Center Configuration Manager 2007 software updates feature provides a set of tools and resources that can help manage the complex task of tracking and applying software updates to client computers in the enterprise. Click any link in the following section for overview information about software updates.For more details on how to do software updates using configuration manager please check this link http://technet.microsoft.com/en-us/library/bb680701.aspx Troubleshooting Server side The component which takes care of software update is software update point (SUP). So first we need to check if the software update point is installed correctly. If installed correctly you will have the entries in the log SUPSetup.log as shown below SUPSetup.log===========<04-27-2010 23:51:04> ====================================================================<04-27-2010 23:51:04> SMSWSUS Setup Started....<04-27-2010 23:51:04> Parameters: C:\PROGRA~1\MICROS~1\bin\i386\ROLESE~1.EXE /install /siteserver:SCCM SMSWSUS<04-27-2010 23:51:04> Installing Pre Reqs for SMSWSUS<04-27-2010 23:51:04> ======== Installing Pre Reqs for Role SMSWSUS ========<04-27-2010 23:51:04> Found 0 Pre Reqs for Role SMSWSUS <04-27-2010 23:51:04> ======== Completed Installion of Pre Reqs for Role SMSWSUS ========<04-27-2010 23:51:04> Installing the SMSWSUS<04-27-2010 23:51:04> Correct and supported WSUS Server version is installed.<04-27-2010 23:51:04> Invoking process "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe" "C:\Program Files\Microsoft Configuration Manager\bin\i386\wsusmsp.dll"<04-27-2010 23:51:30> Registered DLL C:\Program Files\Microsoft Configuration Manager\bin\i386\wsusmsp.dll<04-27-2010 23:51:30> Installation was successful.

Once installed you need to make sure that it is configured the logs which can be of help are WCM.log and WSUSctrl.log. If you find errors then make sure that the WSUS is working well. For the same you can check the following link http://technet.microsoft.com/en-us/library/dd939799(WS.10).aspx The logs if configured correctly should look like this.

WSUSctrl.log=============SMS_EXECUTIVE started SMS_WSUS_CONTROL_MANAGER as thread ID 3432 (0xD68). SMS_WSUS_CONTROL_MANAGER 4/27/2010 11:51:33 PM 3216 (0x0C90)This is a WSUS Role as WSUS registry key exists. SMS_WSUS_CONTROL_MANAGER 4/27/2010 11:51:33 PM 3432 (0x0D68)Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONTROL_MANAGER 4/27/2010 11:51:33 PM 3432 (0x0D68)Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONTROL_MANAGER 4/27/2010 11:51:33 PM 3432 (0x0D68)Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=2.0.0.0, Major Version = 0x20000, Minor Version = 0x0

SMS_WSUS_CONTROL_MANAGER 4/27/2010 11:51:33 PM 3432 (0x0D68)The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226) SMS_WSUS_CONTROL_MANAGER

4/27/2010 11:51:33 PM 3432 (0x0D68)

Successfully connected to local WSUS server SMS_WSUS_CONTROL_MANAGER 4/27/2010 11:51:33 PM 3432 (0x0D68)Local WSUS Server Proxy settings are correctly configured as Proxy Name and Proxy Port 80 SMS_WSUS_CONTROL_MANAGER 4/27/2010 11:51:35 PM 3432 (0x0D68)Waiting for changes for 0 minutes SMS_WSUS_CONTROL_MANAGER 4/27/2010 11:51:35 PM 3432 (0x0D68)Timed Out... SMS_WSUS_CONTROL_MANAGER 4/27/2010 11:51:35 PM 3432 (0x0D68)…………………..…………………..…………………..

SMS_WSUS_CONTROL_MANAGER 4/27/2010 11:51:35 PM 3432 (0x0D68)There are no unhealthy WSUS Server components on WSUS Server SCCM SMS_WSUS_CONTROL_MANAGER 4/27/2010 11:51:35 PM

3432 (0x0D68)Successfully checked database connection on WSUS server SCCM SMS_WSUS_CONTROL_MANAGER 4/27/2010 11:51:38 PM 3432 (0x0D68)

WCM.log=========This SCCM system is the Top Site where WSUS Server is configured to Sync from Microsoft Update (WU/MU) OR do not Sync.

SMS_WSUS_CONFIGURATION_MANAGER 4/27/2010 11:50:36 PM 5992 (0x1768)Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONFIGURATION_MANAGER 4/27/2010 11:50:37 PM 5992 (0x1768)Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONFIGURATION_MANAGER 4/27/2010 11:50:37 PM 5992 (0x1768)Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=2.0.0.0, Major Version = 0x20000, Minor Version = 0x0

SMS_WSUS_CONFIGURATION_MANAGER 4/27/2010 11:50:37 PM 5992 (0x1768)The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226)

SMS_WSUS_CONFIGURATION_MANAGER 4/27/2010 11:50:37 PM 5992 (0x1768)Successfully connected to server: SCCM.MYLAB.IN, port: 80, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 4/27/2010 11:51:23 PM 5992 (0x1768)Verify Upstream Server settings on the Active WSUS ServerSMS_WSUS_CONFIGURATION_MANAGER 4/27/2010 11:51:23 PM 5992 (0x1768)Successfully configured WSUS Server settings and Upstream Server to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 4/27/2010 11:51:34 PM 5992 (0x1768)Successfully connected to server: SCCM.MYLAB.IN, port: 80, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 4/27/2010 11:51:39 PM 5992 (0x1768)……………………….……………………….STATMSG: ID=6617 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=SCCM SITE=LAB PID=3040 TID=5992 GMTDATE=Tue Apr 27 18:23:49.259 2010 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0

SMS_WSUS_CONFIGURATION_MANAGER 4/27/2010 11:53:49 PM 5992 (0x1768)completed unpublishing previous clients SMS_WSUS_CONFIGURATION_MANAGER 4/27/2010 11:53:49 PM 5992 (0x1768)completed checking for client deployment SMS_WSUS_CONFIGURATION_MANAGER 4/27/2010 11:53:49 PM 5992 (0x1768)Successfully inserted the WSUS Enterprise Update Source object {A36F27F1-F657-437E-9EBF-8531FE189A6B}

SMS_WSUS_CONFIGURATION_MANAGER 4/27/2010 11:54:03 PM 5992 (0x1768)

Once you confirm that the WSUS configuration is over then you need to make sure that the SUP is able to synchronize with the Microsoft update catalogue site and the same can be checked in this log. WSUSsyncmgr.log===============Performing sync on local request SMS_WSUS_SYNC_MANAGER 4/27/2010 11:59:54 PM 6112 (0x17E0)STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SCCM SITE=LAB PID=3040 TID=6112 GMTDATE=Tue Apr 27 18:29:54.530 2010 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0

SMS_WSUS_SYNC_MANAGER 4/27/2010 11:59:54 PM 6112 (0x17E0)

STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SCCM SITE=LAB PID=3040 TID=6112 GMTDATE=Tue Apr 27 18:30:18.547 2010 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0

SMS_WSUS_SYNC_MANAGER 4/28/2010 12:00:18 AM 6112 (0x17E0)Synchronizing WSUS server SCCM SMS_WSUS_SYNC_MANAGER 4/28/2010 12:00:18 AM 6112 (0x17E0)Synchronizing WSUS server sccm.mylab.in ... SMS_WSUS_SYNC_MANAGER 4/28/2010 12:02:16 AM 5220 (0x1464)sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER 4/28/2010 12:02:16 AM 5220 (0x1464)sync: WSUS synchronizing categories SMS_WSUS_SYNC_MANAGER 4/28/2010 12:02:44 AM 5220 (0x1464) ……………..,…………………… Synchronizing update e6d5e961-e5c4-4816-b414-648feba450b7 SMS_WSUS_SYNC_MANAGER 28/04/2010 5:53:10 PM 4380 (0x111C)Synchronizing update 35a0b603-61ce-4f1e-b2dd-3cc36cdf8b31 SMS_WSUS_SYNC_MANAGER 28/04/2010 5:53:11 PM 4380 (0x111C)Synchronizing update 333bf753-7abb-4fce-a15f-a1862ecf838b SMS_WSUS_SYNC_MANAGER 28/04/2010 5:53:11 PM 4380 (0x111C)Synchronizing update 136df562-d188-4e79-8879-8d8082c97614: Definition Update for Windows Defender - KB915597 (Definition 1.81.438.0)

SMS_WSUS_SYNC_MANAGER 28/04/2010 5:53:12 PM 4380 (0x111C)Done synchronizing SMS with WSUS Server sccmcen.scs.in SMS_WSUS_SYNC_MANAGER 28/04/2010 5:53:13 PM 4380 (0x111C)STATMSG: ID=6702 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SCCMCEN SITE=CEN PID=1880 TID=3256 GMTDATE=Wed Apr 28 12:23:13.745 2010 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0

SMS_WSUS_SYNC_MANAGER 28/04/2010 5:53:13 PM 3256 (0x0CB8)Updated 3072 items in SMS database, new update source content version is 2 SMS_WSUS_SYNC_MANAGER 28/04/2010 5:53:13 PM

3256 (0x0CB8)

Once the synchronization is successfully done, updates will be available in the update repository. You can then go ahead and create the deployment template and schedule for installation. On more details on how to please check the following link. http://blogs.technet.com/configurationmgr/archive/2009/08/17/guide-to-software-updates-deployment-in-configuration-manager-2007.aspx Once done if you check the status messages for your created update packages you will find the following status messages. Severity Type Site code Date / TimeSystem Component Message IDDescriptionInformation Milestone CEN 28/04/2010 4:21:28 PM SCCMCEN SMS_DISTRIBUTION_MANAGER 2301 SMS Distribution Manager successfully processed package "TEST" (package ID = CEN00003).Information Milestone CEN 28/04/2010 4:21:27 PM SCCMCEN SMS_DISTRIBUTION_MANAGER 2300 SMS Distribution Manager is beginning to process package "TEST" (package ID = CEN00003).Information Milestone CEN 28/04/2010 4:21:21 PM SCCMCEN SMS_DISTRIBUTION_MANAGER 2330 SMS Distribution Manager successfully distributed package "CEN00003" to distribution point "["Display=\\SCCMCEN\"]MSWNET:["SMS_SITE=CEN"]\\SCCMCEN\".Info Distribution Manager is beginning to process package "TEST" (package ID = CEN00003).Information Audit CEN 28/04/2010 4:20:59 PM SCCMCEN Microsoft.ConfigurationManagement.dll 30068

User "SCS\Administrator" updated a package named " TEST " (CEN00003) to the site distribution points.Information Milestone CEN 28/04/2010 4:12:14 PM SCCMCEN SMS_DISTRIBUTION_MANAGER 2300 SMS Distribution Manager is beginning to process package "TEST" (package ID = CEN00003).Information Milestone CEN 28/04/2010 4:12:08 PM SCCMCEN SMS_DISTRIBUTION_MANAGER 2301 SMS Distribution Manager successfully processed package "TEST" (package ID = CEN00003).Information Milestone CEN 28/04/2010 4:12:06 PM SCCMCEN SMS_DISTRIBUTION_MANAGER 2330 SMS Distribution Manager successfully distributed package "CEN00003" to distribution point Distribution Manager is beginning to process package "TEST" (package ID = CEN00003).Information Audit CEN 28/04/2010 4:11:21 PM SCCMCEN Microsoft.ConfigurationManagement.dll 30125

User "SCS\Administrator" added new distribution points to a package named " TEST " (CEN00003).

Information Audit CEN 28/04/2010 4:11:20 PM SCCMCEN Microsoft.ConfigurationManagement.dll 30000User "SCS\Administrator" created a package named " TEST " (CEN00003).

Once these steps are done then the rest of the things happens in the client. Client Side In the client side first thing we need to check is the locationservices.log to make sure that the correct SUP point is detected by the client, else make sure that the client is correctly reporting to the SCCM server and that the software update is enabled. Make sure that the server name and the port is specified correctly. Locationservices.log================Calling back with the following WSUS locations LocationServices 4/29/2010 10:39:40 AM 2844 (0x0B1C)WSUS Path='https://SCCMCEN.SCS.IN:443', Server='SCCMCEN', Version='2' LocationServices 4/29/2010 10:39:40 AM 2844 (0x0B1C)Calling back with locations for WSUS request {10066528-1C1B-4A0C-958B-F29ACBEDBBDF} LocationServices 4/29/2010 10:41:31 AM 2844 (0x0B1C)Calling back with the following distribution points LocationServices 4/29/2010 11:27:23 AM 2552 (0x09F8)Distribution Point='\\SCCMCEN.SCS.IN\SMSPKGC$\CEN00003\4ea80bd5-c8ac-4f98-be8a-1c18f24a34e4', Locality='LOCAL', DPType='SERVER', Version='6487', Capabilities='<Capabilities SchemaVersion="1.0"><Property Name="SSL" Version="1"/></Capabilities>', Signature='' LocationServices 4/29/2010 11:27:23 AM 2552 (0x09F8)

Now once the policy agent triggers the scan cycle the windows update agent in the client will contact the WSUS server which in our case is also the SUP point. Once the scan is successfully completed this information is send as state message to the SCCM server. This can be checked in windowsupadte.log or you can check WUAhandler.log under SCCM client log. WUAHandler.log==============Async searching of updates using WUAgent started. WUAHandler 4/29/2010 10:42:20 AM 3488 (0x0DA0)Async searching completed. WUAHandler 4/29/2010 11:24:21 AM 1496 (0x05D8)Successfully completed scan. WUAHandler 4/29/2010 11:24:25 AM 2752 (0x0AC0)Its a WSUS Update Source type ({D4F72DDB-F6C4-4B05-835F-A8C23098857A}), adding it. WUAHandler 4/29/2010 11:25:24 AM 2752 (0x0AC0)Existing WUA Managed server was already set (https://SCCMCEN.SCS.IN:443), skipping Group Policy registration. WUAHandler 4/29/2010 11:25:25 AM 2752 (0x0AC0)Added Update Source ({D4F72DDB-F6C4-4B05-835F-A8C23098857A}) of content type: 2 WUAHandler 4/29/2010 11:25:25 AM 2752 (0x0AC0)Async searching of updates using WUAgent started. WUAHandler 4/29/2010 11:25:25 AM 2752 (0x0AC0)Async searching completed. WUAHandler 4/29/2010 11:26:28 AM 2396 (0x095C)Successfully completed scan. WUAHandler 4/29/2010 11:26:32 AM 3756 (0x0EAC)

Completion of scan is important and if the same is not successfully done you can take the help of the following link to troubleshoot the issues. This link is of WSUS troubleshooting but you can get hints to troubleshoot the error code. http://blogs.technet.com/sus/archive/2009/11/17/tips-for-troubleshooting-wsus-agents-that-are-not-reporting-to-the-wsus-server.aspx Now when the policy agent triggers the software update deployment cycle the scan result is compared with the catalogue and then it downloads only the required updates and install on schedule. You can check the updatestore.log, updatedeploymemt.log for more details. You can also check windowsupdate.log for more details.

Updatedeployment.log================== Service startup system task UpdatesDeploymentAgent 4/28/2010 7:49:39 PM 3468 (0x0D8C)Software Updates client configuration policy has not been received. UpdatesDeploymentAgent 4/28/2010 7:49:39 PM 3468 (0x0D8C)Software updates functionality will not be enabled until the configuration policy has been received. If this issue persists please check client/server policy communication. UpdatesDeploymentAgent 4/28/2010 7:49:39 PM 3468 (0x0D8C)Software Updates feature is disabled UpdatesDeploymentAgent 4/28/2010 7:49:39 PM 3468 (0x0D8C)Software Updates client configuration policy has not been received. UpdatesDeploymentAgent 4/28/2010 7:49:39 PM 3468 (0x0D8C)Software updates functionality will not be enabled until the configuration policy has been received. If this issue persists please check client/server policy communication. UpdatesDeploymentAgent 4/28/2010 7:49:39 PM 3468 (0x0D8C)………………….…………………Evaluation initiated for (1) assignments. UpdatesDeploymentAgent 4/29/2010 10:39:20 AM 336 (0x0150)Deadline received for assignment ({3B1C5820-953D-4EFB-BDB7-3ABEE4C9788D}) UpdatesDeploymentAgent 4/29/2010 10:39:20 AM

3344 (0x0D10)Enforcement trigger will be effective when the current action completes UpdatesDeploymentAgent 4/29/2010 10:39:20 AM

3344 (0x0D10)Message received: '<?xml version='1.0' ?><SoftwareUpdatesMessage MessageType='EvaluateAssignments'><UseCachedResults>True</UseCachedResults></SoftwareUpdatesMessage>' UpdatesDeploymentAgent

4/29/2010 10:39:30 AM 3940 (0x0F64)Evaluation initiated for (0) assignments. UpdatesDeploymentAgent 4/29/2010 11:01:55 AM 4064 (0x0FE0)……………………………….DetectJob completion received for assignment ({3B1C5820-953D-4EFB-BDB7-3ABEE4C9788D})UpdatesDeploymentAgent 4/29/2010 11:26:59 AM 3856 (0x0F10)……………………..Added update (Site_D4F72DDB-F6C4-4B05-835F-A8C23098857A/SUM_9fb3050e-26f2-4ccc-b9b0-b453ff58aaa9) to the targeted list

UpdatesDeploymentAgent 4/29/2010 11:26:59 AM 3856 (0x0F10)Added update (Site_D4F72DDB-F6C4-4B05-835F-A8C23098857A/SUM_de919dec-2021-474a-8a7f-d632c2068146) to the targeted list

UpdatesDeploymentAgent 4/29/2010 11:26:59 AM 3856 (0x0F10)Added update (Site_D4F72DDB-F6C4-4B05-835F-A8C23098857A/SUM_d2e84b36-f0fd-4434-825d-a753a338b0bd) to the targeted list

UpdatesDeploymentAgent 4/29/2010 11:26:59 AM 3856 (0x0F10)…………………..……………………Update (Site_D4F72DDB-F6C4-4B05-835F-A8C23098857A/SUM_de919dec-2021-474a-8a7f-d632c2068146) Progress: Status = ciStateDownloading, PercentComplete = 83, Result = 0x0 UpdatesDeploymentAgent 4/29/2010 11:27:36 AM 1068 (0x042C)Progress received for assignment ({3B1C5820-953D-4EFB-BDB7-3ABEE4C9788D}) UpdatesDeploymentAgent 4/29/2010 11:27:38 AM

12 (0x000C)DownloadJob completion received for assignment ({3B1C5820-953D-4EFB-BDB7-3ABEE4C9788D}) UpdatesDeploymentAgent 4/29/2010 11:27:38 AM 12 (0x000C)EnumerateUpdates for action (UpdateActionInstall) - Total visible updates = 3 UpdatesDeploymentAgent 4/29/2010 11:27:38 AM

2960 (0x0B90)Starting install for assignment ({3B1C5820-953D-4EFB-BDB7-3ABEE4C9788D}) UpdatesDeploymentAgent 4/29/2010 11:27:38 AM

12 (0x000C) ………………….Update (Site_D4F72DDB-F6C4-4B05-835F-A8C23098857A/SUM_de919dec-2021-474a-8a7f-d632c2068146) Progress: Status = ciStateInstalling, PercentComplete = 100, DownloadSize = 0, Result = 0x0 UpdatesDeploymentAgent 4/29/2010 11:31:26 AM 440 (0x01B8)Update (Site_D4F72DDB-F6C4-4B05-835F-A8C23098857A/SUM_de919dec-2021-474a-8a7f-d632c2068146) Progress: Status = ciStatePendingSoftReboot, PercentComplete = 0, DownloadSize = 0, Result = 0x0 UpdatesDeploymentAgent 4/29/2010 11:31:31 AM 3568 (0x0DF0)CTargetedUpdatesManager - Job completion received. UpdatesDeploymentAgent 4/29/2010 11:31:32 AM 496 (0x01F0)Job Id = {A807D023-9E41-4FE5-A528-6120C46C1134} UpdatesDeploymentAgent 4/29/2010 11:31:32 AM 496 (0x01F0)No pending install assignment UpdatesDeploymentAgent 4/29/2010 11:31:33 AM 440 (0x01B8)EnumerateUpdates for action (UpdateActionInstall) - Total visible updates = 3 UpdatesDeploymentAgent 4/29/2010 11:31:33 AM

2236 (0x08BC)No installations in pipeline, notify reboot. UpdatesDeploymentAgent 4/29/2010 11:31:33 AM 440 (0x01B8)Notify reboot with deadline = Thursday, Apr 29, 2010. - 11:31:33, Ignore reboot Window = False UpdatesDeploymentAgent 4/29/2010 11:31:33 AM 440 (0x01B8)

The execution manager will have the following entries Execmgr.log==========Mandatory execution requested for program Software Updates Program and advertisement {3D49D216-341B-4456-B52C-A0A480C06BEC} execmgr

4/29/2010 11:27:50 AM 2188 (0x088C)Creating mandatory request for advert {3D49D216-341B-4456-B52C-A0A480C06BEC}, program Software Updates Program, package {3D49D216-341B-4456-B52C-A0A480C06BEC} execmgr 4/29/2010 11:27:50 AM 2188 (0x088C)CExecutionRequest::Overriding Service Windows as per policy. execmgr 4/29/2010 11:27:50 AM 2188 (0x088C)Execution Manager timer has been fired. execmgr 4/29/2010 11:27:50 AM 3256 (0x0CB8)Executing program in Admin context execmgr 4/29/2010 11:27:50 AM 2188 (0x088C)Execution Request for package {3D49D216-341B-4456-B52C-A0A480C06BEC} program Software Updates Program state change from NotExist to NotifyExecution execmgr 4/29/2010 11:27:50 AM 2188 (0x088C)Executing program as an update. execmgr 4/29/2010 11:27:51 AM 2188 (0x088C)Executing Update Program execmgr 4/29/2010 11:27:51 AM 2188 (0x088C)Updates Installation started for the passed command line execmgr 4/29/2010 11:27:51 AM 2188 (0x088C)Looking for MIF file to get program status execmgr 4/29/2010 11:31:31 AM 440 (0x01B8)Script for Package:{3D49D216-341B-4456-B52C-A0A480C06BEC}, Program: Software Updates Program succeeded with exit code 0 execmgr

4/29/2010 11:31:31 AM 440 (0x01B8)Execution is complete for program Software Updates Program. The exit code is 0, the execution status is Success execmgr 4/29/2010 11:31:31 AM 440 (0x01B8)The user has logged off. execmgr 4/29/2010 11:38:13 AM 2788 (0x0AE4)

Once update is installed, then depending on the reboot setting the system will be rebooted. This information is tracked using RebootCoordinator.log==================Shutdown is already in progress RebootCoordinator 4/29/2010 11:38:10 AM 3792 (0x0ED0)Reboot initiated RebootCoordinator 4/29/2010 11:38:10 AM 3792 (0x0ED0)User logoff notification received RebootCoordinator 4/29/2010 11:38:13 AM 2788 (0x0AE4)Shutdown is already in progress RebootCoordinator 4/29/2010 11:38:17 AM 2788 (0x0AE4)Reboot initiated RebootCoordinator 4/29/2010 11:38:17 AM 2788 (0x0AE4)

For information on the other logs you can check the following link which will give you more information on the logs which you can use for troubleshooting. http://technet.microsoft.com/en-us/library/bb693878.aspx The other links which will be of help to you Configuring Software Updates : http://technet.microsoft.com/en-us/library/bb633119.aspx Tasks for Software Updates: http://technet.microsoft.com/en-us/library/bb693776.aspx Software Updates Security Best Practices and Privacy Information: http://technet.microsoft.com/en-us/library/bb633068.aspx Troubleshooting Software Updates : http://technet.microsoft.com/en-us/library/bb693492.aspx Technical Reference for Software Updates : http://technet.microsoft.com/en-us/library/bb693784.aspx

Troubleshooting SCCM Part IV............ Software Inventory:

Software inventory

The requirement of the software inventory to function is similar to that of the hardware inventory. The process is also almost similar.

Client Side

The scheduler will send a message to the inventory agent to start the software inventory process.

Scheduler.log:

Sending message for schedule 'Machine/{00000000-0000-0000-0000-000000000002}' (Target: 'direct:InventoryAgent', Name: '')Scheduler4/10/2005 9:39:06 AM3904 (0x0F40)

The agent will determine the type of inventory it has to process (Full, Delta, Resync).The Scan Properties are stored in WMI at the Root\CCM\Policy\Machine namespace.

If you don’t see this, the issue can be the client unable to download the policies or the server has not been configured for Software Inventory.

Once the Software Inventory Client Agent has determined its Scan type, it must now determine precisely what it needs to inventory. This is accomplished by again pulling configuration data from WMI. Software Inventory Rule information (what an administrator has configured SCCM to inventory) is stored within the same namespace of WMI (Root\CCM\Policy\Machine) Each rule is stored in an instance of this class.

The inventory agent will scan the machine according to the software inventory rules and will send an XML file to the software inventory endpoint.

Once the properties of the scan have been determined, and the Advanced Client knows what type of scan (Full, Delta or Resync) to perform, as well as what it is scanning for (as defined in the Software Inventory Rules), it is time for it to perform the actual scan.

Inventoryagent.log

Inventory: *********************** Start of message processing. *********************** InventoryAgent 4/22/2010 12:07:36 AM 2924 (0x0B6C)

Inventory: Message type is InventoryAction InventoryAgent 4/22/2010 12:07:36 AM 2924 (0x0B6C)

Inventory: Temp directory = C:\WINDOWS\system32\CCM\Inventory\Temp\ InventoryAgent 4/22/2010 12:07:36 AM 2924 (0x0B6C)

Inventory: Clearing old collected files. InventoryAgent 4/22/2010 12:07:36 AM 2924 (0x0B6C)

Inventory: Opening store for action {00000000-0000-0000-0000-000000000002} ...InventoryAgent 4/22/2010 12:07:37 AM 2924 (0x0B6C)

Inventory: Action=Software ReportType=Delta InventoryAgent 4/22/2010 12:07:56 AM 2924 (0x0B6C)

Inventory: Initialization completed in 19.849 seconds InventoryAgent 4/22/2010 12:07:56 AM 2924 (0x0B6C)

Collection: Input context, scan rate in milliseconds = 2 InventoryAgent 4/22/2010 12:09:57 AM 3972 (0x0F84)

Collection: Input context, skip file name = skpswi.dat InventoryAgent 4/22/2010 12:09:57 AM 3972 (0x0F84)

Collection: Namespace = \\.\root\ccm\invagt; Query = SELECT Name, Path, LastWriteDate, Size, CompanyName, ProductName, ProductVersion, ProductLanguage, FileVersion, FileDescription FROM FileSystemFile WHERE Name = '*.exe' AND Path = '*\\*' AND IsCompressed = FALSE AND IsEncrypted = FALSE; Timeout = 14400 secs. InventoryAgent 4/22/2010 12:09:57 AM 3972 (0x0F84)

……………………………

……………………………

…………………………..

Inventory: Starting reporting task. InventoryAgent 4/22/2010 12:16:19 AM 2384 (0x0950)

Reporting: 0 report entries created. InventoryAgent 4/22/2010 12:16:20 AM 2384 (0x0950)

Inventory: Reporting Task completed in 0.931 seconds InventoryAgent 4/22/2010 12:16:20 AM 2384 (0x0950)

Inventory: Successfully sent report. Destination:mp:MP_SinvEndpoint, ID: {EBC09961-66DD-4C98-9656-FA370C3259BC}, Timeout: 80640 minutes MsgMode: Signed, Not Encrypted InventoryAgent 4/22/2010 12:16:20 AM 2384 (0x0950)

Inventory: Cycle completed in 541.088 secondsInventoryAgent 4/22/2010 12:16:37 AM 2384 (0x0950)

Inventory: Action completed. InventoryAgent 4/22/2010 12:16:37 AM 2384 (0x0950)

Inventory: ************************ End of message processing. ************************ InventoryAgent 4/22/2010 12:16:37 AM 2384 (0x0950)

If there are some failures there then you can check to make sure that the consistency of the WMI and client of the system. Also we have information on

FileSystemFile.log

************* Start of File System Query. ************* FileSystemFile 4/22/2010 12:09:57 AM 2384 (0x0950)

Query = SELECT __class, __path, __relpath, name, path, lastwritedate, size, companyname, productname, productversion, productlanguage, fileversion, filedescription FROM FileSystemFile WHERE name = '*.exe' and path = '*\\*' and iscompressed = false and isencrypted = false; Timeout = 14400 secs; ScanInterval = 2 msecs; SkipFile = skpswi.dat FileSystemFile 4/22/2010 12:09:57 AM 2384 (0x0950)

Query parsed successfully... ready to scan for files. FileSystemFile 4/22/2010 12:09:57 AM 2384 (0x0950)

Folders to skip: c:\system volume information. FileSystemFile 4/22/2010 12:09:57 AM 2384 (0x0950)

Scanning all local drives using input path *\ FileSystemFile 4/22/2010 12:09:57 AM 2384 (0x0950)

Skipping A:\; GetDriveType indicates it is not a fixed drive path FileSystemFile 4/22/2010 12:09:57 AM 2384 (0x0950)

Scanning C:\ ... FileSystemFile 4/22/2010 12:09:57 AM 2384 (0x0950)

Skipping directory c:\system volume information\ FileSystemFile 4/22/2010 12:11:49 AM 2384 (0x0950)

Skipping directory c:\system volume information\ FileSystemFile 4/22/2010 12:11:49 AM 2384 (0x0950)

Excluding C:\WINDOWS\$NtUninstallKB923845$\ (compressed) FileSystemFile 4/22/2010 12:11:59 AM 2384 (0x0950)

Excluding C:\WINDOWS\$NtUninstallKB923845$\ (compressed) FileSystemFile 4/22/2010 12:11:59 AM 2384 (0x0950)

Once the scan based on software inventory rules is completed, the results are stored within WMI on the Advanced Client

Server Side

The Management Point receives the message from the Advanced Client via a CCM_POST request. This allows the client to upload the message to the C:\SMS_CCM\ServiceData\Messaging\EndpointQueues\MP_SinvEndpoint directory on the Management Point.

Once there, CCMExec on the Management Point processes the message to recreate the XML file. This file is then stored in the <SEREVERDIR>4[1]\MP\Outboxes\Sinv.box folder. Once the Management Point has properly received the message and converted it into an XML file for processing, the XML file is then parsed and used to create a .SIC or .SID file. If the inventory data in the XML file is a Delta, the XML file is used to generate a .SID file. On the other hand, if the XML file is complete inventory information, a .SIC file is created.

Mp_sinv.log:

Mp Message Handler: copying attachment to C:\Program Files\Microsoft Configuration Manager\inboxes\auth\sinv.box\SinvAttachment8920FQG5.xmlMP_SinvEndpoint 1/31/2010 9:49:55 AM 3548 (0x0DDC)

Inv-Sinv Task: processing xml file "C:\Program Files\Microsoft Configuration Manager\inboxes\auth\sinv.box\SinvAttachment8920FQG5.xml"MP_SinvEndpoint 1/31/2010 9:49:55 AM 3280 (0x0CD0)

Sinv Sax: loading C:\Program Files\Microsoft Configuration Manager\inboxes\auth\sinv.box\SinvAttachment8920FQG5.xml MP_SinvEndpoint1/31/2010 9:49:55 AM 3280 (0x0CD0)

4

Full report from client SQL, action description = Software MP_SinvEndpoint 1/31/2010 9:49:55 AM 3280 (0x0CD0)

Sinv Task: Translate report attachment to file "C:\Program Files\Microsoft Configuration Manager\inboxes\auth\sinv.box\9GY0JSG8.SIC" returned 0MP_SinvEndpoint 1/31/2010 9:49:55 AM 3280 (0x0CD0)

Mp Message Handler: copying attachment to C:\Program Files\Microsoft Configuration Manager\inboxes\auth\sinv.box\SinvAttachment4L7OW9WF.xmlMP_SinvEndpoint 2/19/2010 7:37:16 PM 5980 (0x175C)

Inv-Sinv Task: processing xml file "C:\Program Files\Microsoft Configuration Manager\inboxes\auth\sinv.box\SinvAttachment4L7OW9WF.xml"MP_SinvEndpoint 2/19/2010 7:37:16 PM 272 (0x0110)

Sinv Sax: loading C:\Program Files\Microsoft Configuration Manager\inboxes\auth\sinv.box\SinvAttachment4L7OW9WF.xml MP_SinvEndpoint2/19/2010 7:37:16 PM 272 (0x0110)

Sinv Task: Translate report attachment to file "C:\Program Files\Microsoft Configuration Manager\inboxes\auth\sinv.box\AN46DUDY.SIC" returned 0MP_SinvEndpoint 1/31/2010 9:36:45 AM 4812 (0x12CC)

The management point file dispatch manager copies the file to the site server. There the software inventory processor inserts the data into the database.

Sinvproc.log:

Process Inventory Files... SMS_SOFTWARE_INVENTORY_PROCESSOR 1/31/2010 9:27:13 AM 5208 (0x1458)

Processing file: C:\Program Files\Microsoft Configuration Manager\inboxes\auth\sinv.box\W06N50OM.SICSMS_SOFTWARE_INVENTORY_PROCESSOR 1/31/2010 9:27:13 AM 4668 (0x123C)

Processing Inventory for Machine: SCCM ResId: 3 [OpCode=17 Sinv=1 FC=0 Resync=1] Generated: 01/31/2010 09:27:02SMS_SOFTWARE_INVENTORY_PROCESSOR 1/31/2010 9:27:37 AM 4668 (0x123C)

Transactions: Exist=0, Add=1196, Upd=0, Del=0, Total=1196 SMS_SOFTWARE_INVENTORY_PROCESSOR 1/31/2010 9:27:37 AM 4668 (0x123C)

Report for Machine SCCM took 27 secs. for 2290 recs, FP=109, P=985, F=1196, FC=0 SMS_SOFTWARE_INVENTORY_PROCESSOR 1/31/2010 9:27:40 AM4668 (0x123C)

Successfully Processed file C:\Program Files\Microsoft Configuration Manager\inboxes\auth\sinv.box\W06N50OM.SIC !!!SMS_SOFTWARE_INVENTORY_PROCESSOR 1/31/2010 9:27:40 AM 4668 (0x123C)

If the files are not getting processed then we need to make sure that the component SMS_SOFTWARE_INVENTORY_PROCESSOR. In certain circumstances a site reset can also help.

Links

http://technet.microsoft.com/en-us/library/bb693889.aspx : Overview of Inventory

http://technet.microsoft.com/en-us/library/bb632359.aspx : Troubleshooting Inventory

Troubleshooting SCCM Part V.........Heartbeat Discovery

Heartbeat Discovery

This is important for the understanding of the health state of the agent, this can be scheduled in the SCCM server using the console and the settings are available under discovery rules

Depending on the schedules set on the server, once initiated, the agent reads the inventory type to determine by querying WMI.

Once the Discovery Agent has determined its Scan type, it must now determine precisely what it needs to inventory. This is accomplished by again pulling configuration data from WMI. Discovery Rule information is stored within the same namespace of WMI (Root\CCM\Policy\Machine)

The scheduler sends a message to the Inventory Agent:

Client Side

Schedule.log:

Sending message for schedule 'Machine/{00000000-0000-0000-0000-000000000003}' (Target: 'direct:InventoryAgent', Name: '') $$<Scheduler><Sun Apr 24 9:39:06.003 2010 Eastern Standard Time><thread=2768 (0xAD0)>

smscliui.log:

Site is in mixed mode. Internet tab will not be displayed. smscliui 2/1/2010 9:02:22 AM 3544 (0x0DD8)

Perform Action: Discovery Data Collection Cycle - {00000000-0000-0000-0000-000000000103}. Message sent, id={7EAD483B-17D6-45FD-A7E2-

F8B2AE3797B5} smscliui 2/1/2010 9:03:17 AM 3564 (0x0DEC)

Then the Inventory agent collects the data and sends the xml file to the Management Point.

Inventoryagent.log:

Inventory: *********************** Start of message processing. *********************** InventoryAgent 4/23/2010 10:04:46 AM 2176 (0x0880)

Inventory: Message type is InventoryAction InventoryAgent 4/23/2010 10:04:46 AM 2176 (0x0880)

Inventory: Temp directory = C:\WINDOWS\system32\CCM\Inventory\Temp\ InventoryAgent 4/23/2010 10:04:46 AM 2176 (0x0880)

Inventory: Clearing old collected files. InventoryAgent 4/23/2010 10:04:46 AM 2176 (0x0880)

Inventory: Opening store for action {00000000-0000-0000-0000-000000000003} ...InventoryAgent 4/23/2010 10:04:46 AM 2176 (0x0880)

Inventory: Action=Discovery ReportType=Full InventoryAgent 4/23/2010 10:04:46 AM 2176 (0x0880)

Inventory: Initialization completed in 0.400 seconds InventoryAgent 4/23/2010 10:04:46 AM 2176 (0x0880)

Collection: Namespace = \\.\root\cimv2; Query = SELECT __CLASS, __PATH, __RELPATH, IPAddress, IPXAddress, MACAddress FROM Win32_NetworkAdapterConfiguration WHERE IPEnabled=TRUE; Timeout = 600 secs. InventoryAgent 4/23/2010 10:04:46 AM

2176 (0x0880)

Collection: Namespace = \\.\root\cimv2; Query = SELECT __CLASS, __PATH, __RELPATH, UserName FROM Win32_ComputerSystem; Timeout = 600 secs.InventoryAgent 4/23/2010 10:04:46 AM 2176 (0x0880)

Collection: Namespace = \\.\root\ccm\invagt; Query = SELECT __CLASS, __PATH, __RELPATH, IPv6Address FROM

………………….

………………

…………………….

Collection: 13/14 inventory data items successfully inventoried. InventoryAgent 4/23/2010 10:04:47 AM 2176 (0x0880)

Inventory: Collection Task completed in 0.621 seconds InventoryAgent 4/23/2010 10:04:47 AM 2176 (0x0880)

Inventory: 1 Collection Task(s) failed. InventoryAgent 4/23/2010 10:04:47 AM 2176 (0x0880)

Inventory: Temp report = C:\WINDOWS\system32\CCM\Inventory\Temp\302aac72-7191-41b1-9b92-40b6b08b31c6.xml InventoryAgent4/23/2010 10:04:47 AM 2176 (0x0880)

Inventory: Starting reporting task. InventoryAgent 4/23/2010 10:04:47 AM 2176 (0x0880)

Reporting: 11 report entries created. InventoryAgent 4/23/2010 10:04:47 AM 2176 (0x0880)

Inventory: Reporting Task completed in 0.090 seconds InventoryAgent 4/23/2010 10:04:47 AM 2176 (0x0880)

Inventory: Successfully sent report. Destination:mp:MP_DdrEndpoint, ID: {209E69B5-519E-414F-AB47-703B1F1DC1AE}, Timeout: 80640 minutes MsgMode: Signed, Not Encrypted InventoryAgent 4/23/2010 10:04:47 AM 2176 (0x0880)

Inventory: Cycle completed in 1.812 seconds InventoryAgent 4/23/2010 10:04:47 AM 2176 (0x0880)

Inventory: Action completed. InventoryAgent 4/23/2010 10:04:47 AM 2176 (0x0880)

Server Side

After that the processing takes place on the MP. The xml file is translated into a DDR:

MP_Ddr.log:

Ddr Task: Translate report attachment to file "C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\BO4QB24H.DDR" returned 0MP_DdrEndpoint 4/21/2010 10:38:37 AM 4360 (0x1108)

Mp Message Handler: copying attachment to C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\DdrAttachment2R4M0DLR.xmlMP_DdrEndpoint 4/23/2010 10:04:47 AM 2600 (0x0A28)

Inv-Ddr Task: processing xml file "C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\DdrAttachment2R4M0DLR.xml"MP_DdrEndpoint 4/23/2010 10:04:47 AM 2512 (0x09D0)

Full report from client SQL, action description = Discovery MP_DdrEndpoint 4/23/2010 10:04:47 AM 2512 (0x09D0)

Ddr Task: Translate report attachment to file "C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\H5AVRZ5O.DDR" returned 0MP_DdrEndpoint 4/23/2010 10:04:48 AM 2512 (0x09D0)

The Management Point File Dispatch Manager copies the files from the MP folder structure to the site server folder structure.

And after this on the site server the Discovery Data Manager inserts the data into the SCCM database:

ddm.log:

DDM is configured to synchronize the network config data (NCF) files at startup and every 15 minutes thereafter.

SMS_DISCOVERY_DATA_MANAGER 4/23/2010 10:01:34 AM 3864 (0x0F18)

CDiscoverDataManager::GetSiteStatus - Registering SQL types, Server = SQL, Database = SMS_LAB, User = SMS_DISCOVERY_DATA_MANAGER4/23/2010 10:01:34 AM 3864 (0x0F18)

Preparing to sync deletes... SMS_DISCOVERY_DATA_MANAGER 4/23/2010 10:01:34 AM 3864 (0x0F18)

No system deletions to replicate. SMS_DISCOVERY_DATA_MANAGER 4/23/2010 10:01:34 AM 3864 (0x0F18)

Looking for ClientKeyData changes SMS_DISCOVERY_DATA_MANAGER 4/23/2010 10:01:34 AM 3864 (0x0F18)

No ClientKeyData changes to replicate SMS_DISCOVERY_DATA_MANAGER 4/23/2010 10:01:34 AM 3864 (0x0F18)

Synchronizing network config data (NCF) files with site control data in the database. SMS_DISCOVERY_DATA_MANAGER 4/23/2010 10:01:54 AM 1472 (0x05C0)

Synchronization of network config data (NCF) files is complete. SMS_DISCOVERY_DATA_MANAGER 4/23/2010 10:01:54 AM1472 (0x05C0)

Refreshing site settings..... SMS_DISCOVERY_DATA_MANAGER 4/23/2010 10:04:49 AM 3864 (0x0F18)

Updated inbox def 15, Discovery Data Manager SMS_DISCOVERY_DATA_MANAGER 4/23/2010 10:04:49 AM 3864 (0x0F18)

Updated inbox def 41, Discovery Data Manager (Trusted) SMS_DISCOVERY_DATA_MANAGER 4/23/2010 10:04:50 AM 3864 (0x0F18)

Updated inbox def 48, Discovery Data Manager (Registration) SMS_DISCOVERY_DATA_MANAGER 4/23/2010 10:04:50 AM3864 (0x0F18)

Updated inbox def 14, Discovery Asst Rules SMS_DISCOVERY_DATA_MANAGER 4/23/2010 10:04:50 AM 3864 (0x0F18)

Updated inbox def 50, Discovery Data Manager (Notification) SMS_DISCOVERY_DATA_MANAGER 4/23/2010 10:04:50 AM3864 (0x0F18)

Updated inbox def 9, Data Loader SMS_DISCOVERY_DATA_MANAGER 4/23/2010 10:04:50 AM 3864 (0x0F18)

Updated inbox def 10, Software Inventory Processor (Site) SMS_DISCOVERY_DATA_MANAGER 4/23/2010 10:04:50 AM 3864 (0x0F18)

Updated inbox def 23, Client Configuration Record (Incoming) SMS_DISCOVERY_DATA_MANAGER 4/23/2010 10:04:50 AM3864 (0x0F18)

DDM is configured to synchronize the network config data (NCF) files at startup and every 15 minutes thereafter.SMS_DISCOVERY_DATA_MANAGER 4/23/2010 10:04:50 AM 3864 (0x0F18)

CDiscoverDataManager::GetSiteStatus - Registering SQL types, Server = SQL, Database = SMS_LAB, User = SMS_DISCOVERY_DATA_MANAGER4/23/2010 10:04:50 AM 3864 (0x0F18)

The same log but with SQL logging enabled on the site server:

Ddm.log:

Processing file a4z7f6ye.DDRSMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)

SQL>>>select d1.DiscArchKey,d1.DiscArchName,d1.BaseTableName,d1.Flags,d2.PropertyName,d2.ColumnName,d2.ValueType,d2.MaxWidth,d2.Flags,d2.ArrayTableName FROM DiscoveryArchitectures AS d1 LEFT JOIN DiscPropertyDefs AS d2 ON d1.DiscArchKey = d2.DiscArchKey where d1.DiscArchName = "System" order by d1.DiscArchKeySMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)

SQL>>>>> Done.SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)

SQL>>>select ItemKey from System_DISC where SMS_Unique_Identifier0 = "GUID:07114A5F-BE31-49B6-9FFC-5EFA2D897974"SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)


Processing <System> #4...SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)

SQL>>>select convert(varchar(255),IP_Addresses0) from System_IP_Address_ARR where ItemKey = 4SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)


SQL>>>select convert(varchar(255),IP_Subnets0) from System_IP_Subnets_ARR where ItemKey = 4SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)


SQL>>>select convert(varchar(255),IPX_Addresses0) from System_IPX_Addres_ARR where ItemKey = 4SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)


SQL>>>select convert(varchar(255),IPX_Network_Numbers0) from System_IPX_Network_Numbers_ARR where ItemKey = 4SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)


SQL>>>select convert(varchar(255),MAC_Addresses0) from System_MAC_Addres_ARR where ItemKey = 4SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)


SQL>>>select convert(varchar(255),Resource_Names0) from System_Resource_N_ARR where ItemKey = 4SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)


SQL>>>select convert(varchar(255),SMS_Assigned_Sites0) from System_SMS_Assign_ARR where ItemKey = 4SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)


SQL>>>select convert(varchar(255),SMS_Installed_Sites0) from System_SMS_Instal_ARR where ItemKey = 4SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)


SQL>>>select convert(varchar(255),System_Container_Name0) from System_System_Container_Name_A where ItemKey = 4SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)


SQL>>>select convert(varchar(255),System_Group_Name0) from System_System_Group_Name_ARR where ItemKey = 4SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)


SQL>>>select convert(varchar(255),System_OU_Name0) from System_System_OU_Name_ARR where ItemKey = 4SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)


SQL>>>select convert(varchar(255),System_Roles0) from System_System_Rol_ARR where ItemKey = 4SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)


SQL>>>select convert(varchar(255),Active0),convert(varchar(255),AD_Site_Name0),convert(varchar(255),Client0),convert(varchar(255),Client_Type0),convert(varchar(255),Client_Version0),convert(varchar(255),CPUType0),convert(char(10),Creation_Date0,101) +' '+ convert(char(8),Creation_Date0,8),convert(varchar(255),Hardware_ID0),convert(varchar(255),User_Domain0),convert(varchar(255),User_Name0),convert(varchar(255),Name0),convert(varchar(255),Netbios_Name0),convert(varchar(255),Obsolete0),convert(varchar(255),Operating_System_Name_and0),c

onvert(varchar(255),Previous_SMS_UUID0),convert(varchar(255),Resource_Domain_OR_Workgr0),convert(varchar(255),SMS_Unique_Identifier0),convert(char(10),SMS_UUID_Change_Date0,101) +' '+ convert(char(8),SMS_UUID_Change_Date0,8),convert(varchar(255),Community_Name0) from System_DISC where ItemKey = 4SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)


SQL>>>select AgentID,AgentTime,AgentSite from DiscItemAgents where ItemKey = 4 and DiscArchKey = 5SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)


SQL>>>set ansi_padding off; set ANSI_NULLS OFF; set quoted_identifier off; set DATEFORMAT mdy; select convert(int,@@spid)SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)


SQL>>>select AgentID,AgentName,IsResyncable from AgentsSMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)


SQL>>>set ansi_padding off; set ANSI_NULLS OFF; set quoted_identifier off; set DATEFORMAT mdy; select convert(int,@@spid)SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)


SQL>>>exec sp_GetPublicKeySMSUID "GUID:07114A5F-BE31-49B6-9FFC-5EFA2D897974"SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)


CDiscoverySource::VerifyClientPublicKeys - Public key does not exist for client GUID:07114A5F-BE31-49B6-9FFC-5EFA2D897974.SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)

==>Name = <VEMPOP3>SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)

Info: The DDR contains 22 properties, but none has new valuesSMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)

insert agent information: DiscItemAgents : execute sql IF EXISTS (select ItemKey from DiscItemAgents where ItemKey = 4 and DiscArchKey = 5 and AgentID = 8 and AgentSite = "XYZ") update DiscItemAgents set AgentTime = "03/13/2010 15:21:39" where ItemKey = 4 and DiscArchKey = 5 and AgentID = 8 and AgentSite = "XYZ"~ ELSE insert into DiscItemAgents (AgentTime, ItemKey, DiscArchKey, AgentID, AgentSite) values ("03/13/2010 15:21:39", 4, 5, 8, "XYZ")SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)

SQL>>>IF EXISTS (select ItemKey from DiscItemAgents where ItemKey = 4 and DiscArchKey = 5 and AgentID = 8 and AgentSite = "XYZ") update DiscItemAgents set AgentTime = "03/13/2010 15:21:39" where ItemKey = 4 and DiscArchKey = 5 and AgentID = 8 and AgentSite = "XYZ"~ ELSE insert into DiscItemAgents (AgentTime, ItemKey, DiscArchKey, AgentID, AgentSite) values ("03/13/2010 15:21:39", 4, 5, 8, "XYZ")SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)


Database operations finished.SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)

CDiscoverDataManager::FilterDDR - Will not create CCR. The Remote Client is already installed on this resource.SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)

CDiscoverDataManager::ProcessDDRs_PS - finished processing file C:\SMS\inboxes\auth\ddm.box\a4z7f6ye.DDR.SMS_DISCOVERY_DATA_MANAGER3/13/2010 3:24:06 PM316 (0x013C)

On the client reporting part had explained more on the troubleshooting part in case of any failures. Also these logs will give information on what had happened and why the discovery is not coming.

The main issues which are seen in the hardware inventory are

Client are not downloading the polices (Can check on the client status and can use the client reporting troubleshooting)

There is communication issue between the agent and the server (Use client reporting troubleshooting )

There are agent with the same GUID (Check how to deal with client multiple GUID issue. More details in the client reporting troubleshooting section)

The DDM component has issues. (Can try a site reset)

http://technet.microsoft.com/en-us/library/bb632938.aspx :Discovery in Configuration Manager

http://technet.microsoft.com/en-us/library/bb932200.aspx :Troubleshooting Discovery Issues

http://technet.microsoft.com/en-us/library/bb735871.aspx :Discovery Troubleshooting Flowcharts

Troubleshooting SCCM Part VI ..........Software Distribution

Sudheesh N 31 Jan 2011 9:10 PM

Comments 0

Software Distribution

http://blogs.technet.com/sudheesn_4000_microsoft.com/ProfileUrlRedirect.ashx

The Microsoft System Center Configuration Manager 2007 software distribution feature provides a set of tools and resources that help you create and manage packages and advertisements used to distribute software to client resources within your enterprise.

For more details please check the following link


Troubleshooting Software Distribution

Server Side

Once you create a package then you need to check the status messages to see if the package has been created you will have the following entries

Status ID : 30000 => User "Domain\User" created a package named " Test Package " (LAB00003).Status ID : 2301 => SMS Distribution Manager successfully processed package "Test Package" (package ID = LAB00003).

Also you will have 2300 and 2311 for starting and creation of the packages Once you add the distribution point you then have to see if the following status messages are displayed.

Status ID : 30125 User "Domain\User" added new distribution points to a package named " Test Package " (LAB00003).

Severity Type Site code Date / TimeSystem Component Message IDDescription Thread ID Process ID

Information Milestone LAB 4/26/2010 10:28:51 PM SCCM SMS_DISTRIBUTION_MANAGER 2330 SMS Distribution Manager successfully distributed package "LAB00003" to distribution point "["Display=\\SCCM\"]MSWNET:["SMS_SITE=LAB"]\\SCCM\".

4412 3040

Information Milestone LAB 4/26/2010 10:28:51 PM SCCM SMS_DISTRIBUTION_MANAGER 2329 SMS Distribution Manager copied package "LAB00003" from "C:\SOFTDUMP\" to "MSWNET:["SMS_SITE=LAB"]\\SCCM\SMSPKGC$\LAB00003\". 4412

3040

Information Milestone LAB 4/26/2010 10:28:29 PM SCCM SMS_DISTRIBUTION_MANAGER 2342 SMS Distribution Manager is starting to distribute package "Test Package" to distribution point "["Display=\\SCCM\"]MSWNET:["SMS_SITE=LAB"]\\SCCM\".

4412 3040

If you see the errors you can check the distmgr.log for the same. The distmgr.log will have the following entries

STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SCCM SITE=LAB PID=3040 TID=3276 GMTDATE=Mon Apr 26 16:59:00.772 2010 ISTR0="Test Package" ISTR1="LAB00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAB00003" SMS_DISTRIBUTION_MANAGER 4/26/2010 10:29:00 PM 3276 (0x0CCC)

No action specified for the package LAB00003. SMS_DISTRIBUTION_MANAGER 4/26/2010 10:29:00 PM 3276 (0x0CCC)

No action specified for the package on server ["Display=\\SCCM\"]MSWNET:["SMS_SITE=LAB"]\\SCCM\. SMS_DISTRIBUTION_MANAGER 4/26/2010 10:29:00 PM 3276 (0x0CCC)

Updating package info for package LAB00003 SMS_DISTRIBUTION_MANAGER 4/26/2010 10:29:00 PM 3276 (0x0CCC)

Package LAB00003 does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 4/26/2010 10:29:00 PM 3276 (0x0CCC)

The package and/or program properties for package LAB00003 have not changed, need to determine which site(s) need updated package info.SMS_DISTRIBUTION_MANAGER 4/26/2010 10:29:00 PM 3276 (0x0CCC)

StoredPkgVersion (0) of package LAB00003. StoredPkgVersion in database is 0. SMS_DISTRIBUTION_MANAGER 4/26/2010 10:29:00 PM3276 (0x0CCC)

SourceVersion (1) of package LAB00003. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER 4/26/2010 10:29:00 PM3276 (0x0CCC)

STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SCCM SITE=LAB PID=3040 TID=3276 GMTDATE=Mon Apr 26 16:59:01.073 2010 ISTR0="Test Package" ISTR1="LAB00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAB00003" SMS_DISTRIBUTION_MANAGER 4/26/2010 10:29:01 PM 3276 (0x0CCC)

Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 4/26/2010 10:29:01 PM 3276 (0x0CCC)

In case you see errors please make sure that the following

There is no network issue between the server and the and the DP server

Make sure that the SMSPKG$ share has been created and that has the folder with the package ID

There is no DNS resolution issue.

Make sure that the share has the require permission to write the data.

Once this is verified the next step is to check if the advertisement is created .These are the following status which will give you an idea on the creation

Information Milestone LAB 4/26/2010 10:44:36 PM SCCM SMS_OFFER_MANAGER 3900 SMS Offer Manager successfully processed new advertisement Test Advr.

Information Audit LAB 4/26/2010 10:44:24 PM SCCM Microsoft.ConfigurationManagement.dll 30006User "MYLAB\Administrator" created an advertisement named "Test Advr" (LAB20000) advertising program "Test Program".

Once the advertisement is received by the client you will have the following status messages

Severity Type Site code Date / TimeSystem Component Message IDDescription

Information Milestone LAB 4/26/2010 10:44:36 PM SCCM SMS_OFFER_MANAGER 3900 SMS Offer Manager successfully processed new advertisement Test Advr.

Information Audit LAB 4/26/2010 10:44:24 PM SCCM Microsoft.ConfigurationManagement.dll 30006User "MYLAB\Administrator" created an advertisement named "Test Advr" (LAB20000) advertising program "Test Program".

Now on you need to check the client logs.

Client Side

Once the agent refreshes the policy according the policy refresh interval you will have the policy downloaded and evaluated.

Policyagnet.log

Download of policy CCM_Policy_Policy4.PolicyID="LAB20000-LAB00003-9785047B",PolicySource="SMS:LAB",PolicyVersion="1.00" completed (DTS Job ID: {231E2AE2-7ED2-4AA3-84F4-81CA1712217E}) PolicyAgent_PolicyDownload 4/26/2010 10:47:12 PM 1944 (0x0798)

Raising event:

instance of CCM_PolicyAgent_PolicyDownloadSucceeded

{

ClientID = "GUID:76B6D180-F0B6-4689-B294-6CCE9033D7EB";

DateTime = "20100426171712.258000+000";

DownloadMethod = "BITS";

DownloadSource = "http://SCCM.MYLAB.IN/SMS_MP/.sms_pol?LAB20000-LAB00003-9785047B.1_00";

PolicyNamespace = "\\\\SQL\\ROOT\\ccm\\Policy\\Machine\\RequestedConfig";

PolicyPath = "CCM_Policy_Policy4.PolicyID=\"LAB20000-LAB00003-9785047B\",PolicySource=\"SMS:LAB\",PolicyVersion=\"1.00\"";

ProcessID = 3568;

ThreadID = 1944;

};

PolicyAgent_PolicyDownload 4/26/2010 10:47:12 PM 1944 (0x0798)

Policy Evaluvator.log

Raising event:

instance of CCM_PolicyAgent_PolicyEvaluationComplete

{


DateTime = "20100426171716.924000+000";

PolicyNamespace = "\\\\SQL\\ROOT\\ccm\\Policy\\Machine\\RequestedConfig";

PolicyPath = "CCM_Policy_Policy4.PolicyID=\"LAB20000-LAB00003-9785047B\",PolicySource=\"SMS:LAB\",PolicyVersion=\"1.00\"";

ProcessID = 3568;

ThreadID = 1944;

};

PolicyAgent_PolicyEvaluator 4/26/2010 10:47:16 PM 1944 (0x0798)

Policy state for [CCM_Policy_Policy4.PolicyID="LAB20000-LAB00003-9785047B",PolicyVersion="1.00",PolicySource="SMS:LAB"] is currently [Active]PolicyAgent_PolicyEvaluator 4/26/2010 10:47:16 PM 3488 (0x0DA0)

Updating settings in \\sql\root\ccm\policy\machine\actualconfig PolicyAgent_PolicyEvaluator 4/26/2010 10:47:16 PM 3488 (0x0DA0)

Raising event:

instance of CCM_PolicyAgent_SettingsEvaluationComplete

{


DateTime = "20100426171718.827000+000";

PolicyNamespace = "\\\\sql\\root\\ccm\\policy\\machine\\actualconfig";

ProcessID = 3568;

ThreadID = 3488;

};

PolicyAgent_PolicyEvaluator 4/26/2010 10:47:18 PM 3488 (0x0DA0)

On the execution manager you will have the following entry

Execmgr.log

Policy arrived for parent package LAB00003 program Test Program execmgr 4/26/2010 10:47:19 PM 2004 (0x07D4)

Raising event:

[SMS_CodePage(437), SMS_LocaleID(1033)]

instance of SoftDistProgramOfferReceivedEvent

{

AdvertisementId = "LAB20000";


DateTime = "20100426171720.299000+000";

MachineName = "SQL";

ProcessID = 3568;

SiteCode = "LAB";

ThreadID = 2004;

};

execmgr 4/26/2010 10:47:20 PM 2004 (0x07D4)

Requesting content from CAS for package LAB00003 version 1 execmgr 4/26/2010 10:47:25 PM 1944 (0x0798)

Successfully created a content request handle {80539F34-D400-4978-95F2-9D26151C9BF8} for the package LAB00003 version 1 execmgr 4/26/2010 10:47:29 PM 1944 (0x0798)

Then you will see the download in the datatransferservices.log

DatatransferServices.log

UpdateURLWithTransportSettings(): OLD URL - http://SCCM.MYLAB.IN/SMS_MP/.sms_pol?LAB20000-LAB00003-9785047B.1_00 DataTransferService

4/26/2010 10:47:06 PM 3208 (0x0C88)

UpdateURLWithTransportSettings(): NEW URL - http://SCCM.MYLAB.IN:80/SMS_MP/.sms_pol?LAB20000-LAB00003-9785047B.1_00DataTransferService 4/26/2010 10:47:06 PM 3208 (0x0C88)

DTSJob {231E2AE2-7ED2-4AA3-84F4-81CA1712217E} created to download from 'http://SCCM.MYLAB.IN/SMS_MP/.sms_pol?LAB20000-LAB00003-9785047B.1_00' to 'C:\WINDOWS\system32\CCM\Temp\{55C3178E-C27D-4C29-AC2D-439C6E87D53D}.tmp'. DataTransferService 4/26/2010 10:47:06 PM 3208 (0x0C88)

DTSJob {231E2AE2-7ED2-4AA3-84F4-81CA1712217E} in state 'PendingDownload'. DataTransferService 4/26/2010 10:47:06 PM 1944 (0x0798)

DTS::AddTransportSecurityOptionsToBITSJob - Failed to QueryInterface for IBackgroundCopyJobHttpOptions. BITS 2.5+ may not be installed properly.DataTransferService 4/26/2010 10:47:09 PM 1944 (0x0798)

DTSJob {231E2AE2-7ED2-4AA3-84F4-81CA1712217E} in state 'DownloadingData'. DataTransferService 4/26/2010 10:47:09 PM 1944 (0x0798)

DTSJob {231E2AE2-7ED2-4AA3-84F4-81CA1712217E} in state 'RetrievedData'. DataTransferService 4/26/2010 10:47:11 PM 2004 (0x07D4)

DTSJob {B40BBB03-0BA0-460A-B822-3DB2535AFCF1} successfully completed download. DataTransferService 4/26/2010 10:48:10 PM3208 (0x0C88)

DTSJob {B40BBB03-0BA0-460A-B822-3DB2535AFCF1} in state 'NotifiedComplete'. DataTransferService 4/26/2010 10:48:11 PM 3488 (0x0DA0)

DTS job {B40BBB03-0BA0-460A-B822-3DB2535AFCF1} has completed:

Status : SUCCESS

Start time : 04/26/2010 22:48:07

Completion time : 04/26/2010 22:48:10

Elapsed time : 3 seconds DataTransferService 4/26/2010 10:48:11 PM 3488 (0x0DA0)

Then you will see the downloaded progress and completed with the execution of the process. If it is failing make sure that the DP is available and also that the BITS is working fine.

Execmgr.log

Program Test Program change to state STATE_ADVANCED_DOWNLOAD content in progress execmgr 4/26/2010 10:47:29 PM 1944 (0x0798)

Execution Request for package LAB00003 program Test Program state change from NotExist to AdvancedDownload execmgr 4/26/2010 10:47:29 PM 1944 (0x0798)

Mandatory execution requested for program Test Program and advertisement LAB20000 execmgr 4/26/2010 10:47:29 PM 3208 (0x0C88)

Creating mandatory request for advert LAB20000, program Test Program, package LAB00003 execmgr 4/26/2010 10:47:29 PM 3208 (0x0C88)

Raising event:


instance of SoftDistWaitingContentEvent

{



DateTime = "20100426171731.545000+000";


PackageName = "LAB00003";

PackageVersion = "1";

ProcessID = 3568;

ProgramName = "Test Program";

SiteCode = "LAB";

ThreadID = 3208;

};

execmgr 4/26/2010 10:47:31 PM 3208 (0x0C88)

Successfully raised SoftDistWaitingContentEvent event for program Test Program execmgr 4/26/2010 10:47:31 PM 3208 (0x0C88)

Execution Request for package LAB00003 program Test Program state change from WaitingDependency to WaitingContent execmgr 4/26/2010 10:47:31 PM 3208 (0x0C88)

Content is available for program Test Program. execmgr 4/26/2010 10:48:18 PM 3488 (0x0DA0)

CExecutionRequest::Service Windows Manager has allowed us to run. execmgr 4/26/2010 10:48:18 PM 3488 (0x0DA0)

Execution Request for package LAB00003 program Test Program state change from WaitingContent to NotifyExecution execmgr 4/26/2010 10:48:18 PM 3488 (0x0DA0)

Notify user mandatory program Test Program is about to run execmgr 4/26/2010 10:48:18 PM 3488 (0x0DA0)

Execution Manager timer has been fired. execmgr 4/26/2010 10:53:18 PM 2184 (0x0888)

Executing program test.bat in Admin context execmgr 4/26/2010 10:53:19 PM 2184 (0x0888)

Execution Manager timer has been fired. execmgr 4/26/2010 10:53:19 PM 3752 (0x0EA8)

Execution Request for package LAB00003 program Test Program state change from Running to NotifyExecution execmgr 4/26/2010 10:53:19 PM 2184 (0x0888)

Checking content location C:\WINDOWS\system32\CCM\Cache\LAB00003.1.System for use execmgr 4/26/2010 10:53:19 PM 2184 (0x0888)

Successfully selected content location C:\WINDOWS\system32\CCM\Cache\LAB00003.1.System execmgr 4/26/2010 10:53:19 PM2184 (0x0888)

Executing program as a script execmgr 4/26/2010 10:53:19 PM 2184 (0x0888)

Successfully prepared command line "C:\WINDOWS\system32\CCM\Cache\LAB00003.1.System\test.bat" execmgr 4/26/2010 10:53:19 PM2184 (0x0888)

Command line = "C:\WINDOWS\system32\CCM\Cache\LAB00003.1.System\test.bat", Working Directory = C:\WINDOWS\system32\CCM\Cache\LAB00003.1.System\ execmgr 4/26/2010 10:53:19 PM 2184 (0x0888)

Created Process for the passed command line execmgr 4/26/2010 10:53:20 PM 2184 (0x0888)

Raising event:


instance of SoftDistProgramStartedEvent

{



CommandLine = "\"C:\\WINDOWS\\system32\\CCM\\Cache\\LAB00003.1.System\\test.bat\"";

DateTime = "20100426172320.000000+000";



ProcessID = 3568;


SiteCode = "LAB";

ThreadID = 2184;

UserContext = "NT AUTHORITY\\SYSTEM";

WorkingDirectory = "C:\\WINDOWS\\system32\\CCM\\Cache\\LAB00003.1.System\\";

};

execmgr 4/26/2010 10:53:20 PM 2184 (0x0888)

Raised Program Started Event for Ad:LAB20000, Package:LAB00003, Program: Test Program execmgr 4/26/2010 10:53:20 PM 2184 (0x0888)

Program exit code 0 execmgr 4/26/2010 10:53:24 PM 3752 (0x0EA8)

Looking for MIF file to get program status execmgr 4/26/2010 10:53:24 PM 3752 (0x0EA8)

Script for Package:LAB00003, Program: Test Program succeeded with exit code 0 execmgr 4/26/2010 10:53:24 PM 3752 (0x0EA8)

Raising event:


instance of SoftDistProgramCompletedSuccessfullyEvent

{



DateTime = "20100426172324.741000+000";



ProcessID = 3568;


SiteCode = "LAB";

ThreadID = 3752;

UserContext = "NT AUTHORITY\\SYSTEM";

};

execmgr 4/26/2010 10:53:24 PM 3752 (0x0EA8)

Raised Program Success Event for Ad:LAB20000, Package:LAB00003, Program: Test Program execmgr 4/26/2010 10:53:24 PM 3752 (0x0EA8)

Execution is complete for program Test Program. The exit code is 0, the execution status is Success execmgr 4/26/2010 10:53:24 PM2184 (0x0888)

Execution Manager timer has been fired. execmgr 4/26/2010 10:55:29 PM 2184 (0x0888)

If there are errors here you need to check the program command line and check if you can execute this command manually in your system. Please note that in SCCM software distribution is a just a command carrier and it will carry the command which you have requested with the set of files required so if there is any execution error you need to troubleshoot the same differently.

For more details please see the following link

http://technet.microsoft.com/en-us/library/bb632640.aspx Software Distribution in Configuration Manager

http://technet.microsoft.com/en-us/library/bb892792.aspx : Troubleshooting Software Distribution Issues

http://technet.microsoft.com/en-us/library/bb932214.aspx : Software Distribution Troubleshooting Flowcharts

http://technet.microsoft.com/en-us/library/bb735865.aspx : Troubleshooting Software Distribution Using Custom Error Codes.

troubleshooting sccm

Documents

sms client

client files

manager sms

xp client

0x0c7c sms

sql sms

case of client installation

targeted client machine