Overview
When the remediation job or auto-remediation starts deploying patches to a target machine, the following error is encountered: The service did not start due to a logon failure.
Solution
The most common root causes for this issue are that the account used for deployment has credentials problems or does not have required permissions on the target machine. As part of the deployment process, LanGuard temporarily installs the LanGuard Patch Agent service, and the account being used for deployment should have the local administrator privileges and permission to log on to the system as a service.
Verify the Account That Runs GFI LanGuard Patch Agent Service
When installing LanGuard Patch Agent Service, the account is determined based on the type of deployment and the patches' deployment settings. Refer to the articles below for different use cases:
- Configuring Auto-Remediation Options
- Deploying Updates and Software in GFI LanGuard Using Alternate Credentials
In both articles above, you eventually navigate to the Advanced options > Deploy patches under the following administrative account.
- If this option is enabled, the account specified here would install the service and deploy the patches.
- If nothing is checked here, then the currently logged in user or the alternative credentials set up for the machine or group it belongs would be used.
Ensure that the service account credentials are not misspelled, and the account has the local administrator privileges on the target machine.
Enable 'Log on as a Service' for the Account above on the Remote Computer
- Open the Control Panel on the remote system.
- Go to Administrative Tools > Local Security Policy.
- Navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment.
- Find the Log on as a service policy and add the account that would be used to run the service and install the patches.
- Click Apply, then OK.
If you want to set this policy for the entire domain, perform using the domain security policy snap-in.
Testing
Repeat the failing patch deployment and verify that the error is gone. If the issue persists, contact GFI LanGuard Support.