I strongly agree with the lab setup, you need more than just the DCs, you
need a fair representation of all major systems running that will have
interaction with the Domain Controllers/GCs in the new world.
I did a 2K setup, but would wait for XP if time permits, unless you have a
very simple AD design. XP will have some stuff that may be easier to
implement from scratch, AD replication partitioning comes to mind.
Good luck,
Kevin
+-------------------------------------------------------------------+
Kevin Flanagan
C/S Planning Engineer III
I/T Implementation Department
Branch Banking & Trust Company
3261 Atlantic Avenue, Suite 116
MC: 172-85-01-00
Raleigh, NC 27604
Voice: 919-716-6209
-----Original Message-----
From: James Gosnold [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 12, 2001 6:42 AM
To: NT System Admin Issues
Subject: Re: Windows 2000 or Windows XP
Sound advice regarding the setting up of a lab and I certainly intend to put
my foot down for some lab kit when asked to implement a migration for my
company.
Have run the client beta of XP a couple of times and although very impressed
with the features, feel and especially would could be the invaluable
Terminal services running on it, both of my installations ended up in
oblivion, just couldn't boot into them one day and after a few efforts
couldn't be bothered to salvage them. Probably because it was a beta and not
as stable as the released product will hopefully be.
Regards, James.
> Just something to consider. Windows 2002 Server will have some
> improvements to Active Directory that are worth waiting for if your CO
> is sizeable and already has an X500/LDAP infrastructure built. We
> went so far as to test the alpha code to see if it fixed the problems
> we were seeing & with a couple of tweaks & recommendations to
> Mickey$oft, beta code ran the integration fine... (of course, that was
> in the lab).
>
> From a migration stand point, scale up a lab fully, set up 2 BDC's in
> your current domain, get them stable & then pull them out & put it in
> the lab on an isolated network. Promote 1 to PDC and go to town with
> migration testing. Every installation is unique and this exercise is
> well worth testing. Also when you're migrating have a back out plan
> (ie. build a BDC & pull it from the network just before you execute).
>
>
> ----- Original Message -----
> From: "Owsley, Kenneth" <[EMAIL PROTECTED]>
> To: "NT System Admin Issues" <[EMAIL PROTECTED]>
> Sent: Tuesday, September 11, 2001 5:53 PM
> Subject: Windows 2000 or Windows XP
>
>
> : I expecting there are a lot of opinions out there. Please, if you
> haven't
> : experienced the migration from NT Server to Windows 2000 Server, please
> : don't respond. What I am looking for is the advice of the guys and gals
> : who've done the do, so to speak. I don't mean to sound like a jerk,
> : please forgive me.
> :
> : Having said that, my question is simple: I haven't migrated my NT
domain
> : to Windows 2000 and Active Directory. I am totally jazzed on Windows
> : 2000, by comparison, so am ready to migrate. Is there any reason to
wait
> : for .NET server or Windows XP Server, or what-the-heck-ever it is
called?
> : You folks that have made the migration, what is your take? Should I go
> : ahead with my migration, then do the next version when it stabilizes in
> : the market?
> :
> : You guys are in the trenches, and I hope will tell what the trade rags
> : won't. Or maybe there isn't anything to tell? Thanks!
> :
> : http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
> :
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
