Archived from groups: microsoft.public.win2000.active_directory (More info?)
Hi there,
The Windows2003 deployment kit recommends to use a new Windows2003
memberserver to perform a windows2000 domain upgrade.
What are the benefits of this approach compared to an in-place Win2000
domain controller upgrade?
Regards,
Robert.
Archived from groups: microsoft.public.win2000.active_directory (More info?)
"Robert" <Robert@discussions.microsoft.com> wrote in message
news:01173504-C8B0-4B20-8314-0E2E472BB419@microsoft.com...
> Hi there,
> The Windows2003 deployment kit recommends to use a new Windows2003
> memberserver to perform a windows2000 domain upgrade.
> What are the benefits of this approach compared to an in-place Win2000
> domain controller upgrade?
I actually like the direct upgrade of the Win2000
DC -- this way you don't have to explicitly run the
ADPrep: ForestPrep and Domain Prep.
They are run as part of the semi-wizard that comes
up to do the upgrade.
Archived from groups: microsoft.public.win2000.active_directory (More info?)
One clear advantage is to avoid migrating old configuration errors / settings
that are on the old DC. Another point concerns enhanced security settings in
W2k3 that can only be applied for a fresh install.
There is an excellent article in Windows IT Pro Magazine that gives an
insight into not-so-obvious or hard-to-find info in such an exercise (Dec '04
or Jan '05 issue).
Hope this helps. Do let us know. Thanks.
"Robert" wrote:
> Hi there,
> The Windows2003 deployment kit recommends to use a new Windows2003
> memberserver to perform a windows2000 domain upgrade.
> What are the benefits of this approach compared to an in-place Win2000
> domain controller upgrade?
> Regards,
> Robert.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.