| Puppet Version: 7.6.0
Puppet Server Version: 2021.1
OS Name/Version: Primary RHEL8 & Agent(issues) Windows Server 2019 The customer is having issues with running MSSQL service by passing `logonaccount` parameters. Error: Failed to apply catalog: Parameter logonpassword failed on Service[MSSQLSERVER]: Failed to update service configuration: The account name is invalid or does not exist, or the password is invalid for the account name specified. (file: /etc/puppetlabs/code/modules/profiles/manifests/windows/mssql.pp, line: 32) I have attached the code provided by the customer and also a screenshot of their AD structure. The customer has tried to insert different combinations of LogonAccount (also trying to pass full path): 1. PILOT\rma_sql_svc
2. PILOT
rma_sql_svc
3. pilot.usda.lab\rma_sql_svc
4. pilot.usda.lab
rma_sql_svc
6. rma_s...@pilot.usda.lab Code snippet: service {'MSSQLSERVER':
logonaccount => 'pilot.usda.lab
rma_sql_svc',
logonpassword => 'Password1234', #sensitive
ensure => 'running'} **The puppet service account was given both Domain administrator and local administrator rights and nothing has worked. The customer has also stated: "When we install puppet, it is not yet joined to the domain. Puppet will join the server to the domain after the first run of its agent. Until then it has a local service account assigned. When I try to tell puppet to change its account from local service to the domain account, I get an access denied (assuming the local account is unable to do the lookup of the domain account)." Desired Behavior: Run the MSSQL with a specific account without giving puppet service administrator rights. Actual Behavior: Fails to find the domain account specified. |
