Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Clustering / August 2006

Tip: Looking for answers? Try searching our database.

How to change service accounts on a cluster

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
tootsuite@gmail.com - 25 Aug 2006 23:23 GMT
Hello,

Need help. Have 2005 SQL Server cluster... I need to change the service
accounts for SQL Server, SQL Server Agent, etc to a non-administrator
domain user.

What is the correct way to do this? From which node do I change the
service accounts? Do I need to change them on both nodes?

I've tried to make the changes from one of the nodes, but every time I
click "OK" it says - specified network password is incorrect. I've
confirmed with our sysadmin here that it IS the correct password for
the domain user.

I'm not even sure if I'm approaching this correctly. Help.

Thanks,
Kat
Geoff N. Hiten - 26 Aug 2006 01:15 GMT
If you use SSMS you can change the account when you are connected to the
virtual SQL instance and it will do the job cluster-wide.  You need to make
sure the new accounts are in the same groups as the original accounts.  Test
the accounts by logging on to the console of each server before trying to
change the service accounts.

Signature

Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP

> Hello,
>
[quoted text clipped - 14 lines]
> Thanks,
> Kat
Michael Hotek - 28 Aug 2006 19:56 GMT
Actually, you CAN'T use SSMS to change service accounts in 2005.  You need
to use SQL Configuration Manager to change the service accounts.  You only
need to do this once and SQL Configuration Manager takes care of everything
else.

Signature

Mike Hotek
MHS Enterprises, Inc
http://www.mssqlserver.com

> If you use SSMS you can change the account when you are connected to the
> virtual SQL instance and it will do the job cluster-wide.  You need to
[quoted text clipped - 20 lines]
>> Thanks,
>> Kat
tootsuite@gmail.com - 28 Aug 2006 22:38 GMT
> Actually, you CAN'T use SSMS to change service accounts in 2005.  You need
> to use SQL Configuration Manager to change the service accounts.  You only
> need to do this once and SQL Configuration Manager takes care of everything
> else.

That much I've determined from reading BOL, etc - but still not sure
which node to do this from?

Also, it doesn't accept the password I enter - says it's not a "network
password".

Still clueless - any help appreciated!!
Geoff N. Hiten - 29 Aug 2006 01:21 GMT
You are correct.  Configuration manager is the correct tool.

Signature

Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP

> Actually, you CAN'T use SSMS to change service accounts in 2005.  You need
> to use SQL Configuration Manager to change the service accounts.  You only
[quoted text clipped - 25 lines]
>>> Thanks,
>>> Kat
tootsuite@gmail.com - 30 Aug 2006 17:05 GMT
The problem remains - when I try to change the service account using
SQL Server Configuration Manager I always get the same error:

The network password you specified is not correct"

> You are correct.  Configuration manager is the correct tool.
>
[quoted text clipped - 42 lines]
> >>> Thanks,
> >>> Kat
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.