Your steps are fine, you only need to take the application resource offline,
not the whole group. Cluster really has no clue or doesn't interact with
whatever account the app is using. No KBs that I know of as this is more an
issue of the app itself as opposed to the cluster.
Thanks,
--
Jeff Hughes, MCSE
Senior Support Escalation Engineer
Microsoft Enterprise Platforms Support (Server Core/Cluster)
"kb1lxm" <> wrote in message
news:0BBCCA08-0029-46AC-8483-...
> A member of our App/Dev team installed an application using the wrong
> service
> account. While a simple fix on a stand alone box, this is on a cluster,
> as
> the application requires high availablity. Now the account is actually
> for
> the vendor to access the system, and the account expired the other day,
> making the app grind to a halt.
>
> This is not for the Cluster Service account, that one is ok.
>
> Here is what I think I need to do.
>
> 1.) In Cluster Administrator stop the application resources, not the whole
> group
> 2.) On the active node, change the service accounts in services.msc
> 3.) Start the application resources in Cluster Administrator
> 4.) If services come up, change service accounts on the passive node.
> 5.) Bounce the whole group to the passive node and see if it comes up.
>
> Now do I need to stop the whole Resource Group, or can I just stop the
> individual Application Resources, there are 3.
>
> Is there a Kbase article that can confirm this?
>
> Thanks
|