We used the exe to do this as opposed to manually adding to the XML DOM because the exe also generates temporary folders with random GUID names (and populates XML attributes with this path), and it just felt the more ‘supported’ option to use the exe to handle this instead.We have VMware Horizon View 5.2.0 infrastructure and we have created some different pools because we needed to migrate the previous production pools (from QuickPrep Guest Customization to Sysprep Guest Customization, due to a KMS host for Windows and Office licenses perfectly working).
We needed to add new servers by calling C:\Program Files (x86)\VMware\VMware Horizon View Client\vmware-view.exe".We needed to strip out unwanted servers manually by navigating the XML DOM for %AppData% \VMware\VMware Horizon View Client\prefs.txt".In this PowerShell script the two key elements are: Start-Process -WindowStyle hidden -Wait -FilePath $vmwareView -ArgumentList -ErrorAction Silentl圜ontinue #launching as hidden and unattended will add server to %AppData%\VMware\VMware Horizon View Client\prefs.xml #add default connection to newview.alkane $vmwareView = "$env:ProgramFiles (x86)\VMware\VMware Horizon View Client\vmware-view.exe" #path to view agent - used to add new connections #ensure serverName is not view.alkane, but newview.alkane
#remove references to view.alkane from recent connections $file = ($env:APPDATA)+"\VMware\VMware Horizon View Client\prefs.txt" #We launch as a separate job so there is no delay in login script processing And then to add additional servers, we used a PowerShell script based on AD group memberships which ran as a login script: #Add connections to VMWare Horizon Client This provided the default server we required without locking down the setting in the GUI. However, we did set the MRBroker registry entry using policy (via a manual registry configuration): HKLM\SOFTWARE\WOW6432Node\VMware, Inc.\VMware VDM\Client\MRBroker Needless to say, for these reasons we didn’t set this via policy. The second drawback is that if you set this, your VMWare Horizon Client will be locked down to this single server URL, and hence prevents users from adding any other server URLs manually via the ‘New Server’ button! Double bummer! When we looked at the VMWare Horizon view client ADMX there is a configuration called ServerURL:Ī couple of things to mention on this policy object is that firstly, it only permits one URL! Bummer. Unfortunately the ADMX file didn’t support this configuration, so we needed to implement it using PowerShell. We needed to configure VMWare Horizon client connections for different groups of users in an organisation.
0 kommentar(er)
