Fails with the following Errors two errors
1. Setting up Email Account "Unexpected Error Occured" no further details are given
2. Setting User Quotas "MessagingManagement" further details "Unexpected Error Occured"
I suspect this is part of a bigger error as when then going into EMC and clicking on "Microsoft On-Premises" I get the following error:
"Connecting to remote server failed with the 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. For more information, see the about_Remote_Troubleshooting Help topic."
I followed the advise on this link and unless I'm doing something wrong, nothing made any difference as all possible issues were not valid.
http://support.microsoft.com/kb/2028305
When opening EMS I get the following error:
"VERBOSE:Connecting to server.domain.local
[server.domain.local]Connecting to remote server failed with the 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. For
more information, see the about_Remote_Troubleshooting Help topic.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException
+ FullyQualifiedErrorId : PSSSessionOpenFailed"
Ran the EMT Shooter as recommended with the following results:
"These are the possible causes for this error:
1. If the WSMan module entry is missing from the global modules section of theC:\Windows\System32\Inetsrv\config\ApplicationHost.config file, as follows:
<globalModules>
<add name="WSMan" image="C:\Windows\system32\wsmsvc.dll" />
This will result in the WSMan module displaying as a Managed module on the PowerShell virtual directory.
To correct this, make sure that the WSMan module has been registered (but not enabled) at the Server level, and has been enabled on the PowerShell virtual directory. Confirm that the WSMan entry exists in the Global Section of the ApplicationHost.config file as shown above.
2. Remote PowerShell uses Kerberos to authenticate the user connecting. IIS implements this Kerberos authentication method via a native module. In IIS Manager, if you go to the PowerShell Virtual Directory and then look at the Modules, you should see Kerbauth listed as a Native Module, with the dll location pointing to \Program Files\Microsoft\Exchange Server\v14\Bin\kerbauth.dll. If the Kerbauth module shows up as a Managed module instead of Native, or if the Kerbauth module has been loaded on the Default Web Site level (instead of, or in addition to, the PowerShell virtual directory), you can experience this issue. To correct this, make sure that the Kerbauth module is not enabled on the Default Web Site, but is only enabled on the PowerShell virtual directory. The entry type of "Local" indicates that the Kerbauth module was enabled directly on this level, and not inherited from a parent.
3. The Path of the Powershell virtual directory has been modified. The PowerShell virtual directory must point to the
"\Exchange Server\v14\ClientAccess\PowerShell"
directory or you will encounter problems.
After each error is resolved, close this window and re-run the tool to check for additional problems."
Once again as far as I can tell all of these errors are invalid.
Thanks in advance for your help...this issue is driving me crazy at this point and any extra help would be greatly appreciated.