It would seem the scheduler is unable to use (decrypt) the browse credentials. Have you tried deleting and then re-creating the credentials you are setting as the Browse credentials? This is the first thing I would try.
I just tried to re-create the Credentials and it is still failing. To note, I have the same Account assigned to the "Scheduled Console Scans/Operations Credential" as the vCenter Brows Credentials. This account is also set as the Default Credentials as well. Will this have any affect?
The account set for the Scheduled Console Scans only needs to be admin on the Protect server. Setting it as the default would not cause an issue. Gathering logs and opening a support case would be advisable, this way we can see what is failing from the logs.
1. If you are unable to set logging via the GUI see this doc: http://community.shavlik.com/docs/DOC-22938
2. Close the Protect GUI.
3. Stop the following services
a. Shavlik Protect Console Service
b. ST Remote Scheduler Service (In 9.2, the ST Remote Scheduler Service is no longer used on the console. You do not need to stop this service if using 9.2)
4. Delete all the logs from
a. Windows Vista, 7, 8, 10, Server 2008, Server 2012: C:\ProgramData\LANDesk\Shavlik Protect\Logs
5. Start the console service and open the Protect GUI.
6. Attempt to reproduce the issue. Please document steps to reproduce. In this case, please do the following: Create a new Machine Group and add 1 machine to it. Set Browse and Admin credentials to the group. Setup a scan to run in 10 minutes from the group. Wait for it to fail. Screenshots from the Machine Group would be good.
a. Collect the logs from the Logs folder mentioned earlier in step 4 (please zip if possible)
7. Open a case with support: Support Portal Zip and attach the logs to the case once it's created.
Let me know if you have any questions.
Thank you for your assistance. I will open a support case. Have a good one!
Having the same issue. Did you get a resolution??
I've got a Support Case opened and still working on the issue; had to post pone the troubleshooting for a bit. I have narrowed down the cause of my issue to the Credentials assigned to the "Scheduled Console Scans/Operations Credential" Account on on the “Manage ->Scheduled Console Tasks” screen. So you may want to check there if you are having the same issues.
After working with Support, it was determined I had to enable Roles in User Role Assignment. I then had to log into the new Account on the Shavlik Server to create and configure the Credentials under it's own account. Support stated this was due to how Microsoft's scheduler utilizes credentials.
I was having a similar problem with certain OU's in AD not enumerating when I attempted to scan them. I dont see the solution anywhere else, so ill post it here in hopes it helps others in the future.
Certain character in an OU name may not enumerate through LDAP. For instance:
"Servers - Test/Dev" will not enumerate, and therefore no severs will get discovered and scanned.
"Servers - TestDev" will work just fine.
the "/" is not an acceptable character. There are likely other special characters that may cause an error.