Same experience here. It was very easy. Just be sure to shut off all the
IMail services before you start copying the files.
-d
----- Original Message -----
From: "John Doyle" <[EMAIL PROTECTED]>
To: <declude.junkmail@declude.com>
Sent: Wednesday, May 30, 2007 10:38 AM
Subject: RE: [Declude.JunkMail] Version and hardware move
Andy - Mike
So I would move the registery entry for the $virtualnnn and the
corresponding domain entry under Imail. Then the folder (drives and
installation paths are the same) for the domain. Update the persissions,
Then run the wgscvt program to update contacts. It seems too simple. Which
is fine with me.
John
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Andy
Schmidt
Sent: Tuesday, May 29, 2007 7:50 PM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] Version and hardware move
Sensitivity: Personal
Hi,
I didn't encounter any problems when I upgraded two servers from 8.x to
2006.x just by moving the registry and folders. Mailbox and address book
formats have changed. Mailboxes are upgraded on the fly upon first use under
the new version, address books have to be manually upgraded.
Best Regards,
Andy
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John
Doyle
Sent: Tuesday, May 29, 2007 6:34 PM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] Version and hardware move
Sensitivity: Personal
Andy
If the old box is 8.22 and the new one is 2006.2, is it safe to move
the registery and folders? are the formats the same? and all i have to
do is run the conversion on the contact/address book?
John
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Andy
Schmidt
Sent: Tuesday, May 29, 2007 2:51 PM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] Version and hardware move
Sensitivity: Personal
The user and alias information is in the registry. Mailing lists, address
books and mailbox content is in the \Imail\[domain name]\ folder on your
server.
I would start by updating the DNS MX record(s) to a very low refresh ahead
of time.
You export the appropriate Registry section for that domain. See if the
$virtual... is available on the new server, if not, adjust it by using
Notepad in the exported file.
Stop the old Imail server (to prevent more mail from piling up).
Copy the domain folders from the old to the new server's disk.
Import the registry section to the new server.
Use the Imail Admin to confirm that you can see the domain and users on the
new server. Try logging into webmail to confirm that you can see the mailbox
content.
Switch the MX record to the new server. Update the TTL to a normal value.
Delete (or rename the registry section of) the domain on the OLD server and
then start the old Imail again. Confirm on the old Imail that the domain no
longer shows.
Run the contact/address book conversion tool on the new server.
Obviously, it's easier if you do an entire server with all domains (because
then you don't have to worry about cleaning up each domain on the old
server, you simply don't restart it) - but the other steps are essentially
the same.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John
Doyle
Sent: Tuesday, May 29, 2007 12:39 PM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] Version and hardware move
Sensitivity: Personal
Sorry guys,
It was a long weekend and I meant this for the Ipswitch forum.
John
Morning all
I spent the weekend firing up a new W 2003 server and installing Imail
2006.21 on it. I think I've delt with most of the installation issues.
I would like to move clients over a domain at a time w/o doing using the
technique of upgrading the old 8.22 machine and copying over the registery
and Imail folder, as I want to go slow on this process.
I've looked in the archives and I havent been able to find a "best
practices" approach. With more history now, does anyone feel there is a best
approach to moving a domain with all the clients? And if so what would the
steps be.
Thanks in advance
John
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
