This content has been marked as final. Show 3 replies
It certainly sounds as if the necessary credentials are not being passed, although it may be necessary to analyze further log data to be sure.
Try the following:
1) Create a new machine group.
2) Add a single entry for a single machine.
3) Specify credentials for the machine.
4) Scan the new machine group.
5) Once the scan has completed successfully, navigate to the scan results.
6) Select the result, then select the machine in the upper pane.
7) From the alternate (right-click) menu, select 'Machine Properties'.
8) Confirm that the value in the 'Credential' field is correct. If it is not, change it to the correct credential.
9) Attempt to deploy a single update to the machine.
If the deployment is still failing to schedule, verify that the credentials used are granted (and not denied) the following permissions:
User Rights Assignment Permissions (local security policy on target machine)
Backup Files and Directories
Restore Files and Directories
Take Ownership of Files or Other Objects
Manage Auditing and Security Log
Log on as a Batch Job
If you are still unable to resolve the issue, we would urge you to contact Support directly for further assistance in generating, collecting, and analyzing log data.
Thanks for the answer, I did check the "Credential Field" and it has another account, I changed it and it worked.
Why does it have another account if I scan with the one which worked fine? (I used the same Machine group assigning the proper credentials)
Once the credential field is populated within the machine's properties, they will not be changed automatically (i.e. they must be manually changed).