Hello,
we are using Service Discovery Management Pack 2.0 in vROps 6.6.1 to get insight of our guest services. It works great, but since upgrading VMTools to 10.2 in Windows guests, we got errors in the Windows Applicaction log everytime the Service Management Pack user wants to scan the guest (it's a Windows domain account with local admin rights on every VM) that did not occur with VMTools 10.1 before:
Source: User Profile Service
Event ID: 1511
Level: Error
User: Our domain user that is set in vROps Service Discovery Management adapter
"Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off."
Since this Event ID is monitored by our Active directory team, it's generating a lot of false alarms there.
Does anybody have any ideas why this is happening with VMTools 10.2 and how to resolve it?
To resolve this issue. please refer the below VMware article which provides the post-installation configuration steps necessary when windows Heartbeat is administered locally by an account that is a different account than the account used to perform the installation.VMware Knowledge Base
Hi,
we do not use vCenter Server Heartbeart. We are just scanning (Windows) VMs with vROps Service Discovery Managemnt Pack while having VMTools 10.2 installed on them (at least the Windows machines).