thiad_98
asked on
Windows 2003 / Exchange 2003 Migration over a Satellite Link
Hi -
Time to pick some brains and ask for some ideas and creative thinking....
I'm currently scoping out a Windows 2003 / Exchange 2003 Migration from a Windows NT 4.0 multiple domain model with Exchange 5.5.
The existing architecture has has four domains with two way trusts between the central office, and the remote sites. While this is not too bad by itself, the problem is that three of the sites connect to the central office using a satellite uplink - a very SLOW satellite uplink that is not dependable.
My thought on the domain structure is pretty simple and migration, not too painful. A forest root domain at the central office, and then child domains for each of the remote sites. While it is critical that the central office accounts migrate over, the remote office accounts can be recreated if necessary, as long as existing email is somehow moved over.
However, what is really nagging me is how best to migrate the remote Exchange sites. Aside from typical e-mail, there is a heavy dependency on public folders. I'm not a huge fan of ADC and with the link latency, this sounds like nothing but a disaster if we go this path. I think ADC will work fine for migrating the central office users, but this leaves a real mess with the remote sites. Already with 5.5, the event logs are filled with RPC errors. They attempted in the past to do a 2003 installation at one of the remote sites and while it's working, it's not working well. I definitely DON'T want to compound their issues!
Any ideas? Any thoughts would be greatly appreciated.
Has anyone else been down this path and done anything like this?
Time to pick some brains and ask for some ideas and creative thinking....
I'm currently scoping out a Windows 2003 / Exchange 2003 Migration from a Windows NT 4.0 multiple domain model with Exchange 5.5.
The existing architecture has has four domains with two way trusts between the central office, and the remote sites. While this is not too bad by itself, the problem is that three of the sites connect to the central office using a satellite uplink - a very SLOW satellite uplink that is not dependable.
My thought on the domain structure is pretty simple and migration, not too painful. A forest root domain at the central office, and then child domains for each of the remote sites. While it is critical that the central office accounts migrate over, the remote office accounts can be recreated if necessary, as long as existing email is somehow moved over.
However, what is really nagging me is how best to migrate the remote Exchange sites. Aside from typical e-mail, there is a heavy dependency on public folders. I'm not a huge fan of ADC and with the link latency, this sounds like nothing but a disaster if we go this path. I think ADC will work fine for migrating the central office users, but this leaves a real mess with the remote sites. Already with 5.5, the event logs are filled with RPC errors. They attempted in the past to do a 2003 installation at one of the remote sites and while it's working, it's not working well. I definitely DON'T want to compound their issues!
Any ideas? Any thoughts would be greatly appreciated.
Has anyone else been down this path and done anything like this?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.