Old system still exist in SCCM console..

Solution to get Rid fo them .

1. Enable maintanance task to delete the system and check the log files smsdbmon.log to monitor the activity.

OR

2.  I suggest you create collection of computers you haven't heard from in x number of days, and use delete special to get rid of all the objects. below query will return all objects that haven't reported any hw inventory for a month.
Servers that haven’t scanned for hw inventory in 7 days or more:
select * from SMS_R_System inner join SMS_G_System_WORKSTATION_STATUS on SMS_G_System_WORKSTATION_STATUS.ResourceId = SMS_R_System.ResourceId where SMS_R_System.OperatingSystemNameandVersion like "%server%" and (DateDiff(day, SMS_G_System_WORKSTATION_STATUS.LastHardwareScan, GetDate()) >=30)

Any above option can be used to rid of old system that dosn,t exist anymore.

Cheers!!!!!

Move all your default collection using script!!!

Thanks to Richard for this excelent script for moving the collection.

Have you always been annoyed by the default collections cluttering up the view in your ConfigMgr console, well there’s a way that you can store them away under a separate collection. I found this blog post (http://verbalprocessor.com/2009/03/20/how-to-move-collections-in-configmgr) a while ago solving the problem. But hey I’m a lazy guy and after all, I’m installing lots of ConfigMgr servers out at customer sites, so automation is the key that drives lazy admins, right? So in this post I will walk you through using a script that can move collections based on either the name or comment of the collection/collections you want to move.

First up, you need to know some stuff from your environment, like the name of your server and site code. Also you need to know the Collection ID where you want to save the collection to. Start out by going to your ConfigMgr console and locate the site code, you will find it here:

 

Then create a new collection and localize the Collection ID, like this: 

 

Next up download the script (from the bottom of this post) and save it to an appropriate location on your site server, in this case I saved it to the location F:\UTV\Scripts. Then edit the section with site server (I run it on the ConfigMgr server so the name is set to ".") and site code plus the Collection ID of your newly created collection in the script. Also, in this case I will move the collection based on the name they have, so in the script I enter “All%”, which basically means all collections that starts with All… something.  
 
Start an elevated CMD prompt and run the script like below: 



Your output should look similar to this:



Finally refresh you console and your should end up like this:



Hope this help, you can also move collection based on comments just edit the beginning of the script something like this (based on the fact that you have collections with comment like Move).  




The script is here:

just rename it after putting it in notepad.

'
' Script created by: Richard Ulfvin
' http://www.filemilk.se/
'
' Disclaimer:
' This script is provided "AS IS" without express
' or implied warranty of any kind.
'
' Version 1.0
'
Option Explicit
Dim sConfigMgrServer : sConfigMgrServer   = "."
Dim sConfigMgrSiteCode : sConfigMgrSiteCode  = "C01"
Dim sCollectionName : sCollectionName    = ""
Dim sCollectionDesc : sCollectionDesc   = ""
Dim sParentCollectionID : sParentCollectionID  = ""
Dim oConfigMgr, sResult
ConnectToConfigMgr oConfigMgr
MoveCollection oConfigMgr, sCollectionName, sCollectionDesc, sParentCollectionID
Function ConnectToConfigMgr (oConfigMgr)
 'Attempts to use the provided information to connect to the ConfigMgr environment.
 Dim oWMILocator

 On Error Resume Next

 Set oWMILocator = CreateObject("WbemScripting.SWbemLocator")
 Set oConfigMgr = oWMILocator.ConnectServer(sConfigMgrServer, "root\sms\site_" & sConfigMgrSiteCode)
 If Err <> 0 Then
  sResult = "Error: " & Err.description
  Wscript.echo sResult
  Err.Clear
  Wscript.Quit(0)
 Else
  sResult = "Successfully connected to ConfigMgr"
  Wscript.echo sResult
 End If

 On Error Goto 0

End Function
Function MoveCollection(oConfigMgr, sCollectionName, sCollectionDesc, sParentCollectionID)
 Dim cCollections, oCollection, oCollectionRelation, sCollectionID, oCollectionLink, cCollectionLinks
 ' Obtain the collection ID of the collection.
 If sCollectionName <> "" Then
  Set cCollections = oConfigMgr.ExecQuery ("SELECT * FROM SMS_Collection where Name LIKE '" & sCollectionName & "'")
  Wscript.echo "Using Collection Name for parameter: " & sCollectionName
 ElseIf sCollectionDesc <> "" Then
  Set cCollections = oConfigMgr.ExecQuery ("SELECT * FROM SMS_Collection where Comment LIKE '" & sCollectionDesc & "'") 
  Wscript.echo "Using Collection Comment for parameter: " & sCollectionDesc 
 End If

 For each oCollection in cCollections
 
  sCollectionID=oCollection.CollectionID
  Wscript.echo "Found collection with name: " & oCollection.Name & " and CollectionID: " & oCollection.CollectionID
 
  ' Attempts to move the collection into the desired parent collection.
  Set oCollectionRelation = oConfigMgr.Get("SMS_CollectToSubCollect").SpawnInstance_()
  oCollectionRelation.parentCollectionID = sParentCollectionID
  oCollectionRelation.subCollectionID = sCollectionID
  oCollectionRelation.Put_
  Wscript.echo "Moving: " & oCollection.Name & " to rootcollectionID: " & sParentCollectionID
 
  'Delete any prior collectionlink.
  Set cCollectionLinks = oConfigMgr.ExecQuery ("SELECT * FROM SMS_CollectToSubCollect WHERE subCollectionID = '" & sCollectionID & "' AND NOT parentCollectionID = '" & sParentCollectionID & "'" ) 
  For each oCollectionLink in cCollectionLinks
   Wscript.echo "Found collection link for ID: " & oCollectionLink.subCollectionID & " with parrent collectionID: " & oCollectionLink.parentCollectionID & " to delete!"
   oCollectionLink.Delete_
  Next
 
 Next

End Function

Cheers!!!!!!

Remote Tools continues to become disabled even if after setting is to enable it on SCCM server.

Senario :

On some ofmy clients remote control was disable where as on site wise base it is kept to be enabled. When i tryied to take remote of one of my client machine . it gave me error remote control is disabled. Even after reinstalling the client the problem was same. it was getting disabled automatically.

Solution :

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Client\Client Components\Remote Control]
"Enabled"=dword:00000001

