AppInsight for Exchange and WinRM issue: The SSL connection cannot be established

I'm running SAM 6.1.1 and I'm having issues configuring a AppInsight for Exchange on a single Exchange server (Exchange 2012 on Windows 2008 R2).  Getting other Exchange servers set up have worked fine, mostly .

per some other Thwack posts, I've tried removing the template, re-appling it via the "List resources" section, and configuring it from the pop up that appears when you first click on the template in the SAM apps list, but I'm getting the feeling these things are not fix for this.

Issue:

When setting up the "Exchange Server Credentials" step in the template, I get the following Yellow warning when hitting the "test connection" button

"WinRM test was successful.  PowerShell Exchange web site testing failed with the following error:

Connecting to remote server failed with the following error message : The SSL connection cannot be established. Verify that the service on the remote host is properly configured to listen for HTTPS 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 -transport:https". For more information, see the about_Remote_Troubleshooting Help topic."

I ran "winrm quickconfig -transport:https" on the Cxchange system from a cmd line (run as administrator) and it indicated it ran successfully.

When hitting the "Configure Server" button in the template, I receive this red error (the same error. I was hoping it would be different)

"Remote Configuration Failed
Remote configuration was unsuccessful due to the following: "WinRM test was successful. PowerShell Exchange web site testing failed with the following error:Connecting to remote server failed with the following error message : The SSL connection cannot be established. Verify that the service on the remote host is properly configured to listen for HTTPS 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 -transport:https". For more information, see the about_Remote_Troubleshooting Help topic."

I went down the road of "Manual configuration" from here and got all the way down to "Configuring IIS", where this command fails (Step 6):

(Get-WebConfiguration system.webServer/security/authentication/windowsAuthentication 'IIS:\sites\Default Web Site\PowerShell').enabled

with : "Get-WebConfiguration : Cannot find path 'IIS:\Sites\Default Web Site\PowerShell' because it does not exist"

Does anyone have any thoughts/ideas/suggestions?

I've poked around the net a bit and there's a lot about the joys of WinRM but I don't want to just try things randomly on a production server in hopes I'll hit some magical combination of settings.