Skip to main content
Solved

VSPC failing to connect to Cloud Connect – “Failed to connect to the deployment service”

  • January 12, 2026
  • 5 comments
  • 72 views
C

I’m unable to connect VSPC to Cloud Connect. When I try to add the Cloud Connect server from Configuration → Catalog → Veeam Cloud Connect, it fails with “Failed to connect to the deployment service.” I’ve already tried disabling Windows Firewall and antivirus, but the issue persists. I can install the agent manually on the Cloud Connect server without any errors; however, after installation, the server only appears under Discovery in VSPC and does not show up under Catalog → Cloud Connect → Veeam Cloud Connect Integration. Both servers are on the same subnet with no firewall in between. 

 

Best answer by Mohamed Ali

​@chamandeep  We had similars issue during the VCSP 9 upgrade and it was fixed by 

  1. Stop the Veeam Management Agent Service. 
  2. Edit the json file "C:\ProgramData\Veeam\Veeam Availability Console\Configuration\Agent\configuration.overrides.json" 
  3. Find the “Agent_AgentMode” entry and change it to 3 
  4. Start the Veeam Management Agent service

 

      5 comments

      Chris.Childerhose
      Forum|alt.badge.img+21
      • Chris.Childerhose
      • Veeam Legend, Veeam Vanguard
      • January 12, 2026

      Be sure the credentials you are using are local Administrator access.  If you install the agent manual you can move it to VCC using this registry key -

      • Solution: Connect to the Veeam Cloud Connect server machine, stop the Veeam Management Agent Service service, and open the Windows Registry Editor. Navigate to HKLM\SOFTWARE\Veeam\VAC\Agent and change the AgentMode DWORD value to 3. Restart the Veeam Management Agent Service. The server should then appear under Configuration > Cloud Connect Servers in VSPC.
      Chris Childerhose (Enterprise Architect) - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 6* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
        Mohamed Ali
        Forum|alt.badge.img+2
        • Mohamed Ali
        • VUG Leader
        • Answer
        • January 13, 2026

        ​@chamandeep  We had similars issue during the VCSP 9 upgrade and it was fixed by 

        1. Stop the Veeam Management Agent Service. 
        2. Edit the json file "C:\ProgramData\Veeam\Veeam Availability Console\Configuration\Agent\configuration.overrides.json" 
        3. Find the “Agent_AgentMode” entry and change it to 3 
        4. Start the Veeam Management Agent service

         

        Mohamed Ali | VUG leader | VMCE 2024, VCP-DCV, CCP-V
          C
          • chamandeep
          • Author
          • Not a newbie anymore
          • January 13, 2026

          Thank you,

          First I did this - HKLM\SOFTWARE\Veeam\VAC\Agent and change the AgentMode DWORD value to 3 - it didnt work. I left the value as 3, 

           

          Then I followed this -

          1. Edit the json file "C:\ProgramData\Veeam\Veeam Availability Console\Configuration\Agent\configuration.overrides.json" 
          2. Find the “Agent_AgentMode” entry and change it to 3

          It worked. thank you all for your support

            Chris.Childerhose
            Forum|alt.badge.img+21
            • Chris.Childerhose
            • Veeam Legend, Veeam Vanguard
            • January 13, 2026

            Great to hear you solved it.  The registry key might have been from an older release of VSPC and now the v8+ needs the json file.  Glad it worked out.

            Chris Childerhose (Enterprise Architect) - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 6* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
              HangTen416
              Forum|alt.badge.img+11
              • HangTen416
              • Influencer
              • February 2, 2026

              ​@chamandeep  We had similars issue during the VCSP 9 upgrade and it was fixed by 

              1. Stop the Veeam Management Agent Service. 
              2. Edit the json file "C:\ProgramData\Veeam\Veeam Availability Console\Configuration\Agent\configuration.overrides.json" 
              3. Find the “Agent_AgentMode” entry and change it to 3 
              4. Start the Veeam Management Agent service

               

              ​@Mohamed Ali Do you now what the other Agent_AgentMode settings are for? i.e. 3 is for VCC mode. What’s the other mode(s)?

              VMCE2024 | VMCA2022
                Terms & ConditionsAccessibility statement