All my affected machines were still set to 0. This edit is done on the client machines.

Hope this will help!!

Cheers!!!!!

Collection take long time to refresh???

Cause :

A long delay occurs when you click "Refresh" to view the latest membership in a dynamic collection on a System Center Configuration Manager 2007 SP2 site server !!

Reason :

This issue occurs because Collection Evaluator maintains a first-in, first-out (FIFO) queue to handle the collection evaluation requests.

When you click Refresh to view the latest membership of a collection, this request is put at the end of a FIFO queue. If the number of previous requests is very large, Collection Evaluator requires a long time to complete the previous requests. Therefore, a long delay occurs before you view the updated results in the Configuration Manager console.

Solution :

Install SCCM2007-SP2-KB982400-ENU.msi KB.

Pre-Req :

To apply this hotfix, you must have System Center Configuration Manager 2007 Service Pack 2 (SP2) installed.

Cheers!!!! 

Certificates causing registration errors in client files while registering!!!

Senario :

I had a new issue today regarding clients not registering with their MP. The errors I received are below:

ClientIDManagerStartup.log
RegTask: Server rejected registration request: 3

PolicyEvaluator.log
Failed to trigger Machine settings update (80070057)

MP_RegistrationManager.log
Certificate issued to ‘SMS’ has expired.

After seeing the last error stating the certificate had expired I decided to delete the SMS certificates and repair the client. I did this by opening up the MMC and selecting the “Certificates” snapin for the machine with the issue. Once selected, drill down to SMS > Certificates and delete both SMS certificates.



Now all you need to do is repair the SCCM client and it should register correctly with the MP.

Cheers!!!!

SMSCFG.INI missing from client

Q. I was facing one problem in my environment, that I was not able to run the task sequence. I found that SMS Unique Identifier GUID is missing from the SMSCFG.INI file from the client machine. When I add GUID manually Task sequence starts on those client. I was not sure how GUID is missing from all the machine. After long search and communication with IT geeks finally i found the solution.


Soultion :


I found there is a scheduled task running which is deleting files including SMSCFG.ini but sccm client create the file again with less info.

Alternative solution is to repairing the client? or Reinstall it again but this should be last step :)

Cheer!!!!!!!!!!

Move/ change the location of SMS Provider

The SMS Provider is a component of Configuration Manager 2007 primary sites and is used by Configuration Manager consoles to access site database information from the SQL Server hosting the site database.

The SMS Provider is a dynamic-link library file (smsprov.dll) and is installed or moved by running Configuration Manager 2007 Setup. You can install the SMS Provider on the primary site server computer, the computer hosting the site database server, or another computer not hosting the primary site or site database. A server class operating system is required to install the SMS Provider on a computer other than the site server or site database server computers.

