VBScript to get collection schedules

Option Explicit

Dim objFSO : Set objFSO = CreateObject("Scripting.FileSystemObject")
Dim objLogFile : Set objLogFile = objFSO.CreateTextFile("Collections.log")

Dim strSourceServer
strSourceServer   = "XXX"
Dim strSourceSiteCode
strSourceSiteCode = "XXX"

Dim objSourceWMIService
Dim AllCollections
Dim objCollection
Dim strCollectionName
Dim strCollectionComment
Dim schedule
Dim schedtype
Dim bolScheduleAvailable
Dim strRecur
Dim strEvery

Set objSourceWMIService = GetObject("winmgmts://" & strSourceServer & "\root\sms\site_" & strSourceSiteCode)

'objLogFile.WriteLine Now & " start "

'Loop trought all collections exsisting on the source server
Set AllCollections = objSourceWMIService.ExecQuery("SELECT * FROM SMS_Collection WHERE NAME NOT LIKE 'All%' AND NAME NOT LIKE 'Root%'")

For Each objCollection In AllCollections
    strCollectionName    = objCollection.Name
    strCollectionComment = objCollection.Comment

    'objLogFile.WriteLine Now & " - Collection  " & objCollection.Name

    Set objCollection = objSourceWMIService.Get("SMS_Collection='" & objCollection.CollectionID & "'" )

    'Get Collection schedule
    On Error Resume Next
    Set schedule = objCollection.RefreshSchedule(0)

    On Error GoTo 0

    If Err.Number = 424 Then
        objLogFile.WriteLine "Collection has no Schedule  " & objCollection.Name
    ElseIf Err.Number <> 0 Then
        objLogFile.WriteLine "An Error (" & Err.Number & ") occured while getting the Update Schedule from " & objCollection.Name
    Else
        'On Error Resume Next
        schedtype = Schedule.Path_.Class

        Select Case (schedtype)
            Case "SMS_ST_RecurInterval"
                If schedule.MinuteSpan <> 0 Then strRecur = "Minute"
                If schedule.HourSpan <> 0 Then strRecur = "Hour"
                If schedule.DaySpan <> 0 Then strRecur = "Day"

                If schedule.MinuteDuration <> 0 Then strEvery = schedule.MinuteDuration
        If schedule.HourDuration <> 0 Then strEvery = schedule.HourDuration
        If schedule.DayDuration <> 0 Then strEvery = schedule.DayDuration

                    bolScheduleAvailable = True
                    objLogFile.WriteLine objCollection.Name & ",Recurr every " & strEvery & " " &  strRecur & ",Starting " & schedule.StartTime

                Case "SMS_ST_RecurWeekly"

                    If schedule.ForNumberOfWeeks <> 0 Then  strRecur = "Weekly"

                    bolScheduleAvailable = True
                    objLogFile.WriteLine objCollection.Name & ",Recurr every " & strRecur & ",Starting " & schedule.StartTime

                Case "SMS_ST_RecurMonthlyByDate"

            If schedule.ForNumberOfMonths <> 0 Then strRecur = "Monthly"
                    bolScheduleAvailable = True
                    objLogFile.WriteLine objCollection.Name & ",Recurr every " & strRecur & ",Starting " & schedule.StartTime
                Case "SMS_ST_RecurMonthlyByWeekday"

                    Token.StartTime = schedule.StartTime
                    objLogFile.WriteLine Now & " - SMS_ST_RecurMonthlyByWeekday Schedule available " & objCollection.Name

                    bolScheduleAvailable = True

                Case "SMS_ST_NonRecurring"

                    bolScheduleAvailable = True
                    objLogFile.WriteLine Now & " - SMS_ST_NonRecurring Schedule available " & objCollection.Name

                Case Else
                    bolScheduleAvailable = False
                    objLogFile.WriteLine Now & " - Unknown Schedule (skipping) " & objCollection.Name
            End Select

        End If

    Next

    objLogFile.WriteLine Now & " - Finish"
    WScript.Echo "Done"

VBScript Script to Delete Specific SCCM Collections and Associated Advertisements

'need to change the site code in line Set WbemServices = loc.ConnectServer( ,"root\SMS\site_XXX")
'script takes input from a text file collectionslist.txe, having collection names.

Option Explicit
On Error Resume Next

Dim loc

Dim Collection
Dim Collections
Dim strCollection
Dim strCollectionID

Dim Advertisement
Dim Advertisements
Dim objFSO
Dim objFile

Dim WbemServices
Const ForReading = 1

Set loc = CreateObject("WbemScripting.SWbemLocator")

Set WbemServices = loc.ConnectServer( ,"root\SMS\site_XXX")
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objFile = objFSO.OpenTextFile("collectionslist.txt", ForReading)

