{"id":1570,"date":"2019-09-01T11:50:19","date_gmt":"2019-09-01T16:50:19","guid":{"rendered":"http:\/\/zitstif.no-ip.org\/?p=1570"},"modified":"2019-09-01T15:43:14","modified_gmt":"2019-09-01T20:43:14","slug":"on-premise-exchange-2010-headaches","status":"publish","type":"post","link":"http:\/\/zitstif.no-ip.org\/?p=1570","title":{"rendered":"On-premise Exchange 2010 headaches"},"content":{"rendered":"

If you’ve worked in IT and have inherited other systems and networks to manage, you can definitely relate to having to work with situations that are less than ideal. Best practices can’t always be followed due to various reasons. (One main reason seems to be money related.) I am currently working with a client that has on-premise servers that are all bare metal and under-specced. We are in the process gathering information on their current setup and plan to decommission and consolidate their on-premise servers, and push them to use Office 365 instead.<\/p>\n

I hope this post helps someone because I was having next to no luck being able to access the Exchange Management Shell. Oddly, the GUI tool worked fine, but I wanted to run powershell scripts to generate reports on the current configuration of the said Exchange server. Clicking on the powershell management shell for Exchange icon would result in:<\/p>\n

\"\"<\/a><\/p>\n

I troubleshooted all the suggested steps suggested in the error output and everything appeared to check out fine. I then just tried using a standard powershell prompt to try to authenticate to the local exchange powershell, and started getting errors like:<\/p>\n

[ExchServer] Connecting to remote server failed with the following error message : The WinRM client received an HTTP status code of 403 from the remote WS-Management service. For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc eption + FullyQualifiedErrorId : PSSessionOpenFailed<\/strong><\/p>\n

\"\"<\/a><\/p>\n

I found it curious that I was starting to get different error messages and felt like I was starting to get closer to being able to authenticate. What ended up working for me was to issue this command:<\/p>\n

$session = new-pssession -configurationName Microsoft.Exchange -connectionuri\u00a0http:\/\/change.me.local\/PowerShell\/<\/a>\u00a0-Authentication Kerberos -credential $credential\u00a0<\/strong><\/p>\n

You are then prompted with a gui logon prompt. Make sure to use Domain\\UserName in the username field then use the proper password. Lo and behold, no errors were given and it looks like I was authenticated! To import the exchange powershell modules, issue this command:<\/p>\n

Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010;<\/strong><\/p>\n

Again, I really hope this helps save someone a headache and time. As for the root of what’s causing the powershell management shell for Exchange icon shortcut to fail, I’m not clear. So at this point this is just a workaround.<\/p>\n","protected":false},"excerpt":{"rendered":"

If you’ve worked in IT and have inherited other systems and networks to manage, you can definitely relate to having to work with situations that are less than ideal. Best practices can’t always be followed due to various reasons. (One main reason seems to be money related.) I am currently working with a client that … Continue reading On-premise Exchange 2010 headaches<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11,3],"tags":[1012,1011,1016,1005,1014,1004,1013,1008,1017,1010,897,1006,1007,1001,933,1009,1002,1015,1003],"class_list":["post-1570","post","type-post","status-publish","format-standard","hentry","category-code","category-posts","tag-1012","tag-authentication","tag-connecting-to-remote-server-failed-with-the-following-error-message-winrm-cannot-process-the-request","tag-exchange","tag-exchange-powershell","tag-failed-to-connect-to-an-exchange-server-in-the-current-site","tag-http","tag-it","tag-kerberos","tag-microsoft-exchange-2010","tag-money","tag-office365","tag-on-premise","tag-openerror","tag-powershell","tag-under-specced","tag-winrm","tag-winrm-client-received-an-http-status-code-of-403-from-the-remote","tag-winrm-trustedhosts"],"_links":{"self":[{"href":"http:\/\/zitstif.no-ip.org\/index.php?rest_route=\/wp\/v2\/posts\/1570","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/zitstif.no-ip.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/zitstif.no-ip.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/zitstif.no-ip.org\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/zitstif.no-ip.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1570"}],"version-history":[{"count":11,"href":"http:\/\/zitstif.no-ip.org\/index.php?rest_route=\/wp\/v2\/posts\/1570\/revisions"}],"predecessor-version":[{"id":1583,"href":"http:\/\/zitstif.no-ip.org\/index.php?rest_route=\/wp\/v2\/posts\/1570\/revisions\/1583"}],"wp:attachment":[{"href":"http:\/\/zitstif.no-ip.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1570"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/zitstif.no-ip.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1570"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/zitstif.no-ip.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1570"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}