<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Zero clients and Windows Logon/Message Banner in Horizon Desktops and Apps</title>
    <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Zero-clients-and-Windows-Logon-Message-Banner/m-p/2985106#M99852</link>
    <description>&lt;P&gt;Good afternoon!&lt;/P&gt;&lt;P&gt;We're using the latest/greatest Horizon build and have zero clients connecting to Windows 10 VMs using their domain logon creds.&amp;nbsp; On the Windows 10 machines (via group policy), we set the usual logon banners about monitoring, etc.&amp;nbsp; We also have a policy that enables a locking screensaver after 20 minutes.&lt;/P&gt;&lt;P&gt;We have just discovered the following "feature":&lt;/P&gt;&lt;P&gt;1. User enters credentials into the Horizon client from the zero client, selects their desktop pool, and is connected to a VM.&lt;/P&gt;&lt;P&gt;2.&amp;nbsp; User gets the logon banner/message but does NOT click OK (Goes to get coffee)&lt;/P&gt;&lt;P&gt;3.&amp;nbsp; User comes back 25 minutes later (they drink a LOT of coffee!)&lt;/P&gt;&lt;P&gt;4.&amp;nbsp; The screen appears to be locked and user hits CTRL-ALT-DEL.&amp;nbsp; This takes them back to the logon banner from Step 2 (Without re-entering a password).&amp;nbsp; User clicks OK and is then logged into Windows without any additional actions like re-entering their password&lt;/P&gt;&lt;P&gt;In the past (Probably 2-3 years ago), this behavior resulted in the session getting stuck as we had a colleague that would sometimes forget to hit OK and we'd need to clear or log-off his session from the Horizon console.&lt;/P&gt;&lt;P&gt;As a workaround, we'll probably just use the logon message within Horizon instead of a Windows GPO but wanted to see if others have seen and dealt with this situation via other methods.&lt;/P&gt;</description>
    <pubDate>Fri, 01 Sep 2023 17:21:59 GMT</pubDate>
    <dc:creator>MrCheesecake</dc:creator>
    <dc:date>2023-09-01T17:21:59Z</dc:date>
    <item>
      <title>Zero clients and Windows Logon/Message Banner</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Zero-clients-and-Windows-Logon-Message-Banner/m-p/2985106#M99852</link>
      <description>&lt;P&gt;Good afternoon!&lt;/P&gt;&lt;P&gt;We're using the latest/greatest Horizon build and have zero clients connecting to Windows 10 VMs using their domain logon creds.&amp;nbsp; On the Windows 10 machines (via group policy), we set the usual logon banners about monitoring, etc.&amp;nbsp; We also have a policy that enables a locking screensaver after 20 minutes.&lt;/P&gt;&lt;P&gt;We have just discovered the following "feature":&lt;/P&gt;&lt;P&gt;1. User enters credentials into the Horizon client from the zero client, selects their desktop pool, and is connected to a VM.&lt;/P&gt;&lt;P&gt;2.&amp;nbsp; User gets the logon banner/message but does NOT click OK (Goes to get coffee)&lt;/P&gt;&lt;P&gt;3.&amp;nbsp; User comes back 25 minutes later (they drink a LOT of coffee!)&lt;/P&gt;&lt;P&gt;4.&amp;nbsp; The screen appears to be locked and user hits CTRL-ALT-DEL.&amp;nbsp; This takes them back to the logon banner from Step 2 (Without re-entering a password).&amp;nbsp; User clicks OK and is then logged into Windows without any additional actions like re-entering their password&lt;/P&gt;&lt;P&gt;In the past (Probably 2-3 years ago), this behavior resulted in the session getting stuck as we had a colleague that would sometimes forget to hit OK and we'd need to clear or log-off his session from the Horizon console.&lt;/P&gt;&lt;P&gt;As a workaround, we'll probably just use the logon message within Horizon instead of a Windows GPO but wanted to see if others have seen and dealt with this situation via other methods.&lt;/P&gt;</description>
      <pubDate>Fri, 01 Sep 2023 17:21:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Zero-clients-and-Windows-Logon-Message-Banner/m-p/2985106#M99852</guid>
      <dc:creator>MrCheesecake</dc:creator>
      <dc:date>2023-09-01T17:21:59Z</dc:date>
    </item>
    <item>
      <title>Re: Zero clients and Windows Logon/Message Banner</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Zero-clients-and-Windows-Logon-Message-Banner/m-p/2985613#M99881</link>
      <description>&lt;P&gt;I have a quick and interesting update on this.&lt;/P&gt;&lt;P&gt;Forgot to mention in the original post that we're using SSO so that the creds entered in the zero client are passed through to the Windows VM.&amp;nbsp; I tried adjusting the setting (Global Settings\General Settings) to discard SSO creds after XX minutes to something much lower than the screensaver but with no luck.&lt;/P&gt;&lt;P&gt;I was stumped but just observed something interesting...&amp;nbsp; I'm looking at the events in the connection broker and see where I logged in, selected my VM pool and was even assigned WorkstationXX.&amp;nbsp; The machine is currently waiting for me to click OK to the logon banner/message-&amp;nbsp; However, the connection broker does not show me and/or the workstation assigned in a session!&amp;nbsp; But you just told me that I was assigned a workstation!?!&lt;/P&gt;&lt;P&gt;This leads me to think that there's a new feature/hiccup in how Horizon detects sessions.&lt;/P&gt;&lt;P&gt;Strangely, I do get an event in the connection broker later on showing that my SSO credentials are locked (still no session).&amp;nbsp; And when I return to my client, the screen IS locked, but after hitting CTRL-ALT-DEL, I get back to my banner and hitting OK takes me right into Windows.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Sep 2023 21:10:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Zero-clients-and-Windows-Logon-Message-Banner/m-p/2985613#M99881</guid>
      <dc:creator>MrCheesecake</dc:creator>
      <dc:date>2023-09-06T21:10:37Z</dc:date>
    </item>
  </channel>
</rss>

