Jeramy Thompson

Looks like VMware came up with a solution to deploy the access point with powershell. https://communities.vmware.com/docs/DOC-30835

VMwareView.MOF Purpose: To create a WMI framework for querying agent variables created on a View Desktop. Details: The MOF allows you to query the following: ViewClient_Broker_DNS_Name ViewClient_Broker_DomainName ViewClient_Broker_Remote_IP_Address ViewClient_Broker_Tunneled ViewClient_Broker_URL ViewClient_Broker_UserName ViewClient_Client_ID ViewClient_Displays_Number ViewClient_Displays_Topology ViewClient_IP_Address ViewClient_Keyboard_KeyDelayToRepeat ViewClient_Keyboard_KeyRepeatRate ViewClient_Keyboard_Language ViewClient_Keyboard_Layout ViewClient_Keyboard_NumFuncKeys ViewClient_Keyboard_NumIndicators ViewClient_Keyboard_NumKeys ViewClient_Keyboard_ScanCodeMode ViewClient_Keyboard_SubType ViewClient_Keyboard_Type ViewClient_Language ViewClient_Launch_ID ViewClient_Launch_SessionType ViewClient_LoggedOn_Domainname ViewClient_LoggedOn_Username ViewClient_MAC_Address ViewClient_Machine_Domain ViewClient_Machine_Name ViewClient_Mouse_Identif

In some instances you may want to get some information on the users that are logging in to the VM's. This is not easily accessible through View its self. So I have come up with a way get the information from the VM's themselves. First of all your going to need the MOF file i created in an earlier post here for the WMI queries. Install this into your parent image. You will also need the logon script , that runs at logon located here . And lastly a remote SQL database that will hold the data, I have taken the liberty of creating a script to create the database for you here. After running trough this, you will be able to query for users that logged in to a specific VM and find any additional information provided by the agent. So lets get started. Create a database with the script Open up Microsoft Management studio and connect to your database server, create a new database, and use the script to create a new table. Paste the contents of the script into a new q

The purpose of this post is to show how you can query the "Volatile Environment" variables from the View agent to get WMI information. I though I would share what I have done to maybe help others in similar situations. Requirements: The requirements for this view environment is to allow client drive redirection for internal users and disable it for external users. The users are always in the same pool, and in this case we only have one connection server and one security server. Because this is a feature that is either on or off and no built in way to control this, the thought is that we can create a GPO that and run off a WMI query to determine if the users are inside the network or outside of the network and disable client drive redirection based on the IP. Lets Filter! So we can create a simple GPO to disable CDR , however we do not want this to happen internally so we need something to query off of. It would seam this would be an easy task however I ran into the f

One thing to keep in mind when upgrading is that View 5.3.5 disables SSLv3 and TLS 1.0. If you upgrade to View 6.x you will need to View 6.2.0 or 6.2, if you upgrade to 6.0 -6.1.1 you will be missing certain java components that have changed. Looks like it is in the release notes: http://pubs.vmware.com/Release_Notes/en/horizon-view/horizon-view-535-release-notes.html Upgrading View 5.3.5 to View 6.0 is not supported due to JRE incompatibilities. Workaround: Upgrade to View 6.1.0 or later

Ok so after what should have been a simple 20 minute upgrade took 3 hours I'm writing the steps on how to upgrade your ESXi 5.X server to 6.0 in place and using the Realtek drivers If you only have Realtek NIC's you are going to need to firm make sure you have a FAT16 USB stick that will work in your host.  first get to a command line and run the following /etc/init.d/usbarbitrator stop Now insert your USB drive and run this command esxcli storage core device list | grep -i usb You should see something like  "Local USB Direct-Access" now run  ls /vmfs/volumes You should see a volume with  'NO NAME ' as the title (if you do not, then your USB drive is probably not supported or not formatted with FAT 16. format the drive with FAT 16 or try a different USB drive till you get one that works) Now that you have verified you have a Drive you can use on the host lets begin the upgrade. First download the NIC VIB from here  https://vibsdepot.v-front.de/wiki

So One thing to keep in mind is if you are doing a staged upgrade of View, you may run into some issues with older versions of the client, or older versions of the agent. One thing that came up in my testing is if you are using PSG, and upgrade your servers first, you will not be able to connect. This has to do with the fact that TLS 1.0 is completely disabled by default. To fix this you must either enable it or upgrade your agents sooner. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2130798 It looks like they updated the documentation to show this. https://pubs.vmware.com/Release_Notes/en/horizon-6-view/horizon-621-view-release-notes.html