Forum Discussion
How to setup F5 LTM to allow powershell commands through VIP to exchange servers for Airwatch
Ah, yes....I think I know what's happening. The iApp configuration has an iRule that only checks for incoming recognized protocols/applications (OWA/EWS/Autodiscover, etc.) and selects proper persistence method and then select the pool. Since /powershell is not a valid protocol extension in the iApp's realm, it's getting dropped. Thinking about this some more, I'd suggest to simply create another two virtuals(or one, if you just do HTTPS) on default powershell ports 5985/5986 and a dedicated pool of CAS servers on those ports. Sorry for the initial confusion, if I caused one. :)
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com