If you are running the Horizon View Client - login in to the client and then right click on the Pool or icon for the virtual machine. You should get a drop down with an option to change the display to 'fullscreen' which is a single screen or 'all monitors'.
Navigation This article applies to all Horizon Clients for Windows, including 4.10. Carl, real interesting one we have here We’ve been using Horizon VDI for a while. External clients would often choose their connection protocol (BLAST or PCoIP) depending on what worked on their network, usually Blast worked better, but some clients need Scanner redirection which Blast doesn’t support officially, yet.
Now that we’ve started using Workspace ONE we are forcing external clients to multi factor authenticate (MFA). Since Workspace ONE won’t let a client choose the protocol before connecting them to the pool clients are having display issues (black VM screens) when I believe Blast would fix it, but can’t be selected. Is there a registry or GP tweak that we could do on the client’s end to make Blast the default protocol on all new connections? This would only be for those that don’t have to use PCoIP which the pool is at by default. There’s a weird quirk with the desktop shortcuts. I have three VDI desktops on two different servers, two in my local office and one in corporate HQ, and I created desktop shortcuts for all three. If I launch one local desktop from the shortcut it goes through the normal authentication.
When I launch the second local desktop, it skips all that and just opens. So far, so good.
![For For](/uploads/1/2/5/4/125496448/968030086.png)
If I try to launch the 3rd desktop on a different connection server from the shortcut, it warns me it will disconnect all active desktops/sessions if I continue (and it does if I do). However, if I launch the actual Horizon client, I can connect to that 3rd VM on the other server without affecting the active local ones. Carl, Any way to HIDE apps from the horizon client, so it only shows desktops? We use Dell and 10zig thin-clients, that are configured to auto launch a desktop if it is the only available item But we also publish RDS apps So when a user has “Standard Pool” and one or more published apps. When they log into the thin-client, it no longer auto-launches their “Standard Pool” as it has one desktop (Pool) and 1 or more RDS Apps We are slowly replacing Citrix with RDS Apps in Horizon We publish all our RDS Apps in Horizon, and users now use the Horizon client to launch the apps they used to use in Citrix (Working great) But now they have to select their pool on logon.
Hi Carl, Quick query re: Horizon 7 and published applications. From testing, it seems that if you try and open a file located on a UNC path (i.e.a network redirected folder), and select Open With to launch a published application, the Horizon View client opens the application, but unsuccessfully tries to pass the file through as a tsclient hosted file. This of course fails, but suggests that in order to open any UNC hosted files, the user must do this within the published application, rather than leveraging a simple double click. Are you aware of this limitation? Mapping the UNC path as a fixed drive letter is a workaround but surely this is more of a known and widespread issue?