Requirements and checklist when using SuperOffice Onsite
Synchronizer for SuperOffice is also available for SuperOffice CRM Onsite. There are some requirements the environment must meet and also there are additional configuration steps needed for the SuperOffice environment and Synchronizer for SuperOffice.
Synchronizer for SuperOffice will still be running in the cloud but will connect to your local SuperOffice CRM environment via the publicly exposed SuperOffice NetServer in your SuperOffice setup.
Requirements
The following requirements are additional to the main requirements if Synchronizer for SuperOffice is used in combination with SuperOffice CRM Onsite.
SuperOffice CRM Onsite 9.x and higher
SuperOffice System User
SuperOffice NetServer needs to be accessible from the internet through HTTPS
Travel
Travel needs to be enabled for the Synchronizer to work. If you have used the onsite synchronizer (Exchange Online Synchronizer) before, this should be the case.
If you want to check if Travel is enabled on the database run the following SQL query:
select * from [CRM].[USERPREFERENCE] where prefkey = 'EnableTravel'
(Replace CRM with the corresponding prefix for the database)
The result of this query should be:
If the query does not give the above record, follow the procedure on this page to insert this record in the SuperOffice database.
UPN (Microsoft 365)
When using Synchronizer for SuperOffice with SuperOffice Onsite, it is necessary that the UPN (userPrincipalName) matches the primary e-mail address. Which is also what Microsoft recommends as best practice.
When the UPN does not match the primary e-mail address, a syncuser will receive below error when trying to activate the Calendar Synchronization:
Microsoft Exchange
Microsoft Exchange On-premise is not supported when using Synchronizer for SuperOffice with SuperOffice Onsite.
Setup
1. Subscription
A subscription is required to use Synchronizer for SuperOffice. For a subscription, please reach out to your SuperOffice contact or partner.
2. Request a Synchronizer account to access the synchronizer portal
SuperOffice Onsite does not support SuperID, the SuperOffice sign-in service. Therefore, the Log in with SuperOffice button will not link to your SuperOffice Onsite installation. The button Log in with Password is the alternative here. It will not connect you automatically to your local SuperOffice installation, but it will provide access to the synchronizer portal. From there you can connect to your local SuperOffice installation.
However, before you can use this button to log in to the synchronizer portal, you need to have an account. For security reasons, such an account has to be requested. You, or a SuperOffice consultant, need to fill out this form, so we can set up the environment for you.
3. SuperOffice NetServer
Synchronizer for SuperOffice needs to connect to your locally hosted SuperOffice installation. Therefore, NetServer needs to be exposed and accessible by our cloud platform.
In the current SuperOffice installations, the Expose NetServer web services checkbox is selected by default and may not require configuration.
You can verify if NetServer is exposed by checking the result of an .svc endpoint in a browser (for example SOPrincipal.svc).
Do not include the *.svc part when filling in the NetServer URL in the synchronizer profile. This URL should look like https://<your_SuperOffice_url>/Remote/Services88
3. Create a synchronization profile
When you sign in to the synchronizer portal, a license warning will be shown because the local SuperOffice installation is not yet connected and the serial number has not been validated.
In order to validate the serial number, you have to create a synchronization profile by using these instructions.
After completing the steps to create the synchronization profile, your synchronizer license will be retrieved. This can take up to 24 hours.