K2 interacts with the Microsoft Exchange Server in a number of different ways:
The most common usage of the Microsoft Exchange Server within a K2 environment is to leverage Exchange to send K2 generated emails.
With K2 4.5 update 1230 and later, event wizards are surfaced in the K2 workflow design tools that permit interaction with specific Exchange functionality. This permits the below functionality to be part of an automated K2 workflow. The following functionality is exposed via this Exchange wizard:
For full details around this functionality please refer to the product documentation.
K2 SmartObject Services (also known as a ServiceBroker) ships with K2 that permit SmartObject interaction to Exchange Server functionality. All K2 SmartObjects, not just Exchange based, can be leveraged within workflows or external to workflows such as via a custom form via K2 SmartObject API.The following functionality is exposed via the Exchange SmartObject Services:
Microsoft Exchange 2007 (SP2 or SP3)
Microsoft Exchange Server 2010
The following commands should be run through the Exchange Management Shell on the Exchange Server machine: Enable-PSRemoting Set-Item wsman:\localhost\client\trustedhosts “k2server machine fqn”
Configure IIS on the Exchange server machine:By default, WinRM uses http and connects through the Default Web Site on port 80.Add bindings to http port 80, with no hostname and All Unassigned if they don’t exist.\PowerShell should not have SSL enabled.\PowerShell should have only anonymous access enabled.
TroubleshootingTo resolve possible connection issues with WinRM, try the following: On the Exchange server, edit group policy and under Computer Configuration\Administrative Templates\Windows Components\Windows Remote Management (WinRM)\WinRM Service, set IPv4 & IPv6 filters = * IPv6 should be enabled On the K2 server machine, run the following cmdlet in PowerShellSet-ExecutionPolicy Unrestricted PowerShell can’t connect to host headers, so the Exchange certificate should be issued to the Exchange Server machine name and the Exchange service instances should point to the machine name as well
Exchange Components SmartObjects
User Details in the Exchange Event Wizard
For the Meeting and Task Details screens, the e-mail address of the user (or users) is required. This also applies to all three user fields on the Meeting Attendees screen.
Thank you for your submission. We will be in contact shortly to assist you.