Re: Justification for creating a new Domain



"flabob" <flabob@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:97A88DBE-9798-456C-9B45-655F4D99CC63@xxxxxxxxxxxxxxxx
Perhaps I need to clarify. We have two DC's, Exchange, DNS are hosted on
separate machines. We also have a SQL Server, Application Server, SAN. The
hardware was purchased as a life cycle purchase to replace Dell 2650 servers.
I know all the steps we have to go through to create a new Forest and Domain
and I'm trying to convince managment that this doesn't need to be done. My
contention is that we don't need to do any of this. Simply add the new
hardware to the existing domain. I'm looking for particulars that anyone may
have experienced (trouble areas) to convince managment that this is un-needed
work and expense.
--
Thanks


"Isaac Oben [MCITP,MCSE]" wrote:

Hello flabob,
How many domain controllers do you currently have. Do you have your
exchange, DNS and AD in the same server? What was the original purcahse
purpose of the new hardware? You will have to proof to management based on
facts. According to your views, what is the existing problem with DNS and
can it be fixed and how? What is messed up with AD? Can you please post your
full dcdiag as well?

--
Isaac Oben [MCTIP:EA, MCSE]
"flabob" <flabob@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B928F30E-2EAB-4266-9047-7F1F15231015@xxxxxxxxxxxxxxxx
> Long story short. I've taken a new job so I'm the new guy here. Short
> history: We have an existing 2003 single forest/single domain. > Recently
> new
> hardware (blades) have been purchased and are in the rack. It seems > the
> existing task lead has a plan to create an entirely new domain in order > to
> bring the hardware on line. I believe this is totally unnecessary, not > to
> mention the work involved. His reasoning is that DNS and AD are > "messed
> up".
> My arguement is to fix the DNS, because if you can't fix what you have,
> what
> makes you think it'll fix all your problems by creating a new domain. > Of
> course all the users, exchange accounts, etc. will have to be migrated > not
> to
> mention the problems with the MX records and reconfiguring DNS in > general.
> My question is this. I'm looking for specific problems to present to
> management to "unjustify" this procedure.


Explain the name changes that may confuse workers, and especially the time involved in migrating, computer accounts, user accounts, user profiles, mailboxes, and the fact that not every migration goes smoothly. That is on top of the the migration of shares that must be done when a server is replaced anyway. And most importantly, during much of the migration no user access will be allowed meaning many hours of overtime and network downtime. Put the calculator to it then let it (the calculator) do the talking.


--
--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================


.

Relevant Pages

  • Re: Help with Swing Migration
    ... Frank McCallister [SBS MVP] ... > from anyone who has used Jeff Middleton's Swing Migration Kit. ... > server hardware. ... then the IP address for the Primary DNS Server ...
    (microsoft.public.windows.server.sbs)
  • Re: Help with Swing Migration
    ... Frank McCallister [SBS MVP] ... > from anyone who has used Jeff Middleton's Swing Migration Kit. ... > server hardware. ... then the IP address for the Primary DNS Server ...
    (microsoft.public.windows.server.sbs)
  • Re: Installing SBS2008
    ... I'm going to address the DNS and DHCP cleanup first, ... then later installing the server at the production location (your ... enough disk space to do preparation of the server for the migration. ...
    (microsoft.public.windows.server.sbs)
  • Proper rules/procedures for setting up DNS/Default Gateways
    ... I run a small test network behind a hardware firewall ... I recently replaced my 'server' ... Toshiba DOCSIS cable router connected to the WAN side of a Sonicwall SOHO3 ... DG 192.168.1.2 DNS same as above ...
    (microsoft.public.windowsxp.network_web)
  • Re: Cant add computers to domain
    ... posts the big picture with some of the little points on how to do this. ... the existing hardware as the 'source' while needing new hardware to create ... > So I use dcpromo to remove ad from the server. ... and follow the instructions again hoping that all the DNS stuff is set up ...
    (microsoft.public.win2000.active_directory)
Loading