davebaker87's Posts

We have some legacy apps that, for one reason or another, can't be moved from their Horizon 6 RDSH farm into appvolumes. What happens is as follow > 1. Users connect to H7 VDI using the horizo... See more...
We have some legacy apps that, for one reason or another, can't be moved from their Horizon 6 RDSH farm into appvolumes. What happens is as follow > 1. Users connect to H7 VDI using the horizon client or P25 device. 2. From the desktop, they launch the horizon client and log into the Horizon 6 platform to launch an RDSH app. 3. The app opens and it immediately spans 2 monitors and cannot be scaled/re-sized to fit 1 screen. So in effect, they double-hopping to reach the app, which is the only method available until we can migrate the apps. However, this basically makes the desktop unworkable because you can't work side -by-side. If the RDSH apps are launched from a single-hop (i.e. from a laptop) - the session window scales correctly and the app appears seamlessly on the desktop (with no RDP window/bezel). I've tried the following to fix this: 1. GPO to limit the maximum number of monitors to use in RDSH\Connections to 1 (in policy: Computer Confi\Policies\Administrative Templates\System\Group Policy\Windows Components\Remote Desktop Services\Remote Desktop Sessions Host\Remote Session Environment) 2. Set the Horizon client to 'Display scaling' enabled (this is enabled by default) Neither has worked. The issue is isolated to launching a horizon session within a session, specifically with an RDSH app in Horizon 6. Any other suggestions?!
Hi All, We have a H6 dedicated machine desktop pool with a weird bug. I've spun up an additional VM for a user, when I try to assign the username to the VM is says: The user Monitoring Cons... See more...
Hi All, We have a H6 dedicated machine desktop pool with a weird bug. I've spun up an additional VM for a user, when I try to assign the username to the VM is says: The user Monitoring Console 37 cannot be assigned the selected machine because this user has already been assigned ownership of a machine in the desktop pool. I can see there are no desktops assignments in the view console, and nothing in the Pool entitlements for that username. No idea why it's not allowing the assignment? Presumably I need a command to check the database for this or PowerCLI to query desktop assignments, can anybody advise? Thanks Dave
Hi All, We're currently migrating from Teradici console to using Dell Wyse Management. We have 50~ kiosk-style machines (more like dashboards) that we need to do the following: 1. Auto-login ... See more...
Hi All, We're currently migrating from Teradici console to using Dell Wyse Management. We have 50~ kiosk-style machines (more like dashboards) that we need to do the following: 1. Auto-login using a specified account - DONE 2. Choose a specific pool  - PROBLEMOS! Currently the user account (despite being permissioned for 2 pools - the 'default' global pool and the DASHBOARD pool, it always defaults to the global pool. In Teradici it's very easy to configure an auto-logon profile - you enter the username, password, domain and the pool name to select. In Dell, you cannot specify a pool-name. So our dashboard PC's are logging into our 'generic' desktop pool. They are all connecting via the same connection server. Please note, we really don't want to have to setup mac address auto-logins via the connection server (as you would with a kiosk) -I know this is possible, we just want the devices to auto-login and go to a specific pool of non-persistent machines.  For information, We have entitled the pools via global entitlements (not entitlements on the specific pools within view manager). Any ideas how we achieve this in Dell Console or otherwise? Thanks Dave
I'm packaging Foxit Reader in appvolumes. During provisioning, after I've completed the install I launch Foxit once, reboot the machine and re-launch it again (to be safe!) and then finish provis... See more...
I'm packaging Foxit Reader in appvolumes. During provisioning, after I've completed the install I launch Foxit once, reboot the machine and re-launch it again (to be safe!) and then finish provisioning. That's the packaging process covered... When I then deploy the appvolume to a desktop, during boot as the desktop icons are populating, an msi installation window shows and the app appears to be configuring itself /installing itself (again)... Any ideas on what causes this? We have a few apps that have similar behaviours (here's number 2: hich happens to be UEM Management Console, which errors saying a different version is running already (which it isn't) and needs closing before it can open. Clicking Ok, it then reopens fine.)