Error 452 is a scan error and not a deployment error. Add the machine to a new Machine Group, set valid credentials for the machine and attempt to scan. Success? Can you deploy from the scan results? A screenshot of the failure would help.
There are also a few documents on this community regarding Error 452.
1 of 1 people found this helpful
I had the same error with scheduled scans after upgrading to 9.2. I solved this by selecting all scheduled scans and click on "Take Ownership". Maybe this will solve also your problem.
Thank you all,
This was totally a credential problem. After I reapplied the default admin credential to my scheduled jobs, they all performed correctly.
Thanks for letting us know!