How to verify Management Point is working fine in SCCM 2007

Verify Management Point Installation Logs

1. Verify MPsetup.log. Make sure MP is install successfully, if not resolve the problem. If you find any problem in MPSetup.log, then verify MPMSI.log for more information on the issue.

MPSetup.log:
<12-16-2008 17:12:09> Installing the SMSMP
<12-16-2008 17:12:09> Passed OS version check.
<12-16-2008 17:12:09> IIS Service is installed.
<12-16-2008 17:12:09> SMSMP already installed (Product Code: {3945C886-9779-4280-B537-AB8E62A0878E}). Upgrading/Reinstalling SMSMP
<12-16-2008 17:12:09> New SMSMP is a new product code {{7AF53388-F428-4A8B-8F20-DBB4851E3424}}. This is a major upgrade.
<12-16-2008 17:12:09> Enabling MSI logging. mp.msi will log to D:\SMS\logs\mpMSI.log
<12-16-2008 17:12:09> Installing D:\SMS\bin\i386\mp.msi REINSTALLMODE=vmaus CCMINSTALLDIR=”D:\SMS_CCM” CCMSERVERDATAROOT=”D:\SMS” USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<12-16-2008 17:15:59> mp.msi exited with return code: 0
<12-16-2008 17:15:59> Verifying CCM_CLIENT virtual directory.
<12-16-2008 17:15:59> Website path is IIS://LocalHost/W3SVC/1.
<12-16-2008 17:15:59> Connecting to IIS.
<12-16-2008 17:15:59> CCM_CLIENT is currently D:\SMS\Client
<12-16-2008 17:15:59> Installation was successful.
2. Check IIS and make sure that you have virtual directory named SMS_MP under default website.
3.Check mpcontrol.log and find if you have below sucesses status message (Status Code 200). ( I use tracert32 to read log files)
Call to httpsendrequestsync succeeded for port 80 with status code 200,text ok
http test request succeeded

successfully performed Management Point avaialbility check against local computer

4. Fianlly for testing run this on IE from any client and from the server itself and you sould get the results mentioned.

  a) Run http://<MP Name>/sms_mp/.sms_aut?mplist

   This returns a list of MP's installed on this site including the secondary site MP's.

  b) Run http://<MP Name>/sms_mp/.sms_aut?mpcert

   This returns a long list of numbers and letters.

Output of Step a
- <MPList>
- <MP Name="smsserver1" FQDN="smsserver1.example.abc.com">
<Version>6487</Version>
<Capabilities SchemaVersion="1.0" />
</MP>
- <MP Name="smsserver18" FQDN="smsserver18.example.abc.com">
<Version>6487</Version>
<Capabilities SchemaVersion="1.0" />
</MP>
- <MP Name="smsserver2" FQDN="smsserver2.example.abc.com">
<Version>6487</Version>
<Capabilities SchemaVersion="1.0" />
</MP>
- <MP Name="secondary1" FQDN="secondary1.example.abc.com">
<Version>6487</Version>
<Capabilities SchemaVersion="1.0" />
</MP>
</MPList>
More Info on MP and resolving issues:

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

0 comments:

Post a Comment