Important
Installing the SMS Provider on a virtual SQL Server cluster instance is not supported. You can move the SMS Provider after setup has completed to a different server computer system by starting Configuration Manager Setup from the Start menu (if the SMS Provider is installed on the primary site server) or from the Configuration Manager installation media.

To move the SMS Provider using the Start menu

1. Close any open Configuration Manager console connections to the site server.
2. On the primary site server computer, click Start, click All Programs, click Microsoft System Center, click Configuration Manager 2007, and click ConfigMgr Setup, or navigate to the .\bin\i386 directory of the Configuration Manager 2007 installation media and double-click Setup.exe.
3. Click Next on the Configuration Manager Setup Wizard Welcome page.
4. Click Perform site maintenance or reset this site on the Configuration Manager Setup Wizard Setup Options page.
5. Select Modify SMS Provider configuration on the Configuration Manager Setup Wizard Site Maintenance page.
6. Enter the appropriate installation location for the SMS Provider on the Configuration Manager Setup Wizard SMS Provider Settings Modification page.
7. Configuration Manager Setup performs the SMS Provider reinstallation process.

Software Updates Detection State Unknown

If you are seeing a number of clients at a site that is not local to the SUP returning "Detection State Unknown" open up the scanagent.log on one of those clients and see if there's and error 0x80072efd. In the log you should also see which WSUS server the client is attempting to contact and on what port number. If you installed WSUS in the manner described in the docs this should be port 8530 and 8531. Try to telnet from the client to the WSUS server using the address and port number listed. If you do not get a reply have your network team check the firewall settings to make sure that the client is allowed to connect to the WSUS over the listed port.

HTTP 500 Error at Secondary Site Management Point

Most commonly when I have seen HTTP 500 errors on a management point it’s been a SQL permissions issue. Today I ran across another problem that resulted in HTTP 500 errors when testing a management point on a child secondary site. in an effort to resolve the issue I removed the MP using the console on the central site then I noticed that the change was never reflected at the child primary to which to secondary site reports. I opened the sitectrl.ct0 file at the secondary site and I saw there was a delta change reflecting the removal of the MP however that change was not being sent up to the parent site for some reason. To test I made a copy of the sitectrl.ct0, renamed it to sitectrl.ct2 and copied it to the parent sites hman box. The hman.log showed that the site control file serial number was wrong and the file was rejected.

Editing the site control file manually is very unsupported. This is where you should really call CSS.

Of course I figured it was broken already so I may as well take a chance on it before calling support. I took note of the expected serial number version in the HMAN.log at the primary site. I then stopped the sms executive and site component manager services at the secondary site. Open the site control file in notepad, changed the serial number to the number expected by the primary site and saved the file. Next copy the file and rename the extension to ct2. Copy the renamed file to the hman inbox at the primary site and watch the hman.log. You should see the file process successfully this time.

Wait a few minutes then reinstall the management point from the console at the central site. After you see it’s been installed successfully by viewing the mpsetup.log test again using MPList and MPCert.

Cheers!!!!!!! 

WSUS Offline Update – Installing Windows updates without an Internet connection and WSUS

This was orignally post by Maik Koster . Thanks to him for such a wonderful post.

Today I would like to share one of the handiest tools for servicing Windows systems, if they can’t be updated via WSUS or online at Microsoft Update, or if you for any reason want to install the updates from a CD/DVD/USB or even a share.

It’s called WSUS Offline Update (formerly known as c’t offline Update), created and maintained by Torsten Wittrock. It’s main purpose is to download all critical and security related Updates to a local folder and execute the required ones on a system, without the necessity to be connected to the internet or a working WSUS Server.

It supports Updates for Windows XP, Windows Vista, Windows 7, Server 2003, Server 2003 R2, Server 2008 and Server 2008 R2 both in32 and 64 bit (where applicable), Office 2003, Office 2007 and Office 2010. One can select the required languages, in- or exclude ServicePacks, .Net Frameworks, C++ Runtime libraries, Windows Defenders definitions, Microsoft Security Essentials and so on. Updates can come either from Microsoft Update directly or also from your WSUS Server.

Once downloaded, one can create ISO images per product and language or per language only. Or copy a subset of selectable updates on a USB Stick. Then a second component can be called from each individual computer that shall be updated, either locally or over the network. This will then evaluate the current computer against the available updates and install all missing ones plus a bunch of additional items like Internet Explorer, PowerShell, Windows Defender, .Net Frameworks, etc.
OK, let’s have a quick look on how to do that

