#1 Global Leader in Data Resilience

Disabling client authorization check on Veeam ONE Monitor Server

KB ID: 1550
Product: Veeam ONE | 6.0 | 6.5 | 7.0 | 8.0 | 9.0 | 9.5 | 10 | 11
Published: 2012-03-11
Last Modified: 2021-04-21
mailbox
Get weekly article updates
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

error icon

Oops! Something went wrong.

Please, try again later.

Purpose

There might be several reasons to disable client authorization check on the Veeam Monitor Server:

  1. It is necessary to use Veeam ONE Monitor Client outside the domain to which Veeam ONE Monitor Server belongs.
  2. ​It is necessary to disable or bypass client account authentication to connect to the Veeam ONE Monitor Server from Veeam ONE Monitor Client.

Solution

To disable client authorization check on the Veeam ONE Monitor Server, follow the next steps:

  1. Log on to the machine where Veeam ONE Monitor Server is installed.
  2. Stop the Veeam ONE Monitor Server service.
  3. Open the registry editor and navigate to the following registry key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam ONE Monitor\Service
  4. Create a new value with the following settings:

    Type - DWORD
    Name - DisableClientUserCheck
    Value data (decimal) - 1
  5. Start the Veeam ONE Monitor Server service.

NOTE: For the instructions to work, authorization has to take place on Windows level. This requires identical accounts with identical passwords to be created on Veeam ONE Server and Veeam Monitor Client machines if Veeam ONE is used in a workgroup. Additionally if the registry key noted above is not listed manually create as noted or contact support for assistance.

If these instructions do not help, the problem might be in security limitations of cross-domain network communications. Before running Veeam Monitor client, use the following command to pre-establish network connection between the two servers:
 
    net use \\your_monitor_server

You might be asked for security credentials. As a result, the network connection will be established between the Veeam Monitor Server and Veeam Monitor Client workstation. Run the Client to make sure it works.

Please note that disabling Client Authorization is an unsecure way to resolve the problem. Anyone who has Veeam Monitor Client installed would be able to connect to your Veeam Monitor Server, change settings or use remote connection to the virtual machines in your environment via the Console tab.

If you have any questions or problems, contact Veeam Support at http://www.veeam.com/support

More Information


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

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

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

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:
  • Incorrect verification code. Please try again.
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!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.