"WingCommander" <> wrote in message
news:87594FAD-D6B6-4509-96A9-...
> Hello, I have posted the complete information in another forum, and also
> pasted it below so that you guys have all of the information needed. I am
> doing the following project:
>
> Hello everyone. I have a problem that you can hopefully help me with. I
> have a client that has an SBS network that is all but max'd out. There
> are 2
> sister companies on this one domain, and one of the companies has decided
> to
> break off of the existing domain and create their completely own network,
> for
> several reasons and not just the current 75 user limit. I have purchased
> them all of the equipment and software necessary to create them a new 2008
> windows standard domain.
>
> I have only very limited experience with ADMT, and it was suggested that
> one
> of the things that I could do to accomplish this task was to join the 2008
> server to the SBS domain, add it as a domain controller, then simply move
> it
> over to the new network wiring and subnet and upgrade it to the FSMO.
> cleanup AD, and use exmerge to handle exchange mailboxes.
>
> The questions I have are this:
>
> 1.) This suggestion detailed about about joining the 2003 domain seems
> easy
> enough to me, and I have used exmerge before so I a pretty sure that I can
> do
> it this way. Is this what you would recommend?
>
> 2.) Since I will be building this new network from scratch, I am creating
> a
> project plan detailing the project with the informaiton necessary. Is
> there
> a document that list all of the servers necessary to configure on a new
> 2008
> domain, and the steps and order needed?
>
> 3.) Any other suggestions would be greatly appreciated.
>
> Wing Commander
(cross-posted to the microsoft.public.windows.server.sbs newsgroup)
What other forum did you post this in? A Microsoft forum, or elsewhere? Most
of the other 'elsewhere' forums actually push/pull posts into the Microsoft
forums.
Regarding your plan of attack, that's pretty much it. Promote a replica
2008, move FSMOs, etc. No ADMT required in this scenario, since you already
have the user accounts in the domain. Setup a separate machine with Exchange
2007 on it, and use the move-mailbox commands to move mailboxes from the SBS
to the new Exchange 2007 server.
However, you have to double check with the SBS folks if you can install an
additional Exchange 2007 server into an SBS 2008 domain. If not, you will
need to use Exmerge two step method.
Here are my notes on moving away from SBS.
================================================== ================
SBS SBS Migration Moving away from SBS
Swing Migration:
http://www.swingmigration.com
SBS 2003 to Server 2008/Exchange 2007
http://social.technet.microsoft.com/...-65720c1019f5/
Upgrading Small Business Server 2003 to Exchange 2007
http://www.itexpertmag.com/server/up...-exchange-2007
Keep in mind, basically what the second article is indicating, is a method
to preserve your current user base with the same domain name. The 2008 DC
would need a new name, of course.
In a nutshell, you would install the new 2008 servers (one for the DC, and
one for Exchange 2007), then join it to the SBS domain. Of course it
involves upgrading the SBS domain schema. Then promote the 2008 into the SBS
domain, and make it a GC. Don't do anything with the FSMO roles just yet.
This will preserve your user accounts. Then install Exchange 2007 on the
other server, which will add it to the Exchange 2003 org on SBS. From here
you can use Exchange 2007's move mailbox tool to move the mailboxes over.
Then you have to replicate all public folders and hidden system folders over
to the new server. Once replication is complete, remove the Exchange 2003
replica. Once done, you can decommission Exchange 2003. As for the SBS DC,
you would need to unplug it, and seize the FSMO roles over to the new DC. Of
course, before all of that, make sure you move all user profile data,
company data, etc, to the new server.
Also, if you add the new box as a member to the SBS AD it will be subject to
SBS policies. When you promote the new box to a DC in the SBS AD it will
hold a copy of same policies. When, and if, you subsequently remove SBS from
the AD the policies will remain in force, just under the control of the new
server.
Therefore, keep in mind, you shouldn't have to do anything with the client
machines or anything else, if following this method and staying in the same
domain. Just keep that in mind as well, the differences and the GPOs that
SBS put in place. I mean you can keep them, or get rid of them, but just be
aware of what's going on.
That's in a nutshell. Read the whole article for more detail.
================================================== ================
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.
Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.
Similar Threads
Linear Mode
