Exchange cmdlets

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
This topic is 1 year and 3 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
User avatar
Lembasts
Posts: 405
Last visit: Thu Mar 14, 2024 10:47 pm
Has voted: 1 time
Been upvoted: 1 time

Exchange cmdlets

Post by Lembasts »

re: https://www.sapien.com/viewtopic.php?f=12&t=16103

Not sure if this is what you are after but I use Exchange cmdlets in some of my PS forms.
To make the cmdlets available I have to run the following commands:

Code: Select all

			$global:EXSession = New-PSSession -Name ExchangeConn -ConfigurationName Microsoft.Exchange -ConnectionUri "http://<exfqdn>/PowerShell/" -Authentication Kerberos -ea Stop
			Import-Module (Import-PSSession $global:EXSession -allowclobber -DisableNameChecking -ea Stop) -Global -DisableNameChecking -Force -ea stop | out-null
where <exfqdn> is the fqdn of an exchange server.
Cheers
David
This topic is 1 year and 3 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.