Getting the Updates

First, download the most recent version from WSUS Offline Update (http://download.wsusoffline.net/). Be sure to unblock the file and then extract the content to a folder. Can be locally or on a network share. If you place it on a share, be sure to map it with a Drive letter.
Now you want to get the updates and optionally create the Update medias. To do so, start the “UpdateGenerator.exe” from the just extracted folder.



As you can see, there are plenty of options what to download and to create. All downloads will be stored in some subfolders at the location, where you started the application from. So be sure to have some space available. We will go over some of the more important ones a bit later. Also be sure to start the download regularly to always have the latest updates available.

Now if you have selected all the products you would like to download updates for, click on “Start” and the download process will start. It will first get a list of all available updates and then just download the ones that haven’t been downloaded already. Depending on your selection and bandwidth, this can take quite some time.



It will also check for superseded Updates, mark and optionally remove them. It’s also maintaining a list of excluded Updates which can be tweaked to your own needs. See the FAQs in the “doc” folder for more information.

Updating a Client

After the Updates have been downloaded, you an use the created CD/DVD/USB media to update a computer. Optionally it’s also possible to call it over the network, even if that’s not the preferred method and contradicts a bit with the idea of an “Offline” Update . However to do so, just share the Client subfolder and make sure that you map this share with a drive letter on the computer, as the scripts don’t work with a UNC path. Now execute the “UpdateInstaller.exe”. Preferably with Administrative privileges.



The GUI will let you choose only available options. So it might differ depending what you downloaded or have made available on your media and the OS and installed components itself. Interesting to mention here is, that you can tell it to automatically reboot and recall itself as often as required by the Update process. As a side note, the automatic reboot doesn’t work, if you started the process over the network as the temporary account, created for the automatic logon, doesn’t have the appropriate drive mapped. Well, this is the out-of-the-box behavior and as most of the commands are just scripts, it is possible to tweak this to your needs if you really need to have this option available.
However, to start the process, simply click on the “Start” button again and let the magic happen. Just be aware, that it might take some time.

Automation

The whole project has been published under the GNU/GPL and most of its components are vb scripts, batch files or AutoIt scripts. It’s possible to exclude specific Updates, include additional ones, etc. Please see the FAQ (located in the “doc” folder) for some more information on this.
Interesting part here is, that you can also automate the process to keep your medias up to date. In the “cmd” folder you will find a bunch of command line scripts, that you can use for this purpose. E.g. to update your media after each Microsoft Patchday, just create a batch that calls the “DownloadUpdates.cmd” and "CreateISOImage.cmd” (or “CopyToTarget.cmd” for a USB Stick) with the appropriate parameters and schedule it to run on the required dates. Also the execution on the client can be automated as well by either calling the “Update.cmd” file from the root of your media or the “DoUpdate.cmd” from the “cmd” folder. Actually the first one just calls the latter one and as you can see in the screenshot above, also the GUI just calls them with selected parameters.

It is a real benefit to always have a USB Stick available, filled with the latest Updates and ready to execute on any machine whenever needed. Or how about automatically updating your Reference image(s) offline with the latest updates? I will show you how, in the next Blog post 

Cheers!!!!!!!!!

Package is not getting updated on Distribution point.

Imagine the scenario where you find yourself waiting longer then usual for a package to reach a Distribution Point. You have tried a refresh, a removal and every other possible action within the Configmgr Console GUI. Yet, the package never reaches and remains in the "Install Pending" state. Here are 3 nifty logs found in the SMS installation path that will help save you some drops of blood and empower you to find out the problem fast.

DESPOOL.LOG
DISTMGR.LOG
SCHEDULE.LOG

If you see the following entry in the DESPOOL.LOG, the following steps may be able to address your problem.

Received package AAA9999A version 4 SMS_DESPOOLER 9/15/2010 10:11:46 AM 6024 (0x1788)

There is already a newer version of the compressed package for package AAA9999A, discard this one. SMS_DESPOOLER 9/15/2010 10:11:46 AM 6024 (0x1788)

However, when you look at the path and also in the package status, you see that it is not there, and still pending. The above message effectively tells Configmgr there is no need to send the package down since there is a newer one. But this is not true, therefore here is a quick work-around.

It's time to put aside the GUI and go straight to the raw locations of these packages and IDs. It is important to note that prior to attempting this steps, please ensure that the packages are not distributed to the affected distribution point by verifying for example through the GUI.

1. Go to your SMS installation drive of the affected Distribution Point and open up the following folders:
   • SMSPKG
   • SMSPKGSIG
   • SMSSIG$
   • SMS\inboxes\distmgr.box
   • SMS\inboxes\pkginfo.box
2. Search for the packageID in each of the locations and delete them. These will consist of various file extensions i.e. AAA9999A.PKG, .ICO, .NAL, .PCK, .TAR and possibly some deltas as well (i.e. AAA9999A.DLT_x.rf$ etc...). As usual, please exercise caution whenever you do a delete to make sure you know what you are deleting. Check that no sources of the PackageID resides anymore with another search.
3. Send the package back down again to the Distribution Point through the console.
4. Monitor the above 3 logs to see the magic flow. My favourite method is to use Trace32.exe to highlight the PackageID string so that you see it zooming its statuses fast and furious when things start to tinker together. After some time, you should see your packages arrive!

ConfigMgr (SCCM) – New Site to Site data replication flow in SMS 2003 and ConfigMgr 2007 explained

Thanks for Excellent write up on replication process of ConfigMgr in details from Terry McKinney and to Anoop for sharing this  :)

