Change computer name and IP address on an Exchange 2007 server

Well on the IP part thats rather easy. Just make sure the dns records are updated properly. But the name is going to be a problem. The name of the host is written inside the exchange information store. Change that will prop kill your exchange...

You can install a new box and migrate to that envirnoment if you like...

-Regards

So there is no special tool to do that? I have 150 users that I really don't want to go around to every single one and set it up. 150 isn't a lot, how do corporations do it that have 1000 users in multiple states?

I am at the process of moving the mailboxes right now. Is it best to just leave it there and let for say the rest of the week and let everyone log in with both of them running and then down it at the end of the week. Is that what you are saying?

I know that just renaming the server would be tragic I was just hoping there was a tool.

I do have a 2003 Schema master DC

Leaving it there for a week is perfect.  

Are you also migrating public folders? Isnt it funny how there is no public folders tools in the 2007 EMC?

Yes I am migrating public folders. I am a little confused as to exactly what will change if anything. All we use public folders for is for shared email boxes and group calendars. Do you know if that will be affected?

One more question, our 2000 exchange server maillbox size is maxed out, which is the main reason why we are upgrading, if I leave it up for a week will I have any size limit problems as long as the mailboxes have moved?

You can still get your public folders onto 2007, it is just that the tools for managing them are mostly coming in SP1.  First, setup a separate DB in 07.  Then go into the 2k EMC, go into the public folders.  You will need to set the replication for each folder to include the new server. (remove the old server replication at end of week).

I do not have an EMC in front of me, but you can track the replication in there somewhere.

RE: maxed out DB. Once you get your mailboxes moved you will have no problems.  The DB will remain huge though until you do an offline defrag.  I wouldn't worry about that to much, but if you do it, make sure that you back up your DB right before the defrag, because your transaction logs are rendered useless after an offline degrag.

If you setup the exchange server correctly into the Exchange 2000/2003 Organization, and you use the EMC to move the users to the new 2007 server, The client connection settings should automaticaly change from old server to the new one. without any Admin intervention required. This is also true for OWA or Exchange anywhere users. it is however recommended that the clients outlooks be online while you do this, so that the Outlook clients can receive the new connection setting from the server dynamically. I have seen that sometimes offline client's setting dont get migrated, then you have to do it manually

Moving exchange server to different IP subnets is also strait forward. Exchange is DNS intensive. so moving an exchange server to another IP range is easy. You change your DNS settings with the new IP adress and then change the ip on the exchange server. Reboot is required... However if you use AD sites and multiple 2007 servers  you need  HUB Transport role installed. Because AD sites means you have defferent ip subnets between the exchange servers.