Content

Notes before start

Requires Microsoft Exchange calendar sync add-on. Read also how the calendar sync works.

NOTE: We have verified that implementing sync works with the scenario described below.

Possible scenarios that might cause issues with the implementation:

  • Multiple domains
  • Accounts that have been migrated from one server to another

In these scenarios Customer Support can check the error message seen on our error logs but troubleshooting should be done by the service provider or Microsoft. We don't provide support for Microsoft Exchange environment management.

Go to top

Settings in Microsoft Exchange server

Following information is needed from the Exchange server to set up the sync in Visma Severa. Contact your Exchange server system administrator to get this data.

Make sure that Exchange server clock is on time because otherwise there might be collision issues (regarding last update time of an entry)

Domain: Organization NetBIOS domain name

Exchange URL: Exchange WebServices (EWS) URL, which has been set on the Exchange server. Example format of the URL: https://outlook.domain.net/EWS/Exchange.asmx

Delegate username: Delegate user account which has been given impersonator access rights on the Exchange server. This account enables and authenticates the sync for all the users. See more information below Creating delegate user in Exchange 2007 or Creating delegate user in Exchange 2010.

Delegate password: Password of the deletegate user account.

Go to top

Creating a delegate user in Exchange 2007

Exchange server administrator access is required for this to work.

  1. Create a delegate user into Exchange/AD, in this example the user name will be Sync Delegate
  2. Add impersonation extended right to the Sync Delegate user on all client access servers
  3. Add impersonation extended right to the Sync Delegate user on all mailbox databases
 
Example script to be run on Exchange Management Shell to add delegate user to access mailboxes of every user in the domain:
Get-ExchangeServer | Where {$_.ServerRole -match "ClientAccess"} | Add-ADPermission -User "Sync Delegate" -ExtendedRights ms-Exch-EPI-Impersonation -InheritanceType None
Get-MailboxDatabase | Add-ADPermission -User "Sync Delegate" -ExtendedRights ms-Exch-EPI-May-Impersonate -InheritanceType All

Go to top

Creating a delegate user in Exchange 2010

Exchange server administrator access is required for this to work. With Exchange 2010 it is possible to limit the delegate access to a group of users.

  1. Create a delegate user into Exchange/AD
  2. Add full access right to the sync delegate user
  3. Create management scope for impersonation user with mailbox recipient filter
  4. Grant the sync delegate user impersonation role for the management scope
 
The following items are needed to set this up:
  • <OrganizationalUnitIdParameter>
  • <Fqdn>
  • <serviceAccount>
  • <scopename>
  • <recipientFilter>
  • <impersonationAssignmentName>
  • <ApplicationImpersonation>
 
Example, grant full access permissions for sync delegate user:
Get-Mailbox -OrganizationalUnit <OrganizationalUnitIdParameter> -DomainController <Fqdn> | Add-MailboxPermission -User <serviceAccount> -AccessRights Fullaccess -InheritanceType all

Example, create the management scope with recipient filter:

New-ManagementScope -Name <scopename> -RecipientRestrictionFilter <recipientFilter>

Example, impersonation role assignment:

New-ManagementRoleAssignment -Name <impersonationAssignmentName> -Role <ApplicationImpersonation> -User <serviceAccount> -CustomRecipientWriteScope <scopeName>

 For impersonation information, please see the MSDN Article Configuring Exchange Impersonation.

Go to top

Settings in Visma Severa (administrator)

1. Login Visma Severa

2. Click on Tools > Settings in the top menu and then click on Microsoft Exchange in the Organization section.

3. First select the correct Exchange server version from the dropdown: Exchange 2007/Exchange 2010/Exchange 2013/Exchange 2016/Office 365

4. Enter Domain, Exchange URL, Delegate username and Delegate password provided by your Exchange administrator.

It is possible to limit what activities are synced from Severa to Outlook based on activity type. Visma Severa's project tasks cannot be synced from severa to outlook calendar. Note! It is not possible to restrict what calendar entries are synced from Outlook to Severa. Private entries from Outlook are matched to activity type "Personal" if such an activity type exists in Visma Severa. All other entries get the Visma Severa default activity type. Read more about activity types.

Microsoft_Exchange_settings.png

Visma Severa users can now be notified to complete the calendar sync set up on their Personal details page.

Go to top

Settings for user in Visma Severa

1. Click on Tools > Personal details. Open the Calendar synchronization -section, and click to mark the Enable sync checkbox. Verify that the Username displayed below is correct so that the same email address is used as an Exchange email address and VIsma Severa login address. NOTE: Other user cannot enable to another user.

user_sync_enabled.PNG

When enabled, calendars will automatically be synchronized. You can manually start the sync by clicking Refresh button in "My activities" bar.

refresh.png

Go to top



Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.