New deep-dive document: Component details and data flow for site-to-site replication in SMS 2003 and Configuration Manager 2007

=====

NOTE: Question marks (???) in the text below indicate random character generation by SMSExcec thread processing.

SMSExec thread component on source site initiates replication request

SMSExecutive thread component that is requesting data replication places the data to be replicated in replmgr.box\outbound\low OR replmgr.box\outbound\normal OR replmgr.box\outbound\ high folder. Low (3), normal (2), and high (1) specify replication priority requested by the SMSExec thread that requests replication.

Replmgr:

Replication Manager (ReplMgr) scans the three folders listed above for incoming data. Replmgr prepares the job source files by combining data files destined for replication to a given site in the \replmgr.box\process\<destinationsitecode>_<priority> folder (i.e., XYZ_2). If there are no pending replication requests to a given site that have the same replication priority, Replmgr implements steps A and B listed below. It there are pending replication requests to that site that have the same replication priority that are already scheduled for replication, data for new request(s) is held in the Replmgr.box\process\<destinationsitecode>_<priority> folder. Data for the new request(s) will remain in the Replmgr.box\process\<destinationsitecode>_<priority> folder until the pending same-priority request completes data replication OR the new replication request(s) reaches 6 hours in age. At this time, Replmgr will implement steps A and B listed below. If a replication job of the same priority and destination site is still pending, ReplMgr implements steps A and B below to create an additional same-priority replication request for that site.

A. Data to be replicated is moved to \replmgr.box\ready\<priority>_??????.<destinationsitecode> (i.e., 2_SKEJFS.XYZ).  This folder is referenced in log files as the "transfer root".

B. ReplMgr then creates a .JOB file in the \Schedule.box folder.

Scheduler:

At the top of the Scheduler process loop (except on service startup) Scheduler activates any pending jobs by completing the following steps:

A. Compresses all files in the transfer root (i.e., \replmgr.box\ready\2_SKEJFS.XYZ) into a single package file and writes this file to \schedule.box\tosend\<job id>.P??.

B. Creates a destination site despooler instruction file in \schedule.box\tosend\<job id>.I?? to be transmitted immediately after the package file created in step A is transmitted.

C. Creates a send request in the \schedule.box\requests folder (<priority>_???<originatingsite>.SRQ) (i.e., 2_5ZKABC.SRQ).

D. Determines if the package and instruction file needs to be routed through an intermediate child site. If so, a routing instruction file is created (RT??????.INS) for the send request.

E. Schedules the send request by moving it into an appropriate sender outbox. Each installed sender type creates its own folder under schedule.box\outboxes. The most common sender outbox is schedule.box\outboxes\LAN.

Sender:

1. Sender transmits the package file and then the instruction file to the remote site by completing the following steps:

A. Renames the send request (<priority>_???<originatingsite>.SRQ) to (<priority>_???<originatingsite>.SRS (changes the filename extension to .SRS)

B. Transmits the package (\schedule.box\tosend\<jobid>.P??) file to the remote site Despoolr.box\receive folder (the SMS_SITE share) and renames it to <sendrequestid>.PCK

C. Transmits the accompanying instruction file (\schedule.box\tosend\<job id>.I??) to the same location and renames it to <sendrequestid>.INS

D. Flags the <priority>_???<originatingsite>.SRS file with a "sending complete" flag.

E. Creates a \schedule.box\<sendrequestid>.DWS (done with sending) file.

Replication component processing at the destination site Despoolr.box\receive folder)

