The MP Troubleshooter (Management Point Troubleshooter) is a tool that checks a computer system before and after a management point installation to ensure that the installation meets the requirements for management points. The tool indicates whether numerous management point dependencies, which are not obvious during installation, are met. The tool runs a number of tests to ensure that the management point will run. You can use the tool to run these tests after a management point is installed to ensure that the management point is operational.
The results of the tests indicate any action you must take to ensure that the management point functions properly. For example, you have recently upgraded the management point computer from Windows Server 2003 to Windows Server 2008 and now your clients do not operate properly. In this case, the Default Web Site is stopped by default and as result the management point is not functional. Running the tool would indicate that the Default Web site is disabled.
System Requirements
Supported Operating Systems: Windows Server 2003; Windows Server 2008; Windows Server 2008 R2; Windows XP; Windows Vista, Windows 7
Supported Site System: System Center Configuration Manager 2007 SP2 or System Center Configuration Manager 2007 SP1
Additional Requirements: Net 2.0 framework should be installed; ADSI (Active Directory Service Interface) provider is needed for checking BITS’ setting for CCM [Only available for windows server]; WAS (Windows Process Activation Service) is needed for checking Windows Server 2008 or higher Windows Server’s WebDAV setting. [Only available for windows Server 2008, Windows Vista or higher]
Usage
Before you run the tool, you must enter information about the target computer system. Then you can run pre-installation or post-installation tests.
Management Point Pre-Installation
On the Management Point Pre-Installation tab, specify information about the computer that will host the management point. After you have entered the information, the Run button becomes available. Specify the following information:
- Management Point Candidate
- Enter the computer name of the computer where you plan to install the management point.
- Management Point is remote
- When the checkbox is not selected, this prevents the tool from displaying the Site Server field. Not selected by default.
- Site Server
- Use this field to enter the computer name of the ConfigMgr site server. This field is only available when Management Point is remote is selected.
- Product Version
- Use this option to indicate the version of Configuration Manager of the site server. For example, when ConfigMgr 2007 SP1 is selected, operating system checking verifies that the target machine’s operating system version meet the SP1 product’s operating system requirement. The major difference regarding operating system versions are that SP1 do not support Windows Server 2008 R2, but SP2 supports.
After you specify the required information, Run becomes available. Click Run to start the pre-installation requirement tests.
After running the tests, some issues can be fixed automatically. The tool will offer to fix the issues. Click Yes to fix the problems automatically, Click No to view the test result and fix them manually.
Management Point Post-Installation
After you install a management point, you can use the MP Troubleshooter to ensure the management point host computer still meets the necessary requirements.
When you click the Post-Installation tab, you are prompted to connect to the computer running Microsoft SQL Server. Enter the computer name of the computer running SQL Server hosting the ConfigMgr database. Specify whether Windows authentication or SQL Server authentication is used. If SQL Server authentication is used, Specify the logon name and password required to connect.
Before you can run the post-installation tests, specify the following:
- ConfigMgr Database Name
- Select the name of the ConfigMgr site database.
- Site Code
- Select the site code.
- Management Point
- Select the computer name of the management point. After the management point is selected, it will check the site mode of Management Point. If the management point is in native mode, HTTP Port Number is set 443 and Client Certificate Path is displayed.
- HTTP Port Number
- If your management is configured to use a non-standard port, enter the port number. By default, the HTTP port number used by the management port is 80. If management point is in native mode, HTTP port number is set to 443.
- SQL Server
- Specify the computer name of the computer running SQL Server hosting the Configuration Manager 2007 database. If the database is a named instance, you should also specify the instance name. e.g: DatabaseServer\MyInstance.
- Client Certificate Path
- If the Management Point is in native mode, specify
Client Certificate which is used to test Management Point HTTPS
request.
- About how to configure native mode site: (Select “Allow private
key to be exported” in client certificate)
For Windows Server 2003: http://technet.microsoft.com/en-us/library/bb694035.aspx
For Windows Server 2008: http://technet.microsoft.com/en-us/library/cc872789.aspx
- Export the client certificate from MMC tools’ Certificates to
file in X.509 format without username and password. The exported
file is the client certificate needed in this program.Detail
steps:
- Click Run in Start, type
mmc, press Enter.
- Click File in Console1, and click Add\Remove
Snap-in.
- Select Certificates in Add or Remove Snap-ins, and click
Add.
- Select Computer Account in Certificates snap-in, click
Next, click Finish to close Certificates snap-in;
click OK to close Add or Remove Snap-ins.
- Expand Certficates in Console1, expand Personal,
click Certificates under Personal.
- Right click the item which Intended Purposes is Client
Authentication, select All task, click
Export.
- Click Next in Certificate Export Wizard, make sure
No, do not export the private key is selected, and click
Next; Click Next to agree with default select option
DER encoded binary X.509 (.CER).
- Input the file name and location of the stored certificate,
click Next, click Finish to implement
exportation.
- Click Run in Start, type
- About how to configure native mode site: (Select “Allow private
key to be exported” in client certificate)
Active Directory is extended
This indicates whether the schema of Active Directory has been extended.
It is selected by default. When selected, this option indicates that the Active Directory service has been extended. The tool searches Active Directory for the management point certificate is stored and compares the certificate information with the value stored in the registry for the management point and with the value returned from the MPCERT HTTP request. If all three values are equal, the Testing MPCERT HTTP or HTTPS request functionality test passes.
When cleared, the tool verifies that a value stored in the registry of the management point matches the value returned from the MPCERT HTTP or HTTPS request. This ensures that the management point certificate is valid and that communication between an Advanced Client and its management point is protected, preventing an attacker from altering the communication in transit. If both values are equal, the Testing MPCERT HTTP or HTTPS request functionality test passes.
After you specify the required information about management point and site, Run becomes available. When you click Run, several management point post-installation requirement tests are run.
After running the tests, some issues can be fixed automatically. The tool will offer to fix the issues. Click Yes to fix the problems automatically, Click No to view the test result and fix them manually.
Using Test Results
After you have run Management Point Pre-installation or Management Point Post-installation tests, you can export the results of the test with Export Results. When you export the test results, one file is created in the %USERPROFILE%\Local Settings\Temp\TroubleShooterReports directory, depending on the test type. The tool opens the folder in Windows Explorer.
| Type of Test | File Name |
|---|---|
|
Management Point Pre-Installation |
MP_Pre_TroubleShooter_Report.xml |
|
Management Point Post-Installation |
MP_Post_TroubleShooter_Report.xml |
Checking List of Management Point Troubleshooter
Management Point Pre-installation Checking List:
| Index | Name | Dependency on other Checks | Can be fixed automatically |
|---|---|---|---|
|
1 |
Does the MDAC version meet the version requirement? Version number should be equal to or newer than 2.8. |
None |
No |
|
2 |
Does the management point candidate meet the minimum free disk space requirement on the system drive? (Required: 5GB Recommand:15GB). |
None |
No |
|
3 |
Does the management point candidate meet the minimum processor speed requirement? (Required:733MHz Recommand:2000MHz). |
None |
No |
|
4 |
Does the management point candidate meet the minimum RAM requirement? (Required:256MB Recommand:1024MB). |
None |
No |
|
5 |
If management point management point candidate is remote, verify the Site Server's Machine Account is a member of the local admin group of the site system. |
None |
No |
|
6 |
If the management point management point is Windows Server 2003Windows Server 2003 or higher, verify that the Background Intelligent Transfer Service (BITS) extension is enabled. |
#7 passed in Management Point |
Yes |
|
7 |
If the management point management point is Windows Server 2003Windows Server 2003 or higher, verify that the Background Intelligent Transfer Service (BITS) extension is installed. |
#19 #11(If it’s Windows Server 2008) passed in Management Point, Management Point is Windows Server 2003 or higher |
No |
|
8 |
If the management pointmanagement point is Windows Server 2008 or higher: Verify that IIS ASP.Net is installed. |
#19 passed in Management Point, Management Point is Windows Server 2008 or higher |
No |
|
9 |
If the management point is Windows Server 2008 or higher: Verify that IIS Windows Authentication is installed. |
#19 passed in Management Point, Management Point is Windows Server 2008 or higher |
No |
|
10 |
If the management point is Windows Server 2008 or higher: Verify that IIS6 Metabase Compatibility is installed. |
#19 passed in Management Point, Management Point is Windows Server 2008 or higher |
No |
|
11 |
If the management point is Windows Server 2008 or higher: Verify that IIS6 WMI Compatibility is installed. |
#19 passed in Management Point, Management Point is Windows Server 2008 or higher |
No |
|
12 |
If the management point is Windows Server 2008 or higher: Verify that Remote Differential Compression is installed. |
Management Point is Windows Server 2008 or higher |
No |
|
13 |
Determine whether the candidate is running on a supported operating system. |
None |
No |
|
14 |
Determine whether the management point candidate's system drive is NTFS. |
None |
|
|
15 |
Test whether WebDav is configured correctly. |
#19 #28 passed in Management Point, Management Point is Windows Server 2003 or higher If Management Point is Windows Server 2008 or higher: WPAS should be installed in local machine |
Yes(for server 2003) Yes if WPAS is installed in local machine(for server 2008 or higher) |
|
16 |
Verify that the Distributed Transaction Coordinator Service is running. |
None |
Yes if service is not started |
|
17 |
Verify that the Task Scheduler is running. |
None |
Yes if service is not started |
|
18 |
Verify that the Windows Management Instrumentation service is running. |
None |
Yes if service is not started |
|
19 |
Verify that the World Wide Web Publishing Service is running. |
None |
Yes if service is not started |
|
20 |
Verify the Default Web Site is running. |
#19 #11(If it’s Windows Server 2008) passed in Management Point, Management Point is Windows Server 2003 or higher |
No |
|
28 |
If the management point is Windows Server 2003Windows Server 2003 or higher: Verify that the WebDAV is installed |
None |
No |
Management Point Post-installation Checking List:
|
Index |
Name |
Dependency on other Checks |
Can be fixed automatically |
|
21 |
If SQL is remote to the management point: verify the management point's Machine Account is a member of the SQL server's local admin group. |
None |
No |
|
6 |
If the management point is Windows Server 2003 or higher: Verify that the Background Intelligent Transfer Service Extension is enabled. |
#7 passed in Management Point |
Yes |
|
23 |
If the management point is Windows Server 2003 or higher: Verify that the BITS Web Extensions for ConfigMgr are enabled. |
#6 passed in Management Point |
No |
|
8 |
If the management point is Windows Server 2008 or higher: Verify that IIS ASP.Net is installed. |
#19 passed in Management Point, Management Point is Windows Server 2008 or higher |
No |
|
9 |
If the management point is Windows Server 2008 or higher: Verify that IIS Windows Authentication is installed. |
#19 passed in Management Point, Management Point is Windows Server 2008 or higher |
No |
|
24 |
If AD is extended: test whether management point certificate is released to AD. |
None |
No |
|
10 |
If the management point is Windows Server 2008 or higher: Verify that IIS6 Metabase Compatibility is installed. |
#19 passed in Management Point, Management Point is Windows Server 2008 or higher |
No |
|
11 |
If the management point is Windows Server 2008 or higher: Verify that IIS6 WMI Compatibility is installed. |
#19 passed in Management Point, Management Point is Windows Server 2008 or higher |
No |
|
12 |
If the management point is Windows Server 2008 or higher: Verify that Remote Differential Compression is installed. |
Management Point is Windows Server 2008 or higher |
No |
|
15 |
Test whether WebDav is configured correctly. |
#19 #28 passed in Management Point, Management Point is Windows Server 2003 or higher If Management Point is Windows Server 2008 or higher: WPAS should be installed in local machine |
Yes(for server 2003) Yes if WPAS is installed in local machine(for server 2008 or higher) |
|
25 |
Test MPCERT HTTP or HTTPS request functionality. |
#27 passed in Management Point |
No |
|
26 |
Test MPLIST HTTP or HTTPS request functionality. |
#27 passed in Management Point |
No |
|
16 |
Verify that the Distributed Transaction Coordinator Service is running. |
None |
Yes if service is not started |
|
27 |
Verify that the SMS Agent Host Service is running. |
None |
Yes if service is not started |
|
17 |
Verify that the Task Scheduler is running. |
None |
Yes if service is not started |
|
18 |
Verify that the Windows Management Instrumentation service is running. |
None |
Yes if service is not started |
|
19 |
Verify that the World Wide Web Publishing Service is running. |
None |
Yes if service is not started |
|
20 |
Verify the Default Web Site is running. |
#19 #11(If it’s Windows Server 2008) passed in Management Point, Management Point is Windows Server 2003 or higher |
No |