<?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: Agent Unreachable after restore VMware Horizon Connection Server in Horizon Desktops and Apps</title>
    <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Agent-Unreachable-after-restore-VMware-Horizon-Connection-Server/m-p/2893945#M96314</link>
    <description>&lt;P&gt;Unfortunately no, What I did as solution was creating a new connection server from scratch, creating a manual pool and adding all machines to it.&lt;/P&gt;&lt;P&gt;I've used the recovered one to export the assigned users list and assigned it manually for 150 VDIs.&lt;/P&gt;&lt;P&gt;After everything was working I started to migrate them to new pools.&lt;/P&gt;</description>
    <pubDate>Wed, 16 Feb 2022 18:38:56 GMT</pubDate>
    <dc:creator>Andre_Fellipe</dc:creator>
    <dc:date>2022-02-16T18:38:56Z</dc:date>
    <item>
      <title>Agent Unreachable after restore VMware Horizon Connection Server</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Agent-Unreachable-after-restore-VMware-Horizon-Connection-Server/m-p/2820110#M92680</link>
      <description>&lt;P&gt;After a power outage I got both of my View Connection Servers unbootable with BSOD and I could not recovery it and also I don't have backup of it.&lt;/P&gt;&lt;P&gt;After all steps below I could not get things fixed, all VMs are "Agent Unreachable"&lt;/P&gt;&lt;P&gt;Created a new VM for connection server (WITH THE SAME NAME AS THE OLD "VIEWCS01")&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;Before doing it correctly I connected the base disk, and not the last snapshot, to the new VM and broke up the whole thing with the error "file system specific implementation of ioctl [file] failed", I solved this correcting the CID -&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://kb.vmware.com/s/article/1007969" target="_blank" rel="nofollow noopener noreferrer"&gt;https://kb.vmware.com/s/article/1007969&lt;/A&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;UL&gt;&lt;LI&gt;Installed Windows (Same version)&lt;/LI&gt;&lt;LI&gt;As in&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://kb.vmware.com/s/article/76770" target="_blank" rel="nofollow noopener noreferrer"&gt;https://kb.vmware.com/s/article/76770&lt;/A&gt;:&lt;UL&gt;&lt;LI&gt;Installed Connection Server (Same Version)&lt;/LI&gt;&lt;LI&gt;Restored LDF backup&lt;/LI&gt;&lt;LI&gt;Removed all View Connection Servers and all Security Servers&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;(vdmadmin -S -s -r viewcs01, viewss01 and viewcs02)&lt;/LI&gt;&lt;LI&gt;Uninstalled the connection server&lt;/LI&gt;&lt;LI&gt;Reinstalled the connection server reusing the AD LDS&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;I did removed the "viewcs01" because with my previous tests I was not removing it, I think because of &amp;gt;this, after the recovery steps done no console was opening, In previous tests I also not using the old &amp;gt;machine name, instead of it I was using "viewcs03".&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Ok, Console opened, I changed the vCenter credentials (Just putting password was not working with error -&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://kb.vmware.com/s/article/60152" target="_blank" rel="nofollow noopener noreferrer"&gt;https://kb.vmware.com/s/article/60152&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;- Log below:&lt;/P&gt;&lt;PRE&gt;2020-12-31T18:23:48.108-02:00 ERROR (18F8-0D0C) &amp;lt;MessageFrameWorkDispatch&amp;gt; [ws_java_bridgeDLL] BCryptDecrypt FAILED, status={Data Error}
