Moving an existing SBS2003 domain system to a new WIndows 2003 system - same domain
Posted on 2007-04-04
I've picked this job up half way through, so bear with me whilst I get things straightened out.
The original system was a single box running SBS2003 - it was the only server, did everything, and was on a standard PC machine, which caused it to fall over alot. Lets call this machine server-001
There are now two new machines, both running windows 2003 - server-002 and server-003
What we want to end up with is the ability to wipe server-001.
Done so far:
Copied the active directory from server-001 to server-002
Server-002 also has a copy of DNS from the AD system
Installed exchange to server-003 and move everything from server-001 to server-003
1. Exchange problem #1
Even though all the exchange roles have been moved, including OAB, and replication was showing "In Sync", outlook is still using an old copy of the OAB - the changes took place 3 weeks ago, and still the changes made since the change do not show; I've looked on both new & old server, and both say that the new server is in charge of OAB, and previewing it shows all the new changes, and multiple rebuilds have had no effect.
I have created a new outlook profile on a seperate domain login, and that also downloads the aged OAB; I've checked and all versions of the OAB are seemingly up to date, and have upped logging to maximum, and the rebuilds dont show any errors.
2. Exchange problem #2
Is exchange built into SBS2003? The last part of the "removing the first exchange server" is removing exchange itself, but I've not been able to do this - I should point out I've never touched SBS2003 before (I was taught to hate SBS, and thus never installed/used/removed it).
When server-001 goes offline, even though AD has been copied to server-002, which has routing & remote access on it, no-one can log in, for instance via VPN, but as soon as server-001 is back, you can log in - what gives? I have not yet transferred the FSMO roles, but my understanding is that authentication should still take place, no?
In general - am I going about this all wrong? I've read loads about moving from Win2003 to Win2003, and am working on the assumption that this is along the same principle.
The thing is, I've done quite a few of these role-moving jobs, and it's always gone pretty smoothly.
Looking forward to a little help