Cannot Install 64 bit SQL Server 2005 on Windows Server 2008

I am attempting to install 64 bit SQL Server 2005 on a two node Windows
Server 2008 SP2 cluster. I get to the part of the install "Remote Account
Information" where I am required to enter an user name and password that is
a valid administrator on both nodes. I enter the information of an account
that is an administrator on both nodes and I get this message:

================================================== ============================
SQL Server 2005 Setup requires administrator permissions on every cluster
node. To continue, update permissions for the account currently running
Setup, or log in with an account that has administrator permissions on every
cluster node, and then run SQL Server Setup again.

================================================== ============================

I am unable to get further in the installation. I have done many successful
cluster intalls on Windows 2003 clusters. I have gone over documentation on
how to do SQL Server 2005 installs on Windows 2008 clusters and am following
best practices. Is it possible that this can be a result of the way the
server or the cluster was set up?

On the active node I have been right-clicking on the setup file and choosing
"Run as Administrator". Is it possible that it is not running as an
administrator on the second node? I have read that in Windows 2008 a login
belonging to the Administrator's group logs in with two tokens, a restricted
one and an unrestricted one. User applications are started with the
restrictive token and will use the unrestrictive token only when an
application requests higher priviliges or "Run as Adminstrator" is clicked.
How does this work in a Windows 2008 cluster environment?

Doing the install using a domain adminstrator account worked but for
security reasons this is not a long-term solution.

The solution that worked for us to get the domain account with
administrative rights on both nodes to get by the "Remote Account
Information" step was to set a new SPN record for the active node. This was
done using the Windows support tool executable "setspn". Domain admin
permissions were required for this but this only needs to be set when
initially installing SQL Server.



"Loren Z" <> wrote in message
news:eeG$...
>I am attempting to install 64 bit SQL Server 2005 on a two node Windows
> Server 2008 SP2 cluster. I get to the part of the install "Remote Account
> Information" where I am required to enter an user name and password that
> is
> a valid administrator on both nodes. I enter the information of an account
> that is an administrator on both nodes and I get this message:
>
> ================================================== ============================
> SQL Server 2005 Setup requires administrator permissions on every cluster
> node. To continue, update permissions for the account currently running
> Setup, or log in with an account that has administrator permissions on
> every
> cluster node, and then run SQL Server Setup again.
>
> ================================================== ============================
>
> I am unable to get further in the installation. I have done many
> successful
> cluster intalls on Windows 2003 clusters. I have gone over documentation
> on how to do SQL Server 2005 installs on Windows 2008 clusters and am
> following best practices. Is it possible that this can be a result of the
> way the server or the cluster was set up?
>
> On the active node I have been right-clicking on the setup file and
> choosing "Run as Administrator". Is it possible that it is not running as
> an administrator on the second node? I have read that in Windows 2008 a
> login belonging to the Administrator's group logs in with two tokens, a
> restricted one and an unrestricted one. User applications are started with
> the restrictive token and will use the unrestrictive token only when an
> application requests higher priviliges or "Run as Adminstrator" is
> clicked. How does this work in a Windows 2008 cluster environment?
>