<?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>pchapman Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>pchapman Tracker</description>
    <pubDate>Sat, 25 Nov 2023 07:22:33 GMT</pubDate>
    <dc:date>2023-11-25T07:22:33Z</dc:date>
    <item>
      <title>Re: Visual Studio - what actually works ?</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-what-actually-works/m-p/2811327#M8240</link>
      <description>&lt;P&gt;I'm going through this nightmare right now.&lt;/P&gt;&lt;P&gt;Adding to base image isn't an option for us due to the small# of users and the amount of effort involved. &amp;nbsp;Originally I was hoping to have it working as an AppStack and manage the custom settings with DEM. &amp;nbsp;This worked with the first installer I was provided and somehow was licensing OK - as in no steps were required to license is on the machines the AppStacks was deployed to. &amp;nbsp;The team that provides me the installer updated it a few months ago and the license key stopped working, the floating desktops were coming up with that pre-release unlicensed software error. &amp;nbsp;I was unable to get the license to activate automatically using the ddconfigca/storepid commands as either part of app volumes startup.bat or as an elevated app / post-import task with DEM (although they did work if you manually ran them from the command line, but this wasn't an option, I suspect this is related to UAC)&lt;/P&gt;&lt;P&gt;I wanted to avoid writable volumes, as they don't fit into our multiple datacenter design, but I did manage to get VS 2019 Pro to work correctly with a writable volume (custom 50gb UIA only template) along with DEM to manage the user settings. &amp;nbsp;In theory the writable volume shouldn't bloat or degrade over time since the users don't have admin rights, they were only granted during the install of VS 2019. &amp;nbsp;It looks like the writable volume is the supported method from VMware.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/2149369" target="_blank"&gt;2149369&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Nov 2020 13:12:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-what-actually-works/m-p/2811327#M8240</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2020-11-20T13:12:14Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Studio 2017 in App Volumes - Capture Licensing?</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Visual-Studio-2017-in-App-Volumes-Capture-Licensing/m-p/2810678#M6446</link>
      <description>&lt;P&gt;Sadly adding those lines to the startup.bat doesn't seem to work for my VS 2019 Pro. &amp;nbsp;The strange thing is, if I right click the file and run as administrator after logging into the VM, it does license it successfully..&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Nov 2020 16:27:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Visual-Studio-2017-in-App-Volumes-Capture-Licensing/m-p/2810678#M6446</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2020-11-18T16:27:16Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Studio 2019 - Cannot check for updated license</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/2810636#M8234</link>
      <description>&lt;P&gt;Is there anything else beyond running this script and adding those two items to privilege elevation you had to do to get this working?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I added privilege elevation for the two tasks, put the contents of your script in a file and set it to run as a post-import task. &amp;nbsp;The log file is created showing the ddconfigca.exe running and the error level 0 from storepid.exe, but when I launch VS2019 pro it says pre-release software etc. &amp;nbsp;If I run the commands manually from an admin command prompt they work as expect. &amp;nbsp;I'm stumped.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Nov 2020 14:27:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/2810636#M8234</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2020-11-18T14:27:53Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Studio 2017 in App Volumes - Capture Licensing?</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Visual-Studio-2017-in-App-Volumes-Capture-Licensing/m-p/1831948#M3764</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've found this document which states the only supported scenarios for deploying VS with App Volumes is to use writables (yuck!)&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/2149369" title="https://kb.vmware.com/s/article/2149369"&gt;VMware Knowledge Base&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm working on this myself for 2019.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I first tried this method:&lt;/P&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/thread/565635"&gt;Visual Studio 2015 in standard appstack&lt;/A&gt;&amp;nbsp; however these commands resulted in unlicensed visual studio (not sure why...)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And then I tried just capturing without using those commands, and somehow it's magically licensed at every login.&amp;nbsp; I need to talk to the person who built the offline installer to see if they somehow baked the license key into the installer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good luck, I'll update if I figure out what's goin on in my environment. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Jun 2020 17:30:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Visual-Studio-2017-in-App-Volumes-Capture-Licensing/m-p/1831948#M3764</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2020-06-18T17:30:18Z</dc:date>
    </item>
    <item>
      <title>Re: App Volumes Invalid Session Cookie</title>
      <link>https://communities.vmware.com/t5/App-Volumes/App-Volumes-Invalid-Session-Cookie/m-p/501766#M3305</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Vmware didn’t mention the implications of configuring the setting.&amp;nbsp; i would suggest opening a support ticket and asking.&amp;nbsp; It’s interesting that you didn’t see the issue before 2.16 though. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Apr 2019 13:43:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/App-Volumes-Invalid-Session-Cookie/m-p/501766#M3305</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2019-04-30T13:43:35Z</dc:date>
    </item>
    <item>
      <title>Re: App Volumes Invalid Session Cookie</title>
      <link>https://communities.vmware.com/t5/App-Volumes/App-Volumes-Invalid-Session-Cookie/m-p/501764#M3303</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif;"&gt;I can confirm that this fixed the issue (&lt;STRONG style="font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;disable_agent_session_cookie = 1 in the database)&lt;/STRONG&gt;, I opened a support case and they provided the instructions.&amp;nbsp; They said it is due to using Instant Clones with vGPU, since there is an extra reboot involved in that specific use case, it throws off App Volumes manager.&amp;nbsp; It's too bad this isn't documented in the KB anywhere, since I imagine it's a fairly common scenario.&amp;nbsp; Still applies to 2.16...&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Apr 2019 11:25:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/App-Volumes-Invalid-Session-Cookie/m-p/501764#M3303</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2019-04-30T11:25:17Z</dc:date>
    </item>
    <item>
      <title>Re: Capture Cisco Webex Meetings Desktop App</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Capture-Cisco-Webex-Meetings-Desktop-App/m-p/2254991#M4885</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I spent countless hours trying to get this to work about a year ago.&amp;nbsp; I tried everything imaginable, and eventually gave up.&amp;nbsp; It seems to hash the users credentials in a unique way that can not be roamed between different computers.&amp;nbsp; I'd love to hear if anyone has figured it out.&amp;nbsp; At this moment, requiring use of the Webex Meetings Plugin either requires the user to login every time or requires dedicated desktops.&amp;nbsp; This is especially difficult for people who rely on the outlook plugin.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Mar 2019 18:11:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Capture-Cisco-Webex-Meetings-Desktop-App/m-p/2254991#M4885</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2019-03-28T18:11:37Z</dc:date>
    </item>
    <item>
      <title>Re: Edge not showing for new users</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Edge-not-showing-for-new-users/m-p/488569#M690</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm running into a similar issue, but Edge won't even launch for anyone other than the local administrator (if you go to c:\Windows\SystemApps\Microsoft.MicrosoftEdge....\MicrosoftEdge.exe and click it, the cursor disappears and nothing else happens)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;odd part is it's only happening in their environment,, I have the same image built in my lab and it works fine.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Mar 2019 19:34:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Edge-not-showing-for-new-users/m-p/488569#M690</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2019-03-15T19:34:17Z</dc:date>
    </item>
    <item>
      <title>Re: Mandatory User Profile / Start Menu Tiles</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Mandatory-User-Profile-Start-Menu-Tiles/m-p/473872#M419</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'll have to try that but I think it will have the same result as my method of using the ping, it seems that UEM just shoots the command off and immediately moves on without waiting for it to finish.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2019 02:35:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Mandatory-User-Profile-Start-Menu-Tiles/m-p/473872#M419</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2019-03-01T02:35:21Z</dc:date>
    </item>
    <item>
      <title>Re: BSOD when provisioning with AppVolumes agent 2.15</title>
      <link>https://communities.vmware.com/t5/App-Volumes/BSOD-when-provisioning-with-AppVolumes-agent-2-15/m-p/1869309#M6293</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks! I'm deploying 2.15 with 1809 for a customer, and of course all of my test appstacks worked perfect yesterday.&amp;nbsp; Today, during the training session, they failed every single time with a BSOD.&amp;nbsp; Quite embarrassing, especially considering the other 2.15 bug regarding the problem with MSI's and the Windows patch.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2019 00:30:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/BSOD-when-provisioning-with-AppVolumes-agent-2-15/m-p/1869309#M6293</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2019-03-01T00:30:39Z</dc:date>
    </item>
    <item>
      <title>Re: Mandatory User Profile / Start Menu Tiles</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Mandatory-User-Profile-Start-Menu-Tiles/m-p/473870#M417</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, I tried this and am having mixed success.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I did need to add some quotes to get it to run properly, as shown below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif;"&gt;C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -Command "get-service WpnUserService_* | Stop-Service -force"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif;"&gt;It works sometimes, but it seems that the start menu export happens to quickly after.&amp;nbsp; Is there any way to put a pause inbetween?&amp;nbsp; I tried the following command, but it seems that UEM does not wait for it to finish:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif;"&gt;C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -Command "get-service WpnUserService_* | Stop-Service -force" &amp;amp;&amp;amp; ping localhost -n 5&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Feb 2019 15:17:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Mandatory-User-Profile-Start-Menu-Tiles/m-p/473870#M417</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2019-02-28T15:17:07Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Appstack</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Custom-Appstack/m-p/2229417#M6347</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If anyone else sees this beware of following the VMware techzone article on building a Windows 10 image.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The dism /resetbase command makes it impossible to uninstall the updates and you have to build the entire thing from scratch.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P class="x-hidden-focus alert-title" style="font-weight: 600; color: var(--warning-dark); font-family: 'Segoe UI', SegoeUI, 'Segoe WP', 'Helvetica Neue', Helvetica, Tahoma, Arial, sans-serif; font-size: 16px;"&gt;&lt;SPAN class="docon docon-status-warning-outline" style="font-family: docons; font-size: inherit; font-weight: 400; text-align: center;"&gt;&lt;/SPAN&gt; Warning&lt;/P&gt;&lt;P class="x-hidden-focus" style="margin-top: 1rem; color: #000000; font-family: 'Segoe UI', SegoeUI, 'Segoe WP', 'Helvetica Neue', Helvetica, Tahoma, Arial, sans-serif; font-size: 16px;"&gt;All existing service packs and updates cannot be uninstalled after this command is completed. This will not block the uninstallation of future service packs or updates.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Feb 2019 17:45:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Custom-Appstack/m-p/2229417#M6347</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2019-02-27T17:45:05Z</dc:date>
    </item>
    <item>
      <title>Re: Custom Appstack</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Custom-Appstack/m-p/2229415#M6345</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am running into the same issue today with an 1809 image I built yesterday.&amp;nbsp; We followed the VMware Windows 10 optimized image guide and it will not let me uninstall the KB.&amp;nbsp; Currently working on creating a new image and disabling Windows update from the start.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Feb 2019 15:37:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Custom-Appstack/m-p/2229415#M6345</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2019-02-27T15:37:02Z</dc:date>
    </item>
    <item>
      <title>Re: UEM Horizon Smart Policies.</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/UEM-Horizon-Smart-Policies/m-p/491058#M708</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A default installation of the view agent does not enable the USB redirection feature.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you did manually enable the USB redirection feature, and don't put any other policies in place, users will be able to connect any USB devices to their VM (assuming all of the correct firewall rules are in place, etc)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Jan 2019 22:00:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/UEM-Horizon-Smart-Policies/m-p/491058#M708</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2019-01-29T22:00:21Z</dc:date>
    </item>
    <item>
      <title>Re: Mandatory User Profile / Start Menu Tiles</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Mandatory-User-Profile-Start-Menu-Tiles/m-p/473859#M406</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I posted in the other thread as well, but I am seeing the same issue with 1803.&amp;nbsp; Wondering if anyone has a fix?&amp;nbsp; It works perfectly without the mandatory profile but as you all know you really need a mandatory profile for Windows 10 otherwise logon times are rough.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Dec 2018 16:04:03 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Mandatory-User-Profile-Start-Menu-Tiles/m-p/473859#M406</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2018-12-05T16:04:03Z</dc:date>
    </item>
    <item>
      <title>Re: Mandatory Profile Trumps UEM Start Menu persistence?</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Mandatory-Profile-Trumps-UEM-Start-Menu-persistence/m-p/2750861#M6144</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am curious if there has been any progress or suggestions for this with 1803?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have UEM working well for persisting the start menu without mandatory profile.&amp;nbsp; (and even using UEM built in "default settings" for a standardized start menu on first logon!)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mandatory profiles are a requirement due to the fact that logon of Win 10 is simply too slow without them.&amp;nbsp; The UEM Start menu config does not work and I am getting the same results as the original poster (only edge icon)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Dec 2018 16:02:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Mandatory-Profile-Trumps-UEM-Start-Menu-persistence/m-p/2750861#M6144</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2018-12-05T16:02:35Z</dc:date>
    </item>
    <item>
      <title>Re: VMware View Webcam Support</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/VMware-View-Webcam-Support/m-p/853999#M19540</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As mentioned years ago in this thread, RTAV (Real Time audio video) support from Windows/Linux/OSX Horizon clients will support webcams properly.&amp;nbsp; It is still there in the latest Horizon versions.&amp;nbsp; I don't ever see the RTAV functionality coming to Teradici zero clients.&amp;nbsp; I'd suggest looking at a different type of client if it's a requirement of yours.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Nov 2018 12:48:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/VMware-View-Webcam-Support/m-p/853999#M19540</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2018-11-20T12:48:30Z</dc:date>
    </item>
    <item>
      <title>Re: Insane login times - Win10 LTSB</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Insane-login-times-Win10-LTSB/m-p/497847#M11637</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I agree that those steps will help get a great golden image, however 5-7 minute+ logon times would indicate some other issues going on in the environment for sure.&amp;nbsp; even a completely unoptimized image with vmware tools + view agent installed on it won't take anywhere near that amount of time to login.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Oct 2018 12:57:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Insane-login-times-Win10-LTSB/m-p/497847#M11637</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2018-10-05T12:57:44Z</dc:date>
    </item>
    <item>
      <title>Re: Insane login times - Win10 LTSB</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Insane-login-times-Win10-LTSB/m-p/497845#M11635</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please check the VMware Logon monitor log files on one of the suspect VM's, and at the bottom it will give you a summary of what was taking a long time during logon.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #545454; font-family: Roboto, arial, sans-serif; font-size: small;"&gt;C:\ProgramData\&lt;/SPAN&gt;&lt;SPAN style="font-weight: bold; color: #6a6a6a; font-family: Roboto, arial, sans-serif; font-size: small;"&gt;VMware&lt;/SPAN&gt;&lt;SPAN style="color: #545454; font-family: Roboto, arial, sans-serif; font-size: small;"&gt;\&lt;/SPAN&gt;&lt;SPAN style="font-weight: bold; color: #6a6a6a; font-family: Roboto, arial, sans-serif; font-size: small;"&gt;VMware Logon Monitor&lt;/SPAN&gt;&lt;SPAN style="color: #545454; font-family: Roboto, arial, sans-serif; font-size: small;"&gt;\&lt;/SPAN&gt;&lt;SPAN style="font-weight: bold; color: #6a6a6a; font-family: Roboto, arial, sans-serif; font-size: small;"&gt;Logs&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I just built a Win 10 LTSB environment for a customer a few months back and they have excellent logon times, at about 10-15 seconds.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Oct 2018 18:30:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Insane-login-times-Win10-LTSB/m-p/497845#M11635</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2018-10-04T18:30:15Z</dc:date>
    </item>
    <item>
      <title>Re: Oracle web logic server issues in appatack</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Oracle-web-logic-server-issues-in-appatack/m-p/1401630#M3914</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You may need to manually create shortcuts on the all user start menu or desktop for some apps. (Or even better use UEM to do it) This happens often if the app installer puts shortcuts into the user profiles which appvolumes does not capture.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Sep 2018 20:52:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Oracle-web-logic-server-issues-in-appatack/m-p/1401630#M3914</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2018-09-26T20:52:14Z</dc:date>
    </item>
  </channel>
</rss>

