Exchange Server Renaming

[GKnight]

I have a problem which I am fairly sure I already know the answer to but
just thought I would get a second opinion.

Exchange Server 2003 machine with seriously low hardware spec. I want to
move this onto new hardware.

I have an Exchange Organisation with 7 exchange servers. The suggestion was
that I install this new server, transfer all the mailboxes(600+) onto it
allow replication etc. to occur then decommision the old exchange server,
and here is the interesting part RENAME the new exchange server to the old
servers name so that the naming convension is right.

No my instant reaction to this was, "you have to be kidding right??" but no
it was a serious suggestion so I thought I would do some digging around and
I am unable to find ANY documentation that either confirms that it can or
can't be done.

Unfortunately we are unable to move the mailboxes to any of ther other
servers and then decommision the old one and build a new server with the
same name which is a little messy but would work.
We are also unable to have a huge amount of downtime to perform this
migration so any help would be greatfully received.

Can this be done?

Many Thanks
Glen

[Leif Pedersen [MVP]]

Hi,

Renaming of an Exchange server is not supported / possible. A lot of
exchange server information is stored in active directory and this would be
lost when renaming the server.

You have 2 possibilities:

http://support.microsoft.com/default.aspx?scid=kb;en-us;297289

http://www.swinc.com/resources/exchange/faq_db.asp?status=questions&faqID=1001&faqname=Exchange%202000&sectionID=1024&sectionName=Exchange%202000%20Move%20Server%20Method

Leif

"GKnight" <gl...@glenandsarah.co.uk> wrote in message
news:OWwmQQ9N...@TK2MSFTNGP14.phx.gbl...

[Bharat Suneja]

- You can't rename the new Exchange server to the old server's name. You
would need to uninstall Exchange, rename server, the reinstall Exchange,
defeating the purpose.
- Best bet is to install the second server and move mailboxes. Most Outlook
clients will redirect. Involves minimum downtime. Users can be moved in
smaller batches every day, staggering the number of users that may have any
issues.
--
Bharat Suneja
MCSE, MCT
www.zenprise.com
blog: www.suneja.com/blog
-----------------------------------------

"GKnight" <gl...@glenandsarah.co.uk> wrote in message
news:OWwmQQ9N...@TK2MSFTNGP14.phx.gbl...

[GKnight]

You have just confirmed my suspissions, thanks for this, have been working
with Exchange for 8 years and Windows NT/2000/2003. It was mainly some
supporting documentation I was after if you know where I can find any?

Thanks
Glen

"Leif Pedersen [MVP]" <leif.peder...@get2net.dk> wrote in message
news:e0NkcV9N...@TK2MSFTNGP10.phx.gbl...

[GKnight]

It is more about the name of the server rather than the changing of client
information.

All machines have the Outlook Profile Customiser installed modified using a
script at login so this is not the issue.

"Bharat Suneja" <bharat...@no.spam.org> wrote in message
news:eiHLIX9N...@TK2MSFTNGP11.phx.gbl...

[Nick Gillott [MVP]]

If you are using the Outlook Profile Customiser, that is just making a WINS
look up. So swing the server over to a new box (Ed Crowley), replicate the
public folders over, change the bridgehead, shut down the old server and
stick a WINS entry in for the old name pointing at the new IP.

"GKnight" <gl...@glenandsarah.co.uk> wrote in message

news:%235yvdZ9...@TK2MSFTNGP09.phx.gbl...

[Jason Meyer]

Nick Gillott [MVP] wrote:
> If you are using the Outlook Profile Customiser, that is just making a WINS
> look up. So swing the server over to a new box (Ed Crowley), replicate the
> public folders over, change the bridgehead, shut down the old server and
> stick a WINS entry in for the old name pointing at the new IP.
>

Or just leave the old server up for a few days and it will tell the
clients where their mailboxes are and update their profile
automagically. once thats done, shutdown old server.