- #The pcoip protocol requires view security server how to
- #The pcoip protocol requires view security server install
- #The pcoip protocol requires view security server update
- #The pcoip protocol requires view security server series
#The pcoip protocol requires view security server how to
This article provides instructions on how to configure DHCP image upgrade on your Cisco Business switch in two ways: DHCP Auto Configuration and Image Auto Update. If the new configuration is downloaded to a switch that already has a configuration, the downloaded configuration is appended to the configuration file stored on the switch.
#The pcoip protocol requires view security server update
If Image Auto Update is enabled, the flash image is downloaded and updated. DHCP Auto Image Update - Used with DHCP Auto Configuration, this allows you to download both a configuration and a new image to one or more switches in the network.
![the pcoip protocol requires view security server the pcoip protocol requires view security server](https://4sysops.com/wp-content/uploads/2017/11/Horizon-View-Security-Server-topology-courtesy-of-VMware.png)
By default, the switch is enabled as a DHCP client when the Auto Configuration feature is enabled. This functions properly only when the DHCP server is configured to assign the host IP address dynamically.
#The pcoip protocol requires view security server series
Note that it requires that the Active Directory Module for Windows PowerShell be installed, which I believe requires 2008 R2 or Windows 7.VLAN Configuration on the 200/300 Series Managed Switches Objective Unless this gets revised, I suppose this method will have to do. Schedule up a task to run it every so often (I set ours to every 1 hour), and just train the users to choose RDP when they are at home. In any case, I spent a little time writing a powershell script that will delete all of the pae-Prop objects from the correct OU in the ADAM instance for a given server. I suppose we could do something like use a separate connection broker, but I'd rather just use what we've already paid for at the moment.
![the pcoip protocol requires view security server the pcoip protocol requires view security server](https://4sysops.com/wp-content/uploads/2017/11/The-Horizon-View-Security-Server-should-be-accessible-via-the-URLs.png)
Of course, if you're using non-persistent pools then you could have an 'External users' desktop, configured to only support RDP connections, which may be the simplest solution.
#The pcoip protocol requires view security server install
This means though that any client that supports PCoIP will attempt a PCoIP launch, so you would have to get users to install the View 3.1 client at home, the broker will then fall back to providing them with a RDP desktop. That way clients will always connect with the default protocol on launch (so you can trigger PCoIP default protocol selection internally if you set that as the default protocol in the pool settings). These preferences are saved in ADAM on the connection server (under guid=xxx,ou=properties,dc=vdi,dc=vmware,dc=int), so you could potentially clean out the preference regularly using a script. remembering to check display protocol at launch is too much for users, which I can see as valid) I can think of one way to solve both parts of the problem, but it's not trivial.
![the pcoip protocol requires view security server the pcoip protocol requires view security server](https://vmarena.com/wp-content/uploads/2018/06/CON7.5-1.png)
That means there are actually two parts to your problem (1) default is PCoIP when launching from home and (2) if launched using RDP from home the default will be RDP on next launch from the office.Īssuming you must have PCoIP internally and RDP externally with no user interaction (i.e. Display protocol preference is saved by the client by user/pool pair, it's not currently possible to force a preference based on which server the client comes through on.