Often times we do see problems with machines running UAC. You can look to this guide http://kb.vmware.com/kb/2031469 to help identify other possible issues for the 452 error. If they do not help you may need to disable UAC.
Welcome to the communities.
Definitely security admin tendency should be that way .
It may prevent form viruses infection . You can use runas option & provide admin credential.
I am not exactly sure what you are telling the OP but "run as" is not an option for the vCenter Protect Product.
1 of 1 people found this helpful
This is a UAC issue. Once I disable it I am able to patch both agent and agentless devices.
You can try this:
Add HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystemLocalAccountTokenFilterPolicy dword with value 1 in order to allow access to admin shares .
Problem is that on Server 2008 local accounts don't have access to admin shares over the network by default. Shavlik needs access to these shares to scan the servers.
This worked for me.
I have UAC running on my machines and they work fine, albeit when I provide credentials. I always get the 452 Error when I don;t use credentials.
Set yourself up with the correct credentials and assign it to the machine group (or individual server) prior to scanning.