Hi, See my mail a bit earlier in this area. Several mails in feb 2007.
Met vriendelijke groet, Bonno Bloksma hoofd systeembeheer tio hogeschool hotelmanagement en toerisme begijnenhof 8-12 / 5611 el eindhoven t 040 296 28 28 / f 040 237 35 20 [EMAIL PROTECTED] / www.tio.nl ----- Original Message ----- From: Imail Admin To: [email protected] Sent: Saturday, March 10, 2007 4:15 AM Subject: [IMail Forum] 2006.2 migrate or in-place upgrade and what's involved Hi, With the release of 2006.2, we're finally ready to upgrade. We've been waiting a long time, as shown by the fact that our old server runs 7.15. We have a new server ready to run 2006.2, and I can see two paths to take: 1. Copy over the existing 7.15 installation to the new machine, then install 2006.2 over it. 2. Do a fresh install of 2006.2 to the new machine, and then migrate the users. Path #2 is preferrable to two reasons: first, we've been running IMail a long time and the old server has a lot of legacy files and registry entries dating back to Version 4 or 3. So a clean start would be nice and might help to avoid future problems. Second, we would really prefer to move the domains over a few at a time, just to make sure everything is running smoothly. Moving everyone over at once is just asking for trouble in trumps. Path #1 is preferrable for one reason: I make sure that all of the users, their messages, settings, lists, etc. all get moved over correctly. I know that I can generate a list of domains and users to use with adduser.exe, but I don't know about actually moving their mail all over to the new system. Is there an easy or automated way to do that? Will it work to just copy over all of the mailbox files? And what about rules, lists, and other personalized items? I looked through the archives backwards and forwards, and although I saw a couple of questions along this line, I didn't see any detailed answers. Which path is preferrable? And if I follow Path #2, what is involved in migrating the domains, users, their mail, and everything else? Thanks, Ben BC Web
