Hello Everyone,
The accounts I am referring to are added to the Operating System Local User Store automatically through the installation of SQL R Services (renamed to Machine Learning Service in 2017). R Services lets you execute R scripts in the database without moving the data outside of the SQL Server or over the network.
The accounts are in the database so they are not listed as accounts associated to the Database Security Logins, and are unable by default to login locally. But due to the fact that they are added as a Local User the ability to reset the password exists, I just have yet to be able to find any useful information in my research as it relates to changing these passwords and what the impact may be. :)
Can anyone tell me what the best practice is for managing these local user accounts or what the impact of changing the passwords might be?
From Configure Windows service accounts and permissions - SQL Server | Microsoft Docs
• SQL Server Launchpad- A trusted service that hosts external executables that are provided by Microsoft, such as the R or Python runtimes installed as part of R Services or Machine Learning Services. Satellite processes can be launched by the Launchpad process but is resource governed based on the configuration of the individual instance. The Launchpad service runs under its own user account, and each satellite process for a specific, registered runtime inherits the user account of the Launchpad. Satellite processes are created and destroyed on demand during execution time.
Launchpad can't create the accounts it uses if you install SQL Server on a computer that is also used as a domain controller. Hence, setup of R Services (In-Database) or Machine Learning Services (In-Database) fails on a domain controller.
R Services or Machine Learning Services EXTSVCACCOUNT, EXTSVCPASSWORD, ADVANCEDANALYTICS***
R Services/Machine Learning Services: SQLRUserGroup (SQL 2016 and 2017) doesn't have the Allow Log on locally permission by default