You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 useSet-DbaPrivilege
inInstall-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
The text was updated successfully, but these errors were encountered: