HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- BackOffice Products
- >
- Moving exchange 2000 clustered server into new HW.
BackOffice Products
1834017
Members
2560
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-13-2004 10:26 PM
04-13-2004 10:26 PM
Hello,
I'd like to move existing cluster into new hardware. I know how to move mailboxes and all rest, but also I'd like somehow to retain network name of Exchange server. I have over 500 users in different locations so Outlook reconfiguration could be painful. Is it possible to rename running exchange server? Any ideas what side-effect this could cause? Or maybe some other approach?
Thanks for any ideas,
Chris
I'd like to move existing cluster into new hardware. I know how to move mailboxes and all rest, but also I'd like somehow to retain network name of Exchange server. I have over 500 users in different locations so Outlook reconfiguration could be painful. Is it possible to rename running exchange server? Any ideas what side-effect this could cause? Or maybe some other approach?
Thanks for any ideas,
Chris
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2004 05:10 PM
04-14-2004 05:10 PM
Solution
Hello Chris
When you move mailbox from old Exchange server to New, the outlook configuration on the client side automatically pointed to the new server, no need for Outlook reconfiguration.
Hope this helps
Regards
Robin
When you move mailbox from old Exchange server to New, the outlook configuration on the client side automatically pointed to the new server, no need for Outlook reconfiguration.
Hope this helps
Regards
Robin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2004 06:43 PM
04-14-2004 06:43 PM
Re: Moving exchange 2000 clustered server into new HW.
I agree with the previous comment.
Give the servers new name - it will automatically be updated for the clients.
The way it works is that Outlook connects to the old server, get's the message back that the "Home Server" attribute has changed for the mailbox and updates it automatically.
Also take care to move any public folders and unique roles to the new server(s) or another server in the site.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;307917
If the server has connectors take care to move those also (and reconfigure the other side of the connectors to point to the new server). For PF's replicated to this cluster from other Exchange servers, update those to point to the new server.
Moving mailboxes and public folders can basically be done during production with no downtime, so it is much preferrable to the one-shot disaster recovery type of actions needed when replacing an Exchange server's hardware.
Also moving for example 100 mailboxes each evening minimizes impact and also gives you better control if errors occur - but the Move Mailbox is really quite robust.
Cheers,
Rune
Give the servers new name - it will automatically be updated for the clients.
The way it works is that Outlook connects to the old server, get's the message back that the "Home Server" attribute has changed for the mailbox and updates it automatically.
Also take care to move any public folders and unique roles to the new server(s) or another server in the site.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;307917
If the server has connectors take care to move those also (and reconfigure the other side of the connectors to point to the new server). For PF's replicated to this cluster from other Exchange servers, update those to point to the new server.
Moving mailboxes and public folders can basically be done during production with no downtime, so it is much preferrable to the one-shot disaster recovery type of actions needed when replacing an Exchange server's hardware.
Also moving for example 100 mailboxes each evening minimizes impact and also gives you better control if errors occur - but the Move Mailbox is really quite robust.
Cheers,
Rune
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP