Can't access emc and/or management shell

Question

Really need some help with this. Researched all day and no fixes have helped.
Exchange 2010 - Windows 2008 R2 Standard.
EMC error: 
Connecting to remote server failed with teh following error message: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. 
It was running the command 'Discover-ExchangeServer -UseWIA $true-SuppressError $true - CurrentVersion "Version 14.1 (Build 218.15)". 
Exchange Management Shell error: 
Connecting to remote server failed with teh following error message: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. 
So i've read all day a ton of fixes, Time Sync, WinRM config IIS resets and so on, nothing fixes this. However, when I try to go to PowerShell Connections in IIS manager, no matter what I click on gives me the following error: 
There was an error while performing this operation 
C:\Windows\system32\inetsrv\config\applicaitonHost.config 
Line number: 301 
Error:can not log on locally to c:\program files\microsoft\exchange server\v14\clientaccess\powershell as user administrator with virtual directory password 
Please advise, I can't create any new email and I need to get this resolved. 
Mailflow is working fine.
EDIT: I pulled from an AppAssure backup the web.config file and replaced that in ClientAccess\PowerShell also and this did not resolve either.

Answer 1

WinRM already is set up to receive requests on this machine.
WinRM already is set up for remote management on this machine.
Listener
    Address = *
    Transport = HTTP
    Port = 5985
    Hostname
    Enabled = true
    URLPrefix = wsman
    CertificateThumbprint
    ListeningOn = 10.10.1.240, 127.0.0.1, ::1, fe80::100:7f:fffe%15, fe80::5efe:10.10.1.240%14
I can't even run EMTshooter. Although I used to be able to and have used it in the past.
EMTshooter errors:
File C:\EMTshooter\EMTConnectFunctions.ps1 cannot be loaded. The contents of fi
le C:\EMTshooter\EMTConnectFunctions.ps1 may have been tampered because the has
h of the file does not match the hash stored in the digital signature. The scri
pt will not execute on the system. Please see "get-help about_signing" for more
 details..
At C:\EMTshooter\EMTshooter.ps1:175 char:2
+ . <<<<  $loadpath
    + CategoryInfo          : NotSpecified: (:) [], PSSecurityException
    + FullyQualifiedErrorId : RuntimeException
Welcome to the Exchange Management Troubleshooter!
We recommend that you run the troubleshooter after making changes to
IIS to ensure that connectivity to Exchange Powershell is unaffected.
The term 'logevent' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the sp
elling of the name, or if a path was included, verify that the path is correct and try again.
At C:\EMTshooter\EMTshooter.ps1:189 char:9
+ logevent <<<<  $eventID $MessageAndParams $Type
    + CategoryInfo          : ObjectNotFound: (logevent:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
Checking IIS Service...
The term '_CheckServicesStarted' is not recognized as the name of a cmdlet, function, script file, or operable program.
 Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\EMTshooter\EMTshooter.ps1:195 char:31
+ $noIIS = _CheckServicesStarted <<<<
    + CategoryInfo          : ObjectNotFound: (_CheckServicesStarted:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
The term 'resetWindow' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
 spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\EMTshooter\EMTshooter.ps1:198 char:13
+     resetWindow <<<<
    + CategoryInfo          : ObjectNotFound: (resetWindow:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
[EMTS] C:\Windows\System32\WindowsPowerShell\v1.0>