Comments on: Exchange Upgrade 2000-2003

By: wrobinson

wrobinson — Wed, 21 Nov 2007 06:43:16 +0000

Try logging in to some of the mailboxes then see if they appear in ESM.

By: pdmeat

pdmeat — Sat, 13 Jan 2007 16:08:31 +0000

You don’t need exchange on the test server. Just remove exchange and leave it as an SMTP server forwarding all mail for the internal domain to the new server IP.

Exchange 2000-2003 upgrades are easy. I recommend the mailbox move method mysel. I’ve never had a mb move to an upgraded server cause a problem yet (knock on wood).

By: windowsjedi

windowsjedi — Fri, 12 Jan 2007 23:35:56 +0000

What should have been done.
Exchange heavily uses DNS for service location and message delivery, so as long as you’ve updated the DNS records (along with any HOSTS file entries that you might have used to eliminate the need for WINS) for the servers you’re moving, you should be fine. By default, all the virtual servers should use the All unassigned setting, which means that they’ll automatically pick up the new addresses. If you’ve assigned specific IP addresses to any of your virtual servers, you’ll need to update those addresses, too.

If you’re using clustering, the answer is slightly different. In a cluster, you must update three items: the cluster’s IP address resources, the IP addresses assigned to the virtual servers, and the IP addresses assigned to the physical cluster nodes. . . .

By: jmweber

jmweber — Fri, 12 Jan 2007 15:25:40 +0000

Make a group, make it a distribution list.
Add all your users to it.
Send the group a message.

Exchange RUS won’t actually make the mail box unless there is a reason to do so.

John