B
Brendon Rogers
We currently have a single Windows 2000 domain in native mode; there are
several RIS servers in this domain - 1 per site.
We're considering upgrading the domain (forestprep, adprep) to Windows 2003
at Windows 2000 functional level. This should allow us to have one or more
Windows 2003 DCs into our existing Active Directory infrastructure and have
all the DCs play nicely together.
However, something I find very concerning in MS's documentation:
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/win2k/w2ktows03-2.mspx
"Working with Remote Installation Services
All editions of the Windows Server 2003 family, with the exception of the
Web Edition, have Remote Installation Services (RIS), a change and
configuration management feature that was also included with Windows 2000.
RIS enables you to set up new client computers remotely, without the need to
physically visit each client machine. You can use RIS to install operating
systems on remote boot-enabled client computers by connecting the computer
to the network, starting the client computer, and logging on with a valid
user account.
If your network uses RIS with Windows 2000 Server, you should make the RIS
server the first computer that you upgrade to Windows Server 2003. You won't
be able to use RIS later unless it is upgraded first because of design
changes in the way that Active Directory performs authentication. Upgrading
the RIS server to Windows Server 2003 gives it the ability to communicate
with the remaining Windows 2000 domain controllers, as well as with Windows
Server 2003 domain controllers."
If I am reading this right its not possible to have a Windows 2000 RIS
server in a Windows 2003 domain (even if we still have W2K DCs). Because we
have multiple sites, each with a RIS server, we would have to upgrade the
domain to W2K3 then upgrade each RIS server otherwise they would stop
functioning.
Can anyone confirm this is the case? Are there any work arounds?
Thanks in advance
Brendon
several RIS servers in this domain - 1 per site.
We're considering upgrading the domain (forestprep, adprep) to Windows 2003
at Windows 2000 functional level. This should allow us to have one or more
Windows 2003 DCs into our existing Active Directory infrastructure and have
all the DCs play nicely together.
However, something I find very concerning in MS's documentation:
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/win2k/w2ktows03-2.mspx
"Working with Remote Installation Services
All editions of the Windows Server 2003 family, with the exception of the
Web Edition, have Remote Installation Services (RIS), a change and
configuration management feature that was also included with Windows 2000.
RIS enables you to set up new client computers remotely, without the need to
physically visit each client machine. You can use RIS to install operating
systems on remote boot-enabled client computers by connecting the computer
to the network, starting the client computer, and logging on with a valid
user account.
If your network uses RIS with Windows 2000 Server, you should make the RIS
server the first computer that you upgrade to Windows Server 2003. You won't
be able to use RIS later unless it is upgraded first because of design
changes in the way that Active Directory performs authentication. Upgrading
the RIS server to Windows Server 2003 gives it the ability to communicate
with the remaining Windows 2000 domain controllers, as well as with Windows
Server 2003 domain controllers."
If I am reading this right its not possible to have a Windows 2000 RIS
server in a Windows 2003 domain (even if we still have W2K DCs). Because we
have multiple sites, each with a RIS server, we would have to upgrade the
domain to W2K3 then upgrade each RIS server otherwise they would stop
functioning.
Can anyone confirm this is the case? Are there any work arounds?
Thanks in advance
Brendon