Support for running Exchange Management Shell #4995

Closed
opened 2026-01-31 00:02:32 +00:00 by claunia · 2 comments
Owner

Originally created by @InsomniacsDream on GitHub (Nov 14, 2019).

It would be great to be able to add MS Exchange Shell to Terminal to manage On-Prem exchange.

Originally created by @InsomniacsDream on GitHub (Nov 14, 2019). It would be great to be able to add MS Exchange Shell to Terminal to manage On-Prem exchange.
claunia added the Resolution-Duplicate label 2026-01-31 00:02:32 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Nov 14, 2019):

I think this might unfortunately be a /dupe of #1785. It looks like the way the MS Exchange Shell works is fairly incompatible with the way the Terminal launches applications. From that thread:

https://github.com/microsoft/terminal/issues/1785#issuecomment-509060477

This might just boil down to #492. It looks like appref-ms shortcuts are another type of ClickOnce application, which means their launch must be brokered through another process (internet explorer, windows shell, etc.) Right now, we can't support hooking the launch of another console application through a broker.

#1785 (and this issue) will work once we've added support for #492. I've also got mail out to the owners of Exchange Management Shell, hopefully we might be able to find a workaround.

I'm going to close this for now, as a dupe of that other thread. If I hear anything back that's usable as a workaround, I'll make sure to reply here ☺️

@zadjii-msft commented on GitHub (Nov 14, 2019): I think this might unfortunately be a /dupe of #1785. It looks like the way the MS Exchange Shell works is fairly incompatible with the way the Terminal launches applications. From that thread: https://github.com/microsoft/terminal/issues/1785#issuecomment-509060477 > > This might just boil down to #492. It looks like `appref-ms` shortcuts are another type of ClickOnce application, which means their launch _must_ be brokered through another process (internet explorer, windows shell, etc.) Right now, we can't support hooking the launch of another console application through a broker. #1785 (and this issue) will work once we've added support for #492. I've also got mail out to the owners of Exchange Management Shell, hopefully we might be able to find a workaround. I'm going to close this for now, as a dupe of that other thread. If I hear anything back that's usable as a workaround, I'll make sure to reply here ☺️
Author
Owner

@ghost commented on GitHub (Nov 14, 2019):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Nov 14, 2019): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#4995