Veeam Support Knowledge Base
Unable to Connect Veeam Service Provider Console to Veeam Cloud Connect Server Using a Local Account

Unable to Connect Veeam Service Provider Console to Veeam Cloud Connect Server Using a Local Account

KB ID:	2665
Product:	Veeam Service Provider Console \| 6.0 \| 7.0 \| 8.0 \| 8.1
Published:	2018-06-12
Last Modified:	2024-08-02

By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

Oops! Something went wrong.

Please, try again later.

Challenge

Attempting to connect a Veeam Cloud Connect server through the VSPC web UI using a local account fails with the following error message:

Failed to connect to the server. Specified user is invalid or does not have enough permissions on the server.

Cause

The remote connection was blocked by UAC remote restrictions on the Windows OS of the Veeam Cloud Connect server.

Solution

When Veeam Service Provider Console Web UI is provided credentials to connect to a Cloud Connect Server to deploy the Management Agent, the user account provided must comply with the UAC remote restrictions. The account must be either:

A domain account that is a member of the Local Administrators group.

The built-in local Administrator account.
^{Note: The built-in Administrator account may fail if the "User Account Control: Admin Approval Mode for the Built-in Administrator account" policy is enabled on the remote machine.}

Local Account Workaround

If the Veeam Cloud Connect server you are trying to add is not joined to a domain, and you cannot use the Administrator account. The following method can be used to deploy the Management Agent manually.

Deploy Management Agents Manually on the Veeam Cloud Connect server you were attempting to add.
The Veeam Cloud Connect server should now appear under Clients > Discovery.
Change the Management Agent mode so that it appears under Configuration > Cloud Connect Servers:
1. Connect to the Veeam Cloud Connect server.
2. Stop the Veeam Management Agent Service service.
3. Open Registry Editor, and navigate to: HKLM\SOFTWARE\Veeam\VAC\Agent
4. Change AgentMode registry value to 3.
5. Start the Veeam Management Agent Service service.
Alternatively, run the following PowerShell script on the Veeam Cloud Connect server after manually deploying the Management Agent:

Get-Service VeeamManagementAgentSvc | Stop-Service
New-ItemProperty -Path 'HKLM:\SOFTWARE\Veeam\VAC\Agent\' -Name 'AgentMode' -Value 3 -PropertyType DWORD -Force
Get-Service VeeamManagementAgentSvc | Start-Service
                
            

The Veeam Cloud Connect server will now appear under Configuration > Cloud Connect Server.

More Information

If none of the provided solutions are viable, it is possible to disable UAC remote restrictions. This will allow local accounts other than Administrator to be used for remote access. This option should be considered a last resort as it involves disabling a Microsoft Windows OS security feature.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

Product

Topic

Description

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.

Verify your email to continue your product download

We've sent a verification code to:

An email with a verification code was just sent to

Didn't receive the code? Click to resend in sec

Didn't receive the code? Click to resend

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.