Probably the easiest way to resolve the permission issue, which I believe you probably need more than just VirtualMachine.Config.Rename is to make a copy of say "Virtual Machine Power User" and then slowly remove one privilege at a time (trial and error) until you figure out the minimal amount of privileges. Certain ones will standout, like you can easily remove "Global.CancelTask" if you don't need that,etc. This hopefully will then give you the bare minimal for a user to update the "annotation" BUT does not guarantee it won't require other privileges than just updating the annotation. Hopefully that makes sense
=========================================================================
William Lam
VMware vExpert 2009
VMware ESX/ESXi scripts and resources at:
Twitter: @lamw
VMware Code Central - Scripts/Sample code for Developers and Administrators
VMware Developer Community
If you find this information useful, please award points for "correct" or "helpful".