Do Until objFile.AtEndOfStream
strCollection = objFile.ReadLine

    Set Collections = WbemServices.ExecQuery("select * from SMS_Collection where name like '%" & strCollection & "%'")

    For Each Collection In Collections
        strCollectionID = Collection.CollectionID
        Wscript.Echo "Collection    : " + Collection.Name

        Set Advertisements = WbemServices.ExecQuery("select * from SMS_Advertisement where CollectionID = """ & strCollectionID & """")
       
        For Each Advertisement in Advertisements
            Wscript.Echo "Advertisement : " & Advertisement.AdvertisementName
            Advertisement.Delete_
        Next
    On Error Goto 0
    Collection.Delete_
    Next
Loop
objFile.Close

OSD Step by Step in SCCM 2007

Original link: http://social.technet.microsoft.com/wiki/contents/articles/a-step-by-step-for-using-osd-through-system-center-configuration-manager-2007.aspx

Although the steps required to deploy an OS using Configuration Manager 2007 are available in many places, I decided to create a simple, concise step by step procedure for OSD deployment using SCCM that will hopefully come in handy if you are trying to use the OSD feature in SCCM for the first time.
Preparing the Environment for Configuration Manager OSD
Step 1: Create a user account to be assigned as the Network Access Account:
Note: You can user an existing account or you can configure a new account.
1. On the Start menu, point to Administrative Tools, and then click Active Directory Users and Computers. The Active Directory Users and Computers window appears.
2. Create a new user named Network Access with a password and ensure that the password does not have to be changed at next logon.
3. Close Active Directory Users and Computers.
Note: This account is used by the client to access the Configuration Manager Distribution point when booted under WinPE so make sure the account has the necessary permission for this action.
Step 2: Create a Network Access Account:
1. If not already running, on the Start menu, click ConfigMgr Console. The Configuration Manager Console window appears.
2. In the tree pane, expand Site Database, expand Site Management, expand MCM, expand Site Settings, and then click Client Agents. The list of client agents appears in the results pane.
3. In the result pane, click Computer Client Agent, and then in the Actions pane, click Properties. The Computer Client Agent Properties dialog box appears displaying general properties.
4. After Network Access Account, click Set. The Windows User Account dialog box appears prompting for the account and password to configure as the Network Access Account. In the Name box, enter the Domain\NetworkAccessAccount you created in Step 1. In the Password and Confirm password boxes, type password and then click OK.
5. The Computer Client Agent Properties dialog box appears displaying properties for the Computer Client Agent. Click OK.
Step 3: Create the Configuration Manager package that OSD will use to install the Configuration Manager client after distributing the new operating system image:
1. In the tree pane, expand Site Database, expand Computer Management, expand Software Distribution, and then click Packages.
2. The list of packages for the site appears in the results pane. Notice that there are no packages created at this point.
3. In the Actions pane, click New, and then click Package From Definition. The Create Package from Definition Wizard dialog box appears. Click Next.
4. The Create Package from Definition Wizard Package Definition dialog box appears allowing you to select the package definition file to use. Notice the default package definitions built into Configuration Manager 2007 include the Configuration Manager Client Upgrade package definition.
5. Under Package definition, click Configuration Manager Client Upgrade, and then click Next. The Create Package from Definition Wizard Source Files dialog box appears prompting for source file handling instructions.
6. Click Always obtain files from a source directory, and then click Next. The Create Package from Definition Wizard Source Directory dialog box appears allowing the designation of the source file directory.
7. Click Local drive on the site server, and then click Browse. The Browse For Folder dialog box appears.
8. Click C:\Program Files\Microsoft Configuration Manager\Client, and then click OK. The Create Package from Definition Wizard Source Directory dialog box displays the configured source directory. Click Next.
9. The Create Package from Definition Wizard Summary dialog box appears indicating the wizard is ready to create the package. Click Finish.
10. In the tree pane, expand Packages, expand Microsoft Configuration Manager Client Upgrade, and then click Programs. The programs for the package appear in the results pane. Notice that there is only one program for this package, that being a silent upgrade.
11. In the tree pane, click Distribution Points. The distribution points for this package appear in the results pane. Notice that there are no distribution points assigned to this package yet.
12. In the Actions pane, click New Distribution Points. The New Distribution Points Wizard window appears. Click Next.
13. The New Distribution Points Wizard Copy Package dialog box appears displaying the list of distribution points for the package. Under Distribution points, click the DP you want to use and then click Next.
14. The New Distribution Points Wizard Wizard Completed dialog box appears indicating that the wizard was successfully completed. Click Close.
Step 4: Distribute the boot package:
1. In the tree pane, expand Site Database, expand Computer Management, expand Operating System Deployment, and then click Boot Images. The boot images for the site appear in the results pane. Notice that there are two boot images for x64 and x86 platforms.
2. In the tree pane, expand Boot Images, expand Boot image (x86), and then click Distribution Points. The distribution points for this package appear in the results pane. Notice that there are no distribution points assigned to this boot image yet.
3. In the Actions pane, click New Distribution Points. The New Distribution Points Wizard window appears. Click Next.
4. The New Distribution Points Wizard Copy Package dialog box appears displaying the list of available distribution points for the boot image.
5. Under Distribution points, click the DP you want to use and click Next.
6. The New Distribution Points Wizard Wizard Completed dialog box appears indicating that the wizard has completed successfully. Click Close.
Installing a Configuration Manager PXE Service Point
We need to create PXE service point in the Configuration Manager site. A PXE service point must be installed on a Windows Deployment Server (WDS). To install WDS please follow the steps below. You can have this role running on the same server or you can install it on another server and make that a site server.
Step 1: Install WDS service (For windows 2003 SP2 and later):
1. Got to Add/Remove Programs select Windows Components
2. Select Windows Deployment services and install.
For more information please click on the link http://technet.microsoft.com/en-us/library/cc766320.aspx#BKMK_InstallingWDS .
Note: Make sure that you don’t configure anything right now, just do the install. You also need to grant the site server computer administrative rights to the member server where you are installing the WDS services.
Step 2: Install a remote PXE service point:
1. In the tree pane, expand Site Database, expand Site Management, expand MCM, expand Site Settings, and then click Site Systems. If you are using different server as a PXE then in the tree pane, click Site Systems, and then in the Actions pane click New.
2. A new menu appears. Click Server. The New Site System Server Wizard General dialog box appears. In the Name box, type the member server where WDS is deployed.
3. In the Intranet FQDN box, type FQDN of the server Click Next.
4. The New Site System Server Wizard System Role Selection dialog box appears displaying the list of site system roles that can be assigned to this computer. Under Available roles, select PXE service point, and then click next.
5. A PXE Service Point Configuration message box appears indicating that specific ports will be opened up on this site system to support PXE requests. Click Yes to allow the ports to be opened on the computer.
6. The New Site System Server Wizard PXE - General dialog box appears allowing you to configure the PXE service point. Notice that the default configuration is to allow incoming PXE requests on all network adapters and to require the user to supply a password to initiate installation through the PXE service point.
7. Click to clear Require a password for computers that boot to PXE, and then click Next.
8. The New Site System Server Wizard PXE - Database dialog box appears allowing you to configure access to the database and for the required certificate configuration. Notice that the default configuration is to use the computer account to access the Configuration Manager site database to validate client identity, and to create a self-signed certificate that is valid for one year.
9. Click Next to accept the default configuration. The New Site System Server Wizard Summary dialog box appears indicating that the wizard is ready to create the new site system. Click Next.
10. The New Site System Server Wizard Wizard Completed dialog box appears indicating that the wizard was completed successfully. Click Close.
Step 3: Distribute the boot package to the PXE service point:
1. In the tree pane, expand Site Database, expand Computer Management, expand Operating System Deployment, and then click Boot Images. The list of boot images in the site appears in the results pane. Notice that there are two boot images for various platforms.
2. In the tree pane, expand Boot Images, expand Boot image (x86), and then click Distribution Points.
3. The distribution points for this package appear in the results pane. Notice that the boot has already been distributed to the distribution point (which is running on the site server). You also need to distribute it to the PXE service point.
4. In the Actions pane, click New Distribution Points. The New Distribution Points Wizard window appears. Click Next.
5. The New Distribution Points Wizard Copy Package dialog box appears displaying the list of available distribution points for the boot image. Under Distribution points, click Member\<SERVER>PXEImages$, and then click Next.
6. The New Distribution Points Wizard Wizard Completed dialog box appears indicating that the wizard has completed successfully. 6. Click Close.

Preparing the Operating System Image for Deployment
Step 1: Capturing an image from a Reference Computer Manually:

1. Build the reference computer. The reference computer must meet the following requirements:
   1. The computer must be a member of a workgroup.
   2. The local Administrator password must be blank.
   3. Do not require password complexity in the local system policy.
2. In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Computer Management / Operating System Deployment / Task Sequences. Right-click Task Sequences and then click Create Task Sequence Media. The Create Task Sequence Media wizard will open. Select Capture Media. For more information, see Task Sequence Media Wizard.
3. On the Media Type page specify the type of media you want to use for the capture media. You can specify a USB flash drive, CD, or DVD as the media type. If you specify a USB flash drive make sure the device is connected to the computer so that the necessary files can be written directly to the device.
4. Specify the Media file by first clicking the Browse button and browsing to the location where the media file will be created, and then type the name of the media file that will be created. For CD and DVD media, the capture media .ISO file that is created will be written to the location specified. The .iso image will be copied to the media later. USB files can be written directly to the USB device.
5. Select the boot image that should be associated with the media. Click the Browse button to specify the computer architecture to be targeted with the captured image in the Select a Boot Image dialog box. Boot images must be available on one or more distribution points. For more information on distributing boot images, see Manage Distribution Points (Operating System Deployment). To specify the distribution point that contains the specified boot image, use the drop down list of available distribution points. Click OK.

Note: The boot image selected must be of an architecture that will run on the reference computer hardware.

1. For CD and DVD media, use an appropriate software application to create a bootable CD or bootable DVD containing the .ISO file.
2. Boot the computer into the full operating system and insert the capture media (CD, DVD or USB flash drive).

Note: For all supported operating systems except Windows Vista and Windows Server® 2008, the sysprep folder ( %SystemDrive%\Sysprep ) must be present on the computer before you launch the capture CD.

1. Run the Image Capture Wizard and identify the location for the captured image to be stored.

Step 2: Create the image package:
1. In the tree pane, expand Site Database, expand Computer Management, expand Operating System Deployment, and then click Operating System Images. The operating system images for the site appear in the results pane. Notice that there are no images yet. You need to create an operating system image from an image file previously created.
2. In the Actions pane, click Add Operating System Image. The Add Operating System Image Wizard Data Source dialog box appears allowing you to specify the image file to use.
3. In the Path box, type \\<Servername>\Images\Vista.wim and then click Next.
4. In the Name box, type Windows Vista. In the Version box, type 1.0. In the Comment box, type Windows Vista image and then click Next.
5. The Add Operating System Image Wizard Summary dialog box appears indicating that the operating system image is ready to be created. Click Next.
6. The Add Operating System Image Wizard Wizard Completed dialog box appears indicating that the wizard completed successfully. Click Close.
Step 3: Add the image to a distribution point:
1. In the tree pane, expand Site Database, expand Computer Management, Operating System Deployment, expand Operating System Images, and then expand Windows Vista. The Windows Vista image items appear in the tree pane.
2. In the tree pane, click Distribution Points, and then in the Actions pane, click New Distribution Points. The New Distribution Points Wizard window appears. Click Next.
3. The New Distribution Points Wizard Copy Package dialog box appears displaying the list of available distribution points for the OS image. Under Distribution points, click the DP that you want to use and then click Next.
Note: You do not need to distribute the operating system image to the PXE service point. The client will retrieve the image from the distribution point.
4. The New Distribution Points Wizard Wizard Completed dialog box appears indicating that the wizard has completed successfully. Click Close.
Note: This will take a little bit of time to complete.
Preparing for Bare Metal OS Deployment
You now need to prepare the site for a bare metal client deployment through PXE boot. You will begin by creating a collection that you can then advertise the operating system image installation task sequence to. You will then add the bare metal client to this collection.
Step 1: Create a bare metal system collection:
1. In the tree pane, expand Site Database, expand Computer Management, and then click Collections. The collections in the site appear in the results pane. In the Actions pane, click New Collection.
2. The New Collection Wizard General dialog box appears allowing you to name the collection. In the Name box, type Bare Metal Systems and then click Next.
3. The New Collection Wizard Membership Rules dialog box appears allowing you to add membership rules for the collection. You will manually add the client to the collection when you create the client later in this exercise, so no membership rule is needed for our lab.
4. Click Next to not add any membership rules. A Bare Metal Systems Collection message box appears indicating that there will not be any members of the collection until a membership rule is added. Click OK.
5. The New Collection Wizard Advertisements dialog box appears displaying the advertisements targeted to this collection. Notice that currently there are no programs advertised to this collection. Later in this lab you will advertise a task sequence to the collection. Click Next.
6. The New Collection Wizard Security dialog box appears allowing you to configure security rights for the collection. Click Next to use the default security rights.
7. The collection is created. When complete, the New Collection Wizard Confirmation dialog box appears indicating that the collection was created successfully. Click Close.
8. The collections in the site appear in the results pane. Notice that the Bare Metal Systems collection now appears. You will add a manual record for the bare metal client to this collection in an upcoming procedure.
Step 2: Create a bare metal client record:
1. In the tree pane, expand Site Database, expand Computer Management, expand Operating System Deployment, and then click Computer Association. The computer associations for the site appear in the results pane. Notice that by default there are no computer associations.
2. In the Actions pane, click Import Computer Information. The Import Computer Information Wizard Select Source dialog box appears prompting to import systems from a file or to import a single computer.
3. Click Import single computer, and then click Next. The Import Computer Information Wizard Single Computer dialog box appears allowing you to configure properties to identify the computer being added. Notice that you must add a computer name and a MAC address or SMBIOS GUID.
4. In the Computer Name box, type Bare_Metal .The Computer Name supplied is only for display in the collection. It does not have to be what the client will be named when it is installed.
5. In the MAC address box, type the MAC address. Notice that after supplying a MAC address, the requirement for a SMBIOS GUID is no longer valid. You only have to supply one or the other, not both. Click Next.
6. The Import Computer Information Wizard Data Preview dialog box appears displaying the properties of the bare metal system to be added. Click Next.
7. The Import Computer Information Wizard Choose Target Collection dialog box appears allowing you to designate the target collection for the new system. Click Add computers to the following collection, and then click Browse.
8. The Browse Collection dialog box appears displaying all the collections in the site. Under Collections, click Bare Metal Systems, and then click OK.
9. The Import Computer Information Wizard Choose Target Collection dialog box appears displaying the designated collection to add the bare metal system to. Click Next.
10. The Import Computer Information Wizard Summary dialog box appears indicating the wizard is ready to import the single computer. Click Next.
11. The Import Computer Information Wizard Wizard Completed dialog box appears indicating that the wizard completed successfully. Click Close.
Note: The computer associations for the site appear in the results pane. Notice that the new computer does not appear. This is because there is no association with an existing system for a user state migration. The new computer was created however.
12. In the tree pane, expand Site Database, expand Computer Management, expand Collections, and then click Bare Metal Systems. The members of the Bare Metal Systems collection appear in the results pane. Notice that Bare Metal appears as a member of the collection.
Deploying an OS Image Using Configuration Manager 2007
Step 1: Create an image deployment task sequence:
1. In the tree pane, expand Site Database, expand Computer Management, expand Operating System Deployment, and then click Task Sequences. The task sequences for the site appear in the results pane. Notice that there are no task sequences yet. You need to create a task sequence that will allow you to deploy an operating system image.
2. In the Actions pane, click New, and then click Task Sequence. The New Task Sequence Wizard Create a New Task Sequence window appears prompting for the type of task sequence to create: to deploy an image package, build a reference system or a custom task sequence.
3. Click Next to create a task sequence that will install an existing image package. The New Task Sequence Wizard Task Sequence Information dialog box appears prompting for the name and description for the task sequence, as well as which boot image to use.
4. In the Task sequence name box, type Install Vista for PXE in the Comment box, type Installs Windows Vista image in a PXE deployment and then click Browse. The Select a Boot Image dialog box appears displaying the boot images available.
5. Click Boot image (x86) and then click OK. The New Task Sequence Wizard Task Sequence Information dialog box appears displaying the name and description of the task sequence, as well as the boot image to use. Click Next.
6. The New Task Sequence Wizard Install the Windows Operating System dialog box appears prompting for the image package, licensing, and administrator password to use. Click Browse.
7. The Select an Operating System Image dialog box appears displaying the image packages available. Click Windows Vista 1.0 en-US and then click OK.
8. The New Task Sequence Wizard Install the Windows Operating System dialog box appears displaying the image package to use. Notice that the default action is to install all images in the package. Also notice that the default configuration is to partition and format the target computer’s hard disk. That likely is required in a bare metal scenario, which we are performing.
9. Click Next to not designate a product key, not specify a licensing mode, and to disable the local administrator account on the target system. The New Task Sequence Wizard Configure the Network dialog box appears prompting whether the target system will join a workgroup or domain.
10. Click Join a domain, and then after Domain, click Browse. The Select a Domain dialog box appears displaying the available domains. Under Domains, click Domain name and then click OK.
11. The New Task Sequence Wizard Configure the Network dialog box appears displaying the domain the target client should join after installation of the Vista image. Notice that you can also configure a specific OU for the client to join. Click Set.
12. The Windows User Account dialog box appears prompting for the account and password to use to join the new computer to the domain. In the Name box, enter the account that has rights in the domain to add systems to the domain.
13. In the Password and Confirm password boxes, type the password and then click OK. The New Task Sequence Wizard Configure the Network dialog box appears displaying the domain the target client should join after installation of the Vista image as well as the account that will be used to add the client to the domain. Click Next.
14. The New Task Sequence Wizard Install the ConfigMgr client dialog box appears prompting for the package to use for the Configuration Manager client installation, which occurs after the OS image has been deployed. Click Browse. The Select a Package dialog box appears displaying the packages available.
15. Click Microsoft Configuration Manager Client Upgrade 4.0 All and then click OK. The New Task Sequence Wizard Install the ConfigMgr client dialog box appears displaying the package and program to use for the Configuration Manager client installation. Notice that the installation properties include the FSP parameter to allow the new client deployment to report deployment state messages. Click Next.
16. The New Task Sequence Wizard Configure State Migration dialog box appears prompting for configuration of the user state capture process. Since we are deploying through PXE, there is no user or computer state to capture in our scenario. Click to clear Capture user settings. Click to clear Capture network settings. Click to clear Capture Microsoft Windows settings, then click Next.
17. The New Task Sequence Wizard Include Updates in Image dialog box appears prompting for deployment of software updates. Notice that the default configuration is to not deploy software updates with the image.
18. Click Next to not deploy any software updates for our lab. The New Task Sequence Wizard Install Software Packages dialog box appears prompting for deployment of software packages after the image has been installed. This is where you’d configure to add in additional Configuration Manager packages, such as Microsoft Office 2007.
19. Click Next to not deploy any software packages in the lab environment. The New Task Sequence Wizard Summary dialog box appears indicating the wizard has been completed and is ready to create the task sequence. Click Next.
20. The task sequence is created, and then the New Task Sequence Wizard Wizard Completed dialog box appears indicating that the task sequence was successfully created. Click Close.
21. The task sequences for the site appear in the results pane. Notice that there is now one task sequence in the site.
Step 2: Modify the task sequence:
1. In the results pane, click Install Vista for PXE, and then in the Actions pane, click Edit. The Install Vista for PXE Task Sequence Editor dialog box appears displaying the task sequence steps.
2. In the left pane, click Partition Disk. The Partition Disk action properties are displayed in the right pane. Under Volume, click (Primary), and then click Properties (the icon resembles a piece of paper). The Partition Properties dialog box appears displaying the default configuration of the partition action. Notice that the default action is to not perform a quick format.
3. Click Quick format, and then click OK. The Install Vista for PXE Task Sequence Editor dialog box appears displaying the task sequence steps. Click OK.
4. The task sequences for the site appear in the results pane. Notice that there is only one task sequence in the site.
Step 3: Advertise the task sequence:
1. In the results pane, click Install Vista for PXE. The task sequence properties appear at the bottom of the results pane. Click the References tab.
2. The list of packages used by this task sequence appears in the results pane. Notice that there are three packages used by this task sequence. Start Windows Explorer and verify that each of the three packages is available on the distribution point. Do not proceed until the three packages are available on the distribution point.
3. In the Actions pane of the Configuration Manager Console under Install Vista for PXE, click Advertise. The New Advertisement Wizard General dialog box appears prompting for general properties of the advertisement. Notice that the name defaults to the task sequence name.
4. After Collection, click Browse. The Browse Collection dialog box appears. Click Bare Metal Systems, and then click OK.
5. The New Advertisement Wizard General dialog box appears prompting for general properties of the advertisement. To make this task sequence available through PXE, you must configure that option.
6. Click Make this task sequence available to boot media and PXE, and then click Next. The New Advertisement Wizard Schedule dialog box appears prompting for the advertisement schedule. To make the PXE boot scenario unattended, you need to create an assignment for the task sequence.
7. If you do not make the advertisement an assignment, the task sequence will not execute automatically and you’ll be required to select the task sequence on the bare metal system – thus no longer an unattended deployment.
8. Click New (the toolbar icon resembles a starburst). The Assignment Schedule dialog box appears.
9. Click OK to create a schedule for the current date and time. The New Advertisement Wizard Schedule dialog box appears displaying the advertisement schedule. Click Next.
10. The New Advertisement Wizard Distribution Points dialog box appears prompting for how the task sequence will access any content that is required. Click Next to allow content to be downloaded when needed by the task sequence, to not allow access to remote distribution points, and require the use of protected distribution points if available. The New Advertisement Wizard Interaction dialog box appears prompting for how the user will interact with the task sequence.
11. Click Next to not allow the user to run the program as an optional program prior to the mandatory schedule and to display progress of the task sequence. The New Advertisement Wizard Security dialog box appears prompting for security rights for the task sequence.
12. Click Next to use the default security rights. The New Advertisement Wizard Summary dialog box appears indicating the wizard has been completed successfully and is ready to create the advertisement. Click Next.
13. The advertisement is created, and then the New Advertisement Wizard Wizard Completed dialog box appears indicating the advertisement was successfully created.
14. Verify that all processes were completed successfully, and then click Close. The task sequences for the site appear in the results pane. Notice that there is one task sequence in the site. Your site is now ready to deploy a new operating system image through a network boot scenario.
Installing the Image at the Target Client Computer
Step 1: Install the operating system image
1. Start the Bare Metal Client Machine.
2. The image startup is resumed. The boot image should get an IP address from the DHCP server (which is running on the site server) and then get the advertised task sequence from the management point (which is running on the site server). This will include retrieving the boot image from the WDS server (which is running on the PXE service point).
3. An Installation Progress message box appears as the Windows Vista operating system image is installed on the bare metal client computer.
4. It will take a number of minutes for the Windows Vista image to be deployed to the computer (typically around 60 minutes or so). It will automatically restart in the middle of this process. Notice that Windows PE is started and initialized to install the image. After the system reboots into Window PE, the Installation Properties message box appears displaying the progress bar for installing the image.
Eventually your image will be installed and you’ll be well on your way to rolling out images throughout your company with just a few clicks of the button.
Note: This information was originally contributed by Sudheesh Narayanaswamy, Configuration Manager Support Engineer, on the Configuration Manager Support Team blog.

RegKeyToMof v2.6

Mark Cochrane's RegKeyToMof v2.6

Update: changed the version to 2.6

Original article at : http://myitforum.com/cs2/blogs/skissinger/archive/2011/02/18/mark-cochrane-s-regkeytomof-v2-6.aspx


Mark has updated his excellent RegKeytoMof utility for custom regkey MOF edit creations. The coolest part about it is a better method of pulling in registry keys from the 64-bit registry section.
I'm in love with it, because of how the end result is that there is only 1 table and 1 view in your database, making report writing that much easier (fewer joins).
Major kudos go to Jonas Hettich for figuring out the intricasies of how this type of mof edit works.
This blog entry will step through how to use RegKeytoMof to create a (fictitious) custom mof entry for "ABCStuff"
Below is a screen shot of the registry of a x86 computer, and a x64 computer.

How to Use RegKeytoMof:

1. While on either the x64 computer or the x86 computer, launch "RegKeyToMofv2.5.exe"
2. Browse to "Software\ABCStuff"
3. Change the ClassGroup and ClassName to be values you want
   a. For me, I always change the group to be "CUSTOM", however, if you work for ACME Corporation, you may want to change it to "ACMECorp" for example.  It's really simply a label.
   b. Change the ClassName to be something unique, and no spaces is recommended.  For this edit, I'm going to use "ABCStuff"
4. Check the box about "Enable 64bits"

Screen shot of the work so far:

Now we have a very, very close base.  Most of the time you could copy the contents of the tabs "SCCM Configuration.mof" and "SCCM sms_def.mof" directly to the bottom of your inboxes\clifiles.src\hinv files, and be golden.
However, for this particular mof edit, I made sure to add in some special cases, that might trip you up.  As mentioned, most of the time you won't have these special cases.
Three things:

1. I'm asking for the value of the (Default) regkey.  that requires a manual edit.
2. one of the values I want "MultiSZIWant", contains multiple strings.  In order to pull that information in nicely, there is another manual edit.
3. one of the values I want "BinaryIwant", also needs a manual edit.

5. To adjust for the (Default) regkey, a label is required.  There are 6 places to put in that label; 4 places in configuration.mof, and 2 in sms_def.mof.
6. To adjust for the multiple string values, there is 4 places to put in braces [], 2 places in configuration.mof, and 2 in sms_def.mof.
7. To adjust for the binary value, there is 4 places to put in braces [], 2 places in configuration.mof, and 2 in sms_def.mof.
Attached is the completed mof edit. 
Notes: I decided to label the default value "TheDefault"  so search for that in the files to see how that was accomplished.  For the multi-values, search for the [] to see where those should be placed.
8. Now follow the wiki, on updating your mof files and confirming the edit worked:
9. Now that you have data in your database, here's a sample sql query, and the resulting report.
 
To interpret what that means...
   9a. workstation1 is a 32-bit OS, and as such, does not have WMI provider architechture that would try to report on 64-bit regkeys (this line in the
sms_def.mof edit:  SMS_Context_1("__ProviderArchitecture=64|uint32").  For that reason, there is only 1 row of data returned for workstation1.
   9b. workstation2 is a 64-bit OS, and does have both providerarchitechtures, 32 and 64.  So it will *attempt* to report on registry keys in both areas, that's why there are two rows of data, but the attributes that correspond to registry keys are null for those that don't exist, and contain data for the ones that do exist.
From a collection query creation standpoint, or from a reporting standpoint, having to look only in 1 location when you design your SQL or WQL queries is a very cool and timesaving thing.  Not only to you, but your database has 1 less table, view, and stored procedures

Lif of all SCCM log files - client/server

The client logs are located in the %WINDIR%\System32\CCM\Logs folder or %WINDIR%\SysWOW64\CCM\Logs (for x64 OS).
The SCCM server log files are located in the <INSTALL_PATH>\Logs or SMS_CCM\Logs folder. IIS logs can be found in %WINDIR%\System32\logfiles\W3SVC1 folder.

Client Log Files

• CAS - Content Access Service. Maintains the local package cache.
• Ccmexec.log - Records activities of the client and the SMS Agent Host service.
• CertificateMaintenance.log - Maintains certificates for Active Directory directory service and management points.
• ClientIDManagerStartup.log - Creates and maintains the client GUID.
• ClientLocation.log - Site assignment tasks.
• ContentTransferManager.log - Schedules the Background Intelligent Transfer Service (BITS) or the Server Message Block (SMB) to download or to access SMS packages.
• DataTransferService.log - Records all BITS communication for policy or package access.
• Execmgr.log - Records advertisements that run.
• FileBITS.log - Records all SMB package access tasks.
• Fsinvprovider.log (renamed to FileSystemFile.log in all SMS 2003 Service Packs) - Windows Management Instrumentation (WMI) provider for software inventory and file collection.
• InventoryAgent.log - Creates discovery data records (DDRs) and hardware and software inventory records.
• LocationServices.log - Finds management points and distribution points.
• Mifprovider.log - The WMI provider for .MIF files.
• Mtrmgr.log - Monitors all software metering processes.
• PolicyAgent.log - Requests policies by using the Data Transfer service.
• PolicyAgentProvider.log - Records policy changes.
• PolicyEvaluator.log - Records new policy settings.
• Remctrl.log - Logs when the remote control component (WUSER32) starts.
• Scheduler.log - Records schedule tasks for all client operations.
• Smscliui.log - Records usage of the Systems Management tool in Control Panel.
• StatusAgent.log - Logs status messages that are created by the client components.
• SWMTRReportGen.log - Generates a usage data report that is collected by the metering agent. (This data is logged in Mtrmgr.log.)

Server Log Files

• Ccm.log - Client Configuration Manager tasks.
• Cidm.log - Records changes to the client settings by the Client Install Data Manager (CIDM).
• Colleval.log - Logs when collections are created, changed, and deleted by the Collection Evaluator.
• Compsumm.log - Records Component Status Summarizer tasks.
• Cscnfsvc.log - Records Courier Sender confirmation service tasks.
• Dataldr.log - Processes Management Information Format (MIF) files and hardware inventory in the Configuration Manager 2007 database.
• Ddm.log - Saves DDR information to the Configuration Manager 2007 database by the Discovery Data Manager.
• Despool.log - Records incoming site-to-site communication transfers.
• Distmgr.log - Records package creation, compression, delta replication, and information updates.
• Hman.log - Records site configuration changes, and publishes site information in Active Directory Domain Services.
• Inboxast.log - Records files that are moved from the management point to the corresponding SMS\INBOXES folder.
• Inboxmgr.log - Records file maintenance.
• Invproc.log - Records the processing of delta MIF files for the Dataloader component from client inventory files.
• Mpcontrol.log - Records the registration of the management point with WINS. Records the availability of the management point every 10 minutes.
• Mpfdm.log - Management point component that moves client files to the corresponding SMS\INBOXES folder.
• MPMSI.log - Management point .msi installation log.
• MPSetup.log - Records the management point installation wrapper process.
• Ntsvrdis.log - Configuration Manager 2007 server discovery.
• Offermgr.log - Records advertisement updates.
• Offersum.log - Records summarization of advertisement status messages.
• Policypv.log - Records updates to the client policies to reflect changes to client settings or advertisements.
• Replmgr.log - Records the replication of files between the site server components and the Scheduler component.
• Rsetup.log - Reporting point setup log.
• Sched.log - Records site-to-site job and package replication.
• Sender.log - Records files that are sent to other child and parent sites.
• Sinvproc.log - Records client software inventory data processing to the site database in Microsoft SQL Server.
• Sitecomp.log - Records maintenance of the installed site components.
• Sitectrl.log - Records site setting changes to the Sitectrl.ct0 file.
• Sitestat.log - Records the monitoring process of all site systems.
• Smsdbmon.log - Records database changes.
• Smsexec.log - Records processing of all site server component threads.
• Smsprov.log - Records WMI provider access to the site database.
• SMSReportingInstall.log - Records the Reporting Point installation. This component starts the installation tasks and processes configuration changes.
• SMSSHVSetup.log - Records the success or failure (with failure reason) of installing the System Health Validator point.
• Srvacct.log - Records the maintenance of accounts when the site uses standard security.
• Statmgr.log - Writes all status messages to the database.
• Swmproc.log - Processes metering files and maintains settings.

Admin Console Log Files

• RepairWizard.log - Records errors, warnings, and information about the process of running the Repair Wizard.
• ResourceExplorer.log - Records errors, warnings, and information about running the Resource Explorer.
• SMSAdminUI.log - Records the local Configuration Manager 2007 console tasks when you connect to Configuration Manager 2007 sites.

Management Point Log Files

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

Mobile Device Management Log Files

• DmClientHealth.log - Records the GUIDs of all the mobile device clients that are communicating with the Device Management Point.
• DmClientRegistration.log - Records registration requests from and responses to the mobile device client in Native mode.
• DmpDatastore.log - Records all the site database connections and queries made by the Device Management Point.
• DmpDiscovery.log - Records all the discovery data from the mobile device clients on the Device Management Point.
• DmpFileCollection.log - Records mobile device file collection data from mobile device clients on the Device Management Point.
• DmpHardware.log - Records hardware inventory data from mobile device clients on the Device Management Point.
• DmpIsapi.log - Records mobile device communication data from device clients on the Device Management Point.
• dmpMSI.log - Records the MSI data for Device Management Point setup.
• DMPSetup.log - Records the mobile device management setup process.
• DmpSoftware.log - Records mobile device software distribution data from mobile device clients on the Device Management Point.
• DmpStatus.log - Records mobile device status messages data from mobile device clients on the Device Management Point.
• FspIsapi.log - Records Fallback Status Point communication data from mobile device clients and client computers on the Fallback Status Point.

Mobile Device Client Log Files

• DmCertEnroll.log - Records certificate enrollment data on mobile device clients.
• DMCertResp.htm (in \temp) - Records HTML response from the certificate server when the mobile device Enroller program requests a client authentication certificate on mobile device clients.
• DmClientSetup.log - Records client setup data on mobile device clients.
• DmClientXfer.log - Records client transfer data for Windows Mobile Device Center and ActiveSync deployments.
• DmCommonInstaller.log - Records client transfer file installation for setting up mobile device client transfer files on client computers.
• DmInstaller.log - Records whether DMInstaller correctly calls DmClientSetup and whether DmClientSetup exits with success or failure on mobile device clients.
• DmInvExtension.log - Records Inventory Extension file installation for setting up Inventory Extension files on client computers.
• DmSvc.log - Records mobile device management service data on mobile device clients.

Operating System Deployment Log Files

• CCMSetup.log - Provides information about client-based operating system actions.
• CreateTSMedia.log - Provides information about task sequence media when it is created. This log is generated on the computer running the Configuration Manager 2007 administrator console.
• DriverCatalog.log - Provides information about device drivers that have been imported into the driver catalog.
• MP_ClientIDManager.log - Provides information about the Configuration Manager 2007 management point when it responds to Configuration Manager 2007 client ID requests from boot media or PXE. This log is generated on the Configuration Manager 2007 management point.
• MP_DriverManager.log - Provides information about the Configuration Manager 2007 management point when it responds to a request from the Auto Apply Driver task sequence action. This log is generated on the Configuration Manager 2007 management point.
• MP_Location.log - Provides information about the Configuration Manager 2007 management point when it responds to request state store or release state store requests from the state migration point. This log is generated on the Configuration Manager 2007 management point.
• Pxecontrol.log - Provides information about the PXE Control Manager.
• PXEMsi.log - Provides information about the PXE service point and is generated when the PXE service point site server has been created.
• PXESetup.log - Provides information about the PXE service point and is generated when the PXE service point site server has been created.
• Setupact.log Setupapi.log Setuperr.log Provide information about Windows Sysprep and setup logs.
• SmpIsapi.log - Provides information about the state migration point Configuration Manager 2007 client request responses.
• Smpmgr.log - Provides information about the results of state migration point health checks and configuration changes.
• SmpMSI.log - Provides information about the state migration point and is generated when the state migration point site server has been created.
• Smsprov.log - Provides information about the SMS provider.
• Smspxe.log - Provides information about the Configuration Manager 2007 PXE service point.
• SMSSMPSetup.log - Provides information about the state migration point and is generated when the state migration point site server has been created.
• Smsts.log - General location for all operating system deployment and task sequence log events.
• TaskSequenceProvider.log - Provides information about task sequences when they are imported, exported, or edited.
• USMT Log loadstate.log - Provides information about the User State Migration Tool (USMT) regarding the restore of user state data.
• USMT Log scanstate.log - Provides information about the USMT regarding the capture of user state data.

Network Access Protection Log Files

• Ccmcca.log - Logs the processing of compliance evaluation based on Configuration Manager NAP policy processing and contains the processing of remediation for each software update required for compliance.
• CIAgent.log - Tracks the process of remediation and compliance. However, the software updates log file, *Updateshandler.log - provides more informative details on installing the software updates required for compliance.
• locationservices.log - Used by other Configuration Manager features (for example, information about the client’s assigned site) but also contains information specific to Network Access Protection when the client is in remediation. It records the names of the required remediation servers (management point, software update point, and distribution points that host content required for compliance), which are also sent in the client statement of health.
• SDMAgent.log - Shared with the Configuration Manager feature desired configuration management and contains the tracking process of remediation and compliance. However, the software updates log file, Updateshandler.log, provides more informative details about installing the software updates required for compliance.
• SMSSha.log - The main log file for the Configuration Manager Network Access Protection client and contains a merged statement of health information from the two Configuration Manager components: location services (LS) and the configuration compliance agent (CCA). This log file also contains information about the interactions between the Configuration Manager System Health Agent and the operating system NAP agent, and also between the Configuration Manager System Health Agent and both the configuration compliance agent and the location services. It provides information about whether the NAP agent successfully initialized, the statement of health data, and the statement of health response.

System Health Validator Point Log Files

• Ccmperf.log -Contains information about the initialization of the System Health Validator point performance counters.
• SmsSHV.log - The main log file for the System Health Validator point; logs the basic operations of the System Health Validator service, such as the initialization progress.
• SmsSHVADCacheClient.log - Contains information about retrieving Configuration Manager health state references from Active Directory Domain Services.
• SmsSHVCacheStore.log - Contains information about the cache store used to hold the Configuration Manager NAP health state references retrieved from Active Directory Domain Services, such as reading from the store and purging entries from the local cache store file. The cache store is not configurable.
• SmsSHVRegistrySettings.log - Records any dynamic changes to the System Health Validator component configuration while the service is running.
• SmsSHVQuarValidator.log - Records client statement of health information and processing operations. To obtain full information, change the registry key LogLevel from 1 to 0 in the following location:HKLM\SOFTWARE\Microsoft\SMSSHV\Logging\@GLOBAL

Desired Configuration Management Log Files

• ciagent.log - Provides information about downloading, storing, and accessing assigned configuration baselines.
• dcmagent.log - Provides high-level information about the evaluation of assigned configuration baselines and desired configuration management processes.
• discovery.log - Provides detailed information about the Service Modeling Language (SML) processes.
• sdmagent.log - Provides information about downloading, storing, and accessing configuration item content.
• sdmdiscagent.log - Provides high-level information about the evaluation process for the objects and settings configured in the referenced configuration items.

Wake On LAN Log Files

• Wolmgr.log - Contains information about wake-up procedures such as when to wake up advertisements or deployments that are configured for Wake On LAN.
• WolCmgr.log - Contains information about which clients need to be sent wake-up packets, the number of wake-up packets sent, and the number of wake-up packets retried.

Software Updates Site Server Log Files

• ciamgr.log - Provides information about the addition, deletion, and modification of software update configuration items.
• distmgr.log - Provides information about the replication of software update deployment packages.
• objreplmgr.log - Provides information about the replication of software updates notification files from a parent to child sites.
• PatchDownloader.log - Provides information about the process for downloading software updates from the update source specified in the software updates metadata to the download destination on the site server.
• replmgr.log - Provides information about the process for replicating files between sites.
• smsdbmon.log - Provides information about when software update configuration items are inserted, updated, or deleted from the site server database and creates notification files for software updates components.
• SUPSetup - Provides information about the software update point installation. When the software update point installation completes, Installation was successful is written to this log file.
• WCM.log - Provides information about the software update point configuration and connecting to the Windows Server Update Services (WSUS) server for subscribed update categories, classifications, and languages.
• WSUSCtrl.log - Provides information about the configuration, database connectivity, and health of the WSUS server for the site.
• wsyncmgr.log -Provides information about the software updates synchronization process.

WSUS Server Log Files

• Change.log - Provides information about the WSUS server database information that has changed.
• SoftwareDistribution.log - Provides information about the software updates that are synchronized from the configured update source to the WSUS server database.

Software Updates Client Computer Log Files

• CAS.log - Provides information about the process of downloading software updates to the local cache and cache management.
• CIAgent.log - Provides information about processing configuration items, including software updates.
• LocationServices.log - Provides information about the location of the WSUS server when a scan is initiated on the client.
• PatchDownloader.log - Provides information about the process for downloading software updates from the update source to the download destination on the site server. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.
• PolicyAgent.log - Provides information about the process for downloading, compiling, and deleting policies on client computers.
• PolicyEvaluator - Provides information about the process for evaluating policies on client computers, including policies from software updates.
• RebootCoordinator.log - Provides information about the process for coordinating system restarts on client computers after software update installations.
• ScanAgent.log - Provides information about the scan requests for software updates, what tool is requested for the scan, the WSUS location, and so on.
• ScanWrapper - Provides information about the prerequisite checks and the scan process initialization for the Inventory Tool for Microsoft Updates on Systems Management Server (SMS) 2003 clients.
• SdmAgent.log - Provides information about the process for verifying and decompressing packages that contain configuration item information for software updates.
• ServiceWindowManager.log - Provides information about the process for evaluating configured maintenance windows.
• smscliUI.log - Provides information about the Configuration Manager Control Panel user interactions, such as initiating a Software Updates Scan Cycle from the Configuration Manager Properties dialog box, opening the Program Download Monitor, and so on.
• SmsWusHandler - Provides information about the scan process for the Inventory Tool for Microsoft Updates on SMS 2003 client computers.
• StateMessage.log - Provides information about when software updates state messages are created and sent to the management point.
• UpdatesDeployment.log - Provides information about the deployment on the client, including software update activation, evaluation, and enforcement. Verbose logging shows additional information about the interaction with the client user interface.
• UpdatesHandler.log - Provides information about software update compliance scanning and about the download and installation of software updates on the client.
• UpdatesStore.log - Provides information about the compliance status for the software updates that were assessed during the compliance scan cycle.
• WUAHandler.log - Provides information about when the Windows Update Agent on the client searches for software updates.
• WUSSyncXML.log - Provides information about the Inventory Tool for the Microsoft Updates synchronization process. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.

Windows Update Agent Log File

• WindowsUpdate.log - Provides information about when the Windows Update Agent connects to the WSUS server and retrieves the software updates for compliance assessment and whether there are updates to the agent components.

List of all SCCM log files - client/server

The client logs are located in the %WINDIR%\System32\CCM\Logs folder or %WINDIR%\SysWOW64\CCM\Logs (for x64 OS).
The SCCM server log files are located in the <INSTALL_PATH>\Logs or SMS_CCM\Logs folder. IIS logs can be found in %WINDIR%\System32\logfiles\W3SVC1 folder.

Client Log Files

• CAS - Content Access Service. Maintains the local package cache.
• Ccmexec.log - Records activities of the client and the SMS Agent Host service.
• CertificateMaintenance.log - Maintains certificates for Active Directory directory service and management points.
• ClientIDManagerStartup.log - Creates and maintains the client GUID.
• ClientLocation.log - Site assignment tasks.
• ContentTransferManager.log - Schedules the Background Intelligent Transfer Service (BITS) or the Server Message Block (SMB) to download or to access SMS packages.
• DataTransferService.log - Records all BITS communication for policy or package access.
• Execmgr.log - Records advertisements that run.
• FileBITS.log - Records all SMB package access tasks.
• Fsinvprovider.log (renamed to FileSystemFile.log in all SMS 2003 Service Packs) - Windows Management Instrumentation (WMI) provider for software inventory and file collection.
• InventoryAgent.log - Creates discovery data records (DDRs) and hardware and software inventory records.
• LocationServices.log - Finds management points and distribution points.
• Mifprovider.log - The WMI provider for .MIF files.
• Mtrmgr.log - Monitors all software metering processes.
• PolicyAgent.log - Requests policies by using the Data Transfer service.
• PolicyAgentProvider.log - Records policy changes.
• PolicyEvaluator.log - Records new policy settings.
• Remctrl.log - Logs when the remote control component (WUSER32) starts.
• Scheduler.log - Records schedule tasks for all client operations.
• Smscliui.log - Records usage of the Systems Management tool in Control Panel.
• StatusAgent.log - Logs status messages that are created by the client components.
• SWMTRReportGen.log - Generates a usage data report that is collected by the metering agent. (This data is logged in Mtrmgr.log.)

Server Log Files

• Ccm.log - Client Configuration Manager tasks.
• Cidm.log - Records changes to the client settings by the Client Install Data Manager (CIDM).
• Colleval.log - Logs when collections are created, changed, and deleted by the Collection Evaluator.
• Compsumm.log - Records Component Status Summarizer tasks.
• Cscnfsvc.log - Records Courier Sender confirmation service tasks.
• Dataldr.log - Processes Management Information Format (MIF) files and hardware inventory in the Configuration Manager 2007 database.
• Ddm.log - Saves DDR information to the Configuration Manager 2007 database by the Discovery Data Manager.
• Despool.log - Records incoming site-to-site communication transfers.
• Distmgr.log - Records package creation, compression, delta replication, and information updates.
• Hman.log - Records site configuration changes, and publishes site information in Active Directory Domain Services.
• Inboxast.log - Records files that are moved from the management point to the corresponding SMS\INBOXES folder.
• Inboxmgr.log - Records file maintenance.
• Invproc.log - Records the processing of delta MIF files for the Dataloader component from client inventory files.
• Mpcontrol.log - Records the registration of the management point with WINS. Records the availability of the management point every 10 minutes.
• Mpfdm.log - Management point component that moves client files to the corresponding SMS\INBOXES folder.
• MPMSI.log - Management point .msi installation log.
• MPSetup.log - Records the management point installation wrapper process.
• Ntsvrdis.log - Configuration Manager 2007 server discovery.
• Offermgr.log - Records advertisement updates.
• Offersum.log - Records summarization of advertisement status messages.
• Policypv.log - Records updates to the client policies to reflect changes to client settings or advertisements.
• Replmgr.log - Records the replication of files between the site server components and the Scheduler component.
• Rsetup.log - Reporting point setup log.
• Sched.log - Records site-to-site job and package replication.
• Sender.log - Records files that are sent to other child and parent sites.
• Sinvproc.log - Records client software inventory data processing to the site database in Microsoft SQL Server.
• Sitecomp.log - Records maintenance of the installed site components.
• Sitectrl.log - Records site setting changes to the Sitectrl.ct0 file.
• Sitestat.log - Records the monitoring process of all site systems.
• Smsdbmon.log - Records database changes.
• Smsexec.log - Records processing of all site server component threads.
• Smsprov.log - Records WMI provider access to the site database.
• SMSReportingInstall.log - Records the Reporting Point installation. This component starts the installation tasks and processes configuration changes.
• SMSSHVSetup.log - Records the success or failure (with failure reason) of installing the System Health Validator point.
• Srvacct.log - Records the maintenance of accounts when the site uses standard security.
• Statmgr.log - Writes all status messages to the database.
• Swmproc.log - Processes metering files and maintains settings.

Admin Console Log Files

• RepairWizard.log - Records errors, warnings, and information about the process of running the Repair Wizard.
• ResourceExplorer.log - Records errors, warnings, and information about running the Resource Explorer.
• SMSAdminUI.log - Records the local Configuration Manager 2007 console tasks when you connect to Configuration Manager 2007 sites.

Management Point Log Files

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

Mobile Device Management Log Files

• DmClientHealth.log - Records the GUIDs of all the mobile device clients that are communicating with the Device Management Point.
• DmClientRegistration.log - Records registration requests from and responses to the mobile device client in Native mode.
• DmpDatastore.log - Records all the site database connections and queries made by the Device Management Point.
• DmpDiscovery.log - Records all the discovery data from the mobile device clients on the Device Management Point.
• DmpFileCollection.log - Records mobile device file collection data from mobile device clients on the Device Management Point.
• DmpHardware.log - Records hardware inventory data from mobile device clients on the Device Management Point.
• DmpIsapi.log - Records mobile device communication data from device clients on the Device Management Point.
• dmpMSI.log - Records the MSI data for Device Management Point setup.
• DMPSetup.log - Records the mobile device management setup process.
• DmpSoftware.log - Records mobile device software distribution data from mobile device clients on the Device Management Point.
• DmpStatus.log - Records mobile device status messages data from mobile device clients on the Device Management Point.
• FspIsapi.log - Records Fallback Status Point communication data from mobile device clients and client computers on the Fallback Status Point.

Mobile Device Client Log Files

• DmCertEnroll.log - Records certificate enrollment data on mobile device clients.
• DMCertResp.htm (in \temp) - Records HTML response from the certificate server when the mobile device Enroller program requests a client authentication certificate on mobile device clients.
• DmClientSetup.log - Records client setup data on mobile device clients.
• DmClientXfer.log - Records client transfer data for Windows Mobile Device Center and ActiveSync deployments.
• DmCommonInstaller.log - Records client transfer file installation for setting up mobile device client transfer files on client computers.
• DmInstaller.log - Records whether DMInstaller correctly calls DmClientSetup and whether DmClientSetup exits with success or failure on mobile device clients.
• DmInvExtension.log - Records Inventory Extension file installation for setting up Inventory Extension files on client computers.
• DmSvc.log - Records mobile device management service data on mobile device clients.

Operating System Deployment Log Files

• CCMSetup.log - Provides information about client-based operating system actions.
• CreateTSMedia.log - Provides information about task sequence media when it is created. This log is generated on the computer running the Configuration Manager 2007 administrator console.
• DriverCatalog.log - Provides information about device drivers that have been imported into the driver catalog.
• MP_ClientIDManager.log - Provides information about the Configuration Manager 2007 management point when it responds to Configuration Manager 2007 client ID requests from boot media or PXE. This log is generated on the Configuration Manager 2007 management point.
• MP_DriverManager.log - Provides information about the Configuration Manager 2007 management point when it responds to a request from the Auto Apply Driver task sequence action. This log is generated on the Configuration Manager 2007 management point.
• MP_Location.log - Provides information about the Configuration Manager 2007 management point when it responds to request state store or release state store requests from the state migration point. This log is generated on the Configuration Manager 2007 management point.
• Pxecontrol.log - Provides information about the PXE Control Manager.
• PXEMsi.log - Provides information about the PXE service point and is generated when the PXE service point site server has been created.
• PXESetup.log - Provides information about the PXE service point and is generated when the PXE service point site server has been created.
• Setupact.log Setupapi.log Setuperr.log Provide information about Windows Sysprep and setup logs.
• SmpIsapi.log - Provides information about the state migration point Configuration Manager 2007 client request responses.
• Smpmgr.log - Provides information about the results of state migration point health checks and configuration changes.
• SmpMSI.log - Provides information about the state migration point and is generated when the state migration point site server has been created.
• Smsprov.log - Provides information about the SMS provider.
• Smspxe.log - Provides information about the Configuration Manager 2007 PXE service point.
• SMSSMPSetup.log - Provides information about the state migration point and is generated when the state migration point site server has been created.
• Smsts.log - General location for all operating system deployment and task sequence log events.
• TaskSequenceProvider.log - Provides information about task sequences when they are imported, exported, or edited.
• USMT Log loadstate.log - Provides information about the User State Migration Tool (USMT) regarding the restore of user state data.
• USMT Log scanstate.log - Provides information about the USMT regarding the capture of user state data.

Network Access Protection Log Files

• Ccmcca.log - Logs the processing of compliance evaluation based on Configuration Manager NAP policy processing and contains the processing of remediation for each software update required for compliance.
• CIAgent.log - Tracks the process of remediation and compliance. However, the software updates log file, *Updateshandler.log - provides more informative details on installing the software updates required for compliance.
• locationservices.log - Used by other Configuration Manager features (for example, information about the client’s assigned site) but also contains information specific to Network Access Protection when the client is in remediation. It records the names of the required remediation servers (management point, software update point, and distribution points that host content required for compliance), which are also sent in the client statement of health.
• SDMAgent.log - Shared with the Configuration Manager feature desired configuration management and contains the tracking process of remediation and compliance. However, the software updates log file, Updateshandler.log, provides more informative details about installing the software updates required for compliance.
• SMSSha.log - The main log file for the Configuration Manager Network Access Protection client and contains a merged statement of health information from the two Configuration Manager components: location services (LS) and the configuration compliance agent (CCA). This log file also contains information about the interactions between the Configuration Manager System Health Agent and the operating system NAP agent, and also between the Configuration Manager System Health Agent and both the configuration compliance agent and the location services. It provides information about whether the NAP agent successfully initialized, the statement of health data, and the statement of health response.

System Health Validator Point Log Files

• Ccmperf.log -Contains information about the initialization of the System Health Validator point performance counters.
• SmsSHV.log - The main log file for the System Health Validator point; logs the basic operations of the System Health Validator service, such as the initialization progress.
• SmsSHVADCacheClient.log - Contains information about retrieving Configuration Manager health state references from Active Directory Domain Services.
• SmsSHVCacheStore.log - Contains information about the cache store used to hold the Configuration Manager NAP health state references retrieved from Active Directory Domain Services, such as reading from the store and purging entries from the local cache store file. The cache store is not configurable.
• SmsSHVRegistrySettings.log - Records any dynamic changes to the System Health Validator component configuration while the service is running.
• SmsSHVQuarValidator.log - Records client statement of health information and processing operations. To obtain full information, change the registry key LogLevel from 1 to 0 in the following location:HKLM\SOFTWARE\Microsoft\SMSSHV\Logging\@GLOBAL

Desired Configuration Management Log Files

• ciagent.log - Provides information about downloading, storing, and accessing assigned configuration baselines.
• dcmagent.log - Provides high-level information about the evaluation of assigned configuration baselines and desired configuration management processes.
• discovery.log - Provides detailed information about the Service Modeling Language (SML) processes.
• sdmagent.log - Provides information about downloading, storing, and accessing configuration item content.
• sdmdiscagent.log - Provides high-level information about the evaluation process for the objects and settings configured in the referenced configuration items.

Wake On LAN Log Files

• Wolmgr.log - Contains information about wake-up procedures such as when to wake up advertisements or deployments that are configured for Wake On LAN.
• WolCmgr.log - Contains information about which clients need to be sent wake-up packets, the number of wake-up packets sent, and the number of wake-up packets retried.

Software Updates Site Server Log Files

• ciamgr.log - Provides information about the addition, deletion, and modification of software update configuration items.
• distmgr.log - Provides information about the replication of software update deployment packages.
• objreplmgr.log - Provides information about the replication of software updates notification files from a parent to child sites.
• PatchDownloader.log - Provides information about the process for downloading software updates from the update source specified in the software updates metadata to the download destination on the site server.
• replmgr.log - Provides information about the process for replicating files between sites.
• smsdbmon.log - Provides information about when software update configuration items are inserted, updated, or deleted from the site server database and creates notification files for software updates components.
• SUPSetup - Provides information about the software update point installation. When the software update point installation completes, Installation was successful is written to this log file.
• WCM.log - Provides information about the software update point configuration and connecting to the Windows Server Update Services (WSUS) server for subscribed update categories, classifications, and languages.
• WSUSCtrl.log - Provides information about the configuration, database connectivity, and health of the WSUS server for the site.
• wsyncmgr.log -Provides information about the software updates synchronization process.

WSUS Server Log Files

• Change.log - Provides information about the WSUS server database information that has changed.
• SoftwareDistribution.log - Provides information about the software updates that are synchronized from the configured update source to the WSUS server database.

Software Updates Client Computer Log Files

• CAS.log - Provides information about the process of downloading software updates to the local cache and cache management.
• CIAgent.log - Provides information about processing configuration items, including software updates.
• LocationServices.log - Provides information about the location of the WSUS server when a scan is initiated on the client.
• PatchDownloader.log - Provides information about the process for downloading software updates from the update source to the download destination on the site server. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.
• PolicyAgent.log - Provides information about the process for downloading, compiling, and deleting policies on client computers.
• PolicyEvaluator - Provides information about the process for evaluating policies on client computers, including policies from software updates.
• RebootCoordinator.log - Provides information about the process for coordinating system restarts on client computers after software update installations.
• ScanAgent.log - Provides information about the scan requests for software updates, what tool is requested for the scan, the WSUS location, and so on.
• ScanWrapper - Provides information about the prerequisite checks and the scan process initialization for the Inventory Tool for Microsoft Updates on Systems Management Server (SMS) 2003 clients.
• SdmAgent.log - Provides information about the process for verifying and decompressing packages that contain configuration item information for software updates.
• ServiceWindowManager.log - Provides information about the process for evaluating configured maintenance windows.
• smscliUI.log - Provides information about the Configuration Manager Control Panel user interactions, such as initiating a Software Updates Scan Cycle from the Configuration Manager Properties dialog box, opening the Program Download Monitor, and so on.
• SmsWusHandler - Provides information about the scan process for the Inventory Tool for Microsoft Updates on SMS 2003 client computers.
• StateMessage.log - Provides information about when software updates state messages are created and sent to the management point.
• UpdatesDeployment.log - Provides information about the deployment on the client, including software update activation, evaluation, and enforcement. Verbose logging shows additional information about the interaction with the client user interface.
• UpdatesHandler.log - Provides information about software update compliance scanning and about the download and installation of software updates on the client.
• UpdatesStore.log - Provides information about the compliance status for the software updates that were assessed during the compliance scan cycle.
• WUAHandler.log - Provides information about when the Windows Update Agent on the client searches for software updates.
• WUSSyncXML.log - Provides information about the Inventory Tool for the Microsoft Updates synchronization process. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.

Windows Update Agent Log File

• WindowsUpdate.log - Provides information about when the Windows Update Agent connects to the WSUS server and retrieves the software updates for compliance assessment and whether there are updates to the agent components.

Solution to problem : ERROR ExecMethod(): Failed to execute AppCreate2.

If a package gets stuck in the "Install Retrying" state at a BITS-enabled ditribution point.
 
And you see the following error message logged in the Microsoft Configuration Manager\Logs\distmgr.log on the server:
"ERROR ExecMethod(): Failed to execute AppCreate2. error = The service cannot be started, either because it is disabled or because it has no enabled devices associated with it."
It might be because of the "COM+ System Application" service is set to anything other then automatic startup. It may be set by a group policy or it could have been set manually.
More info can be found here: http://support.microsoft.com/kb/917485