Do I Need A Domain Controller?

I'm wondering if I really need a domain controller. I believe that having a
domain controller will require me to establish a SA password in SQL Server
2005, which will be a problem.

I'm setting up a 2-server active/passive cluster with Win 2003 Enterprise Ed
with a SAN. There will be two Win 2000 consoles attached to the LAN. The
cluster will have three physical networks: one private crossover, one class B
"data" network, one class A "public" network. Two cisco switches will be
used to provide VLANS of the later two networks. All networked components
will be fixed logon's. There will be NO need for connecting to any outside
networks, This is a stand-alone system used in a highly secure location.

The reason I want to avoid using a SQL Server password authentication is
because I have a unique software application written for NT/SQLv7 that I
absolutely do not want to change...that application connects to SQL v7 as SA
without a password.

The software and equipment described above is being used to replace the
existing system. Major changes are: win2k3 vs. winnt, sql2005EtrpEd vs
sqlv7, three nets vs 2 nets, SAN vs. SCSI array, win2k consoles vs. winnt
consoles.

I have this replacement system clustered on the bench, but without any
consoles (just the two servers and SAN). When I tried to install and cluster
SQL 2005, the installation was forcing either win logon authentication (which
will not work for my unique software app), or manual authentication with a
password. Apparently, you can manual authenticate without a password, but
only if the machines are not domain controllers.

If I do not need a Domain Controller, can it be easily removed without
re-clustering?

Any thoughts on this are greatly appreciated. Please don't be surprised if
I have to ask some more questions...I am NOT an IT Professional (just a
wannbe I guess). Thank you.

OK, I'll just answer this myself.

NO, domain controllers are required for clustering. Cannot cluster with
workgroups. Found this out the hard way.