Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class
447 views

Prevent Powershell service from contacting Exchange Server

Hello IDM experts,

In my company we use the AD driver to execute simple, Exchange-unrelated Powershell scripts on user creation.
Even though we do not use any Exchange Cmdlets, the IDM_PowerShell_Service appears to look for an Exchange server on every call.
If the server is unavailable for some reason at that time, the execution will just fail, which is a bit annoying.

Is there a way to prevent the Powershell service from contacting an Exchange server? Maybe by locally installing Exchange management tools?

I know that the scripting driver exists, its purchase/deployment is however not an option for my company 😞
Labels (1)
0 Likes
4 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

On 4/18/2018 11:26 AM, mgolor wrote:
>
> Hello IDM experts,
>
> In my company we use the AD driver to execute simple, Exchange-unrelated
> Powershell scripts on user creation.
> Even though we do not use any Exchange Cmdlets, the
> IDM_PowerShell_Service appears to look for an Exchange server on every
> call.
> If the server is unavailable for some reason at that time, the execution
> will just fail, which is a bit annoying.
>
> Is there a way to prevent the Powershell service from contacting an
> Exchange server? Maybe by locally installing Exchange management tools?
>
>
> I know that the scripting driver exists, its purchase/deployment is
> however not an option for my company 😞


There is a driver setting to enable Exchange provisioning. I assume you
have tried disabling those settings? The question is, does the service
request cmdlets on startup always, or according to the commands/settings
from the shim.


0 Likes
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

Thanks for your quick reply!

> There is a driver setting to enable Exchange provisioning. I assume you
> have tried disabling those settings?

If you are talking about the setting "Enable Exchange mailbox provisioning" from the driver parameters section, disabling this option was indeed the first thing I tried.
It didn't help though.

> The question is, does the service
> request cmdlets on startup always, or according to the commands/settings
> from the shim.

I'm not sure what you mean by that, could you please elaborate a little more?
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

mgolor <mgolor@no-mx.forums.microfocus.com> wrote:
>
>> The question is, does the service
>> request cmdlets on startup always, or according to the

commands/settings
>> from the shim.

> I'm not sure what you mean by that, could you please elaborate a little

more?

From what I recall it tries to connect on first command that references
powershell. So maybe a dummy powershell command right after startup to init
the powershell support might work.

There is no way (that I have found/seen) to disable the exchange checks.
The driver is deliberately crippled to work best with exchange/ad cmdlets.
It was never designed to be an all purpose powershell tool.

Alex McHugh - Knowledge Partner - Stavanger, Norway
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

> From what I recall it tries to connect on first command that references
> powershell. So maybe a dummy powershell command right after startup to init
> the powershell support might work.


I've looked into this, and the connection error indeed seems to only appear in the first call after the driver (re)connected with the remote loader.
Thank you very much for the hint, maybe a dummy call thing will already improve the situation, I will try it!
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.