Re: updating to 2003
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 16 Jan 2006 22:45:43 -0500
In F_Vyf.317$MJ.123@fed1read07">news:F_Vyf.317$MJ.123@fed1read07,
anon <not@xxxxxxxxx> typed:
> i'm faced with the task of updating windows 2000 advanced server
> (with 2 active directory/fileservers clustered together in failover
> configuration).
>
> since the domain they have set up is sales.company.com, i'm probably
> just going to start them on a new domain as per todays standard such
> as company.local or company.corp. any recommendations for which
> naming scheme i should use?
Well, if sales.company.com doesn't exist on the Internet for any useful
purpose, no harm in leaving it in place as your AD DNS namespace. It may
actually be preferable over using .local or .kitten or .whatnot. I often
use internal.company.com or local.company.com.
>
> also, i'm pretty sure i should just start a brand new domain
> structure from scratch to ensure that there are no previous "ghosts"
> or some such floating around waiting to deliver the hammer.
Why? Are you worried that the current installation is full of problems?
Don't make more work for yourself ...I'm no clustering expert, but I think
you don't want to muck around with something that works.
> does
> anyone have books or other reading related for planning and deploying
> such and move?
>
> -a
.
- Follow-Ups:
- Re: updating to 2003
- From: anon
- Re: updating to 2003
- References:
- updating to 2003
- From: anon
- updating to 2003
- Prev by Date: Re: "Rogue" IP address?
- Next by Date: Re: "Rogue" IP address?
- Previous by thread: updating to 2003
- Next by thread: Re: updating to 2003
- Index(es):
Relevant Pages
|
