LDAP and GC connectivity checks take long time to fail about set-outlooksignatures HOT 2 CLOSED

System.DirectoryServices.Protocols.LdapConnection and System.DirectoryServices.Protocols.LdapConnection.SendRequest have timeout values, but I could solve the issue with them.

Putting the connectitivy check in a background job and combining Start-Job with (Wait-Job -Timeout 5) is a reliable timeout mechanism, but it creates other issues:

• A new PowerShell instance is started for each backgroung job, which slows down even successful LDAP connectivity checks.
• How to define the timeout? It's not predictable how long it will take to fire up a new PowerShell instance , especially when the script is run as part of the user logon where a system is often under heavier load.

Invoke-Command seems to be way faster, but it requires WinRM enabled.
ForEach -Parallel, InlineScript, etc. are not available in PowerShell 5, which is part of Windows.

Runspaces might be an alternative, I will have a look at it in the next weeks.

from set-outlooksignatures.

Solved by using Runspaces: 3471b15

from set-outlooksignatures.