Hello Mark,
Thanks for the reply. It's very helpful.
One question though: When we ran the "vdmadmin -F" on the connection broker, it looked like we didn't have to run it again each time we renamed an AD user account - View Admin reflected the change right away. Does the process run in the background until the services are stopped or when the host gets rebooted? Is it safe to run the command at any time?
Thanks,
Ricky
>>> markbenson <communities-emailer@vmware.com> 11/13/2014 6:05 AM >>>
VMware Communities ( https://communities.vmware.com/index.jspa )
Renaming AD User Account created by markbenson ( https://communities.vmware.com/people/markbenson ) in VMware View - View the full discussion ( https://communities.vmware.com/message/2448487#2448487 )
View Connection Server references to AD users and groups are done through Foreign Security Principals (FSPs - basically SID references) and not names. View Connection Server does cache the actual names as well but this is only for display purposes.
When you are changing the AD user accounts, does the SID change, or is it just the username etc.? If the SID remains the same, test this by renaming one of the AD accounts. Then use vdmadmin -F -u domain\user to update the details (such as username) of the single user in the FSP cache - see View 6.0 Admin Guide ( https://pubs.vmware.com/horizon-view-60/topic/com.vmware.ICbase/PDF/horizon-view-60-administration.pdf ) for details (search the document for vdmadmin -F). If that works for that user, then you can do all your changes in AD and then run vdmadmin -F to update the FSP cache for all users.
Reply to this message by going to VMware Communities ( https://communities.vmware.com/message/2448487#2448487 )
Start a new discussion in VMware View at VMware Communities ( https://communities.vmware.com/choose-container.jspa?contentType=1&containerType=14&container=2347 )
