Forget about a new subnet. There is no point in it at all. Domains and
Subnetst have absolutely NOTHING to do with each other,...there is no
relationship at all. If you have less than 254 Hosts on the LAN then a
single /24bit Segment is all you need,...anything else is needless and
excess complexity.
All you need to create a new domain is one temporary machine to build up as
a new DC (hence new forest, new domain). Then you need one more set of
temporary hardware if there is an Exchange Server. If you don't have
hardware for that then virtualize it as a VM (just don't do it on an
existing DC or an exisiting Exchange Server). Run the VM on a powerful
dependable workstatio or another server.
Your VM options are VirtualPC (free), VirtualServer (free), or VMWare Server
(free). But Hyper-V, or VMWare ESXi,...although great products,... are
probably too complex to deal with in a project like this. If you are
dealing with only x32 bit OS then VirtualPC running on XP Pro is the
simplest,...VMware Server runing on a Server OS is the next simplest. MS's
Virtual Server requires IIS and is kind of a pain to deal with (in my
opinion). VMWare's products can handle 64bit OS under the proper
conditions,...mainly they need 64bit hardware to run on with a
virtualizzation capable CPU.
After building the new temp DC and Exchange do a nromal domain Migration
with ADMT (active Directory Migration Tool). Then backup/restore the
mailbox contents from the old Exchange tot he new "Temp" Exchange using
"ExMerge.exe" which will export the mailboxes to PST files and then import
into the new fresh mailboxes on the new "temp" Exchange
Once the original DC and Exchange have been "relieved of their duties" you
can wipe them out and rebuild them fresh. Promote the DC Machine to a new
DC in and Existing Domain, let run for a day then demote the Temp CD, then
move to "workgroup" then remove. Build the new Exchange into the exisiting
Exchange Organization. Use the Move Mailbox feature to move the mailboxes
from the Temp Exchange to the Permanent Exchange. The follow the **proper**
proceedure for "Removing the First Exchange in an Exchange Organization".
--
Phillip Windell
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
"waybig" <(E-Mail Removed)> wrote in message
news:59179794-b4e9-40ac-85c5-(E-Mail Removed)...
>I have a domain that is mixed 2K and 2003 servers. Has been cobbled
> together over past 8 years. Straigh forward setup with router
> (SonicWall NSA240) 2- 48 port GB switches all running on subnet of
> 192.168.10.x with subnet of 255.255.255.0. I want to build an entirely
> new domain with all new servers, leaving all the sins of the past on
> the old domain. I was thinking about making a new subnet on one of the
> other LAN ports of the firewall, something like 192.168.100.xxx, and
> bring all the new servers online with static ips. What would the new
> subnet mask be for something like this. I want to be able to have the
> XP pro workstations that are currently on the old domain, still
> talking on the 192.168.10.xxx subnet, but be able to access the new
> 192.168.100.xxx net at the same time. Is this doable?
> thanks
> Chris
|
Similar Threads
Linear Mode
