Hello, That reminds me a couple other things the FAQ didn't go into (e2K):
-If you set the old server's mailbox stores to point to the new server's PF, then any remaining users in the old Mailbox store will be unable to see the PFs thru OWA. There are several Q articles on this. -Outlook users that are remote and in "off-line" mode don't automatically find their moved mailbox. If you can get them to just connect once "on-line" after the move everything works out. An issue if you've got a lot of remote users. Good Luck, Brent -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of MSXLIST (MSX Discussions List) Posted At: Wednesday, October 01, 2003 12:43 AM Posted To: MS Exchange List Conversation: Exchange 2000 Server Replacement Subject: RE: Exchange 2000 Server Replacement If you're using public folders, make sure you set the Private Information Store setting to point to the PF server as well. The trick here, as well as the obvious job of setting the new server to point to itself as the PF server, is also to do the less obvious job of setting the old (now empty of mailboxes and PFs server) to also point to the new server as its PF server. -----Original Message----- From: Dean Cunningham [mailto:[EMAIL PROTECTED] Sent: 01 October 2003 04:25 To: Exchange Discussions Subject: RE: Exchange 2000 Server Replacement So long as the server there were homed on is not removed before *all* client profiles on all machines have had outlook opened on them. It goes like this User logs in and runs up outlook (Outlook reads its configuration info Oulook connects to old home server and asks to connect to mailbox Old server says "clear off and talk to this new server" Outlook talks to new server and gets mailbox Outlook writes new mailbox location to outlook profile. If old mail server is removed and user has not logged in yet, When user goes to log on , outlook can't find the old server and has no idea about the new one. All it means is ya go into outlook/services and put the new server name in. cheers Dean If the old server is the "first exchange server" check the FAQ for Ed's move server method. >>> [EMAIL PROTECTED] 1/10/2003 9:38:46 a.m. >>> No need to reconfigure clients. Sincerely, Andrey Fyodorov Systems Engineer Messaging and Collaboration Spherion -----Original Message----- From: Jeremy T. Slater [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 30, 2003 5:11 PM To: Exchange Discussions Subject: Exchange 2000 Server Replacement Greetings! I am going to throw out a question, showing my obvious exchange ignorance. We have 4 Exchange Mail Servers in our Organization and we need to replace one of them, as the box is old and slow. This server serves about 100 mailboxes. I am assuming I can build out the new server, install exchange and just move the mailboxes to the new server. The only problem I see with this, is having to reconfigure all of the clients to point to the new server. I would really like to keep the server name the same, but don't think it is possible. Any ideas? Thanks, Jeremy --- Jeremy T. Slater Network Administrator MMA Financial, LLC - http://www.mmafin.com 727.373.8153 - Direct 727.461.4801 - Receptionist 727.443.6067 - Fax [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&; lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
