<?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>Markansas Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>Markansas Tracker</description>
    <pubDate>Sat, 25 Nov 2023 06:13:19 GMT</pubDate>
    <dc:date>2023-11-25T06:13:19Z</dc:date>
    <item>
      <title>Re: Acceptable Horizon Desktop Logon Time?</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Acceptable-Horizon-Desktop-Logon-Time/m-p/2224673#M4375</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ohhh... wow. This shaved a couple seconds off the desktop appearance! That's when our bosses stop the timer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I set the value to 2, and our generic Win10 images (LTSB 1607 / Office 365 / browsers) is now at 6-7 seconds! &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is nice, thank you &lt;B&gt;JohnTwilley&lt;/B&gt;​ !!&lt;/P&gt;&lt;P&gt;-Markansas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Aug 2017 14:09:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Acceptable-Horizon-Desktop-Logon-Time/m-p/2224673#M4375</guid>
      <dc:creator>Markansas</dc:creator>
      <dc:date>2017-08-22T14:09:25Z</dc:date>
    </item>
    <item>
      <title>Re: Acceptable Horizon Desktop Logon Time?</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Acceptable-Horizon-Desktop-Logon-Time/m-p/2224671#M4373</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are currently getting the following logon times for different desktop configurations:&lt;/P&gt;&lt;P&gt;- Windows 10 LTSB 1607 (non-GPU accelerated): 10-11 seconds&lt;/P&gt;&lt;P&gt;- Windows 10 LTSB 1607 (nVidia M10 GPU accererated): 14-16 seconds&lt;/P&gt;&lt;P&gt;- Windows 10 LTSB 1607 (nVidia M10 GPU accererated) with full application suite (Adobe CC, Office, Statistics, etc): 26-28 seconds&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our environment is similar to yours (Horizon 7.2; UEM 9.2; App Volumes 2.12). GPU drivers have some per-user setup that adds a few seconds no matter what, but we feel this is as good as it is going to get.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We've done the following to achieve this logon time:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Use W10 LTSB - much of the W10 fluff is stripped out&lt;/LI&gt;&lt;LI&gt;VMware OSOT &lt;/LI&gt;&lt;LI&gt;Disable as much user experience stuff as you can via Group Policy.&lt;/LI&gt;&lt;LI&gt;Disable OneDrive and Defender (local group policy is the only way for OneDrive)&lt;/LI&gt;&lt;LI&gt;Disable as many scheduled tasks as possible (there are tons and tons set to "at user logon")&lt;/LI&gt;&lt;LI&gt;Use QuickPrep or Instant Clones&lt;/LI&gt;&lt;LI&gt;Disable scanner redirection and unneeded Horizon client features.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Aug 2017 15:34:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Acceptable-Horizon-Desktop-Logon-Time/m-p/2224671#M4373</guid>
      <dc:creator>Markansas</dc:creator>
      <dc:date>2017-08-21T15:34:05Z</dc:date>
    </item>
    <item>
      <title>Re: Windows 10 slow login</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Windows-10-slow-login/m-p/2703604#M73174</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here's something I've noticed recently - the Windows 10 Start Menu is hosed, exhibiting the same thing you mention, you can see the icons, but they are unclickable. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Turns out that for us, UEM is the culprit. I was able to solve this by DISABLING the Windows Explorer setting in UEM. Yes: UEM default config is somehow gakking Windows 10 start menu - by default. So, by default, I now pretty much disable most of the user environment stuff in UEM and stick to ADMX template method of customizations.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 25 Feb 2017 03:14:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Windows-10-slow-login/m-p/2703604#M73174</guid>
      <dc:creator>Markansas</dc:creator>
      <dc:date>2017-02-25T03:14:10Z</dc:date>
    </item>
    <item>
      <title>Re: Windows 10 slow login</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Windows-10-slow-login/m-p/2703599#M73169</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Couple things on this. We've been tinkering with it for a couple months now, and have non persistent Windows 10 logins down to about 16 seconds as a baseline, which grows to around 24-27 when using GPU (Tesla M10), UEM 9.1 clients, and AppVolumes 2.12 agent in the base image. Here are a few things we've found that made a difference:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Use group policy (local or AD central store) to disable OneDrive, Windows Defender, etc, the "consumer experience" and other Windows 10 bloat (such as the initial sign on message "We're glad you're here. You won't be leaving for 1:10 at least.") All the registry hacking in the world wont fix those things reliably, but group policy will.&lt;/LI&gt;&lt;LI&gt;Use the Windows 10 1607 LTSB and Horizon 7.0.3 - the 1607 version has fundamentally different Start Menu workings than the older 2015 releases. 7.0.3 officially supports that release. Use Export-StartLayout to put the start menu somewhere locally, then use local group policy to reference that .xml file. Seems to work flawlessly, unlike every single other method.&lt;/LI&gt;&lt;LI&gt;When using the OS optimization tool, go to Public Templates, find the win10 beta one. &lt;STRONG&gt;Click update.&lt;/STRONG&gt; Some settings have been updated for 1607 and newer Windows releases. Now run it, but leave some things 'un-optimized'. Leave unchecked at least "Device Setup", "Windows Search", "Windows Firewall", and "Windows Themes". Believe it or not we have seen that surgically disabling the firewall causes start menu problems (HUH? I know right?). Anything that you can turn off via group policy or configuration manager packages in Windows 10, &lt;EM&gt;use that method instead of registry hacks or OSOT.&lt;/EM&gt;&lt;/LI&gt;&lt;LI&gt;Use QuickPrep. There is almost never a need to generate a new SID for these machines. Sysprep and a new SID caused an almost exactly 60 second increase when logging in with AD user accounts. &lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These are our findings, your mileage may vary. Windows 10 is an incredibly frustrating experience with respect to VDI.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Jan 2017 17:42:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Windows-10-slow-login/m-p/2703599#M73169</guid>
      <dc:creator>Markansas</dc:creator>
      <dc:date>2017-01-26T17:42:59Z</dc:date>
    </item>
    <item>
      <title>Re: Windows 10 slow login</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Windows-10-slow-login/m-p/2703589#M73159</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We experienced similar times with Win10 1607. Always 1:00+, no matter what. Test machines had quick initial logons (15-20 secs), but a pool extended it to over the 1 minute mark. We switched to QuickPrep method of linked clone pools, and it brought the time down to around 20-30 seconds.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 14 Jan 2017 18:09:13 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Windows-10-slow-login/m-p/2703589#M73159</guid>
      <dc:creator>Markansas</dc:creator>
      <dc:date>2017-01-14T18:09:13Z</dc:date>
    </item>
  </channel>
</rss>

