Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install-DbaInstance and Set-DbaPrivilege: Which account should be used to grant SeManageVolumePrivilege? #9344

Open
andreasjordan opened this issue May 11, 2024 · 0 comments
Labels
feature triage required New issue that has not been reviewed by maintainers

Comments

@andreasjordan
Copy link
Contributor

Summarize Functionality

This is based on our findings that we documented here: https://blog.ordix.de/instant-file-initialization-microsoft-sql-server-set-up-check

TL;DR: setup.exe uses "NT SERVICE\MSSQLSERVER", the Configuration Manager uses "LABDOM\SQLServerGMSA$".

We currently use "LABDOM\SQLServerGMSA$" with Set-DbaPrivilege. And we use Set-DbaPrivilege in Install-DbaInstance.

First of all I would like to change Install-DbaInstance to use the setup.exe parameter SQLSVCINSTANTFILEINIT when installing version 2016 or later. That would allign the behavior to the setup.exe GUI.

But I would also question the use of the StartName property inside of Set-DbaPrivilege. Does anyone have a contact to the SQL Server development team to get their opinion?

Is there a command that is similiar or close to what you are looking for?

No

Technical Details

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature triage required New issue that has not been reviewed by maintainers
Projects
None yet
Development

No branches or pull requests

1 participant