"Kizetoni" <kizet***@mail.ru> wrote in message
news:enFwALvrFHA.1168@TK2MSFTNGP10.phx.gbl...
> 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
>
>

"Miha Pihler [MVP]" <mihap-n***@atlantis.si> skrev i en meddelelse
news:O1xYwjyrFHA.1168@TK2MSFTNGP10.phx.gbl...
> 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" <kizet***@mail.ru> wrote in message
> news:enFwALvrFHA.1168@TK2MSFTNGP10.phx.gbl...
> > 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
> >
> >
>
>

"Miha Pihler [MVP]" <mihap-n***@atlantis.si> skrev i en meddelelse
news:%23nwHhx9rFHA.1252@TK2MSFTNGP09.phx.gbl...
> Hi,
>
> <snip>
>
> > 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?)
>
> Once you setup new PDC the old one would be demoted and would still work
as
> BDC.
>
> > 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?
>
> Yes, since your temporary server is running Windows 2003 you can easily
> demote it to member server (not acting as domain controller any more). You
> do this by running dcpromo (first you will run it to make your server
domain
> controller; now you will run same tool to make it a member server). You
can
> now disjoin the server from domain.
>
> What about the
> > original old NT server? Just turn it off?
>
> Yes, and you should be then able to remove any objects from active
directory
> connected to old domain controller (e.g. computer account).
>
> > 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)?
>
> I usually remove it within weeks; but I _never_ have less then two domain
> controllers in any production domain environment.
>
> I hope this helps,
>
> --
> Mike
> Microsoft MVP - Windows Security
>
>

"Kizetoni" <kizet***@mail.ru> wrote in message
news:e0sw5SMsFHA.3668@TK2MSFTNGP10.phx.gbl...
> Hello Mike,
>
> thanx, it helps a lot!
>
> I'll try the solution, it seems like something where nothing can go
> wrong...
>
> Or is there anything I should take extra care of?
>
> Regards,
>             Kizetoni
>
> "Miha Pihler [MVP]" <mihap-n***@atlantis.si> skrev i en meddelelse
> news:%23nwHhx9rFHA.1252@TK2MSFTNGP09.phx.gbl...
>> Hi,
>>
>> <snip>
>>
>> > 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?)
>>
>> Once you setup new PDC the old one would be demoted and would still work
> as
>> BDC.
>>
>> > 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?
>>
>> Yes, since your temporary server is running Windows 2003 you can easily
>> demote it to member server (not acting as domain controller any more).
>> You
>> do this by running dcpromo (first you will run it to make your server
> domain
>> controller; now you will run same tool to make it a member server). You
> can
>> now disjoin the server from domain.
>>
>> What about the
>> > original old NT server? Just turn it off?
>>
>> Yes, and you should be then able to remove any objects from active
> directory
>> connected to old domain controller (e.g. computer account).
>>
>> > 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)?
>>
>> I usually remove it within weeks; but I _never_ have less then two domain
>> controllers in any production domain environment.
>>
>> I hope this helps,
>>
>> --
>> Mike
>> Microsoft MVP - Windows Security
>>
>>
>
>

"Miha Pihler [MVP]" <mihap-n***@atlantis.si> skrev i en meddelelse
news:Os8s%23oWsFHA.2604@TK2MSFTNGP14.phx.gbl...
> - plan your DNS and NetBIOS name of your Active Directory carefully (they
> can't be changed easily)
> - make sure your clients point to the right DNS server for name resolution
> (they should point to your Active Directory DNS server or clients will
fail
> to find domain controllers); don't forget about this when you remove old
and
> temporary servers (update your clients configuration if necessary)
> - if you plan to use DHCP also use it to configure clients DNS settings
> - have at least two domain controllers for your domain
>
> I hope this helps,
>
> --
> Mike
> Microsoft MVP - Windows Security
>
> "Kizetoni" <kizet***@mail.ru> wrote in message
> news:e0sw5SMsFHA.3668@TK2MSFTNGP10.phx.gbl...
> > Hello Mike,
> >
> > thanx, it helps a lot!
> >
> > I'll try the solution, it seems like something where nothing can go
> > wrong...
> >
> > Or is there anything I should take extra care of?
> >
> > Regards,
> >             Kizetoni
> >
> > "Miha Pihler [MVP]" <mihap-n***@atlantis.si> skrev i en meddelelse
> > news:%23nwHhx9rFHA.1252@TK2MSFTNGP09.phx.gbl...
> >> Hi,
> >>
> >> <snip>
> >>
> >> > 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?)
> >>
> >> Once you setup new PDC the old one would be demoted and would still
work
> > as
> >> BDC.
> >>
> >> > 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?
> >>
> >> Yes, since your temporary server is running Windows 2003 you can easily
> >> demote it to member server (not acting as domain controller any more).
> >> You
> >> do this by running dcpromo (first you will run it to make your server
> > domain
> >> controller; now you will run same tool to make it a member server). You
> > can
> >> now disjoin the server from domain.
> >>
> >> What about the
> >> > original old NT server? Just turn it off?
> >>
> >> Yes, and you should be then able to remove any objects from active
> > directory
> >> connected to old domain controller (e.g. computer account).
> >>
> >> > 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)?
> >>
> >> I usually remove it within weeks; but I _never_ have less then two
domain
> >> controllers in any production domain environment.
> >>
> >> I hope this helps,
> >>
> >> --
> >> Mike
> >> Microsoft MVP - Windows Security
> >>
> >>
> >
> >
>
>