is it possible to rename an exchange server

[timbo343]

Hello All:

 

I am installing Exchange 2007. Ive got over all my problems with the bloody thing and now I am at the point to where I am beginning to move mailboxes over from my legacy system to Exchange 2007. My question is after the mailboxes are moved and I have finished decommisioning the old exchange server - can I rename the new Exchange 2007 server and call it the Computer Name of the old exchange server without any problems? For example, the present old exchange server is called Server1 and the New Echange 2007 server is called Server2. I would like to rename the Server2 and call it Server1.

 

Is this possible?

 

Thanks

 

Tim

[PiqueABoo]

You should NOT do that with E2K3 because it breaks. I expect the same is true for 2K7. Look at PRFs if the concern is to get clients hooked up to the new server.

[zag]

I wouldn't do this, infact I'm pretty sure you cant do it.

 

Also what would be the point? It's just a name.

[Dos_Box]

To quote Egon from Ghostbusters: 'It would be bad'.

[timbo343]

well what about all the data then? How do you get all the emails across to the new server if the old server is off? if i have to set the server up with another name, does that mean ive got to go round all the machines that use outlook and pst files and change the name of the server path?

[Dos_Box]

Oh yes.

And pst files!! OST (offline exchnage files. are the way ahead now as pst are just to flaky, as well as having a 2GB file limit.

[PiqueABoo]

How do you get all the emails across to the new server if the old server is off?

 

Not entirely sure what you're doing but Exmerge has worked for me (saves mailboxes to PST file that can be imported on another Exchange box).

 

Oh yes.

 

So what's wrong with PRFs then?

[timbo343]

How do you get all the emails across to the new server if the old server is off?

 

Not entirely sure what you're doing but Exmerge has worked for me (saves mailboxes to PST file that can be imported on another Exchange box).

 

Oh yes.

 

So what's wrong with PRFs then?

 

what im trying to do is set up a brand new exchange 2007 machine with the same name as the current exchange server which is hermes. Obviously a domain wont accept 2 machines with the same name and you cannot set up an exchange server, move the mail boxes and then rename the server, so how do i go about moving all the mailboxes from one server to another?? About 80% of staff use OWA too, so creating pst files probably ain thte best idea.

[OutLawTorn]

Could you create a dns alias that points the old server name to the new server, and then phase the old one out once the new one is stable? you may have to tell the old server to not register its name in dns under the tcp/ip settings.

 

Not sure if it would work or not, just a possible suggestion?

[Disease]

Why not just re-setup the Exchange 2007 server and call it Mailserver_new then migrate the mailboxes using the mailbox migration tool that is available. The length of time you are waiting for a solution to the initial problem you could have had it up and running by now. Bite the bullet and reinstall is what I would do.

[timbo343]

Im going to use the Mailbox merge wizard, has anyone used this program before? Does it only backup the mailboxes? Im a bit worried if it deletes them too, as im going to do a dummy run tonight

[maniac]

Oh yes.

And pst files!! OST (offline exchnage files. are the way ahead now as pst are just to flaky, as well as having a 2GB file limit.

 

I hate PST and OST files, causes all sorts of issues for us if a staff member logs onto a different machine where their OST or PST file isn't present. I've got exchange cached mode firmly switched off on our domain, outlook problems have evaportated overnight!

 

Mike.

[zag]

Oh yes.

And pst files!! OST (offline exchnage files. are the way ahead now as pst are just to flaky, as well as having a 2GB file limit.

 

I hate PST and OST files, causes all sorts of issues for us if a staff member logs onto a different machine where their OST or PST file isn't present. I've got exchange cached mode firmly switched off on our domain, outlook problems have evaportated overnight!

 

Mike.

 

You could just store the pst files on the network share.

[DMcCoy]

I hate pst files to. Last time I used it Exmerge also only supported 2000 and below psts for import. I have none and like Maniac also have cached mode turned off.

[john]

There is a way somewhere in the MS KB for doing that with 2000 to 2003 as i've done it but I did use the MS KB as a step by step guide but it is possible so I would say its possible to re-use the same name again. I would search the MS KB harder and see what you can find.

[SYNACK]

If you want to keep the old server name you could setup a middleman server. What you must do is setup another Exchange 2003 server with a different name possibly in a virtual machine. You then transfer all of the email accounts over to the middleman server using the move mailbox option in Exchange System Manager, this is the fastest and safest way to move the mailboxes so long as the servers are both online. Also transfer the Public folders across.

 

Once you have done that you can decommission the old server, ie uninstall exchange which removes it from AD and change its name. You can then install the new server to the domain using the old name and transfer the mailboxes and public folders back to your new server.

 

I think that Outlook 2007 has a server auto location feature so changing the server name may not be necessary anyway depending on you policy settings.

 

Oh and if get errors when attempting to move any of the mailboxes across from the old server you can run a database compact and repair. Just use the ESEUtil.exe app which usually fixes up corrupted mailboxes that refuse to transfer.