Microsoft System Center Configuration Manager/SMS Troubleshooting Guide

If the test to connect to Microsoft System Center Configuration Manager/SMS from FootPrints fails on the Microsoft System Center Configuration Manager/SMS System Administration page, the error message displayed in the test window help you determine the cause of the failure. Here are some common causes for failure:

• Wrong server name or ID/password—Confirm that the Microsoft System Center Configuration Manager/SMS server name and the ID/password entered on the setup page are correct.  If you entered a one-word machine name (e.g., skippy), try the fully qualified name (e.g., skippy.widget.com) or IP address (e.g., 12.34.365.678).  Also check that the ID and password combination is correct and that they have enough permission to access Microsoft System Center Configuration Manager/SMS Inventory data on the Microsoft System Center Configuration Manager/SMS server.
• Ping test—Sometimes the ping test fails, but the connection from within FootPrints to Microsoft System Center Configuration Manager/SMS works.  If the ping test fails, and you know the server name and ID/password are correct, enter your password and click GO, then try enabling the Microsoft System Center Configuration Manager/SMS link for a workspace.

• Incorrect version of the Windows Management Instrumentation (WMI)—The FootPrints Microsoft System Center Configuration Manager/SMS Integration requires WMI (the Windows interface FootPrints uses to connect to Microsoft System Center Configuration Manager/SMS) version 1.5 or greater.  If you do not have WMI 1.5 or greater, you must upgrade WMI on both the FootPrints server and the Microsoft System Center Configuration Manager/SMS server. This is not typically a problem for Windows 2000. You can download the required version of WMI from the Microsoft web site.
• Domain and login—You can try specifying the domain as part of the login, e.g., BMC\Administrator.  This may not work for all networks, but it has worked for some users.
• Permissions—The connection may fail because of permissions.  The login ID specified during the setup must have permissions to read all of the Microsoft System Center Configuration Manager/SMS Inventory data.  This is typically tested with an "Administrator" ID.  Because permissions vary from network to network, you might need to try a few different IDs with different Windows permissions (e.g., Full Control, etc.) before it works.  One user could only connect after changing the user running the IIS web server from IUSR_machineName to a real user who was the same one associated with the Microsoft System Center Configuration Manager/SMS server.  
• If all else fails, please contact BMC Support.

Microsoft System Center Configuration Manager/SMS Server Permissions

The following procedure is to help in setting up Microsoft System Center Configuration Manager/SMS. Frequently these steps help when the connection succeeds but the test query returns no results.

1. Open the Microsoft System Center Configuration Manager or SMS Administration Console on the Microsoft System Center Configuration Manager/SMS server.
2. Open up the Security Rights folder.
3. Right-click in the right-hand frame and pick "new->class security right".
4. Set the user to the DOMAIN\user that FootPrints is connecting as, which is the user that you specified on the FootPrints Microsoft System Center Configuration Manager/SMS setup page.
5. Pick "Collection" from the drop-down list.
6. Make sure that the Read checkbox is checked.
7. Click "OK" and continue to select OK until you have exited the setup.
8. Try the FootPrints test link again.
   In Microsoft System Center Configuration Manager/SMS, there are two categories to which you can assign permissions:
   • Class Permissions (Collections)
   • Instant Permissions

If the instructions above, in which you are instructed to assign Read permissions to the Collections class, fails, try assigning permissions to All Systems Collection, which is not a class.