Hello Mike,
thanx for your quick answer.
Now, upgrading of NT machine to 2003 is out of a question, as you
anticipated - the machine is too old and weak, and I would be frightened to
try that.
Now, let me check if I understood you right.
You say that, besides the old and the new server (hardware), I get a 3rd
machine, a temporary hardware, which I would install as an NT server first,
then make it BDC, promote to PDC, upgrade to 2003. That would make this 3rd
machine my first AD server (what would happen with the old NT PDC in that
case? would it still be a BDC, and functioning?)
Then I install a 2003 on the new server, and promote it to DC (by running DC
promo?). After that this new 2003 server should be the new DC, and then I
could remove the 3rd machine, and the original old NT server? How do I do
that - when you say "run dcpormo on it again" you mean running DCpromo
command on the 3rd machine, afterwards just detaching it? What about the
original old NT server? Just turn it off?
What if that original old NT server should be running side by side with the
new one for a while (fx next 3 to 6 months)?
Have a nice week end!
Regards,
Kizetoni, DK
"Miha Pihler [MVP]" <mihap-(E-Mail Removed)> skrev i en meddelelse
news:(E-Mail Removed)...
> Hi,
>
> the upgrade path would be like this:
> - join Windows 2003 to existing Windows NT domain
> - upgrade existing Windows NT PDC to Windows 2003
> - once this process is complete you have your first Windows 2003 Active
> Directory server
> - now you can promote your second Windows 2003 (your new server) to Active
> Directory.
> - now it should be easy to remove old server from domain
>
> If you can't upgrade existing Windows NT server to Windows 2003 (e.g.
> hardware limitations), look for temporary hardware where you can install
> Windows NT (and that will later hold Windows 2003). Install Windows NT on
> this temporary hardware. Make the server PDC (make it BDC and promote it
> later to PDC) of your existing domain.
> Now upgrade it to Windows 2003. Once the process is complete this will be
> your first Windows 2003 Active Directory server.
> Promote your new Windows 2003 server to Domain Controller. Now you can
> remove temporary Windows 2003 server (run dcpormo on it again).
>
> Note: you should always have at least two domain controllers in every
> domain.
>
> --
> Mike
> Microsoft MVP - Windows Security
>
> "Kizetoni" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Hello All,
> >
> > our sister-company bought a new server to replace an old machine.
> >
> > It is a file/print server, and a domain controller vi are talking about.
> >
> > Then old server is a NT machine, a domain controller, with not more than
> > 10
> > workstations as domain members, and not more than 10 users.
> >
> > Now I have to install the new server machine with 2003 server STD, and
> > since
> > the old server should be running together with the new one for a while,
I
> > had an idea that I would just make the 2003 machine as an BDC to the NT
> > PDC,
> > but I read somewhere that it cannot be done!
> >
> > Now, what do I do?
> >
> > Should I make a totally new domain (which is a pitty, since the old
domain
> > has the company's name) and then make all workstations members of the
new
> > one? But how do they then access the old domain?
> >
> > Maybe to make a trust between those two domains? But can I delete the
old
> > domain once the old server is detached, and gone? Can I rename
afterwards
> > the new domain name, so it becomes the same as the old domain name? Or
is
> > it
> > too dangerous?
> >
> > And at last, how do I preserve the user profiles at every workstation,
> > once
> > I change theirs domain membership...?
> >
> > Thanx in advance!
> >
> > Regards,
> > Kizetoni, Denmark
> >
> >
>
>
|
Similar Threads
Linear Mode
