May 1, 2024 at 3:25 am
We have a windows account that currently has access to half of the sql server machines.(Both RDP and SQLAccess)
The rest of the servers we do not have both RDP and SQLAccess.
Does this mean when our accounts were created in AD we were not assigned to all relevant security groups which allows us to access all sqlserver windows machines ? I am sure all computers were joined to the domain within AD because the rest of machines having working sql instances.
Should we check our groups to which we have been added in AD first ?
And how can our windows login gain access to all sql instances ? (AD authentication). What needs to be done to get access to the rest of the windows machines along with SQL Access on them.
Assuming once we have access to all windows machines we add the relevant security groups to the SQL instance. Can in AD a security group be created which allows access to all SQLInstances ?
How are users granted access to all windows machines in a domain once they have their account created in AD.
Thanks
May 1, 2024 at 8:37 am
What groups are provisioned on the servers with rdp access too?
that is do you see the same AD group in windows admins as you see as syssdmin in the sql instance or is it a separate group?
Security best practice would dictate an AD group for sql access and another which is used for server access, it’s typical in some role separated environments for dbas to not have OS access.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply