<?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>gnavas Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>gnavas Tracker</description>
    <pubDate>Sat, 18 Nov 2023 00:08:42 GMT</pubDate>
    <dc:date>2023-11-18T00:08:42Z</dc:date>
    <item>
      <title>A question about NVIDIA Shield pro</title>
      <link>https://communities.vmware.com/t5/Workspace-Members/A-question-about-NVIDIA-Shield-pro/m-p/2964574#M50</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;Greetings. I recently installed a certified wso at a Spanish customer's premises and the customer plans to enroll an NVIDIA Shield pro Android virtual device. Can you give me some tips, links and references on the possibilities of this type of enrollment?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Thank you!&lt;BR /&gt;KR.&lt;BR /&gt;Gemma Navas&lt;BR /&gt;gnavas@offshoretech.net&lt;/P&gt;</description>
      <pubDate>Wed, 19 Apr 2023 08:09:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-Members/A-question-about-NVIDIA-Shield-pro/m-p/2964574#M50</guid>
      <dc:creator>gnavas</dc:creator>
      <dc:date>2023-04-19T08:09:35Z</dc:date>
    </item>
    <item>
      <title>Re: Cache Folder Workspace ONE UEM</title>
      <link>https://communities.vmware.com/t5/Digital-Workspace-Members/Cache-Folder-Workspace-ONE-UEM/m-p/2943594#M80</link>
      <description>&lt;P&gt;Phil_Helming&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are updating a on-prem environment from 22.06 ( for instance in 21.05 version, Java 1.8 was added by the installer) up to 22.09 (without checking version of the Java). The problem is the Windows Server 2016 is installed on a RED-HAT with an openjdk 11+ version.&lt;/P&gt;&lt;P&gt;Could any incompatiblity with this java version for the AWCM service?&lt;/P&gt;&lt;P&gt;Many thanks!&lt;/P&gt;&lt;P&gt;Gemma Navas&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Offshoretech SL&lt;/P&gt;</description>
      <pubDate>Tue, 13 Dec 2022 10:33:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Digital-Workspace-Members/Cache-Folder-Workspace-ONE-UEM/m-p/2943594#M80</guid>
      <dc:creator>gnavas</dc:creator>
      <dc:date>2022-12-13T10:33:53Z</dc:date>
    </item>
    <item>
      <title>Java version in the 22.09 on-prem WS1 ONE UEM</title>
      <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Java-version-in-the-22-09-on-prem-WS1-ONE-UEM/m-p/2943592#M18002</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;We are updating a on-prem environment from 22.06 ( for instance in 21.05 version, Java 1.8 was added by the installer) up to 22.09 (without checking version of the Java). The problem is the Windows Server 2016 is installed on a RED-HAT with an openjdk 11+ version.&lt;/P&gt;&lt;P&gt;Could any incompatiblity with this java version for the AWCM service?&lt;/P&gt;&lt;P&gt;Many thanks!&lt;/P&gt;&lt;P&gt;Gemma Navas&lt;/P&gt;&lt;P&gt;Offshoretech SL&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Dec 2022 10:32:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Java-version-in-the-22-09-on-prem-WS1-ONE-UEM/m-p/2943592#M18002</guid>
      <dc:creator>gnavas</dc:creator>
      <dc:date>2022-12-13T10:32:48Z</dc:date>
    </item>
    <item>
      <title>Re: Cache Folder Workspace ONE UEM</title>
      <link>https://communities.vmware.com/t5/Digital-Workspace-Members/Cache-Folder-Workspace-ONE-UEM/m-p/2942618#M71</link>
      <description>&lt;P&gt;Hi Phil,&lt;/P&gt;&lt;P&gt;Thank you for your reply. We have just added size to HD because it was just over 93% and the cache folder is not increasing, it keeps in the same size. We are going to schedule an upgrade of Device Server and Console (the issue is in the Console) to 22.10 version and see if this fix it.&amp;nbsp; I don't know if the root cause is an IIS performance problem in the server but actually the Event Viewer does not show any suspicious in this way.&lt;/P&gt;&lt;P&gt;Much appreciated!&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 07 Dec 2022 10:13:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Digital-Workspace-Members/Cache-Folder-Workspace-ONE-UEM/m-p/2942618#M71</guid>
      <dc:creator>gnavas</dc:creator>
      <dc:date>2022-12-07T10:13:46Z</dc:date>
    </item>
    <item>
      <title>Re: Intelligent HUB</title>
      <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Intelligent-HUB/m-p/2878033#M16350</link>
      <description>&lt;P&gt;Hi Everyone&lt;/P&gt;&lt;P&gt;Any news about when the next Intelligent HUB release come up. There are a lot of customers with restrictions profile affected.&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;Gemma&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 15 Nov 2021 08:06:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Intelligent-HUB/m-p/2878033#M16350</guid>
      <dc:creator>gnavas</dc:creator>
      <dc:date>2021-11-15T08:06:37Z</dc:date>
    </item>
    <item>
      <title>Intelligent HUB</title>
      <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Intelligent-HUB/m-p/2877654#M16338</link>
      <description>&lt;P&gt;&lt;BR /&gt;We have identified BUG in 2109 version and fix version available is 21.10, I am working with R&amp;amp;D team to get more details on our issue with restriction profile. This may be a reason for us to get stuck.&lt;/P&gt;&lt;P&gt;Thank you,&lt;BR /&gt;--&lt;BR /&gt;Nagabharana S&lt;BR /&gt;Technical Support Engineer Level 2&lt;BR /&gt;Global Support Services, VMware Inc.&lt;/P&gt;&lt;P&gt;Do you know a schedule/roadmap to get the new HUB version in Google Play?&lt;/P&gt;&lt;P&gt;Thank you!&lt;BR /&gt;Gemma Navas&lt;BR /&gt;&lt;A href="mailto:gnavas@offshoretech.net" target="_blank" rel="noopener"&gt;gnavas@offshoretech.net&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Support&lt;/P&gt;&lt;P&gt;n1cloud@vodafone.com&lt;/P&gt;</description>
      <pubDate>Fri, 12 Nov 2021 09:14:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Intelligent-HUB/m-p/2877654#M16338</guid>
      <dc:creator>gnavas</dc:creator>
      <dc:date>2021-11-12T09:14:40Z</dc:date>
    </item>
    <item>
      <title>VMware Tunnel Proxy Relay-Endpoint 9.7 windows cannot open SSL channel over 2020 port</title>
      <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/VMware-Tunnel-Proxy-Relay-Endpoint-9-7-windows-cannot-open-SSL/m-p/2275127#M12840</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are experiencing a issue related to Tunnel Proxy in SaaS environment. The point is we have just reniewed the Relay certificate ans re-isntall Proxy and Endpoint from console instaler (Console is in 1810 version) but since then, RELAY is not able to open the SSL channel to ENDPOINT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These are the Logs:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;17:37:06.373 INFO&amp;nbsp; [main] [SslHelper:85] - VMwareTunnelProxy [jdk.tls.disabledAlgorithms=RC4]&lt;/P&gt;&lt;P&gt;17:37:06.435 INFO&amp;nbsp; [main] [SslProxyContext:36] - Added SSL context to proxy [HTTP @ &lt;A href="http://magendpoint.corporacion.lavoz.es:2030/" target="_blank"&gt;magendpoint.corporacion.lavoz.es:2030&lt;/A&gt;]&lt;/P&gt;&lt;P&gt;17:37:06.841 ERROR [main] [ProxyLauncher:43] - VMware Tunnel Proxy failed to initialize!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Otherwise ENDPOINT shows a non secure certificate because it is using a sha-1 logaritm instead of sha256. Would it be the real problem?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gemma&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-email-small" href="mailto:gnavas@icloud.com"&gt;gnavas@icloud.com&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Feb 2020 08:28:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-ONE-Discussions/VMware-Tunnel-Proxy-Relay-Endpoint-9-7-windows-cannot-open-SSL/m-p/2275127#M12840</guid>
      <dc:creator>gnavas</dc:creator>
      <dc:date>2020-02-11T08:28:02Z</dc:date>
    </item>
    <item>
      <title>Re: Connecting with Azure AD</title>
      <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Connecting-with-Azure-AD/m-p/1835194#M6257</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Sean, can you enroll Android devices with this integration or just only Windows 10 devices instead of?. I did a service request to VMWARE and answer us that eht only way to do that is&amp;nbsp; configure LDAPS with SAML authentication. When we checked (and worked) With the AD DS we added users but not users groups.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Jul 2019 07:00:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Connecting-with-Azure-AD/m-p/1835194#M6257</guid>
      <dc:creator>gnavas</dc:creator>
      <dc:date>2019-07-19T07:00:44Z</dc:date>
    </item>
    <item>
      <title>Re: Android Device Enrollment using Azure AD Users</title>
      <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Android-Device-Enrollment-using-Azure-AD-Users/m-p/519439#M2196</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Any tips?. We cannot enroll Android Device using Azure AD Users.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 May 2019 12:48:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Android-Device-Enrollment-using-Azure-AD-Users/m-p/519439#M2196</guid>
      <dc:creator>gnavas</dc:creator>
      <dc:date>2019-05-07T12:48:34Z</dc:date>
    </item>
    <item>
      <title>Re: Android Device Enrollment using Azure AD Users</title>
      <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Android-Device-Enrollment-using-Azure-AD-Users/m-p/519438#M2195</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Having the same issue as well. Is it possible to enroll Android Devices?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Apr 2019 15:49:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Android-Device-Enrollment-using-Azure-AD-Users/m-p/519438#M2195</guid>
      <dc:creator>gnavas</dc:creator>
      <dc:date>2019-04-30T15:49:20Z</dc:date>
    </item>
    <item>
      <title>Re: Connecting with Azure AD</title>
      <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Connecting-with-Azure-AD/m-p/1835192#M6255</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Gautam, please,could you kindly provide us the exact steps how you got that Azure AD worked with Airwatch. In my case, the device is not enrolling so I can add any user.&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;Done it. But we cannot enroll Android Devices with Azure AD users. Is that correct?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Apr 2019 15:48:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Connecting-with-Azure-AD/m-p/1835192#M6255</guid>
      <dc:creator>gnavas</dc:creator>
      <dc:date>2019-04-30T15:48:06Z</dc:date>
    </item>
  </channel>
</rss>