Despoolr:

The Despooler process first checks the signature on the replicated files. If signed correctly, despoolr decompresses the instruction file and implements the instructions contained within that file – to decompress the package into the \replmgr.box\incoming folder in this case.

ReplMgr:

Replication Manager analyzes incoming files and replicates the objects to appropriate inbox folders. The appropriate inbox folder is specified by the component on the source site server that began the replication process. Inbound replication jobs that use transactions must bear a transaction ID that is greater than the existing number for that object type that is contained in the sitecode.trs present on the destination site. If this condition is met, the transaction is considered valid and the inbound replication objects are passed to the destination component/inbox. If this condition is not met, the transaction is considered invalid and the replication objects are discarded by Replication Manager.

Post - replication cleanup on originating site:

Scheduler:

A. Updates the corresponding job status to "complete" when it finds the \<sendrequestid>.DWS during its

processing cycle.

B. Performs cleanup - deletes the related package and instruction files in the \schedule.box\tosend folder

C. Deletes the transfer root folder (i.e., replmgr\ready\2_SKEJFS.XYZ)

D. Marks the send request for deletion

ReplMgr:

After the transfer root has been deleted, pending replication requests with the same priority and destination site that are less than 6 hours in age can be created. Note that if there are existing jobs of the same priority and with the same destination site that are older than 6 hours, ReplMgr will request scheduling an additional replication job of the same priority for replication to that site.

Scheduler:

A. Deletes completed send requests when it finds the associated <job_id>.dws file for that job during its processing cycle.

B. Deletes the completed job files (minimum cycle: once per hour, maximum cycle: once per process loop).

Daily Best Practice for Healthy SCCM server

In order to make sure that you sccm environment should run smoothly always follow the below best practice

Ø  Administrative Checklist for Configuration Manager 2007

1.       Go to the site component and check SMS _SITE_BACKUP Component and last date when it was run and was it successful. I my experience I have seen that even if backup fail the SMS _Site_ Backup will not show it as fail. To be on safer side I recommend checking smsbkg.log on server.

2.       Expand the Site Status and look for error or warning in the site by check Component Status or Site System Status.

3.    Check the Processor :

The processor point status check is a check on the relevant servers Task Management status and the current status of the Processor on that server. If for some reason the processor is running high on utilization then this should be addressed to ensure that the issue is not a serious one.

To do this check the status of that sites Components and Site System Status information as above.

If the process is running ok (hovering between 30 and 60% generally) then a simple green box entry should be added to the Daily Checks spreadsheet as before,

However if there are failings on the processor checks (utilization is running very high into the 90 to 100% and steady) then these should be added into the spreadsheet as red boxes again as before which should also include an inserted comment explaining the issue and what you are doing to resolve the issue.

Important: If the processor is maxing out at around 90 to 100% on Primary site servers, check the following to ensure that is no excessive traffic to and fro the server cross the LAN / WAN

It’s also worth noting that a check on the Primary Site Servers SQL instance will be worth a look; as if SQL itself is struggling to process data quickly enough into the SQL Site database then this will cause the server to on occasions max out on the CPU.

4.       Check the size of SMS folder Structure to make sure that it is not flooding with any error or files.

         SMS inbox size andAlso\AUTH\DDM.BOX

5.       Check the IIS log Files :

Check the properties of the c:\windows\system32\logfiles\W3SVC1 folder

If the size of the folder (contents) exceeds 200Mb, then simply select all but the last 2 log entries (filter the display list by Date modified) and delete the log files. Keep the log files since last week and delete the rest

6.    SCCM Server Disk Space Check : Make sure that server should have 20% minimum disk space if you find that the space is less then just clean up the space to make sure that SCCM should not face any space issue.

7.    SCCM MP Check: To make sure that MP is working fine check the mpcontrol.log and also you can use the MP troubleshooter tool to check the health of MP.

8.    Removing the obsolete Systems: Create the collection with the query to collect all the obsolete systems in the environment.

Note: Always use delete special option while deleting the systems

Troubleshooting SCCM Software Updates

This was origanlly written by Sudheesh from Micorosoft. I thought to just share this good artical with you guys

Software Updates

Providing 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 Server                        SMS_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 / Time                         System         Component Message ID                        Description

Information                        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               30000            User "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