An error in reading or writing data occurred. (0xC000003E)
2020-12-31T18:23:48.109-02:00 ERROR (18F8-0C54) &amp;lt;VCHealthUpdate&amp;gt; [SecurityManagerUtil] decryptAsText: com.vmware.vdi.crypto.SecurityManagerException: decrypt: Cannot decrypt: Cipher scheme decryption failed.
2020-12-31T18:23:48.109-02:00 DEBUG (18F8-0C54) &amp;lt;VCHealthUpdate&amp;gt; [ServiceConnection25] Connecting instance VCHealth Test instance at URL https://vcenterd.DOMAIN.net:443/sdk&lt;/PRE&gt;&lt;P&gt;Corrected Composer credentials, and added license.&lt;/P&gt;&lt;P&gt;All machines are "Agent Unreachable" - Connection Server Log below:&lt;/P&gt;&lt;PRE&gt;2020-12-31T18:23:49.160-02:00 DEBUG (18F8-1A6C) &amp;lt;DesktopControlJMS&amp;gt; [DesktopTracker] CHANGEKEY message from agent/bda3fbe6-029c-41f8-b9f8-017af574f56b accepted as key and thumbprints match machine record
2020-12-31T18:23:49.162-02:00 DEBUG (18F8-1A6C) &amp;lt;DesktopControlJMS&amp;gt; [DesktopTracker] found broker thumbprints: 0f:9e:80:5d:f6:33:c7:1b:a2:d5:8c:9a:9f:12:45:16:0f:6f:c0:2b:46:8d:d0:33:62:87:53:a9:48:8d:57:8c#SHA_256;51:c5:d0:44:02:7f:ca:6d:5a:ad:5b:f6:8d:f5:11:23:e8:aa:e1:91:d0:5c:ff:71:3b:fb:e2:4b:f4:12:5e:d5#SHA_256
2020-12-31T18:23:49.162-02:00 WARN  (18F8-1A6C) &amp;lt;DesktopControlJMS&amp;gt; [JMSMessageSecurity] Failed to sign message: Cannot sign message
2020-12-31T18:23:49.162-02:00 DEBUG (18F8-1A6C) &amp;lt;DesktopControlJMS&amp;gt; [DesktopTracker] CHANGEKEY message from agent/bda3fbe6-029c-41f8-b9f8-017af574f56b result: true (success)&lt;/PRE&gt;&lt;P&gt;Excerpt from VM agent log:&lt;/P&gt;&lt;PRE&gt;2020-12-31T19:53:44.322-03:00 DEBUG (1EDC-0FA8) &amp;lt;Thread-4&amp;gt; [AgentJmsConfig] Using paired signing key
2020-12-31T19:53:44.322-03:00 DEBUG (1EDC-0FA8) &amp;lt;Thread-4&amp;gt; [AgentMessageSecurityHandler] Configuring message security (ENHANCED).
2020-12-31T19:53:44.369-03:00 DEBUG (1EDC-0FA8) &amp;lt;Thread-4&amp;gt; [BrokerUpdateUtility] Published CHANGEKEY request
2020-12-31T19:53:59.386-03:00 DEBUG (1EDC-0FA8) &amp;lt;Thread-4&amp;gt; [BrokerUpdateUtility] Timeout waiting for success response
2020-12-31T19:59:33.944-03:00 DEBUG (1430-2558) &amp;lt;Thread-4&amp;gt; [JmsManager] Using connection broker viewcs01.DOMAIN.net
2020-12-31T19:59:33.944-03:00 DEBUG (1430-2494) &amp;lt;MessageFrameWorkDispatch&amp;gt; [MessageFrameWork] KeyVault service got operation=getEndEntityCertificates, ok=1, msecs=0
2020-12-31T19:59:33.944-03:00 DEBUG (1430-2494) &amp;lt;MessageFrameWorkDispatch&amp;gt; [MessageFrameWork] KeyVault service got operation=getEndEntityCertificates, ok=1, msecs=0
2020-12-31T19:59:33.975-03:00 DEBUG (1430-2558) &amp;lt;Thread-4&amp;gt; [JmsManager] username for swiftmq connection is: agent/90916ab8-704c-4fe3-a605-c4a7745b246e
2020-12-31T19:59:33.975-03:00 DEBUG (1430-2558) &amp;lt;Thread-4&amp;gt; [AgentJmsConfig] Skipping pair operation: already paired
2020-12-31T19:59:33.975-03:00 DEBUG (1430-2558) &amp;lt;Thread-4&amp;gt; [AgentMessageSecurityHandler] Configuring message security (ENHANCED).
2020-12-31T19:59:33.975-03:00 DEBUG (1430-2558) &amp;lt;Thread-4&amp;gt; [JmsManager] Re-connecting using secure port 4002
2020-12-31T19:59:34.381-03:00 DEBUG (1430-2780) &amp;lt;SwiftMQ-ConnectorPool-2&amp;gt; [AgentSSLSocketFactory] Received cert with subject cn=router/viewcs01
2020-12-31T19:59:34.381-03:00 WARN  (1430-2780) &amp;lt;SwiftMQ-ConnectorPool-2&amp;gt; [AgentSSLSocketFactory] Certificate thumbprint verification failed, no matching thumbprint. Presented identity: router/viewcs01
2020-12-31T19:59:34.381-03:00 DEBUG (1430-2558) &amp;lt;Thread-4&amp;gt; [JmsManager] Unable to connect to JMS server viewcs01.DOMAIN.net com.vmware.vdi.logger.Logger.debug(Logger.java:44)
javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Unexpected certificate: router/viewcs01
2020-12-31T19:59:34.381-03:00 WARN (1430-2558) &amp;lt;Thread-4&amp;gt; [JmsManager] Unable to connect to any listed host. The agent will continue to retry: [viewcs02.DOMAIN.net, viewcs01.DOMAIN.net]&lt;/PRE&gt;&lt;P&gt;Reinstalled the agent and also tried the command below, as mentioned in&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://kb.vmware.com/s/article/2038679" target="_blank" rel="nofollow noopener noreferrer"&gt;https://kb.vmware.com/s/article/2038679&lt;/A&gt;, nothing has worked at all.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;vdmadmin -A -d desktop-pool-name -m name-of-machine-in-pool -resetkey&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 31 Dec 2020 23:30:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Agent-Unreachable-after-restore-VMware-Horizon-Connection-Server/m-p/2820110#M92680</guid>
      <dc:creator>Andre_Fellipe</dc:creator>
      <dc:date>2020-12-31T23:30:22Z</dc:date>
    </item>
    <item>
      <title>Re: Agent Unreachable after restore VMware Horizon Connection Server</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Agent-Unreachable-after-restore-VMware-Horizon-Connection-Server/m-p/2893942#M96313</link>
      <description>&lt;P&gt;Did you ever get a solution on this?&lt;/P&gt;</description>
      <pubDate>Wed, 16 Feb 2022 18:15:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Agent-Unreachable-after-restore-VMware-Horizon-Connection-Server/m-p/2893942#M96313</guid>
      <dc:creator>heimdm</dc:creator>
      <dc:date>2022-02-16T18:15:48Z</dc:date>
    </item>
    <item>
      <title>Re: Agent Unreachable after restore VMware Horizon Connection Server</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Agent-Unreachable-after-restore-VMware-Horizon-Connection-Server/m-p/2893945#M96314</link>
      <description>&lt;P&gt;Unfortunately no, What I did as solution was creating a new connection server from scratch, creating a manual pool and adding all machines to it.&lt;/P&gt;&lt;P&gt;I've used the recovered one to export the assigned users list and assigned it manually for 150 VDIs.&lt;/P&gt;&lt;P&gt;After everything was working I started to migrate them to new pools.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Feb 2022 18:38:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Agent-Unreachable-after-restore-VMware-Horizon-Connection-Server/m-p/2893945#M96314</guid>
      <dc:creator>Andre_Fellipe</dc:creator>
      <dc:date>2022-02-16T18:38:56Z</dc:date>
    </item>
  </channel>
</rss>

