Edit the .VMC file in Notepad and add the following 

<integration>
    <microsoft> 
        <components>
            <host_time_sync>
                <enabled type="boolean">false</enabled>
            </host_time_sync>
        </components>

Close notepad and save the .VMC file. Start the virtual machine.

1. Install Windows 2003 Cluster

2. Install SQL 2000/2005 Cluster

3. By default, Windows will not register SQL Server virtual name in Active Directory, for successfully installing SCCM 2007 on Clustered SQL Server, you must register it. Go to step 4

4. Run setspn.exe (you can download it from Microsoft download center:http://www.microsoft.com/downloads/details.aspx?FamilyID=5fd831fd-ab77-46a3-9cfe-ff01d29e5c46&displaylang=en) utility as below:

setspn MSSQLSvc/SQLSERVER1:1433 

SQLSERVER1 is your SQL Server virtual name

setspn MSSQLSvc/SQLSERVER1.contoso.com:1433

SQLSERVER1.contoso.com is FQDN for SQL Server virtual name

5. Add computer account for installing SCCM 2007 to local administrators group on every SQL cluster node.

6. Add user account for installing SCCM 2007 to local administrators group on every SQL cluster node.

7. Restart computer for installing SCCM 2007, and logon with user account for setup

8. Launch SCCM 2007 installer, conduct a normal setup.

This came from a blog post by lxchen

The process always comes up so here is the link http://technet.microsoft.com/en-us/library/bb633121.aspx

How to move the SCOM database:   http://technet.microsoft.com/en-us/library/cc540384.aspx

How to move the datawarehouse: http://technet.microsoft.com/en-us/library/cc540368.aspx

Other useful SCOM procedures: http://technet.microsoft.com/en-us/library/cc540402.aspx

Moving the SCCM database:  http://technet.microsoft.com/en-us/library/bb680707.aspx and http://technet.microsoft.com/en-us/library/bb632383.aspx

http://blogs.technet.com/smsandmom/archive/2008/07/22/opsmgr-2007-the-operations-manager-32-bit-agent-is-supported-on-64-bit-operating-systems.aspx

Monitoring SMS Activity

You can use Performance Monitor utility to track various processes on a Windows system in real time. The utility uses a graphical display that you can use to view current data, or log data. You can specify specific elements or components that should be tracked. You can determine resource usage by monitoring trends.  

With Performance Monitor, objects, counters and instances are used to monitor the system. An object is a collection of counters which are associated with a system resource or service. As the object executes a function, its associated counters are updated. A counter represents data for a particular component of the system or service. Each object has a set of counters. An instance refers to the incident of multiple performance objects of the identical type on a computer. An object can have one or multiple instances.

The objects most commonly used to monitor network activity are listed below:

• Browser object, monitors the Browser service for the domain or the workgroup
• Cache object, monitors disk cache usage
• Memory object, monitors physical and virtual memory performance
• Objectsobject, monitors the events, processes and threads on the computer as data is collected.
• Paging File object, monitors page file usage
• Physical Disk object, monitors the hard disks
• Process object, monitors the processes running on the computer
• Processorobject, monitors the processors on the system.
• Server object, monitors items such as bytes, sessions, pool paged usage, and pool non-paged usage.
• System object, monitors counters associated with system hardware and software
• Thread object, monitors threads running in the system

When you install SMS 2.0, a number of SMS specific counters are added in Performance Monitor, and are displayed when the SMS site server is started. In addition to using SMS specific performance counters, there are a number of other objects and counters that should be used to monitor system performance, and identify resource and processing bottlenecks.

The subsystems which should be monitored when monitoring system performance are listed below:

• Memory subsystem
• Network subsystem
• Processor subsystem
• Processes subsystem
• Disk subsystem

It is recommended that you use the following Performance Monitor objects and counters to monitor overall SMS system performance, detect disk usage issues, and identify resource and processing bottlenecks:

• Memory\Committed Bytes:This counter indicates the number of committed bytes of virtual memory on the system, and should be monitored together with the Memory\Available Bytes counter if you suspect that a memory leak exists.
• Memory\Available Bytes: The counter indicates what your available memory capacity is. To efficiently run a server, you need to have at least 4MB of memory available. When the memory drops below 4MB, you might need to immediately add more memory.
• Memory\Pages/Sec: With a recommended counter threshold of 20, this counter indicates the rate at which pages are written to disk or read from disk. The counter should generally be beneath 20.
• Network Interface\Bytes Total/sec; Bytes Sent/sec; Bytes Received/sec: These counters indicate the manner in which your network adapters are performing in relation to network traffic.
• Physical Disk\% Disk Time; Physical Disk\ Avg. Disk Queue Length: A memory shortage would exist if an increase in queue length is not followed by a decrease in the Memory\ Page Read/Sec counter value. System performance is typically satisfactory if the Physical Disk\% is equal to, or lower than 80 percent.
• Physical Disk\ Current Disk Queue Length: The counter indicates the number of requests which are in queue for disk access. The counters should be consistently at 1.5 to 2 times the number of spindles which comprise of the physical disk.
• Physical Disk\ Disk Reads/Sec and Disk Writes/Sec: These counters show the speed at which data is written to disk and read from disk. The information of these counters could assist you in more efficiently balancing the load of your servers. A lengthy delay could be indicative of a hard disk issue. When usage is close to the defined transfer rate of the physical disk, you might need to consider decreasing the load of the server. You could also upgrade to RAID.
• Processor\% Processor Time: This counter should be tracked if you want to detect a process which is utilizing over 85 percent of the processor time. In this case, you might have to consider either upgrading the processor, or installing an additional processor.
• Processor\% User Time: This counter indicates the non-idle processor time percentage which takes place in user mode. If the value of the counter is constantly high, consider upgrading the processor, or installing an additional processor.
• Processor\ Interrupts/Sec: This counter shows the number of interrupts which are being received from devices. An increase in the counter’s value should be accompanied by an increase in system activity. If not, you could have an existing hardware issue that needs to be resolved.
• SQL Server\ ache Hit Ratio: Shows the number of times that SQL Server requests were resolved using the SQL Server cache instead of querying the SQL databases.
• Server\Bytes Total/Sec: This counter indicates how busy the server is, and displays the number of bytes which the server has sent to and received from the network. A drastic increase in this counter value could indicate that you need to add more memory.
• Server Work Queues\Queue Length: The counter shows what the queue length of the Server Work queue is. An acceptable value for this counter is four. If there are constantly over four items in the queue, it could be indicative of processor congestion.
• System\ Processor Queue Length: This counter shows the number of requests waiting in queue to be processed. If you constantly have a queue length of over 10 for a processor, you may have an existing bottleneck.

The SMS specific performance objects and counters added when you install SMS are listed here:

• SMS Discovery Data Manager object: The associated counters are:
  • DDRs Processed/minute; indicates the number of discovery data records (DDRs) that Discovery Data Manager processed in the last minute.
  • Total Bad DDRs Processed; indicates the number of invalid DDRs processed by the Discovery Data Manager in the existing session.
  • Total DDRs Enqueued; indicates how many discovery data records are in the input queue of the Discovery Data Manager. The processed discovery data records are not included.
  • Total DDRs Processed; indicates the total number of DDRs processed by the Discovery Data Manager in the existing session.
• SMS Executive Thread States object: The associated counters are:
  • Running Thread Count; indicates the number of running SMS threads.
  • Sleeping Thread Count; specifies the number of threads blocked in Yield functions - pending conditions defined by the blocked threads.
  • Yielding Thread Count; specifies the number of threads blocked in Yield functions – cannot run because the running threads need to be limited.
• SMS In-Memory Queues object: The associated counters are:
  • Total Objects Dequeued; indicates the total number of objects added to the queue by a specific component since the source and destination components were last started.
  • Total Objects Enqueued; indicates the total number of objects which the destination component removed from the queue since the source and destination components were last started.
• SMS Inventory Data Loader object: The associated counters are:
  • MIFs Processed/minute; indicates the total number of inventory records, Management Information Format (MIF) files, processed by the Inventory Data Loader in the last minute.
  • Total Bad MIFs Processed; represents the total number of invalid inventory records processed by the Inventory Data Loader in this session.
  • Total MIFs Enqueued; specifies the number of inventory records in the input queue of the Inventory Data Loader.
  • Total MIFs Processed; indicates the total number of inventory records, Management Information Format (MIF) files, processed by the Inventory Data Loader in the current session.
• SMS Software Inventory Processor object: The associated counters are:
  • SINVs Processed/minute; indicates the total number of software inventory records (SINVs) processed by the Software Inventory Processor in the last minute.
  • Total Bad SINVs Processed; represents the total number of invalid SINVs processed by the Software Inventory Processor in this session.
  • Total SINVs Enqueued; specifies the number of SINVs in the input queue of the Software Inventory Processor.
  • Total SINVs Processed; indicates the total number of SINVs processed by the Software Inventory Processor in the current session.
• SMS Standard Sender object: The associated counters are:
  • Average Bytes/sec; represents the average throughput of the sender for all SMS sites or for a specific site.
  • Current Bytes being Sent; indicates the current number of bytes that sending threads are trying to write to all SMS sites or to a specific SMS site.
  • Sending Thread Count; indicates the number of threads currently sending to the destination.
  • Total Bytes Attempted; specifies the number of bytes that the specific sender has tried to send, as from the time when it started running.
  • Total Bytes Failed; indicates the number of bytes that the specific sender failed to send, as from the time when it started running.
  • Total Bytes Sent; represents the total number of bytes which the sender has successfully sent to all SMS sites or to a specific SMS site.
• SMS Status Messages object: The associated counters are:
  • Corrupt; represents the total number of corrupted status message files that the Status Message Manager received from the Status Manager inbox, from when the Status Message Manager was last started.
  • Processed/sec; indicates the number of status messages which the Status Message Manager received, from when the Status Message Manager was last started.
  • Replicated at High Priority; indicates the number of status messages which the Status Message Manager replicated to the parent site through high priority, from when the Status Message Manager was last started.
  • Replicated at Low Priority; indicates the number of status messages which the Status Message Manager replicated to the parent site through low priority, from when the Status Message Manager was last started.
  • Replicated at Normal Priority; indicates the number of status messages which the Status Message Manager replicated to the parent site through normal priority, from when the Status Message Manager was last started.
  • Reported To Application Event Log; indicates the number of status messages which the Status Message Manager reported to the Windows application event log, from when the Status Message Manager was last started.
  • Written To SMS Database; indicates the number of status messages which the Status Message Manager has written to the SMS site database, from when the Status Message Manager was last started.

The Health Monitor utility, HealthMon, is a component in SMS that you can use to obtain a view of the status a Windows based computer. Health Monitor utilizes the objects and counters of Performance Monitor to determine status threshold levels and to collect gather data. With Health Monitor, the threshold levels are called monitoring policies. You have to though manually install the utility. The HealthMon Agent must be installed on each computer system that you want to monitor.

The Health Monitor objects and their associated counters are listed here:

• Exchange Server object; contains the MSEXCHANGEDS Service Started, MSEXCHANGEIS Service Started, MSEXCHANGEMTA Service Started, and MSEXCHANGESA Service Started counters.
• Fault object contains the Pool Non-Paged Failures, Pool Paged Failures, and Sessions Errored Out counters.
• IIS Server object contains the IIS Service Started counter.
• Logical Disk object contains the Percent Free Disk Space counter.
• Memory object; contains the Available Memory Bytes, Pages Per Second, Page Reads Per Second, Percent Committed Bytes to Limit, and Pool Non-Paged Bytes counters.
• Network Interface object contains the Excessive Network Traffic Bytes Total/Sec counter.
• Paging File object contains the Percent Peak Usage and Percent Usage counters.
• Physical Disk object contains the Disk Queue Length, Diskperf Driver Started, and Percent Disk Time counters.
• Process object; contains the Interrupts Per Second and Percent Total System Time counters.
• Security object; contains the Errors Access Permission and Errors Logon counters.
• Server Work Queues object; contains the Context Blocks Queued/Sec and Processor Queue Length counters.
• SMS object; contains the SMS_Executive Service Started, SMS_Site_Component_Manager Service Started, and SMS_SQL_Monitor Service Started counters.
• SNA Server object; contains the Host Connection Status and SNABASE Service Started counters.
• SQL Server object; contains the MSDTC Service Started and MSSQL Server Service Started counters.

You can use the SMS Service Manager to monitor and control the status of SMS components:

• Started
• Stopped
• Paused
• Resumed

The SMS Service Manager provides a view of the following information:

• SMS components and services running on the SMS site server.
• SMS components and services running on each SMS site system.

The SMS Trace utility can be used to display and view SMS log file content. With the SMS Trace utility, you can open and view multiple log files at the same time. You can also search and select text. The log file view displayed in the SMS Trace utility is also dynamically updated as the log file changes. This means that all new log file entries are displayed without you having to reopen the file. The SMS Trace utility is not automatically installed when you install the SMS site server. You have to manually install the utility.

The SMS 2.0 installation CD-ROM contains a number of troubleshooting tools located beneath the \SUPPORT\RESKIT directory which you can utilize for the following tasks:

• Manage the site hierarchy and the site database.
• Manage and examine inventory and software distribution
• Examine client computer discovery data
• Manage and remove client components
• Configure the Remote Tools Client Agent
• Examine the log files and to schedule files

How to create a Performance Monitor chart

1. Open Performance Monitor.
2. Click the Edit menu and then click Add To Chart.
3. The Add To Chart dialog box opens.
4. In the Computer box, provide the name of the system being monitored. Click the Browse button to locate the system name.
5. In the Object drop-down list box, choose the object.
6. In the Counter list box, specify the counter.
7. In the Instance box, specify the instance.
8. Use the Color, Scale, Width and Style drop-down list boxes to specify the desired settings for the chart lines.
9. Click the Add button to start the charting process.

How to create a Performance Monitor log

1. Open Performance Monitor.
2. Click the View menu and then select Log.
3. The Performance Monitor Log window opens.
4. Click the Edit menu and select Add To Log.
5. The Add To Log dialog box opens.
6. Specify each particular object that you want to collect information for in the Objects list and then click Add.
7. After all the required objects are added, click Done.
8. The Performance Monitor Log window is displayed.
9. Click the Options menu and then click Log.
10. The Log Options dialog box opens.
11. Specify the name for the log file.
12. Specify where the log file should be stored.
13. Specify the update interval.
14. Click the Start Log button to start collecting the required data.
15. The Performance Monitor Log window is displayed.
16. Check the File Size box to monitor the log file size.
17. Once the desired data has been collected, click the Options menu and then click Log.
18. When the Log Options dialog box opens, click the Stop Log button.
19. To save the log file, click the Options menu and then click Log.
20. When the Log Options dialog box opens, click the Save button.

How to create a chart using log file data

1. Open Performance Monitor.
2. Click the Options menu and then click Data.
3. The Data From dialog box dialog box opens.
4. Provide the name of the log file and then click OK.
5. Click the Edit menu and then click Add To Chart from the shortcut menu.
6. The Add To Chart dialog box opens.
7. Use the list of available objects and their associated counters to create the log chart.

How to add the systems to monitor in the Health Monitor console

1. Open the Health Monitor console. If this is the first time that you are going to use Health Monitor to monitor systems, then no monitored systems will appear in the Health Monitor console.
2. In the console tree, right-click Monitored Systems and select New and then System from the shortcut menu.
3. The New Monitored System dialog box opens.
4. In the textbox, provide the name of the system which you want to monitor.
5. Click OK.
6. In the console tree of the Health Monitor console, expand the mew monitored system entry that you created to display the components status and events status of the system.

How to configure Health Monitor

1. Open the Health Monitor console.
2. Right-click the monitored system that you want to configure and then select Properties from the shortcut menu.
3. The System Properties dialog box opens.
4. On the General tab, select the components which you want to monitor by selecting the checkbox alongside each component which should be enabled.
5. Click OK.

How to use the SMS Service Manager

1. Open the SMS Administrator console.
2. Expand the Tools node.
3. Select the SMS Service Manager node.
4. Click the Action menu, select All Tasks and then select Start SMS Service Manager.
5. In the SMS Service Manager, the SMS site components for the site are listed using two methods:
   • The Components node contains all components for the site.
   • The Servers node contains the components listed according to site system.
6. For the components that are displayed in the details pane of the SMS Service Manager, you can sort them in ascending order or in descending order.

How to view log files in SMS Trace

1. Navigate to the Systems Management Server program group and then start the SMS Trace utility.
2. The SMS Tracer window opens.
3. Click the File menu and then click Open.
4. The Open dialog box opens.
5. Choose the log file thats content you want to view, and then click OK.
6. The SMS Tracer window displays the contents of the log file.

Info from a good article at http://www.tech-faq.com/monitoring-sms.shtml

http://blogs.technet.com/smsandmom/archive/2008/10/30/creating-custom-reports-by-using-configuration-manager-2007-sql-views.aspx

You have set the required permissions in the security rights area in the SMS/SCCM console but you are still getting "access is denied" when you open the MMC?  Make sure that you added the user/group the local Distributed COM Users group on the site server.  Everyone remembers the SMS Admins group but the Distributed COM group gets missed. 

SCCM version of a great SMS tool.  http://smsclictr.sourceforge.net/smsclictrv2/

' Setup a connection to the local provider.

Set swbemLocator = CreateObject("WbemScripting.SWbemLocator")

Set swbemServices= swbemLocator.ConnectServer(".", "root\sms")

Set providerLoc = swbemServices.InstancesOf("SMS_ProviderLocation")

For Each Location In providerLoc

    If location.ProviderForLocalSite = True Then

        Set swbemServices = swbemLocator.ConnectServer(Location.Machine, "root\sms\site_" + Location.SiteCode)

        Exit For

    End If

Next

Set swbemContext = CreateObject("WbemScripting.SWbemNamedValueSet")

swbemContext.Add "SessionHandle", swbemServices.ExecMethod("SMS_SiteControlFile", "GetSessionHandle").SessionHandle

Call DeleteCollectionRules(swbemServices, "BLB0000D")

Sub DeleteCollectionRules(connection, existingCollectionID)

    Dim instCollection

    Dim RuleSet

    Dim Rule

    ' Get a collection using the existingCollectionID variable passed in.   

    Set instCollection = connection.Get("SMS_Collection.CollectionID='" & existingCollectionID & "'")

    'Get the array of embedded SMS_CollectionRule objects.

    RuleSet = instCollection.CollectionRules

    'Delete all membership rules in the collection.

    For Each Rule In RuleSet

        instCollection.DeleteMembershipRule Rule

    Next

    'Refresh the collection members to reflect any deletions.

    'The False parameter value tells the method not to refresh subcollections.

    instCollection.RequestRefresh False

End Sub

Create a .vbs file called getcomputername.vbs or something like that.  Add these commands to the file:

set env = CreateObject("Microsoft.SMS.TSEnvironment")

Name = inputbox("Enter the name for the new computer" ,"Prompt for Computer Name:",env("_SMSTSMachineName"),400,0)

env("OSDComputerName") = Name

Create an SCCM package and point the package source to the source folder that you stored the .vbs file in.  You don’t need to create a program item, just the package.  Add it to the DPs.

Edit your OSD task sequence and add a task to “Run Command Line”.   For the name use something like “Get Computer Name”.  For the command line use “cscript.exe getcomputername.vbs”  (get rid of the quotes).  Select the Package option and choose the package you built in the previous step.

I added my Get Computer Name task sequence after the Partition Disk 0 task but I’m not sure it matters. 

Advertise the task sequence

Updating my original post of Jan 2009 to reflect updated information about the CM RAP.

Microsoft PFE has had a ConfigMgr Health Check available for about about a year and half and we are now in the final stages of converting that delivery into a RAP (Risk Assessment Program).  The offical name will be "CMRAP (Risk and Health Assessment Program for Configuration Manager)".  This delivery should be released around holiday 2010. If your organization needs a CMRAP performed please contact your MS TAM.

Also here is a link to the Facebook page for the Microsoft RAP program:  http://facebook.com/MicrosoftRAPs

Linking to mwiles' post:  http://blogs.technet.com/mwiles/archive/2009/02/06/client-schedule-id-s.aspx.  Copying the schedule ID info here in case his blog entry is not available.

If you are reading this you probably already know what sendsched and schedule ID's are.  If you need sendsched.vbs you can get it in the SMS 2003 Toolkit.  Not sure why it's not in the SCCM Toolkit. 

Hardware Inventory Collection Task

{00000000-0000-0000-0000-000000000001}

Software Inventory Collection Task

{00000000-0000-0000-0000-000000000002}

Heartbeat Discovery Cycle

{00000000-0000-0000-0000-000000000003}

Software Inventory File Collection Task

{00000000-0000-0000-0000-000000000010}

Request Machine Policy Assignments

{00000000-0000-0000-0000-000000000021}

Evaluate Machine Policy Assignments

{00000000-0000-0000-0000-000000000022}

Refresh Default MP Task

{00000000-0000-0000-0000-000000000023}

Refresh Location Services Task

{00000000-0000-0000-0000-000000000024}

Location Services Cleanup Task

{00000000-0000-0000-0000-000000000025}

Software Metering Report Cycle

{00000000-0000-0000-0000-000000000031}

Source Update Manage Update Cycle

{00000000-0000-0000-0000-000000000032}

Policy Agent Cleanup Cycle

{00000000-0000-0000-0000-000000000040}

Request Machine Policy Assignments

{00000000-0000-0000-0000-000000000042}

Certificate Maintenance Cycle

{00000000-0000-0000-0000-000000000051}

Peer Distribution Point Status Task

{00000000-0000-0000-0000-000000000061}

Peer Distribution Point Provisioning Status Task

{00000000-0000-0000-0000-000000000062}

Compliance Interval Enforcement

{00000000-0000-0000-0000-000000000071}

Software Updates Agent Assignment Evaluation Cycle

{00000000-0000-0000-0000-000000000108}

Send Unsent State Messages

{00000000-0000-0000-0000-000000000111}

State Message Manager Task

{00000000-0000-0000-0000-000000000112}

Force Update Scan

{00000000-0000-0000-0000-000000000113}

AMT Provision Cycle

{00000000-0000-0000-0000-000000000120}

http://myitforum.com/cs2/blogs/cstauffer/archive/2009/02/09/sccm-client-health-check-startup-script.aspx

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

Did you configure DCOM?  http://technet.microsoft.com/en-us/library/bb633148.aspx