RTVNoord's Posts

Within our Horizon 8 (2206) environment, we have several different desktop pools. A group of users has access to multiple desktop pools. This is a desktop pool for the standard office environment and a desktop pool for video editing. Now we see more and more that users, for all kinds of reasons, start both desktop pools. Something that is not desirable. The question is whether it is possible to allow users to log in to only 1 desktop pool at once. Is there perhaps a setting within ADSI Edit for this? Tips/solutions are welcome Pascal

Hay, We are using several NVIDIA M10 cards and use the vGPU within VMWARE Horizon. The issue I’m dealing with is how and when the NVIDIA license are released within the NVIDIA license Server. Therefore in your client / golden image you can use 2 registry keys: LingerInterval and LicenseInterval (see here: Client Licensing User Guide :: NVIDIA Virtual GPU Software Documentation) In our situation, the LingerInterval is set at 0 and the LicenseInterval is set at 480 (8 hours) With this settings applied I see oversubscribed licenses and also double machine names within the NVIDIA license server. My question is: what are the correct settings for these 2 regkeys, so grid licenses are released / removed immediately when the computer will shutdown. Regards, Pascal

Hi there, We run Horizon 8.3.0 with several different Desktop Pools. Within these desktop pools we have set the "Log Off After Disconnect" at 90 minutes.  This setting is not set in the VMware Horizon Agent GPO, but only within the Pools This "Log off after disconnect" setting is to make sure our lazy users who just hit the X instead of logging off , still will be (forced) logged off. But.. this disconnect setting per desktop pool does not seem to work. As you can see in the image below, users are disconnected for many hours but not logged off. Finally, after the famous 10 hours (..the default setting for timeout is 10 hours) these users will finally be logged off. But as you can understand, that's not what we want. We want disconnected users to be logged off after 90 minutes, as set in the desktop pool. What's the bug overhere? And, how can we fix this so users are logged off after the set 90 minutes? Any ideas / help would be great  Regards, Pascal

We have some strange behaviour on our Horizon environment. We have several desktoppools where people can connect to. At the office everything works like a charm. Only from the outside (like home etc.) one pool is giving troubles; sometimes. When connecting to this pool, the horizon desktop just keeps loading and loading. In the Horizon admin interface you see no active connection on the machines in this specific pool. In the events no error is shown either and only mentions that the pending session for that machine has ended. The connection broker and uag's events, that are forwarded to our syslogserver are showing no errors  When connecting to this desktop / pool the events is only showing this information DOMAIN\bart Warning Agent The pending session on machine W10-XXX for user DOMAIN\bart has expired DOMAIN\bart Info Agent The agent running on machine W10-XXX has accepted an allocated session for user DOMAIN\bart DOMAIN\bart Info Connection Server User DOMAIN\bart requested Pool win10-avid, allocated machine W10-XXX DOMAIN\bart Info Connection Server User DOMAIN\bart requested Pool win10-avid The whole situation is not consistent. It works when on the Office network, and almost not when at home. People can connect to other desktops / pools from home without any problems. It's just that 1 desktop / pool that is giving problems. To make it even weirder: at home, sometimes people can connect from Windows desktops to this specific pool, but not from a MacBook. But not always. Some time later it also works on the MacBook. How weird.  We have 2 connection brokers (version 8.3.0-18294467) and 2 UAGs (version 21.06.2.0-18528989_OVF10) The Horizon clients is the latest for Windows and Mac The NVIDIA M10 GPU we are using runs at driver version 12.4 - 460.107 The desktop with problems is a clone from other pools, is running the latest W10 21H2 fully patched and optimized. The Horizon desktops run on esxi 7.0.0 And yes, I've also deleted the pool and recreated it etc. etc. But the behaviour stays the same: unpredictable What causes that users cannot connect to this desktop / pool from outside the network? Any help would be great.

When our users login from external, they first have to enter their username and their Two-Factor Authentication code. As you can see, within the Horizon client this is mentioned as Passcode I probably don't have to tell you how often people don't read this well and just entering their Password.. instead of Passcode. Is there any way / place / option to change this Passcode text into something else?     

If users type in a wrong password or username three times, the Horizon Client displays a message saying: Maximum login attempts exceeded. In previous versions this could be changed with Adsiedit on the connection broker, by changing the value "cs-loginattemptslimit=3" to a higher value. But within Horizon 8, when I look at pae-NameValuePair in the CN=Common object under OU=Global,OU=Properties this value is not there anymore. The question is: is this setting in Horizin 8 (2004) now placed elsewhere (I can't find it), or do I simply have to add this value cs-loginattemptslimit=10 to this Attribute??

We are using the 2-Factor Authentication from Google in Horizon View for all our external Horizon users. Therefore we have setup a CentOS VM with the Google Authenticator package installed. The Guide for this can be found here: https://blogs.vmware.com/consulting/files/2015/02/VMW_15Q1_TD_Horizon-View-Google-Authenticator_021715_FINAL_EMonjoin.pdf Because Sysadmins are a bit lazy :smileygrin: and we also do not want to generate every QR-code by hand for all our Users, we have come up with this fully automated Linux script. A cronjob runs this script every 5 minutes. If a new user and HomeDir is created, the script automaticly creates the QR-code for this user and places a textfile with the URL for the QR-code in the Users Homedir. It works like a charm and saves us a lot of time. :smileyinfo:  Feel free to use this script in your own environment, but please leave the header info as it is #!/bin/bash # This script is created by John at RTV-Noord. You may use and distribute # it as long as you keep this header as it is. # # THE USAGE OF THIS SCRIPT IS AT YOUR OWN RISK! # # There are some prerequisites to make this script work: # - machine you run it from is a Active Directory Domain member # - the share with AD homedirs is mounted on /mnt/home # - the google-authenticator package is installed # - replace domainname.com with your AD domainname ls /mnt/home > all_users MAKEQR=$(comm -3 all_users users_with_qr | wc -l) if [ $MAKEQR -gt 0 ]; then     echo "Found users without QR."     comm -3 all_users users_with_qr > users_without_qr     for user in $(cat users_without_qr); do         echo "    $(date) make qr for $user..."         su -l "$user@domainname.com" -c "google-authenticator -tdf -r 3 -R 30 -w 17 -Q UTF8 | grep http > google-authenticator.txt"         mv /home/$user@domainname.com/google-authenticator.txt /mnt/home/$user/     done     cat all_users > users_with_qr     rm users_without_qr     echo     echo "$MAKEQR QR-code has been created" fi