AH,
You can configure and install whatever OS version you please in mixed mode.
But once you encounter the first hint of trouble and you place a call to
Microsoft, there stands a very good chance you may be asked to upgrade the
Windows 2000 node to Windows 2003. Because mixed mode was only put in place
as a short term resolution until the rolling upgrade could be completed.
Due to the major binary differences between both OS, I would not recommended
you risk data in a production environment for whatever reason you may have.
Because there are several resource types differences between the two OS that
will not work at all in mixed mode. If this cluster is planning to simply
be a File & Print server cluster, then you may not see any problems in mixed
mode. If it's for economical reason, then leave both nodes in Windows 2000
to maintain high availability.
See excerpt from the referenced whitepaper listed below:
Server Clusters: Rolling Upgrades. Upgrading to Windows Server 2003
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/clustering/rllupnet.mspx
Cluster service guarantees that an up-level node can always join a cluster
formed by a down-level node. It also guarantees that resources can fail over
and fail back to and from a down-level node. However, it does not guarantee
that applications can also support rolling upgrades of the operating system.
--
Hope this helps,
Mike Rosado
Windows 2000 MCSE + MCDBA
Microsoft Enterprise Platform Support
Windows NT/2000/2003 Cluster Technologies
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
<
http://www.microsoft.com/info/cpyright.htm>
-----Original Message-----