|
|
|
Question : Need to forward email from one exchange server to another on separate domains both local
|
|
I am transferring a company over to a new SBS server. I want to retain the old SBS server as a backup, and it also runs the database system.
Exchange server is setup on both servers, and works on both servers. I want to forward incoming mail from the old server to the new server, for users as they get transferred to the new system. The transfer is being done in stages, hence the need for this forwarding, as the old server still has to be working.
I have tried setting up a contact on the old server, and choosing it as the forwarding address for the account I am working on, but the message doesn't get to the second server, and instead bounces back.
Is there something I am missing, does some extra DNS information have to be setup on the old server for it to see the new server?
Both servers are on separate domains.
|
Answer : Need to forward email from one exchange server to another on separate domains both local
|
|
You can't modify the plan... as I stated, migration of an SBS to new hardware is a VERY specific process. A Small Business Server is only an "easier-to-use" system if it's properly installed and configured according to its design, which, by the way, is one of Microsoft's most complex server systems. Unlike standard Server 2003's which each hold specific roles and can be plugged into and pulled out of a network, SBS requires that all roles be carefully coordinated and synchronized so that the system remains both stable and secure. You cannot use a secondary SBS as a limited backup system. There are already proven methods to do what you are ultimately wanting to achieve. It's not a question of not being recommended, and SBS implementations always have budget constraints in mind.
The key is to understand the SBS methodology, and to work with it rather than trying to use an Enterprise Network mindset to solve perceived problems. There is no need for a cluster-based system... and even the thought of switching to the "old domain" is a nightmare.
You have raised two very separate issues though... one is of making a fluid migration to new hardware, and the other is to ensure reliability and business continuity.
So lets first start with the migration. If you've never performed an SBS migration, then I'd suggest you do a couple of practice runs. Just image the current server with something like Acronis True Image or Symantec System Restore, and create a non-production test environment. Then, go through the Microsoft prescribed method a few times until you are confident that you are able to successfully perform the migration on the production server.
If you or your client don't have either the time or budget for such testing, then I'd strongly suggest that you spend the couple hundred bucks for enlisting the expertise of the folks at www.sbsmigration.com who have assisted in thousands of similar migration projects, or bring in a seasoned SBS Consultant who has done this type of work before and knows how to guide you through the process.
The advantage of the www.sbsmigration.com process is that it is a gradual migration... you do switch over varioius items and services one-by-one... but they MUST be done in the order prescribed by their documentation. Most of their method is done off-line, so if at any time during the process you want to revert back to the original server you just do it, and it doesn't take switching between domains and all the horrors that would create.
Want more views on this? Check out: http://msmvps.com/blogs/kwsupport/archive/category/895.aspx
Then, to the issue of longer term reliability and business continuity?
After deploying more than 100 Small Business Server based networks over the past couple of years, I've yet to find a need for a backup domain controller on a single-site network with less than 20 client workstations. I'm not entirely sure what you mean by "as exchange would be required, etc", but the key to having a reliable SBS-based network is to first make sure that your server is properly provisioned with redundant storage, a good backup system, proper networking equipment/firewall, etc. There is a very good overview of these standards here:
http://www.smallbizserver.net/Articles/tabid/266/articleType/ArticleView/articleId/192/Default.aspx
The second part of ensuring a reliable and secure system is to deploy it according to its design, and using the proven methods of the thousands upon thousands of successful SBS deployments which are enthusiastically supported by a worldwide "SBS Community". http://www.microsoft.com/technet/community/en-us/windowssbs/default.mspx. You'll find that there are very few circumstances which haven't already been addressed.
Jeff
TechSoEasy
|
|
|
|
|
|
|
