In the above article one assumtion states "The cluster group in which you
configure AS always runs on the same node as the default cluster group, wich
contains the clister IP and cluster name"

Question - Is this statement referring to the Win2K3 Cluster IP and Name or
the SQL Cluster IP and Name?

Thanks in advance
--
Michael Krok
President
Mallard Solutions LLC
Microsoft Certified Partner

Win2K3
Analysis Services knows nothing about SQL clustering.
It is a separate component.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Michael Krok" <TheDuck (AT) newsgroup (DOT) nospam> wrote

Thank You very much for the reply....

Any thoughts on applying ASSP3a? Should this be done on each node before
clustering as a generic service or after.

I already clustered it without SP3a so if I need to tear it down again not
problem but it would bee nice if I can apply SP3a to each node and be done.

Thanks
Mike

"Dave Wickert [MSFT]" wrote:

You ABSOLUTELY should upgrade to SP3 prior to clustering.
There are many security issues addressed in SP3; along with lots of
functionality fixes.
There are different registry settings so failover across different services
packs is probably NOT going to work. For example, the repository connection
is encrypted in the registry with SP3 and is not in earlier service packs.
So mixed environments won't work.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Michael Krok" <TheDuck (AT) newsgroup (DOT) nospam> wrote

Thanks Again

So just for sanity now -
Uncluster
Uninstall on each node
Reinstall on each node
Apply sp3a for AS on each node
Then cluster, using the Win2K Cluster ip address and name ;-)

Thanks much...
Mike

"Dave Wickert [MSFT]" wrote: