Even in Exchange Teams there are many routine tasks to be done every day. With ScriptRunner ActionPack for Exchange, these tasks can be automated and delegated quickly and securely.
Only 3 steps are necessary to use the scripts from the ActionPack for Exchange in ScriptRunner:
Actions can then be set up and delegated using the scripts from the collection.
The ScriptRunner ActionPacks are made available on the ScriptRunner GitHub repository, and more scripts and topics are added and updated regularly.
There are several ways to include the scripts from the ActionPacks in ScriptRunner. According to best practice, an alternative directory is created for the Sync Script. This way the scripts are always available internally on the latest version.
The scripts to be used can be migrated to the working directory manually or by action with an appropriate ScriptRunner script.
Configure a scheduled action with “Pull”-mode. This will automatically update the scripts in the specified target directory.
Copy the desired scripts or the entire directory of an ActionPack into the ScriptRunner working directory. The scripts will be automatically recognized and tagged by ScriptRunner. Now the scripts are available in ScriptRunner.
To use the scripts from the ActionPack for Exchange in ScriptRunner, you first need to set up an Exchange administration account and the Exchange Server in ScriptRunner. These steps are done in the ScriptRunner Admin App.
The Exchange administrator to be configured must have administrative rights for mailboxes, etc. Multiple, different accounts can be entered.
IMPORTANT: For error messages, check the authentication method and set it accordingly with the second option “Use a non-default authentication method”. Depending on the domain constellation Kerberos, Negotiate or another may be necessary !
Simply activate the implicit remoting. Additional session options such as -SkipNCheck, -SkipRevocationCheck, -SkipCACheck must be entered in the bottom option field. A switch option must be assigned the value 1. An entry of options would then look like this:
SkipNCheck=1
SkipRevocationCheck=1
SkipCACheck=1
To ensure that a connection to Exchange server can be established, a check is performed.
>$pw = ConvertTo-SecureString -String ‘password' -AsPlainText -Force >$cred = New-Object -TypeName pscredential -ArgumentList ‘account',$pw >$session=new-pssession -ConfigurationName Microsoft.Exchange -ConnectionUri http://exchangeserver.fqdn/powershell/ -Credential $cred # additional session options may be necessary depending on the constellation in your environment # Eg: -Authentication method -SkipNCheck, -SkipRevocationCheck, -SkipCACheck >Import-PSSession -Session $session >get-command –module ‚temp_module_name‘ -> in the given example >get-command –module tmpkc1p04s0.z4c
Configure sample command in the PowerShell actions with the scripts from the ActionPack. The connection to the Exchange server works, the setup is complete and actions can now be configured and executed.
Are you interested in the topic Exchange Administration with the ScriptRunner ActionPack? More information can be found in our webinar recording “Effectively Design and Securely Delegate Exchange Administration with PowerShell and ScriptRunner ActionPack“!