Okay, that is gonna be my scenario. I want the SBS machine to hold the FSMO roles and keep the original Windows 2000 DC as an additional DC in the new SBS environment. What you did is just like the installation of a normal W2K3 DC in an existing W2K structure, the SBS part can be performed afterwards and it's pretty straightforward, is this correct?
On the Microsoft website I found also a whitepaper about this issue (http://www.microsoft.com/WindowsServer2003/sbs/upgrade/default.mspx) . It is recommended to use another DNS name, another domain name and use ADMT for migration. This is nonsense.
Thanks again.
really, it doesn't matter what you want, SBS _must_ have the FSMO roles.
Yes, once you have the 2K3 machine as DC and holding the FSMO roles it's
pretty well 'follow the bouncing ball'.
The upgrade document you refer to has info about two procedures 'upgrade' or
'migrate', the new server name, new domain name, and ADMT is only required
for 'migrate'.
> Okay, that is gonna be my scenario. I want the SBS machine to hold the FSMO roles and keep the original Windows 2000 DC as an additional DC in the
new SBS environment. What you did is just like the installation of a normal
W2K3 DC in an existing W2K structure, the SBS part can be performed
afterwards and it's pretty straightforward, is this correct?
> On the Microsoft website I found also a whitepaper about this issue (http://www.microsoft.com/WindowsServer2003/sbs/upgrade/default.mspx) . It
is recommended to use another DNS name, another domain name and use ADMT for
migration. This is nonsense.
> Thanks again.