<?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>Mario_Rivas Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>Mario_Rivas Tracker</description>
    <pubDate>Sat, 25 Nov 2023 10:08:34 GMT</pubDate>
    <dc:date>2023-11-25T10:08:34Z</dc:date>
    <item>
      <title>MS Photos issue</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/MS-Photos-issue/m-p/2935427#M98018</link>
      <description>&lt;P&gt;Hello.&amp;nbsp; At my work, we are running Horizon 7.13.1 with Link-Cloned desktop pools.&amp;nbsp; VMs have been upgraded, recently, to W10 v20H2.&amp;nbsp; After running OSOT on the master template and recomposing the VMs on the desktop pool, MS Photos does not show up as installed nor as the default app to open .jpg, .png, etc., files.&amp;nbsp; Most of the time it will not respond when the user selects the "Print" option, after opening an image.&amp;nbsp; For several users we have to run a PowerShell script to "repair" the installed apps (among them MS Photos) on the VM.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We had made sure, on the master template, that MS Photos is installed (after analyzing, generalizing, etc.) and to place it as the default app for pictures.&amp;nbsp; Also, made sure that the "Print" option will work.&amp;nbsp; But these settings do not stick, once the master template is finalized, a snapshot is created, and the new image is used for recomposing the VMs.&lt;/P&gt;&lt;P&gt;Any ideas for a fix will be greatly appreciated.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Mario&lt;/P&gt;</description>
      <pubDate>Wed, 26 Oct 2022 16:06:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/MS-Photos-issue/m-p/2935427#M98018</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2022-10-26T16:06:11Z</dc:date>
    </item>
    <item>
      <title>Outlook issues after Recomposing</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Outlook-issues-after-Recomposing/m-p/2935076#M98000</link>
      <description>&lt;P&gt;Hello, we do run Horizon 7.13.1 environment with linked-clone desktop pools for W10 v20H2 VMs.&amp;nbsp; Since we went to W10 20H2, after recomposing VMs (finalizing with OSOT), from a master that got latest updates, users are getting an Outlook error:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Mario_Rivas_0-1666643697662.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/97951iC57955A878BD4EEB/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="Mario_Rivas_0-1666643697662.png" alt="Mario_Rivas_0-1666643697662.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Also Teams would not start.&lt;/P&gt;&lt;P&gt;The fix for this error, helpdesk disconnects the user, from the MS Work account (we have Office 365), ran Outlook in safe mode and also reset NAVPANE.&amp;nbsp; This procedure will fix both, Outlook and Teams.&lt;/P&gt;&lt;P&gt;This is becoming very annoying, since about 15-20% of the recomposed VMs end up with this issue.&lt;/P&gt;&lt;P&gt;Anyone knows a way to prevent the error from happening, from the Master Template, before recomposing?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Mario&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2022 20:44:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Outlook-issues-after-Recomposing/m-p/2935076#M98000</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2022-10-24T20:44:48Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid response code: 500</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Invalid-response-code-500/m-p/2931979#M97857</link>
      <description>&lt;P&gt;Hello.&amp;nbsp; I did experience the same issue.&amp;nbsp; What I did to avoid getting the error was, first, on the master image, create a snapshot.&amp;nbsp; Then, export it as an OVF template. Finally, on a different VCenter, deploy OVF Template, using all the files created when the VM was export it as an OVF.&amp;nbsp; The process finished successfully.&amp;nbsp; Creating the snapshot, first, did make the difference.&amp;nbsp; Didn't need to disable any service nor use putty nor to use ovftool.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Oct 2022 22:09:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Invalid-response-code-500/m-p/2931979#M97857</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2022-10-25T22:09:06Z</dc:date>
    </item>
    <item>
      <title>Re: Mapped printers disappearing on VM</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Mapped-printers-disappearing-on-VM/m-p/2881991#M95559</link>
      <description>&lt;P&gt;Hello.&amp;nbsp; Thanks for your reply.&amp;nbsp; We do not have DEM running on our Horizon environment.&amp;nbsp; The registry change recommendation, from the link you sent me, is not present on our VMs.&amp;nbsp; Users do have local admin rights on the VMs they access.&amp;nbsp; Also, we use linked-Clone desktop pools.&amp;nbsp; But, nevertheless, we are looking into this issue as, probably, coming from a Windows Update.&lt;/P&gt;&lt;P&gt;We have, also, opened a ticket with VMware tech support.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Dec 2021 17:45:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Mapped-printers-disappearing-on-VM/m-p/2881991#M95559</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2021-12-07T17:45:20Z</dc:date>
    </item>
    <item>
      <title>Mapped printers disappearing on VM</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Mapped-printers-disappearing-on-VM/m-p/2881854#M95545</link>
      <description>&lt;P&gt;Hello.&amp;nbsp; We are running a VDI environment for our W10 v2004 VMs.&amp;nbsp; Horizon 7.13.1, VMware ESXi 7.0.2 on a vSAN cluster.&amp;nbsp; We are using domain GPO to map printers for users accessing their VMs.&amp;nbsp; Too many times, the mapping is failing, printers are disappearing and the default printer is assigned to a different one. When this happens, we have to run a script on the user's VM, which would re-install the printers and re-assigned the default printer.&amp;nbsp; TP AutoConnect Service and TP VC Gateway Service are both enabled, on the master template, and running on the VMs.&amp;nbsp; We tried disabling both services, recomposing VMs but got the same results.&lt;/P&gt;&lt;P&gt;Any ideas of what can we do to fix this issue?&amp;nbsp; Are we missing something?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Mario&lt;/P&gt;</description>
      <pubDate>Mon, 06 Dec 2021 22:13:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Mapped-printers-disappearing-on-VM/m-p/2881854#M95545</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2021-12-06T22:13:36Z</dc:date>
    </item>
    <item>
      <title>Re: Accessing VDI through Chromebook and sharing screen in Teams</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Accessing-VDI-through-Chromebook-and-sharing-screen-in-Teams/m-p/2841872#M93694</link>
      <description>&lt;P&gt;Hi jutianzheng&lt;/P&gt;&lt;P&gt;Thanks for your suggestion.&amp;nbsp; We are currently testing it and will update this discussion with the results.&lt;/P&gt;&lt;P&gt;Mario&lt;/P&gt;</description>
      <pubDate>Wed, 14 Apr 2021 21:19:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Accessing-VDI-through-Chromebook-and-sharing-screen-in-Teams/m-p/2841872#M93694</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2021-04-14T21:19:24Z</dc:date>
    </item>
    <item>
      <title>Re: Accessing VDI through Chromebook and sharing screen in Teams</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Accessing-VDI-through-Chromebook-and-sharing-screen-in-Teams/m-p/2840807#M93643</link>
      <description>&lt;P&gt;Hi jutianzheng.&lt;/P&gt;&lt;P&gt;By the way, can the Media Optimization for Microsoft Teams, feature, be disabled on the Horizon Client for Chromebook?&amp;nbsp; I found a way to do it on the client for Windows, at the install process.&amp;nbsp; Have not found a way on the client for Chromebook.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Mario&lt;/P&gt;</description>
      <pubDate>Thu, 08 Apr 2021 21:58:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Accessing-VDI-through-Chromebook-and-sharing-screen-in-Teams/m-p/2840807#M93643</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2021-04-08T21:58:35Z</dc:date>
    </item>
    <item>
      <title>Re: Accessing VDI through Chromebook and sharing screen in Teams</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Accessing-VDI-through-Chromebook-and-sharing-screen-in-Teams/m-p/2840733#M93641</link>
      <description>&lt;P&gt;Hi Jutianzheng&lt;/P&gt;&lt;P&gt;Yes, that is the message the Chromebook user gets when it selects About, in MS Teams.&amp;nbsp; I also found out that the option "Media Optimization for Microsoft Teams" is enabled, by default, on the newest versions of VMware Horizon Client.&amp;nbsp; I do have it enabled on my laptop, which is running Horizon Client v5.5.1.&amp;nbsp; The Chromebook user has Horizon Client 5.5.0, which most likely is running also with that option enabled.&lt;/P&gt;&lt;P&gt;We will try, re-installing the client on the Chromebook and make sure to disabled that option.&amp;nbsp; Will update this discussion with the results.&lt;/P&gt;&lt;P&gt;Thanks for your reply.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Apr 2021 15:59:52 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Accessing-VDI-through-Chromebook-and-sharing-screen-in-Teams/m-p/2840733#M93641</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2021-04-08T15:59:52Z</dc:date>
    </item>
    <item>
      <title>Accessing VDI through Chromebook and sharing screen in Teams</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Accessing-VDI-through-Chromebook-and-sharing-screen-in-Teams/m-p/2840169#M93603</link>
      <description>&lt;P&gt;Hello, just recently, users accessing their VM, through a ChromeBook, are not able to share the desktop screen in Teams. They can make calls, with sound and video, but they only get the option to share PowerPoint, not their Desktop.&lt;/P&gt;&lt;P&gt;We run a VMware 7.0 environment with Horizon 7.12, WIndows 10 v2004 and Teams 1.3.0.28779.&lt;/P&gt;&lt;P&gt;We have noticed this change in the last 2-3 weeks.&lt;/P&gt;&lt;P&gt;Has anyone experienced this issue?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Mario&lt;/P&gt;</description>
      <pubDate>Tue, 06 Apr 2021 16:30:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Accessing-VDI-through-Chromebook-and-sharing-screen-in-Teams/m-p/2840169#M93603</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2021-04-06T16:30:28Z</dc:date>
    </item>
    <item>
      <title>Re: Changes in registry on master do not reflect on VMs after composing</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Changes-in-registry-on-master-do-not-reflect-on-VMs-after/m-p/2839456#M93585</link>
      <description>&lt;P&gt;Hello jshaole808.&amp;nbsp; Enforcing the changes through Domain Group Policy did the trick.&amp;nbsp; VMs will be recomposed and get the correct registry value.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 01 Apr 2021 21:10:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Changes-in-registry-on-master-do-not-reflect-on-VMs-after/m-p/2839456#M93585</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2021-04-01T21:10:17Z</dc:date>
    </item>
    <item>
      <title>Re: Adobe 2020 DC</title>
      <link>https://communities.vmware.com/t5/ThinApp/Adobe-2020-DC/m-p/2839455#M7391</link>
      <description>&lt;P&gt;Hi Lavome.&amp;nbsp; Thanks for the reply.&amp;nbsp; We decided that ThinApp for Adobe would not work for us and opted for deployment via installing it on our master VMs.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Mario&lt;/P&gt;</description>
      <pubDate>Thu, 01 Apr 2021 21:08:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Adobe-2020-DC/m-p/2839455#M7391</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2021-04-01T21:08:21Z</dc:date>
    </item>
    <item>
      <title>VM sending internet requests using its IP address, instead of AD account logged on</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/VM-sending-internet-requests-using-its-IP-address-instead-of-AD/m-p/2839454#M93584</link>
      <description>&lt;P&gt;Hello, one of our Master VMs, all of the sudden, started to send internet requests, using its IP address, instead of the AD account logged on.&amp;nbsp; The firewall, has a policy to allow/block internet access depending on the AD account.&amp;nbsp; Because of this, the firewall is blocking these requests because it does not recognize the IP address as an AD account.&lt;/P&gt;&lt;P&gt;Sometimes, making a change on the registry will make the internet connectivity work, for some time, until the VM starts doing it again.&amp;nbsp; Same when I run IPConfig /release and IPConfig /renew.&lt;/P&gt;&lt;P&gt;Access to internal resources works fine.&amp;nbsp; It is access to internet resources, like to run MS Updates or AntiVirus updates, what are being affected.&lt;/P&gt;&lt;P&gt;We run a Horizon 7.12 VDI environment, using VMware 7.&amp;nbsp; The master VM runs WIndows 10 v2004.&amp;nbsp; We also added the registry settings for DisablePassivePolling=0 and NoActiveProbe=0, under HKLM\Software\Policies\Microsoft\Windows\NetworkConnectivityStatusIndicator.&amp;nbsp; Internet adapter shows "connected to the internet", and is a VMXNET3.&lt;/P&gt;&lt;P&gt;Has anyone run into a similar issue?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Apr 2021 21:06:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/VM-sending-internet-requests-using-its-IP-address-instead-of-AD/m-p/2839454#M93584</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2021-04-01T21:06:11Z</dc:date>
    </item>
    <item>
      <title>Adobe 2020 DC</title>
      <link>https://communities.vmware.com/t5/ThinApp/Adobe-2020-DC/m-p/2824588#M7365</link>
      <description>&lt;P&gt;Hello, has anyone tried a Thinapp for Adobe Pro 2020 DC?&amp;nbsp; I am able to build it, successfully.&amp;nbsp; The thinapp runs fine if we open and/or edit pdf files.&amp;nbsp; When we test the signature feature, the screen gets darker and freezes to the point that to get it out, we have to end the program using Task Manager.&lt;/P&gt;&lt;P&gt;Any help would be greatly appreciated.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Mario&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jan 2021 17:52:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Adobe-2020-DC/m-p/2824588#M7365</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2021-01-21T17:52:46Z</dc:date>
    </item>
    <item>
      <title>Re: Changes in registry on master do not reflect on VMs after composing</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Changes-in-registry-on-master-do-not-reflect-on-VMs-after/m-p/2824304#M92888</link>
      <description>&lt;P&gt;Hello jshaole808. Thanks for your reply.&amp;nbsp; We are testing forcing, through Domain Group Policy, to have those registry settings with the required setting value.&lt;/P&gt;&lt;P&gt;Will update this discussion on the results.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jan 2021 17:39:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Changes-in-registry-on-master-do-not-reflect-on-VMs-after/m-p/2824304#M92888</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2021-01-20T17:39:25Z</dc:date>
    </item>
    <item>
      <title>Re: Adobe Acrobat ThinApp</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Adobe-Acrobat-ThinApp/m-p/2819177#M92642</link>
      <description>&lt;P&gt;Hello vasquezu.&lt;/P&gt;&lt;P&gt;Finally, yesterday, VMware techsupport gave me a fix for the ThinApp Exception Error.&lt;/P&gt;&lt;P&gt;When building the ThinApp, on the package.ini file, add the following lines, under the "General Purpose Parameters" section:&lt;/P&gt;&lt;P&gt;EnableExternalHookInterception=1&lt;/P&gt;&lt;P&gt;ExternalDlls=libcef.dll&lt;/P&gt;&lt;P&gt;I did enter the above 2 lines, rebuilt the ThinApp, test it and, finally!, Adobe started without showing the Exception Error window.&lt;/P&gt;&lt;P&gt;Good Luck!&lt;/P&gt;&lt;P&gt;Mario&lt;/P&gt;</description>
      <pubDate>Thu, 24 Dec 2020 16:21:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Adobe-Acrobat-ThinApp/m-p/2819177#M92642</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2020-12-24T16:21:09Z</dc:date>
    </item>
    <item>
      <title>Changes in registry on master do not reflect on VMs after composing</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Changes-in-registry-on-master-do-not-reflect-on-VMs-after/m-p/2817899#M92602</link>
      <description>&lt;P&gt;Hello.&amp;nbsp; We run a Horizon 7.12 VDI for Windows 10 v2004 VMs, using the VMware OSOT to prepare the Master VM to be used for recomposing.&lt;/P&gt;&lt;P&gt;Before, due to getting a "No Network" issue, we had implemented the following registry settings on the master VM. Under, &lt;STRONG&gt;Computer\HKLM\Software\Policies\Microsoft\Windows\NetworkConnectivityStatusIndicator\&lt;/STRONG&gt; we made the following changes:&amp;nbsp; &lt;STRONG&gt;NoActiveProbe&lt;/STRONG&gt;, from &lt;STRONG&gt;1&lt;/STRONG&gt; it was changed to &lt;STRONG&gt;0&lt;/STRONG&gt; and &lt;STRONG&gt;DisableActiveProbing&lt;/STRONG&gt;. from &lt;STRONG&gt;1&lt;/STRONG&gt; it was changed to &lt;STRONG&gt;0&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;This is set along with of a local policy, under &lt;STRONG&gt;Computer Configuration\Administrative Templates\Network\Network Connectivity Status Indicator&lt;/STRONG&gt;, the item &lt;STRONG&gt;Specify passive polling&lt;/STRONG&gt; is &lt;STRONG&gt;Enabled&lt;/STRONG&gt; with &lt;STRONG&gt;Disable passive polling&lt;/STRONG&gt;&amp;nbsp;checked.&lt;/P&gt;&lt;P&gt;This setting has been working just fine until we recently ran MS Updates on the master VM and did recompose VMs with this new update.&amp;nbsp; The registry settings, on the VMs, changed back to &lt;STRONG&gt;1&lt;/STRONG&gt;, making them to get the "No Network issue" (with Outlook 365) not working.&amp;nbsp; Interesting fact is that the master template still has the registry changes we did before.&lt;/P&gt;&lt;P&gt;Has anyone ran into this issue?&amp;nbsp; Any help is greatly appreciated.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Mario&lt;/P&gt;</description>
      <pubDate>Thu, 17 Dec 2020 17:24:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Changes-in-registry-on-master-do-not-reflect-on-VMs-after/m-p/2817899#M92602</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2020-12-17T17:24:05Z</dc:date>
    </item>
    <item>
      <title>Startup Folder on user's profile</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Startup-Folder-on-user-s-profile/m-p/2817887#M92599</link>
      <description>&lt;P&gt;Hello.&amp;nbsp; We have a Horizon 7.12 environment, for Windows 10 v2004 VMs.&amp;nbsp; The user's profile is created on a persistent data disk (D: drive).&amp;nbsp; We noticed that the Startup folder does not get created when a user is assigned to a VM.&amp;nbsp; We have to manually create the folder, under this path, D:\Users\&amp;lt;User&amp;gt;\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\&lt;/P&gt;&lt;P&gt;Has anyone ran into this issue?&amp;nbsp; If so, is there any fix to it?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Mario&lt;/P&gt;</description>
      <pubDate>Thu, 17 Dec 2020 16:51:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Startup-Folder-on-user-s-profile/m-p/2817887#M92599</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2020-12-17T16:51:19Z</dc:date>
    </item>
    <item>
      <title>Re: Microsoft Teams</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Microsoft-Teams/m-p/2814909#M92486</link>
      <description>&lt;P&gt;Thanks for the link!&amp;nbsp; You are correct.&amp;nbsp; the Control options are not available in a VDI environment.&lt;/P&gt;&lt;P&gt;Now I am searching for the Zoom In and Zoom out feature, not showing up in Teams.&lt;/P&gt;&lt;P&gt;Thanks again&lt;/P&gt;&lt;P&gt;Mario&lt;/P&gt;</description>
      <pubDate>Fri, 04 Dec 2020 18:56:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Microsoft-Teams/m-p/2814909#M92486</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2020-12-04T18:56:04Z</dc:date>
    </item>
    <item>
      <title>Microsoft Teams</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Microsoft-Teams/m-p/2814655#M92475</link>
      <description>&lt;P&gt;Hello, running MS Teams 1.3.00.21759 on VM with Windows 10 v2004, in a Horizon VDI 7.12 environment is coming up with some issues.&amp;nbsp; Among them&lt;/P&gt;&lt;P&gt;- When a user shares a full screen, the option to "give control" does not come up for the user who is sharing and the option to "request control" does not come up for the other user(s).&lt;/P&gt;&lt;P&gt;-&amp;nbsp; The option to Zoom In or Out does not show.&amp;nbsp; User is stuck with the same font size.&lt;/P&gt;&lt;P&gt;Has anyone experienced the same?&amp;nbsp; Is there any way to fix these issues?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Mario RIvas&lt;/P&gt;</description>
      <pubDate>Thu, 03 Dec 2020 22:13:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Microsoft-Teams/m-p/2814655#M92475</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2020-12-03T22:13:15Z</dc:date>
    </item>
    <item>
      <title>Re: Adobe Acrobat ThinApp</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Adobe-Acrobat-ThinApp/m-p/2812369#M92332</link>
      <description>&lt;P&gt;I need to revert my previous comment.&amp;nbsp; The issue IS WITH VMware OSOT.&amp;nbsp; I tried a clean W10 v2004 VM, added all the programs and apps, tried the Thinapp and it worked just fine.&amp;nbsp; Once the OSOT was applied, using the template for Windows 10 1809-2004, is when the issue with Adobe Thinapp.&lt;/P&gt;&lt;P&gt;This has also been informed to VMware tech support and awaiting for their feedback.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Nov 2020 19:09:03 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Adobe-Acrobat-ThinApp/m-p/2812369#M92332</guid>
      <dc:creator>Mario_Rivas</dc:creator>
      <dc:date>2020-11-24T19:09:03Z</dc:date>
    </item>
  </channel>
</rss>

