Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Service account change


SQL Service account change

Author
Message
hambo12
hambo12
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 24
Was there any resolution to this issue? I am experiencing a very similar issue at the moment...
SQLAssAS
SQLAssAS
SSC-Addicted
SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)

Group: General Forum Members
Points: 418 Visits: 1146
muthyala_51 (4/29/2013)
Does the new Service account is added in the Local administrator group on both the servers (Primary and seconday)?


This is not required - The account just needs to be able to read\write from the location of the logs, both primary and secondary. Do not add service accounts to local admin groups.
deep_kkumar
deep_kkumar
SSC-Enthusiastic
SSC-Enthusiastic (127 reputation)SSC-Enthusiastic (127 reputation)SSC-Enthusiastic (127 reputation)SSC-Enthusiastic (127 reputation)SSC-Enthusiastic (127 reputation)SSC-Enthusiastic (127 reputation)SSC-Enthusiastic (127 reputation)SSC-Enthusiastic (127 reputation)

Group: General Forum Members
Points: 127 Visits: 756
SQLSteve (10/30/2013)
muthyala_51 (4/29/2013)
Does the new Service account is added in the Local administrator group on both the servers (Primary and seconday)?


This is not required - The account just needs to be able to read\write from the location of the logs, both primary and secondary. Do not add service accounts to local admin groups.



Can you explain in detail why a service account doesn't need to be added in admin group ? Pros n Cons.
Keith Tate
Keith Tate
SSChasing Mays
SSChasing Mays (614 reputation)SSChasing Mays (614 reputation)SSChasing Mays (614 reputation)SSChasing Mays (614 reputation)SSChasing Mays (614 reputation)SSChasing Mays (614 reputation)SSChasing Mays (614 reputation)SSChasing Mays (614 reputation)

Group: General Forum Members
Points: 614 Visits: 979
When setting up your service accounts you want to follow the principle of least privilege. Basically this means that you only want to grant the necessary rights to your service accounts to do it's job and nothing more. I have never come across a reason that I needed my service account to be a domain admin or a local admin. I simply grant the necessary permissions to the account and that is all.

The reason for this is security, plain and simply. If you service account gets hacked you want to limit your potential damage by limiting the hackers surface area. Domain admin and/or local admin is a pretty big surface area.

Now a couple of people have asked if the new account has read/write access to the location of the Tlog backups. Does it? Start there. Also, any changes you make to your service account needs to be done through SQL Server Configuration Manager not by going directly to the service itself.



Microsoft Certified Master - SQL Server 2008
Follow me on twitter: @keith_tate

Forum Etiquette: How to post data/code on a forum to get the best help
SQLAssAS
SQLAssAS
SSC-Addicted
SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)SSC-Addicted (418 reputation)

Group: General Forum Members
Points: 418 Visits: 1146
Keith Tate (10/31/2013)
When setting up your service accounts you want to follow the principle of least privilege. Basically this means that you only want to grant the necessary rights to your service accounts to do it's job and nothing more. I have never come across a reason that I needed my service account to be a domain admin or a local admin. I simply grant the necessary permissions to the account and that is all.

The reason for this is security, plain and simply. If you service account gets hacked you want to limit your potential damage by limiting the hackers surface area. Domain admin and/or local admin is a pretty big surface area.

Now a couple of people have asked if the new account has read/write access to the location of the Tlog backups. Does it? Start there. Also, any changes you make to your service account needs to be done through SQL Server Configuration Manager not by going directly to the service itself.


+1
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search