Professional Documents
Culture Documents
V4.0
MIGRATION GUIDE
28 February 2014
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
Contents
Section 1 Introduction ............................................................................................................................... 4
Section 2 Overview ..................................................................................................................................... 5
Section 3 Preparation ................................................................................................................................ 6
3.1 Enter Maintenance Mode ................................................................................................................ 6
3.2 Backup The OVD Session Manager Data ...................................................................................... 7
Section 4 Installing OVD V4 ....................................................................................................................... 8
4.1 Upgrade The Session Manager ...................................................................................................... 8
4.1.1 Install OVD 4 ............................................................................................................................... 8
4.1.2 Session Manager Database Migration.................................................................................. 11
4.2 OVD Web Portal .............................................................................................................................. 12
4.2.1 Install OVD 4 ............................................................................................................................. 12
4.2.2 Modify The Web Portal Configuration .................................................................................. 14
4.3 OVD Windows Application Server ................................................................................................ 16
4.4 OVD Linux Application Server ....................................................................................................... 17
4.4.1 Update OVD 4 Subsystem ...................................................................................................... 17
4.4.2 Install OVD 4 Application Server Package ............................................................................ 18
4.4.3 Restarting the Linux Application Server ............................................................................... 20
4.5 OVD File Server ............................................................................................................................... 21
4.5.1 Update OVD 4 Subsystem ...................................................................................................... 21
4.5.2 Install OVD 4 File Server Package .......................................................................................... 24
4.5.3 Restarting the File Server ....................................................................................................... 26
4.6 OVD Gateway .................................................................................................................................. 27
4.6.1 Update OVD 4 Gateway .......................................................................................................... 27
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
Section 1 Introduction
This document describes the process to migrate an existing OVD v3.x farm to the latest major
version of OVD, v4.0
If your OVD installation contains swat patches, you need first to list them and contact us
to define how to proceed.
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
Section 2 Overview
The migration is a manual process that consists of the multiple steps. Each step is explained in
greater detail below.
Preparation: The system must be offline and should be backed up before migrating.
Installation: Each system component is updated in turn.
Completion: Run a test to make sure the migration worked.
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
Section 3 Preparation
3.1 Enter Maintenance Mode
In order to migrate to OVD V4, you will need to take the current system offline. First of all, stop
the services on each of the servers you have in your OVD farm and then switch the system to
maintenance mode.
OVD L INUX A PPLICATION S ERVER
root@server:~# /etc/init.d/ulteo-ovd-subsystem stop
OVD G ATEWAY
root@server:~# /etc/init.d/ulteo-ovd-slaveserver stop
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
4.1.1.1 Debian/Ubuntu
root@server:~# vi /etc/apt/sources.list.d/ulteo-ovd.list
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
You should see lines that have the value 4.0.0.0 as in the example below.
root@server:~# vi /etc/yum.repos.d/ovd.repo
[ovd-4.0.0]
name=Ulteo OVD 4.0.0
baseurl=http://archive.ulteo.com/ovd/4.0.0/rhel/6.0/
enabled=1
gpgcheck=1
gpgkey=http://archive.ulteo.com/ovd/4.0.0/rhel/6.0/keyring
You should see lines that have the value 4.0.0.0 as in the example below.
ulteo-ovd-administration-console-4.0.0.0.XXX.noarch
ulteo-ovd-l10n-4.0.0.0.XXX.noarch
ulteo-ovd-session-manager-4.0.0.0.XXX.noarch
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
You should see lines that have the value 4.0.0.0 as in the example below.
ulteo-ovd-administration-console-4.0.0.0.XXX.noarch
ulteo-ovd-l10n-4.0.0.0.XXX.noarch
ulteo-ovd-session-manager-4.0.0.0.XXX.noarch
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
You should see lines that have the value 4.0.0.0 as in the example below.
ulteo-ovd-administration-console-4.0.0.0.XXX.noarch
ulteo-ovd-l10n-4.0.0.0.XXX.noarch
ulteo-ovd-session-manager-4.0.0.0.XXX.noarch
root@server:~# vi migration_database.sql
Copy the following lines into the script and save it.
ALTER TABLE `ulteo_servers` DROP PRIMARY KEY, ADD `id` varchar(255), ADD
UNIQUE U_FQDN (`fqdn`);
UPDATE `ulteo_servers` SET `id` = `fqdn`;
ALTER TABLE `ulteo_servers` ADD PRIMARY KEY (`id`);
ALTER TABLE `ulteo_servers_properties` DROP PRIMARY KEY, CHANGE `fqdn`
`server` VARCHAR( 255 ) CHARACTER SET utf8 COLLATE utf8_general_ci NOT
NULL DEFAULT '', ADD PRIMARY KEY (`server`, `property`);
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
4.2.1.1 Debian/Ubuntu
root@server:~# vi /etc/apt/sources.list.d/ulteo-ovd.list
root@server:~# vi /etc/yum.repos.d/ovd.repo
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
[ovd-4.0.0]
name=Ulteo OVD 4.0.0
baseurl=http://archive.ulteo.com/ovd/4.0.0/rhel/6.0/
enabled=1
gpgcheck=1
gpgkey=http://archive.ulteo.com/ovd/4.0.0/rhel/6.0/keyring
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
// Option force SSO: do not allow the user to enter a login and
password. The login is set to use REMOTE_USER if possible
// define('OPTION_FORCE_SSO', true);
// define('OPTION_FORCE_SSO', false);
// default
// define('DEBUG_MODE', true);
// define('DEBUG_MODE', false);
// default
// default
//
//
//
//
//
//
//
//
//
//
//
//
// default
continued
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
// default
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
The subsystem should have already been stopped as part of the preparation. If not,
then issue the following command:
Modify the software installation sources file to add the new source
(OVD)root@srv:/#: vi /etc/apt/sources.list.d/ulteo_ovd.list
Add the new source for OVD 4 and save the changes
Update the software packages for the subsystem using the following command
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
NOTE: If you have installed the File Server on the same server, do not restart the slave
server now. The subsystem and slave server will be restarted once you have completed
the File Server migration.
Restart the slave server if the File Server is not installed on this server.
4.4.2.1 Debian/Ubuntu
root@server:~# vi /etc/apt/sources.list.d/ulteo-ovd.list
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
root@server:~# vi /etc/yum.repos.d/ovd.repo
[ovd-4.0.0]
name=Ulteo OVD 4.0.0
baseurl=http://archive.ulteo.com/ovd/4.0.0/rhel/6.0/
enabled=1
gpgcheck=1
gpgkey=http://archive.ulteo.com/ovd/4.0.0/rhel/6.0/keyring
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
Install OVD 4
To restart the Application Server, issue the following command to restart the
subsystem from outside the chroot
NOTE: If you have installed the File Server on the same server, do not restart the slave
server now. The subsystem and slave server will be restarted once you have completed
the File Server migration.
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
(OVD)root@server:/#: vi /root/profiles_migration.sh
#!/bin/bash
LOG=profiles_migration.log
DATETIME="[$(date '+%Y/%m/%d') - $(date '+%H:%M:%S')]"
echo "${DATETIME} Move fs directory to fs.real directory " >> $LOG 2>&1
mv /var/lib/ulteo/ovd/slaveserver/fs
/var/lib/ulteo/ovd/slaveserver/fs.real >> $LOG 2>&1
echo "${DATETIME} Create new fs directory " >> $LOG 2>&1
mkdir -p /var/lib/ulteo/ovd/slaveserver/fs >> $LOG 2>&1
for p in /var/lib/ulteo/ovd/slaveserver/fs.real/p_*
do
echo "${DATETIME} Start copying data from directory ${p}" >> $LOG
2>&1
continued ..
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
if [ -e ${p}/conf.Windows ]; then
echo "${DATETIME} Create conf directories in ${p}" >> $LOG 2>&1
mkdir ${p}/conf.Windows.2008R2 ${p}/conf.Windows.2008
${p}/conf.Windows.2003 >> $LOG 2>&1
echo "${DATETIME} Rename AppData and LocalAppData in ${p}" >> $LOG
2>&1
mv ${p}/conf.Windows/AppData ${p}/conf.Windows/CSIDL_APPDATA >>
$LOG 2>&1
mv ${p}/conf.Windows/LocalAppData
${p}/conf.Windows/CSIDL_LOCAL_APPDATA >> $LOG 2>&1
echo "${DATETIME} Copy data from directory in ${p}" >> $LOG 2>&1
cp -R ${p}/conf.Windows/* ${p}/conf.Windows.2003 >> $LOG 2>&1
cp -R ${p}/conf.Windows/* ${p}/conf.Windows.2008 >> $LOG 2>&1
cp -R ${p}/conf.Windows/* ${p}/conf.Windows.2008R2 >> $LOG 2>&1
rm -rf ${p}/conf.Windows/ >> $LOG 2>&1
fi
echo "${DATETIME} Move Desktop and Documents to Data directory in
${p} " >> $LOG 2>&1
mkdir ${p}/Data >> $LOG 2>&1
mv ${p}/Desktop ${p}/Documents ${p}/Data >> $LOG 2>&1
done
echo "${DATETIME} Chown on /var/lib/ulteo/ovd/slaveserver/fs ">> $LOG
2>&1
chown ovd-fs:ovd-fs /var/lib/ulteo/ovd/slaveserver/fs >> $LOG 2>&1
Make the file executable and run the script. The script will create a log file in the
same folder.
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
Now update the OVD software. Working inside the OVD Subsystem, remove the
package ulteo-ovd-desktop-settings.
Modify the software installation sources file to add the new source
(OVD)root@srv:/#: vi /etc/apt/sources.list.d/ulteo_ovd.list
Add the new source for OVD 4 and save the changes
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
4.5.2.1 Debian/Ubuntu
root@server:~# vi /etc/apt/sources.list.d/ulteo-ovd.list
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
root@server:~# vi /etc/yum.repos.d/ovd.repo
[ovd-4.0.0]
name=Ulteo OVD 4.0.0
baseurl=http://archive.ulteo.com/ovd/4.0.0/rhel/6.0/
enabled=1
gpgcheck=1
gpgkey=http://archive.ulteo.com/ovd/4.0.0/rhel/6.0/keyring
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
To restart the File Server, issue the following command to restart the subsystem
from outside the chroot
NOTE: If you have installed the File Server on the same server as the Application
Server, this command will start both the File Server and the Application Server.
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0
root@server:~# vi /etc/apt/sources.list.d/ulteo-ovd.list
Add the OVD source for Debian/Ubuntu and save the file
Install OVD 4
U l t e o O p e n V ir t u a l D e s k t o p v4 . 0