Hi,

We use a 3rd party mail archive solution that connects to /powershell in order to process mail. I'm trying to use a hardware load balancer (netscaler) to publish the that virtual directory. I'm using the same configuration that I've previously published /owa/ and the other vdirs with, however, trying to access /powershell always fails, even when I check the URL in a browser. The /powershell vdir is configured with the default settings.

Here's a quick snippet from the IIS log on one of my Exchange servers. When a client PC accesses the URL, it succeeds. When my HLB tries, I get a 500 error:

2015-07-28 18:07:10 192.168.1.103 GET /powershell/healthcheck.htm - 443 - 192.168.40.130 Mozilla/5.0+(Windows+NT+6.1;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko - 200 0 0 109
2015-07-28 17:59:16 192.168.1.103 GET /powershell/healthcheck.htm - 443 - 192.168.1.251 - - 500 0 64 15

The guides I've seen for publishing Exchange 2013 this way all focus on the /owa, /ecp, /oa, etc directories, not /powershell.
Is publishing /powershell via HLB supported? Are there any tests I can run to narrow down the issue, or guides that I can follow to get this up and running?

Thanks,
Greg

Hi Greg,

Based on my knowledge, there is no reference about publish /PowerShell to the external internet environment. I suggest we can contact your third-party support to ask for help about how to achieve the Archive solution.

Additioally, in Exchange 2013, we can also use in-place archive feature to help you regain control of your organization's messaging data by eliminating the need for personal store (.pst) files and allowing users to store messages in an archive mailbox accessible in Microsoft Outlook 2010 and later and Microsoft Office Outlook Web App. For more information about In-Place Archive in Exchange 2013, please refer to:

https://technet.microsoft.com/en-us/library/dd979800%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

Re

Hi Greg,

You need to enable basic authentication on the PowerShell Vdir.

Please read the below article to understand how it works.

Exchange Server 2013 PowerShell Implicit Remoting over the Internet using IIS ARR as the Reverse Proxy

Secondly powershell/healthcheck.htm this file is not physically present and is dynamically generated in memory, hence it might be tricky sometimes to get through this.

Hi,

We use a 3rd party mail archive solution that connects to /powershell in order to process mail. I'm trying to use a hardware load balancer (netscaler) to publish the that virtual directory. I'm using the same configuration that I've previously published /owa/ and the other vdirs with, however, trying to access /powershell always fails, even when I check the URL in a browser. The /powershell vdir is configured with the default settings.

Here's a quick snippet from the IIS log on one of my Exchange servers. When a client PC accesses the URL, it succeeds. When my HLB tries, I get a 500 error:

2015-07-28 18:07:10 192.168.1.103 GET /powershell/healthcheck.htm - 443 - 192.168.40.130 Mozilla/5.0+(Windows+NT+6.1;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko - 200 0 0 109
2015-07-28 17:59:16 192.168.1.103 GET /powershell/healthcheck.htm - 443 - 192.168.1.251 - - 500 0 64 15

The guides I've seen for publishing Exchange 2013 this way all focus on the /owa, /ecp, /oa, etc directories, not /powershell.
Is publishing /powershell via HLB supported? Are there any tests I can run to narrow down the issue, or guides that I can follow to get this up and running?

Thanks,
Greg

It wont work on 443. It's listening on port 80. 

To illustrate this, go to a CAS role server directly on 80:

http://<server>/powershell/healthcheck.htm

that works.

Now go on 443:

https://<server>/powershell/healthcheck.htm

That does not.

Hi Satyajit,

Thanks for your suggestion, however Basic Authentication is already enabled on the front-end Powershell vdir, this is the default setup.

Thanks,
Greg

Hi Andy,

Thanks for your reply, however, that's not at all what I experience.
Whether I type in "https://<server>/powershell/healthcheck.htm" OR "http://<server>/powershell/healthcheck.htm", I get back a "200 OK" page.

I showed that in the log snippet I'd included - the PC 192.168.40.130 successfully accessed the /powershell/healthcheck.htm file on 192.168.1.103 via. port 443.

Thanks for your suggestion, I appreciate you taking the time to reply,
Greg

Hi Andy,

Thanks for your reply, however, that's not at all what I experience.
Whether I type in "https://<server>/powershell/healthcheck.htm" OR "http://<server>/powershell/healthcheck.htm", I get back a "200 OK" page.

I showed that in the log snippet I'd included - the PC 192.168.40.130 successfully accessed the /powershell/healthcheck.htm file on 192.168.1.103 via. port 443.

Thanks for your suggestion, I appreciate you taking the time to reply,
Greg

Thats interesting. I dont see that with either a single role CAS or dual role server. It only works with http

Hi Greg,

Please confirm if you are able to successfully Remote using the virtual name.