To resolve this issue:
 
- Identify the Group policy which is overriding the local policy using the rsop.msc tool.
  
- Add these accounts to the Log on as a batch job policy of effective GPO. To add the accounts, navigate to Computer Configuration > Windows Settings >Security Settings >Local Policies > User Rights Assignment > Log on as a batch job
Note:  Add the account without the browse option.
- cm
 
- content-library
 
- eam
 
- imagebuilder
 
- mbcs
 
- netdumper
 
- perfcharts
 
- rbd
 
- vapiEndpoint
 
- vmware-vpostgres
 
- vsan-health
 
- vsm
 
- vsphere-client
 
- vsphere-ui
Note: You wont be able to make these changes on the vCenter itself, it will have to be done at their top level AD domain.
  
 
- Push the new policies to the vCenter Server.
 
- Open Command Prompt on vCenter Server.
  
- Run the command gpupdate/force to push the new policies. You see output similar to:
#gpupdate/force
Updating Policy...
User Policy update has completed successfully.
Compute Policy update has completed successfully.
  
- Reboot the vCenter Server.
  
- Verify that new active policies are pushed down and you are able to see them in the batch job policy.
  
 
- Start the vCenter services:
 
cd C:\Program Files\VMware\vCenter Server\bin
Note: This command uses the default installation path. If you have installed vCenter Server and/or Platform Services controller to another location, modify this command to reflect the correct install location.
service-control --start --all