...
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 | |
4. Move PeopleSync Console & Backend4 Moving PeopleSync | |
5. Move PeopleSync Frontend | 5 Moving PeopleSync Frontend |
...
| Info |
|---|
Always follow the checklist in the given order. If you are moving the database, move it first. This prevents duplicate work. |
Example: You are moving all components of PeopleSync. Therefore, you need to perform steps 1, 4, and 5 of the checklist. Steps 2 and 3 should be skipped as you will retire the old components.
...
This chapter outlines how to move the PeopleSync database to a different server.
Important Note: You should not move the PeopleSync database to a SQL Server with a lesser version than the source SQL Server.
...
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, 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.
...
Detach the PeopleSync database on the old SQL Server by right-clicking on the database in SQL Server Management Studio and selecting Tasks|Detach.
...
If the PeopleSync frontend server is not moving to a different server, please follow these steps to change the database connection to the new SQL Server:
Login to the PeopleSync Web server.
Run Notepad using Run as Administrator.
In File|Open, go to the PeopleSync Frontend installation directory, i.e. C:\Program Files\messageconcept GmbH\PeopleSync Server, then to the www subdirectory. Open the server.ini file.
Edit the db_host parameter to reflect the new server name.
Save server.ini and close Notepad.
...
If the PeopleSync Console & Service are not moving to a different server, please follow these steps to change the database connection to the new SQL Server:
Login to the PeopleSync Service server.
Run Notepad using Run as Administrator.
In File|Open, go to the PeopleSync Agent installation directory, i.e. C:\Program Files\messageconcept GmbH\PeopleSync\Agent. Open the Agent.exe.config file.
Search for ConnectionString in the file. You should find an element such as:
<add name="ConnectionString" connectionString="Integrated Security=SSPI;Pooling=false; Data Source=srv-1;Initial Catalog=PeopleSync" />
Please note that “<add name=..” may not be preceded by “<!--“Change the value in “Data Source” to reflect the new server name. For example:
<add name="ConnectionString" connectionString="Integrated Security=SSPI;Pooling=false;Data Source=newSQLServer;Initial Catalog=PeopleSync"/>Save agent.exe.config.
Repeat steps 13-16 with the WorkflowExecutor.exe.config file in the Workflow Executor directory, i.e. C:\Program Files\messageconcept\PeopleSync\Agent\wfx.
In File|Open, go to the PeopleSync Console installation directory, i.e. C:\Program Files\messageconcept GmbH\PeopleSync\Console. Open the PeopleSync.Console.exe.config file.
Repeat steps 13-16.
Close Notepad.
Repeat Steps 18-20 for each computer with a PeopleSync Console.
Login to the PeopleSync Service server.
Set the startup type of the service "PeopleSync Service" back to "Automatic" and start the service.
...
If the PeopleSync Console & Service are not moving to a different server, please follow these steps to change the database connection to the new SQL Server:
Login to the PeopleSync Service server.
Run Notepad using Run as Administrator.
In File|Open, go to the PeopleSync Agent installation directory, i.e. C:\Program Files\messageconcept GmbH\PeopleSync\Agent. Open the Agent.dll.config file.
Search for ConnectionString in the file. You should find an element such as:
<add name="ConnectionString" connectionString="Integrated Security=SSPI;Pooling=false; Data Source=srv-1;Initial Catalog=PeopleSync" />
Please note that “<add name=..” may not be preceded by “<!--“Change the value in “Data Source” to reflect the new server name. For example:
<add name="ConnectionString" connectionString="Integrated Security=SSPI;Pooling=false;Data Source=newSQLServer;Initial Catalog=PeopleSync"/>Save agent.exe.config.
Repeat steps 13-16 with the WorkflowExecutor.dll.config file in the Workflow Executor directory, i.e. C:\Program Files\messageconcept\PeopleSync\Agent\wfx.
In File|Open, go to the PeopleSync Console installation directory, i.e. C:\Program Files\messageconcept GmbH\PeopleSync\Console. Open the PeopleSync.Console.dll.config file.
Repeat steps 13-16.
Close Notepad.
Repeat Steps 18-20 for each computer with a PeopleSync Console.
Login to the PeopleSync Service server.
Set the startup type of the service "PeopleSync Service" back to "Automatic" and start the service.
...
This chapter outlines how to move the PeopleSync Console & Agent to a different server.
...
To prepare for the move, please assemble the following information:
PeopleSync Admins group
As specified during initial setup. If you don’t know the group any more, please create a new one in Active Directory and make a note of the name. Please add all users of PeopleSync console to this group, if not already the case.PeopleSync Service account:
On the old PeopleSync server, go to Administrative Tools > Services and make a note of the account used to run the service named “PeopleSync Service”.PeopleSync encryption key:
The encryption key you set using PeopleSync Encryption configurator during initial install.PeopleSync License keys
Copy the license keys from your old PeopleSync Server. They are in %ProgramFiles%\messageconcept\PeopleSync\Agent\licensekeys.
On the new server, please add the PeopleSync Service account to the local admins group.
...
Run “PeopleSync Console Setup-*.exe” as described in the PeopleSync Setup and Configuration Guide, section 4.1. During setup, please enter the configuration values from the previous section.
Hint: When you specify your existing PeopleSync database during setup, the installer will configure PeopleSyn Console & Agent to use it. The database will not be overwritten.
After setup, copy the license keys to %ProgramFiles%\messageconcept\PeopleSync\Agent\licensekeys.
If you are not moving PeopleSync Frontend, you can start PeopleSync Service now, otherwise you should do it after you have moved PeopleSync Frontend.
...
This chapter outlines how to move the PeopleSync Frontend component to a different server.
...
To prepare for the installation of the new PeopleSync Frontend, please assemble the following information:
Firewall ports: If the new PeopleSync Frontend is in the DMZ, please make sure all necessary firewall ports are open. The default ports are:
...
Source
...
Target
...
TCP-Port
...
Descrption
...
CardDAV Clients
...
PeopleSync Web
...
443
...
HTTPS CardDAV
...
CardDAV Clients
...
PeopleSync Web
...
8843
...
iOS HTTPS CardDAV
...
PeopleSync Service
...
PeopleSync Web
...
443
...
PeopleSync Frontend (HTTPS CardDAV)
...
CardDAV Clients
...
PeopleSync Web
...
88
...
PeopleSync Frontend (HTTP CardDAV)
...
PeopleSync Service
...
PeopleSync Web
...
88
...
PeopleSync Frontend (HTTP CardDAV)
If you have used custom ports, please open these as well.
SSL Certificate: Prepare an SSL certificate for the new server.
Bindings: Make a note of the bindings or the PeopleSync website on the old server:
Open Internet Information Services (IIS) manager.
Go to the PeopleSync website.
Right-click on the PeopleSync Website and select Edit Bindings.
Make a note of the port bindings and the certificates used.
SQL Server user: On the old Server, open the file %ProgramFiles%\messageconcept\PeopleSync Server\web\server.ini. Note down the value of the db_login variable. This is the username of the user which is used to connect to the PeopleSync database.
...
Run PeopleSync Frontend Setup-*.exe as described in the PeopleSync Setup and Configuration Guide, section 4.2.2. During setup, please enter the configuration values you have assembled in the previous section.
Import the SSL certificate.
Re-Create any non-default bindings on the PeopleSync website, such as https on port 443 or 8843.
After setup, please open PeopleSync Console and go to System Settings. Change Internal URL to point to the new PeopleSync Frontend.
...
The following steps help you establish if all PeopleSync components work.
...
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".
...
On the Server where the PeopleSync Service is installed,check whether the PeopleSync Service is running.
If the service is not running, check the Application log for error messages from source PeopleSync_Agent.
...
Open the PeopleSync Console and log in.
If you can open the console and log in, the console is configured correctly. Otherwise, an error message will appear.
...
Open the PeopleSync Console and log in.
Manually start an agent from the console.
Open Log and verify that Agents have run successfully.
...
If this manual unfortunately does not help to solve your problem, please contact messageconcept support.
Our support staff will guide you through the troubleshooting process or will establish a remote session, if needed.
Please download our TeamViewer QuickSupport Module to receive remote support in a guided session before giving us a call.
...
messageconcept GmbH
Gesellschaft für IT-Marketing
Grosse Witschgasse 17
50676 Cologne Germany
Phone +49 221 677 855 0
Fax +49 221 677 855 99
E-Mail info@messageconcept.com
Internet www.messageconcept.com
...
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
Our support team is further reachable via Skype:messageconcept (voice-only).
Our hotlines are available 24/7. Outside European business hours you will be connected to one of our call center agents and will receive a callback during business hours of your time zone.
1
I