<?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>topic Re: Thinapp Not Installed on Clients Windows 10 20H2 in ThinApp</title>
    <link>https://communities.vmware.com/t5/ThinApp/Thinapp-Not-Installed-on-Clients-Windows-10-20H2/m-p/2842741#M7397</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since W10 there always were additional SMB v1-3 impacts concerning access from newer patches and/or releases.&amp;nbsp;Smb/cifs file server And W10 client should support at least one smb version+dialect (SMB v1 &amp;lt;-&amp;gt; SMB v1, SMB v2 &amp;lt;-&amp;gt; SMB v2, SMB v3 &amp;lt;-&amp;gt; SMB v3).&amp;nbsp;This is relevant for Thinapp' unc path connections method, too.&lt;/P&gt;&lt;P&gt;&amp;nbsp;As the smb/cifs file server hasn't changed, and assuming it is more desirable to have a 1909 &amp;amp; 20H2 working set, you could do a few workarounds to check. I've started a listing which may help.&lt;/P&gt;&lt;P&gt;1) Allow SMBv1 interoperability (see &lt;A href="https://answers.microsoft.com/en-us/windows/forum/all/smb-sharing-not-working-after-windows-10-update/298f9988-ddd7-48dd-9924-a21541d98c05?page=23" target="_self"&gt;thread&lt;/A&gt;)&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;W10 clients:&lt;BR /&gt;Get-WindowsOptionalFeature -Online -FeatureName "SMB1Protocol"&lt;BR /&gt;Disable-WindowsOptionalFeature -Online -FeatureName "SMB1Protocol"&lt;BR /&gt;Reboot&lt;BR /&gt;&lt;/FONT&gt;Enable-WindowsOptionalFeature -Online -FeatureName "SMB1Protocol" -All&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;:: Autostart on user login. U = Driveletter for the server share&lt;BR /&gt;net use U: “\\server\share” /persistent:no&lt;BR /&gt;reg.exe ADD HKCU\Network\U /v ProviderFlags /t dword /d 1 /f&lt;BR /&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Windows server: KB5000856&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;2) Allow &lt;A href="https://docs.microsoft.com/en-us/troubleshoot/windows-server/networking/guest-access-in-smb2-is-disabled-by-default" target="_self"&gt;SMBv2 Insecure Guest Authentification&lt;/A&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters AllowInsecureGuestAuth dword 1&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;3) &lt;A href="https://msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-1206" target="_self"&gt;SMBleed "SMBv3" related patch&lt;/A&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters DisableCompression dword 1&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;SMB dialect key features mapping between server and client is signifant. Some 'Microsoft SMB'-only descriptions are:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;A href="https://docs.microsoft.com/en-us/windows-server/storage/file-server/file-server-smb-overview" rel="nofollow" target="_blank"&gt;https://docs.microsoft.com/en-us/windows-server/storage/file-server/file-server-smb-overview&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;learning curve story at&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://techcommunity.microsoft.com/t5/storage-at-microsoft/controlling-smb-dialects/ba-p/860024" rel="nofollow" target="_blank"&gt;https://techcommunity.microsoft.com/t5/storage-at-microsoft/controlling-smb-dialects/ba-p/860024&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;SMB protocol revision at&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-smb2/5606ad47-5ee0-437a-817e-70c366052962" rel="nofollow" target="_blank"&gt;https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-smb2/5606ad47-5ee0-437a-817e-70c366052962&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;SMB 3.0 with encryption is supported by Microsoft Windows 8, Server 2012 and above.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;For Linux, Samba 4.0 and above supports SMB 3.0 (see&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://wiki.samba.org/index.php/LinuxCIFSKernel" rel="nofollow" target="_blank"&gt;https://wiki.samba.org/index.php/LinuxCIFSKernel&lt;/A&gt;&lt;SPAN&gt;).&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;That said, the SMB (3.x) compliancy for storage solutions never was a client golden image property only.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 20 Apr 2021 08:33:23 GMT</pubDate>
    <dc:creator>DCasota</dc:creator>
    <dc:date>2021-04-20T08:33:23Z</dc:date>
    <item>
      <title>Thinapp Not Installed on Clients Windows 10 20H2</title>
      <link>https://communities.vmware.com/t5/ThinApp/Thinapp-Not-Installed-on-Clients-Windows-10-20H2/m-p/2840893#M7392</link>
      <description>&lt;P&gt;Dear Community,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I updated the Golden Image from Windows 10 1909 to 20H2 and now the Thinapp won't installed on the Client:&lt;BR /&gt;If I copy the Thinapps (5.2.9) local to the machine it works without problems. The Windows 10 1909 Clients are not affected, their the Thinapps works.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;In Vmware View Horizon Admin Console following Error is shown up:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;OpenPackageError details. HRESULOT hr = 0x80010105 ErrorInfo object is NULL, There was no error object to return&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;In the Client Workstation Windows 10 20H2 following Errors are shown in the VDM Log of the Client:&lt;/STRONG&gt;&lt;BR /&gt;2021-04-09T09:11:41.449+02:00 DEBUG (1570-1134) &amp;lt;pool-3-thread-4&amp;gt; [AbstractTopicPublishingManager] (DesktopControlPublishingManager-agent) Message published.&lt;BR /&gt;2021-04-09T09:11:44.164+02:00 DEBUG (1570-1158) &amp;lt;SwiftMQ-SessionPool-5&amp;gt; [msgid] Validating message with ID: 'null'.&lt;BR /&gt;2021-04-09T09:11:44.164+02:00 DEBUG (0B84-1E64) &amp;lt;MessageFrameWorkDispatch&amp;gt; [wsnm_desktop] DesktopManager got a InstallApps message&lt;BR /&gt;2021-04-09T09:11:44.164+02:00 DEBUG (0B84-1E64) &amp;lt;MessageFrameWorkDispatch&amp;gt; [ws_thinappmgmt] ThinApp Install applications called for 1 applications&lt;BR /&gt;2021-04-09T09:11:44.214+02:00 DEBUG (0B84-1E64) &amp;lt;MessageFrameWorkDispatch&amp;gt; [ws_thinappmgmt] Application ID: app1&lt;BR /&gt;2021-04-09T09:11:44.214+02:00 DEBUG (0B84-1E64) &amp;lt;MessageFrameWorkDispatch&amp;gt; [ws_thinappmgmt] ThinAppMgmt: Application Details: APP_CN = "8c5c43e5-f12c-4843-a942-e2907e0ab39d"&lt;BR /&gt;OPERATION = "INSTALL"&lt;BR /&gt;INSTALL_FLAGS = "0"&lt;BR /&gt;APPLICATION_PATH = "\\xxxxxl\xxxxx$\Igel6iH20\bin\igel6i.msi"&lt;BR /&gt;INSTALL_TYPE = "FULL"&lt;BR /&gt;APP_DISPLAYNAME = "Igel6i"&lt;/P&gt;&lt;P&gt;2021-04-09T09:11:44.214+02:00 DEBUG (0B84-1E64) &amp;lt;MessageFrameWorkDispatch&amp;gt; [ws_thinappmgmt] ThinAppMgmt: Opening application Igel6i package at path: \\xxxxx\xxxxxx\Igel6iH20\bin\igel6i.msi&lt;BR /&gt;2021-04-09T09:11:44.214+02:00 DEBUG (0B84-1E64) &amp;lt;MessageFrameWorkDispatch&amp;gt; [ws_thinappmgmt] ThinApp: OpenPackage&lt;BR /&gt;2021-04-09T09:11:44.239+02:00 ERROR (0B84-1E64) &amp;lt;MessageFrameWorkDispatch&amp;gt; [ws_thinappmgmt] OpenPackage failed, path = &amp;nbsp;\\xxxxx\xxxxxx\\Igel6iH20\bin\igel6i.msi. Error details. HRESULT hr = 0x80010105. ErrorInfo object is NULL, There was no error object to return.&lt;BR /&gt;2021-04-09T09:11:44.354+02:00 DEBUG (0B84-1E64) &amp;lt;MessageFrameWorkDispatch&amp;gt; [ws_thinappmgmt] ThinAppMgmt: Success, returning Application Response: APPLICATION_COUNT = "1"&lt;BR /&gt;app1 =&lt;BR /&gt;APP_CN = "8c5c43e5-f12c-4843-a942-e2907e0ab39d"&lt;BR /&gt;OPERATION = "INSTALL"&lt;BR /&gt;RESULT = "FAILED"&lt;BR /&gt;SkippedErrorContext = "OpenPackage"&lt;BR /&gt;SkippedErrorCode = "-2147417851"&lt;BR /&gt;SkippedError = "Error details. HRESULT hr = 0x80010105. ErrorInfo object is NULL, There was no error object to return."&lt;/P&gt;&lt;P&gt;Has somebody the same error?&lt;/P&gt;&lt;P&gt;thx for your helpt&lt;/P&gt;&lt;P&gt;Best Regards&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Apr 2021 10:47:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Thinapp-Not-Installed-on-Clients-Windows-10-20H2/m-p/2840893#M7392</guid>
      <dc:creator>Donwurzel</dc:creator>
      <dc:date>2021-04-09T10:47:08Z</dc:date>
    </item>
    <item>
      <title>Re: Thinapp Not Installed on Clients Windows 10 20H2</title>
      <link>https://communities.vmware.com/t5/ThinApp/Thinapp-Not-Installed-on-Clients-Windows-10-20H2/m-p/2840897#M7393</link>
      <description>&lt;P&gt;What I found out is&amp;nbsp; that I have a Horizon Agent 7.11 installed in the Clients and that Version ist not compatible with Windows 10 20H2 - I will update and reply if the error is solved after the upgrade...&lt;BR /&gt;&lt;BR /&gt;Here the Product Matrix&lt;BR /&gt;&lt;A href="https://kb.vmware.com/s/article/2149393" target="_blank"&gt;https://kb.vmware.com/s/article/2149393&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Apr 2021 11:25:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Thinapp-Not-Installed-on-Clients-Windows-10-20H2/m-p/2840897#M7393</guid>
      <dc:creator>Donwurzel</dc:creator>
      <dc:date>2021-04-09T11:25:20Z</dc:date>
    </item>
    <item>
      <title>Re: Thinapp Not Installed on Clients Windows 10 20H2</title>
      <link>https://communities.vmware.com/t5/ThinApp/Thinapp-Not-Installed-on-Clients-Windows-10-20H2/m-p/2842586#M7394</link>
      <description>&lt;P&gt;Updated - Horizon Agent to 7.13 / DEM to 2103 but the error still exist, No Thinapp Creation with the new Windows 20H2.&lt;BR /&gt;&lt;BR /&gt;021-04-19T14:44:12.367+02:00 ERROR (0AA8-09A8) &amp;lt;MessageFrameWorkDispatch&amp;gt; [ws_thinappmgmt] OpenPackage failed, path = xxxxxx\igel6i.msi. &lt;STRONG&gt;Error details. HRESULT hr = 0x80010105. ErrorInfo object is NULL, There was no error object to return.&lt;/STRONG&gt;&lt;BR /&gt;2021-04-19T14:44:12.482+02:00 DEBUG (0AA8-09A8) &amp;lt;MessageFrameWorkDispatch&amp;gt; [ws_thinappmgmt] ThinAppMgmt: Success, returning Application Response: APPLICATION_COUNT = "2"&lt;BR /&gt;app1 =&lt;BR /&gt;APP_CN = "d3daf633-0aaa-458d-8c04-84003972c78b"&lt;BR /&gt;OPERATION = "INSTALL"&lt;BR /&gt;RESULT = "FAILED"&lt;BR /&gt;&lt;STRONG&gt;SkippedErrorContext = "OpenPackage"&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;SkippedErrorCode = "-2147417851"&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;SkippedError = "Error details. HRESULT hr = 0x80010105. ErrorInfo object is NULL, There was no error object to return."&lt;/STRONG&gt;&lt;BR /&gt;app2 =&lt;BR /&gt;APP_CN = "298e567c-6efe-4a92-a03f-fca18cb1cee6"&lt;BR /&gt;OPERATION = "INSTALL"&lt;BR /&gt;RESULT = "FAILED"&lt;BR /&gt;SkippedErrorContext = "OpenPackage"&lt;BR /&gt;SkippedErrorCode = "-2147417851"&lt;BR /&gt;SkippedError = "Error details. HRESULT hr = 0x80010105. ErrorInfo object is NULL, There was no error object to return."&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;The Same Image with 1909 works, but a clone with 20H2 gets that error....&lt;/P&gt;&lt;P&gt;Thx for your Help !&lt;/P&gt;&lt;P&gt;Best Regards Wurzel&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Apr 2021 12:57:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Thinapp-Not-Installed-on-Clients-Windows-10-20H2/m-p/2842586#M7394</guid>
      <dc:creator>Donwurzel</dc:creator>
      <dc:date>2021-04-19T12:57:01Z</dc:date>
    </item>
    <item>
      <title>Re: Thinapp Not Installed on Clients Windows 10 20H2</title>
      <link>https://communities.vmware.com/t5/ThinApp/Thinapp-Not-Installed-on-Clients-Windows-10-20H2/m-p/2842651#M7395</link>
      <description>&lt;P&gt;Does the Windows 20H2 image exclude the Msft &lt;A href="https://support.microsoft.com/en-us/topic/december-8-2020-kb4592438-os-builds-19041-685-and-19042-685-a548ef85-dec5-e58e-0c33-206784bfcf91" target="_self"&gt;KB4592438&lt;/A&gt;? It has been mentioned in &lt;A href="https://docs.vmware.com/en/VMware-ThinApp/5.2.9/rn/VMware-ThinApp-529-Release-Notes.html" target="_self"&gt;5.2.9 Release Notes&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Apr 2021 18:03:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Thinapp-Not-Installed-on-Clients-Windows-10-20H2/m-p/2842651#M7395</guid>
      <dc:creator>DCasota</dc:creator>
      <dc:date>2021-04-19T18:03:29Z</dc:date>
    </item>
    <item>
      <title>Re: Thinapp Not Installed on Clients Windows 10 20H2</title>
      <link>https://communities.vmware.com/t5/ThinApp/Thinapp-Not-Installed-on-Clients-Windows-10-20H2/m-p/2842720#M7396</link>
      <description>&lt;P&gt;Yes, the KB4592438 s not installed on the Golden Image - I think otherwise the Thinapps would 'nt work if i start them. (I can manually copy the Thinapp to the Image or start it over UNC Path, both work)&lt;/P&gt;&lt;P&gt;The only Problem I have is that the Thinapp isn't copied to the image.&lt;BR /&gt;I think I will change the behavior and start the Thinapps over UNC Paths with Shortcuts to them, or copy them to the Golden Image manually....&lt;/P&gt;&lt;P&gt;Best Regards Wurzel&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Apr 2021 06:09:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Thinapp-Not-Installed-on-Clients-Windows-10-20H2/m-p/2842720#M7396</guid>
      <dc:creator>Donwurzel</dc:creator>
      <dc:date>2021-04-20T06:09:24Z</dc:date>
    </item>
    <item>
      <title>Re: Thinapp Not Installed on Clients Windows 10 20H2</title>
      <link>https://communities.vmware.com/t5/ThinApp/Thinapp-Not-Installed-on-Clients-Windows-10-20H2/m-p/2842741#M7397</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since W10 there always were additional SMB v1-3 impacts concerning access from newer patches and/or releases.&amp;nbsp;Smb/cifs file server And W10 client should support at least one smb version+dialect (SMB v1 &amp;lt;-&amp;gt; SMB v1, SMB v2 &amp;lt;-&amp;gt; SMB v2, SMB v3 &amp;lt;-&amp;gt; SMB v3).&amp;nbsp;This is relevant for Thinapp' unc path connections method, too.&lt;/P&gt;&lt;P&gt;&amp;nbsp;As the smb/cifs file server hasn't changed, and assuming it is more desirable to have a 1909 &amp;amp; 20H2 working set, you could do a few workarounds to check. I've started a listing which may help.&lt;/P&gt;&lt;P&gt;1) Allow SMBv1 interoperability (see &lt;A href="https://answers.microsoft.com/en-us/windows/forum/all/smb-sharing-not-working-after-windows-10-update/298f9988-ddd7-48dd-9924-a21541d98c05?page=23" target="_self"&gt;thread&lt;/A&gt;)&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;W10 clients:&lt;BR /&gt;Get-WindowsOptionalFeature -Online -FeatureName "SMB1Protocol"&lt;BR /&gt;Disable-WindowsOptionalFeature -Online -FeatureName "SMB1Protocol"&lt;BR /&gt;Reboot&lt;BR /&gt;&lt;/FONT&gt;Enable-WindowsOptionalFeature -Online -FeatureName "SMB1Protocol" -All&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;:: Autostart on user login. U = Driveletter for the server share&lt;BR /&gt;net use U: “\\server\share” /persistent:no&lt;BR /&gt;reg.exe ADD HKCU\Network\U /v ProviderFlags /t dword /d 1 /f&lt;BR /&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Windows server: KB5000856&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;2) Allow &lt;A href="https://docs.microsoft.com/en-us/troubleshoot/windows-server/networking/guest-access-in-smb2-is-disabled-by-default" target="_self"&gt;SMBv2 Insecure Guest Authentification&lt;/A&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters AllowInsecureGuestAuth dword 1&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;3) &lt;A href="https://msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-1206" target="_self"&gt;SMBleed "SMBv3" related patch&lt;/A&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters DisableCompression dword 1&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;SMB dialect key features mapping between server and client is signifant. Some 'Microsoft SMB'-only descriptions are:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;A href="https://docs.microsoft.com/en-us/windows-server/storage/file-server/file-server-smb-overview" rel="nofollow" target="_blank"&gt;https://docs.microsoft.com/en-us/windows-server/storage/file-server/file-server-smb-overview&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;learning curve story at&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://techcommunity.microsoft.com/t5/storage-at-microsoft/controlling-smb-dialects/ba-p/860024" rel="nofollow" target="_blank"&gt;https://techcommunity.microsoft.com/t5/storage-at-microsoft/controlling-smb-dialects/ba-p/860024&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;SMB protocol revision at&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-smb2/5606ad47-5ee0-437a-817e-70c366052962" rel="nofollow" target="_blank"&gt;https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-smb2/5606ad47-5ee0-437a-817e-70c366052962&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;SMB 3.0 with encryption is supported by Microsoft Windows 8, Server 2012 and above.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;For Linux, Samba 4.0 and above supports SMB 3.0 (see&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://wiki.samba.org/index.php/LinuxCIFSKernel" rel="nofollow" target="_blank"&gt;https://wiki.samba.org/index.php/LinuxCIFSKernel&lt;/A&gt;&lt;SPAN&gt;).&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;That said, the SMB (3.x) compliancy for storage solutions never was a client golden image property only.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Apr 2021 08:33:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Thinapp-Not-Installed-on-Clients-Windows-10-20H2/m-p/2842741#M7397</guid>
      <dc:creator>DCasota</dc:creator>
      <dc:date>2021-04-20T08:33:23Z</dc:date>
    </item>
    <item>
      <title>Re: Thinapp Not Installed on Clients Windows 10 20H2</title>
      <link>https://communities.vmware.com/t5/ThinApp/Thinapp-Not-Installed-on-Clients-Windows-10-20H2/m-p/2842772#M7399</link>
      <description>&lt;LI-SPOILER&gt;You might identify which SMB version *should* and *are allowed* be used between server and client. On W10 client you can run &lt;FONT face="courier new,courier"&gt;get-smbclientconfiguration&lt;/FONT&gt; and compare &lt;FONT face="courier new,courier"&gt;EnableInsecureGuestLogons, EnableSecuritySignature, RequireSecuritySignature&lt;/FONT&gt; with the settings required from the specific file share server. Hope this helps. Daniel&lt;BR /&gt;&lt;BR /&gt;&lt;/LI-SPOILER&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Apr 2021 10:15:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Thinapp-Not-Installed-on-Clients-Windows-10-20H2/m-p/2842772#M7399</guid>
      <dc:creator>DCasota</dc:creator>
      <dc:date>2021-04-20T10:15:48Z</dc:date>
    </item>
  </channel>
</rss>

