...
...
...
...
...
...
...
PeopleSync
...
Content
| Table of Contents |
|---|
Important Note: Please read the complete manual carefully.
Hint: The blue hint boxes will save you time and are very helpful for the understanding of the software functionality.
Last Update: 2023-11-03
...
PeopleSync consists of three main components: the database, PeopleSync Agent and Console, and PeopleSync front end server. This guide shows how to move the PeopleSync components to a different Server.
...
Migration Checklist
The following Checklist helps you move PeopleSync Components. Please follow the checklist in the given order.
...
What you want to do | What steps to perform |
1. Move the PeopleSync Database | 3.1 Moving How to move the database |
2. PeopleSync Frontend is staying | |
3. PeopleSync Console & Backend are staying | 3.3 Configuring the PeopleSync Backend |
4. Move PeopleSync Console & Backend | 4 Moving PeopleSync Backend |
5. Move PeopleSync Frontend | 5 Moving PeopleSync Frontend |
...
Close all running PeopleSync Consoles.
Set the startup type of the service PeopleSync Service to Disabled.
Restart the system.
Backup the PeopleSync database on the old SQL Server and restore the database on the new SQL Server as outlined in Microsoft KB article 314546 (http://support.microsoft.com/kb/314546/en).
On the old SQL Server, create the necessary stored procedures sp_hexadecimal and sp_help_revlogin for transferring the PeopleSync logins by following step 1 of method 2 from Microsoft KB article 918992 (http://support.microsoft.com/kb/918992/en).
On the old SQL Server, in SQL Server Management Studio, switch to the PeopleSync Database:
To create a script for re-creating the logins, run the following command in the query window:
In the Messages window, copy the output between the “copy below” and “end copy” lines to the clipboard.
To recreate the logins on the new SQL Server, use SQL Server Management Studio to connect to the new SQL Server instance and run the script you copied before in a query window with Master database selected:
On the new Server, check that for each user in the PeopleSync database you have a corresponding login at the server level:
Open the properties of each login relevant to PeopleSync and make sure that they have at least db_datareader and db_datawriter permissions in the PeopleSync database. For reference, compare with the old database.
Users performing updates of PeopleSync must have db_owner permissions on the PeopleSync database.Detach the PeopleSync database on the old SQL Server by right-clicking on the database in SQL Server Management Studio and selecting Tasks|Detach.
...
In System Settings, copy the internal URL.Anchor _Toc480404229 _Toc480404229 Open a browser on the PeopleSync Backend server and put in the internal URL.
A popup should appear prompting you for credentials.
Now enter the service account credentials from Address Lists > Service Accounts.
If authentication is successful, a message is shown saying "Everything is working is as expected".
| Anchor | ||||
|---|---|---|---|---|
|
...
For technical sales and software support please use the following contact details.
Languages | Countries | Hotline Numbers |
English | US/CA | +1 778 786 3475 |
UK | +44 870 479 8657 | |
Other | +49 221 677 855 44 | |
German | DE/AT/CH | +49 221 677 855 49 |
...