Best way to migrate from Kolab 3.0 to 3.3?

[Thomas Weyers]

I thought to do it by this way:

stop services
do a complete ldapdump
do an ldif-export of relevant branch
change all userpasswords in the ldif by script into a unique password
recharge modified ldif
do imapsync
restore previous saved ldapdump
restart services

Thomas

-------- Message initial --------
De: Alan Miller <kolab at fencepost.net>
À: users at lists.kolab.org
Sujet: Best way to migrate from Kolab 3.0 to 3.3?
Date: Tue, 21 Oct 2014 02:35:33 -0500
Client de messagerie: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.5.0

I have a single-site, single-server installation still running on Kolab 
3.0 on CentOS, and I'd like to look at moving them up to 3.3. Rather 
than doing an upgrade (or 2 or more upgrades) given the changes between 
the versions, would I be better off setting up a new 3.3 server and 
recreating the accounts, then using imapsync to pull everything across? 
I do have (or can get) all of the relevant passwords and already have 
the imapsync mostly scripted from when they first moved onto Kolab.

Thanks for any suggestions,
Alan
_______________________________________________
users mailing list
users at lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users

-- 
*********************************
Thomas Weyers
Muséum National d’Histoire Naturelle
CP 25 – Pavillon Chevreul
57, rue Cuvier
75005 PARIS

Tel : 01 40 79 31 15
Fax : 01 40 79 38 99
mél : thomas.weyers at mnhn.fr
***********************************
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4336 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/users/attachments/20141021/f23ce670/attachment.bin>