Hi,

I'm trying to run the System Center 2012 sp1 configuration analyzer on my SCCM 2012 Sp1 server and after I start the System Center 2012 sp1 configuration analyzer, I leave the server field blank and don't put anything in the credentials since I'm running this on my SCCM 2012 server.  After I click the Start Scan button I get the following error:

Category: Operation

Source: SMSSERVER

Issue: Unable to connect to SMSSERVER. Please check computer name, credentials and/or remoting is enabled on target computer. See exception for details
Connecting to remote server failed with the following error message : The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see the about_Remote_Troubleshooting Help topic.

I've also tried putting in my SCCM 2012 server name in the server field and entering my admin account for the credentials and I still get this same error message.

Seems strange I can't connect to SCCM 2012 on the actual server itself?

Thanks

Nick

Are you sure that the list of required services are running on the server, the account has access, there is no firewall in the way, and tried fully qualifying your server name?

I'm running the configuration analyzer directly on my SCCM 2012 Sp1 server, so I would think that all the services and things are running.  The account I'm running as is an admin on the box and is specified as one the SCCM admins and the firewall is turned off.  I tried fully qualifying the name and also putting in the admin account directly.

It seems like the error is complaining about either IIS or WMI. I wouldn't think that WMI would be an issue since I'm on the server itself?

Nick

Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?

Since no one has answer this post, I recommend opening  a support case with Microsoft Customer Support Services (CSS) as they can work with you to solve this problem.