February 6, 2017 at 7:18 am
Hello, I tried on MS SQL SERVER 2016 Standard change with SQL Configuratin Manager service SQL Agent from LocalSystem to
NT SERVICE\SQLSERVERAGENT (without problems).
When I change SQL Server service from LocalSystem to NT SERVICE\MSSQLSERVER i get message "WMI Provider Error" - not object or property found 0x80092004 Systemlog: SQL Server service (MSSQLSERVER) ended with the following specific error Service: object or property is not found. ID: 7024
The server normally works with SQL services under Local System and works without problems. For Database Mail I need to configure the service to NT SERVICE.
SQL run under Windows Server 2012 R2.
I tried unsuccessfully to:
Reboot the server, change login name direct with Services.msc, Powershell get-service | foreach {Write-Host NT Service \ $ ($ _. Name)} NT SERVICE\MSSQLSERVER exists, WMI Diagnosis Utility (in my opinion, nothing major found).
Thank you for your help ...
February 7, 2017 at 12:34 pm
kyssling - Monday, February 6, 2017 7:18 AMHello, I tried on MS SQL SERVER 2016 Standard change with SQL Configuratin Manager service SQL Agent from LocalSystem to
NT SERVICE\SQLSERVERAGENT (without problems).When I change SQL Server service from LocalSystem to NT SERVICE\MSSQLSERVER i get message "WMI Provider Error" - not object or property found 0x80092004 Systemlog: SQL Server service (MSSQLSERVER) ended with the following specific error Service: object or property is not found. ID: 7024
The server normally works with SQL services under Local System and works without problems. For Database Mail I need to configure the service to NT SERVICE.
SQL run under Windows Server 2012 R2.I tried unsuccessfully to:
Reboot the server, change login name direct with Services.msc, Powershell get-service | foreach {Write-Host NT Service \ $ ($ _. Name)} NT SERVICE\MSSQLSERVER exists, WMI Diagnosis Utility (in my opinion, nothing major found).Thank you for your help ...
NT SERVICE\SQLSERVER and NT SERVICE\SQLSERVERAGENT are virtual accounts from the service SID. You set your accounts as needed and these accounts are automatically created as part of the per service sid architecture. They aren't local accounts, they aren't domain accounts, they are services. You can find more information on these accounts here:
Configure Windows Service Accounts and Permissions
I'm not real sure what exactly you are trying to do when you say you need to change it to NT SERVICE as that isn't an account. It may be easier to just get a domain account or accounts for the services you want to change and use those in Configuration Manager.
Sue
February 9, 2017 at 4:40 am
Thank you for the tip,
it is possible do it on domain controller ?
see : You cannot run SQL Server services on a domain controller under a local service account.
(https://msdn.microsoft.com/en-us/library/ms143506.aspx#DC_Support)
February 9, 2017 at 10:37 am
kyssling - Thursday, February 9, 2017 4:40 AMThank you for the tip,it is possible do it on domain controller ?
see : You cannot run SQL Server services on a domain controller under a local service account.
(https://msdn.microsoft.com/en-us/library/ms143506.aspx#DC_Support)
Domain controllers do not have a local SAM so there are no local accounts, only domain accounts.
SQL Server should never be run on a domain controller, it's bad practice
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 10, 2017 at 3:07 am
Hello, just last two comments ....
1) SQLSERVERAGENT service works without problem
2) I'm surprised that I can not find powershell script for create permissions and rights SQL folder structure ...
https://msdn.microsoft.com/en-us/library/ms143504.aspx
I'm alone who have Domain and SQL ... or nobody create separate user for SQL services ...
- I think the script would be very helpful
February 10, 2017 at 9:52 am
kyssling - Friday, February 10, 2017 3:07 AMHello, just last two comments ....1) SQLSERVERAGENT service works without problem
2) I'm surprised that I can not find powershell script for create permissions and rights SQL folder structure ...
https://msdn.microsoft.com/en-us/library/ms143504.aspx
I'm alone who have Domain and SQL ... or nobody create separate user for SQL services ...
- I think the script would be very helpful
1. But now you are running SQL Agent with elevated rights it does not need. Since you used the virtual account, I would hope you know the impacts for that and if you will hit any issues in the future, what will happen if there are security changes in a service pack and the effects of that, impact on any upgrades, etc. Just because you CAN do something doesn't mean you SHOULD do it.
2. You really don't want to try to set all the permissions. The permissions are different for the virtual account, the service account and there is also the group to manage. That's why its recommended to use Configuration Manager as it will all be taken care using Configuration Manager.
Sue
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply