<?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>Beebes Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>Beebes Tracker</description>
    <pubDate>Sat, 25 Nov 2023 07:46:00 GMT</pubDate>
    <dc:date>2023-11-25T07:46:00Z</dc:date>
    <item>
      <title>Re: Default printer issues with Zero Clients after DEM Agent upgrade from 9.10 to 2209:</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Default-printer-issues-with-Zero-Clients-after-DEM-Agent-upgrade/m-p/2958999#M7976</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/3228914"&gt;@DEMdev&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I installed 2209 and I pointed to a new Share and ran Easy Start. I see that Network printers are disabled and created a new config for Default Printer&lt;/P&gt;&lt;P&gt;#&lt;BR /&gt;# Expanded settings for Windows Common Setting 'Default printer':&lt;BR /&gt;#&lt;BR /&gt;[SpecialSettings]&lt;BR /&gt;DefaultPrinter&lt;/P&gt;&lt;P&gt;[IncludeIndividualRegistryValues]&lt;BR /&gt;HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows\UserSelectedDefault\[SKIPLOGGING]&lt;/P&gt;&lt;P&gt;Is this the new settings you were referencing?&amp;nbsp;&lt;/P&gt;&lt;P&gt;If so, is this all we need to make it work like it used too where if the user logged into a Zero Client it would save their default printer and if they logged into the Horizon Client it would redirect their local printer?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Mar 2023 20:16:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Default-printer-issues-with-Zero-Clients-after-DEM-Agent-upgrade/m-p/2958999#M7976</guid>
      <dc:creator>Beebes</dc:creator>
      <dc:date>2023-03-13T20:16:46Z</dc:date>
    </item>
    <item>
      <title>Re: Default printer issues with Zero Clients after DEM Agent upgrade from 9.10 to 2209:</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Default-printer-issues-with-Zero-Clients-after-DEM-Agent-upgrade/m-p/2958946#M7975</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/3228914"&gt;@DEMdev&lt;/a&gt;&lt;/P&gt;&lt;P&gt;I agree that our settings were probably expanded. How do I get a copy of the new settings?&lt;/P&gt;&lt;P&gt;Is there a way to change settings back that were expanded so we get notified?&lt;/P&gt;&lt;P&gt;It would great if we could run a check to make sure we have the latest config settings or at least be able to download and compare them.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Mar 2023 13:42:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Default-printer-issues-with-Zero-Clients-after-DEM-Agent-upgrade/m-p/2958946#M7975</guid>
      <dc:creator>Beebes</dc:creator>
      <dc:date>2023-03-13T13:42:30Z</dc:date>
    </item>
    <item>
      <title>Re: Default printer issues with Zero Clients after DEM Agent upgrade from 9.10 to 2209:</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Default-printer-issues-with-Zero-Clients-after-DEM-Agent-upgrade/m-p/2958582#M7967</link>
      <description>&lt;P&gt;Hello &lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/3228914"&gt;@DEMdev&lt;/a&gt;&lt;/P&gt;&lt;P&gt;At one stage we were able to download Config's but that was deprecated.&lt;/P&gt;&lt;P&gt;Where should I go to get the latest DEM configs?&lt;/P&gt;&lt;P&gt;In regards to your suggestion to move&amp;nbsp;&lt;FONT face="courier new,courier"&gt;.\&lt;/FONT&gt;&lt;SPAN&gt;&lt;FONT face="courier new,courier"&gt;Applets\Regedit&lt;/FONT&gt;&amp;nbsp;settings to their own config file is this bascially splitting up Reg settings and Folder settings into separate DEM Configs? If so, is there a reason to do this?&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks for your help!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Mar 2023 20:10:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Default-printer-issues-with-Zero-Clients-after-DEM-Agent-upgrade/m-p/2958582#M7967</guid>
      <dc:creator>Beebes</dc:creator>
      <dc:date>2023-03-09T20:10:21Z</dc:date>
    </item>
    <item>
      <title>Re: Default printer issues with Zero Clients after DEM Agent upgrade from 9.10 to 2209:</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Default-printer-issues-with-Zero-Clients-after-DEM-Agent-upgrade/m-p/2958178#M7959</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sorry for the delayed response. The email notification was quarantined.&lt;/P&gt;&lt;P&gt;This is our Network Printers config.&lt;/P&gt;&lt;P&gt;#&lt;BR /&gt;[IncludeRegistryTrees]&lt;BR /&gt;HKCU\Printers&lt;BR /&gt;HKCU\Software\Microsoft\Windows NT\CurrentVersion\Devices&lt;BR /&gt;HKCU\Software\Microsoft\Windows NT\CurrentVersion\PrinterPorts&lt;BR /&gt;HKCU\Software\Microsoft\Windows\CurrentVersion\Applets\Regedit&lt;/P&gt;&lt;P&gt;[IncludeIndividualRegistryValues]&lt;BR /&gt;HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows\Device&lt;BR /&gt;HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows\UserSelectedDefault&lt;/P&gt;&lt;P&gt;I will try and get the logs in the next day or so.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your help!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Mar 2023 18:35:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Default-printer-issues-with-Zero-Clients-after-DEM-Agent-upgrade/m-p/2958178#M7959</guid>
      <dc:creator>Beebes</dc:creator>
      <dc:date>2023-03-07T18:35:44Z</dc:date>
    </item>
    <item>
      <title>Default printer issues with Zero Clients after DEM Agent upgrade from 9.10 to 2209:</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Default-printer-issues-with-Zero-Clients-after-DEM-Agent-upgrade/m-p/2954485#M7938</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;Environment&lt;/P&gt;&lt;P&gt;DEM 9.10&lt;/P&gt;&lt;P&gt;Horizon 2111 with Windows 10, 1809&lt;/P&gt;&lt;P&gt;Mixture of Horizon Clients and Zero Client (PCOIP and Blast)&lt;/P&gt;&lt;P&gt;With the 9.10 DEM Agent if a user logs in with a Zero Client, the default printer is set to a printer that they set. Normally this is a network printer at the office.&lt;/P&gt;&lt;P&gt;If they login with the Horizon Client on a Windows desktop that has a locally attached printer, it will set the locally attached printer as default.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Upgrade to DEM Agent only 2209&lt;/P&gt;&lt;P&gt;Login with Zero Client's don't save default printer. If I log back into to a Pool with 9.10 agent it does.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I understand that the new 2209 DEM agent made some modifications to VIP and how it works. What I would like to do is make it work like it did before.&lt;/P&gt;&lt;P&gt;Is the only solution to use this workaround?&amp;nbsp;&lt;A href="https://kb.vmware.com/s/article/78496" target="_blank"&gt;DEM Printer default / Network Mapped default printer conflicts with VMware Integrated Printing Feature (78496)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;My goal is to have users default printer captured and set when connected using Zero Clients and redirected to a locally attached printer when connected using the Horizon Client on a Windows Desktop.&lt;/P&gt;&lt;P&gt;TIA&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Feb 2023 20:57:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Default-printer-issues-with-Zero-Clients-after-DEM-Agent-upgrade/m-p/2954485#M7938</guid>
      <dc:creator>Beebes</dc:creator>
      <dc:date>2023-02-14T20:57:31Z</dc:date>
    </item>
    <item>
      <title>Re: Edge Update on Windows 10</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Edge-Update-on-Windows-10/m-p/2949408#M7909</link>
      <description>&lt;P&gt;I found my answer.&lt;/P&gt;&lt;P&gt;The Optimization tool changes the registry to disable Edge Updates. I removed the following Registry Key and reopened Edge and it updated.&lt;/P&gt;&lt;P&gt;HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\EdgeUpdate&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jan 2023 18:33:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Edge-Update-on-Windows-10/m-p/2949408#M7909</guid>
      <dc:creator>Beebes</dc:creator>
      <dc:date>2023-01-18T18:33:08Z</dc:date>
    </item>
    <item>
      <title>Edge Update on Windows 10</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Edge-Update-on-Windows-10/m-p/2949225#M7906</link>
      <description>&lt;P&gt;I'm updating our Windows 10 Gold Images and normally I will download the latest offline installer and run it. I do this because I receive the message that "Edge updates are managed by our organization". We didn't setup any policies, but I believe the Optimization Tool has set this in the registry.&lt;/P&gt;&lt;P&gt;I've done this before routine before to update Edge, but this time I receive an error.&lt;/P&gt;&lt;P&gt;There is a problem with this installer package. A program run as part of the setup didn't finish as expected. Contact your support personal or package vendor.&lt;/P&gt;&lt;P&gt;In Apps, I don't see Microsoft Edge anymore. I do see Microsoft Edge Update.&lt;/P&gt;&lt;P&gt;Edge is still available and it's updated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone else experienced this issue?&lt;/P&gt;&lt;P&gt;Any suggestions to update Edge where it actually doesn't fail and Microsoft Edge remains in the Apps program list?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Jeff&lt;/P&gt;</description>
      <pubDate>Tue, 17 Jan 2023 21:37:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Edge-Update-on-Windows-10/m-p/2949225#M7906</guid>
      <dc:creator>Beebes</dc:creator>
      <dc:date>2023-01-17T21:37:57Z</dc:date>
    </item>
    <item>
      <title>Office Shared Settings large with many files</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Office-Shared-Settings-large-with-many-files/m-p/2944959#M7881</link>
      <description>&lt;P&gt;Good Day!&lt;/P&gt;&lt;P&gt;Below are the settings that capture folder in Office Shared Settings. These settings are basically the default from when I set UEM up 3 years ago.&lt;/P&gt;&lt;P&gt;Some users have over 250 MB (almost 600 uncompressed) shared settings.zip with over 13K of files and it slows DEM processing down by 30 or more seconds.&lt;/P&gt;&lt;P&gt;I found that the Wef folder is the folder with the largest size and number of files.&amp;nbsp;&lt;/P&gt;&lt;P&gt;\ProfileArchives\Microsoft Office 2016\Shared Settings\LocalAppData\Microsoft\Office\16.0\Wef&lt;/P&gt;&lt;P&gt;[IncludeFolderTrees]&lt;BR /&gt;&amp;lt;AppData&amp;gt;\Microsoft\AddIns&lt;BR /&gt;&amp;lt;AppData&amp;gt;\Microsoft\Bibliography&lt;BR /&gt;&amp;lt;AppData&amp;gt;\Microsoft\Office&lt;BR /&gt;&amp;lt;AppData&amp;gt;\Microsoft\Proof&lt;BR /&gt;&amp;lt;AppData&amp;gt;\Microsoft\Spelling&lt;BR /&gt;&amp;lt;AppData&amp;gt;\Microsoft\Templates&lt;BR /&gt;&amp;lt;AppData&amp;gt;\Microsoft\UProof&lt;BR /&gt;&amp;lt;LocalAppData&amp;gt;\Microsoft\Office\ONetConfig&lt;BR /&gt;&amp;lt;LocalAppData&amp;gt;\Microsoft\Office\16.0\Licensing&lt;BR /&gt;&amp;lt;LocalAppData&amp;gt;\Microsoft\Office\&lt;BR /&gt;&amp;lt;AppData&amp;gt;\Microsoft\Crypto&lt;BR /&gt;&amp;lt;AppData&amp;gt;\Microsoft\Protect&lt;BR /&gt;&amp;lt;AppData&amp;gt;\Microsoft\Credentials&lt;BR /&gt;&amp;lt;LocalAppData&amp;gt;\Microsoft\IdentityCache&lt;BR /&gt;&amp;lt;LocalAppData&amp;gt;\Microsoft\OneAuth&lt;BR /&gt;&amp;lt;LocalAppData&amp;gt;\Microsoft\TokenBroker&lt;BR /&gt;&amp;lt;LocalAppData&amp;gt;\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\AC&lt;BR /&gt;&amp;lt;LocalAppData&amp;gt;\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;[ExcludeFolderTrees]&lt;BR /&gt;&amp;lt;AppData&amp;gt;\Microsoft\Templates\LiveContent&lt;BR /&gt;&amp;lt;LocalAppData&amp;gt;\Microsoft\Office\16.0\OfficeFileCache&lt;/P&gt;&lt;P&gt;Does anyone know what this folder is actually capturing and if we exclude it, what is the user experience?&lt;/P&gt;&lt;P&gt;Is there an updated Office Template that we should apply?&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;P&gt;Jeff&lt;/P&gt;</description>
      <pubDate>Wed, 21 Dec 2022 19:51:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Office-Shared-Settings-large-with-many-files/m-p/2944959#M7881</guid>
      <dc:creator>Beebes</dc:creator>
      <dc:date>2022-12-21T19:51:11Z</dc:date>
    </item>
    <item>
      <title>Upgrade DEM</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Upgrade-DEM/m-p/2943927#M7869</link>
      <description>&lt;P&gt;Good Day!&lt;/P&gt;&lt;P&gt;We are currently using DEM 9.10 and I would like to upgrade to 2209 and I have some questions.&lt;/P&gt;&lt;P&gt;1, Am I able to upgrade from 9.10 to 2209 or do I have to upgrade to previous versions first? I believe I should be able to go to the latest version.&lt;/P&gt;&lt;P&gt;2, I assume that I just upgrade the Management console by running the install. Is there any further configuration required or does it just maintain the previous settings?&lt;/P&gt;&lt;P&gt;3, I believe I can update the the ADMX files by replacing them in the Central Store and they will retain the previous configs. Is this correct?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Dec 2022 17:24:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Upgrade-DEM/m-p/2943927#M7869</guid>
      <dc:creator>Beebes</dc:creator>
      <dc:date>2022-12-14T17:24:32Z</dc:date>
    </item>
    <item>
      <title>Re: Modern Auth for O365</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Modern-Auth-for-O365/m-p/2921895#M7746</link>
      <description>&lt;P&gt;No we don't. Are you saying we need to implement a hybrid solution?&lt;/P&gt;&lt;P&gt;Do you have any further information that explains the proper setup?&lt;/P&gt;</description>
      <pubDate>Tue, 02 Aug 2022 14:30:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Modern-Auth-for-O365/m-p/2921895#M7746</guid>
      <dc:creator>Beebes</dc:creator>
      <dc:date>2022-08-02T14:30:01Z</dc:date>
    </item>
    <item>
      <title>Modern Auth for O365</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Modern-Auth-for-O365/m-p/2920396#M7727</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;We have been using DEM ver 9.10 to capture O365 settings and it has been working great. User passwords were saved and they weren't prompted unless the password was changed.&lt;/P&gt;&lt;P&gt;We enabled Modern Auth on our O365 Tenant and now users are constantly prompted for their passwords when opening outlook. My guess is that our current DEM config isn't capturing the new modern auth and saving it.&lt;/P&gt;&lt;P&gt;Has anyone experienced this issue and solved it? Any help would be appreciated.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jul 2022 16:21:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Modern-Auth-for-O365/m-p/2920396#M7727</guid>
      <dc:creator>Beebes</dc:creator>
      <dc:date>2022-07-25T16:21:53Z</dc:date>
    </item>
    <item>
      <title>Community Config Template Downloads</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Community-Config-Template-Downloads/m-p/2920394#M7726</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;We used to be able to download config templates from VMware Marketplace using DEM. Now we get an error of 403 and it seems this has been decommissioned. Does anyone know if there is a replacement for these templates?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jul 2022 16:17:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Community-Config-Template-Downloads/m-p/2920394#M7726</guid>
      <dc:creator>Beebes</dc:creator>
      <dc:date>2022-07-25T16:17:34Z</dc:date>
    </item>
    <item>
      <title>Re: o365 credentials not being saved. DEM horizon 7.13, non-persistent instant clones</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/o365-credentials-not-being-saved-DEM-horizon-7-13-non-persistent/m-p/2912909#M7667</link>
      <description>&lt;P&gt;I turned on Modern Auth in the options for 0365 and my experience was that the passwords weren't saved by DEM. Before enabling Modern Auth (and after disabling it) Outlook (mailbox) passwords were saved by DEM. I'm thinking that the Modern Auth password is being saved into another location that DEM is capturing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Jun 2022 19:15:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/o365-credentials-not-being-saved-DEM-horizon-7-13-non-persistent/m-p/2912909#M7667</guid>
      <dc:creator>Beebes</dc:creator>
      <dc:date>2022-06-06T19:15:58Z</dc:date>
    </item>
    <item>
      <title>Registry comparison tool</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Registry-comparison-tool/m-p/2847530#M6969</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;Does anyone use a registry comparison tool to compare before and after registry changes to help profile software and windows settings? If so, does anyone have any suggestions for a good easy tool?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 17 May 2021 15:36:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Registry-comparison-tool/m-p/2847530#M6969</guid>
      <dc:creator>Beebes</dc:creator>
      <dc:date>2021-05-17T15:36:55Z</dc:date>
    </item>
    <item>
      <title>Windows 10 "Ease of Access" capturing settings</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Windows-10-quot-Ease-of-Access-quot-capturing-settings/m-p/2847529#M6968</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I need to capture the Windows 10 "Ease of Access" settings. In particular, I need to capture the setting&amp;nbsp; "Make text Bigger" where you can adjust the text size and make it larger.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've created a new config capturing the following. It partially works. When a user logs off and logs back on, the setting seems to be captured but not for all fonts. IE when I check the setting after log off and log on, it's applied, but any Windows menu's are back to default while they should be larger as well.&amp;nbsp;&lt;/P&gt;&lt;P&gt;[IncludeRegistryTrees]&lt;BR /&gt;HKCU\Software\Microsoft\Accessibility&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone have any suggestions?&lt;/P&gt;</description>
      <pubDate>Mon, 17 May 2021 15:34:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Windows-10-quot-Ease-of-Access-quot-capturing-settings/m-p/2847529#M6968</guid>
      <dc:creator>Beebes</dc:creator>
      <dc:date>2021-05-17T15:34:55Z</dc:date>
    </item>
  </channel>
</rss>

