#1 Global Leader in Data Protection & Ransomware Recovery

Veeam ONE creates or changes local accounts of the "Veeam_*" format at the Veeam ONE server machine

KB ID: 4042
Product: Veeam ONE
Published: 2020-11-06
Last Modified: 2020-11-10
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.

Challenge

Veeam ONE creates or changes local accounts of the "Veeam_*" format on the Veeam ONE server machine.

Cause

This behavior is a part of the Veeam ONE design. Veeam ONE creates these temporary Windows accounts for login and authentication operations between Veeam ONE components and VMware virtual servers with VMware local or Single Sign-On users, which are not present on the Veeam ONE machine or in the AD domain. These accounts also act as "Tenants".
kb4042
These temporary accounts are normally present on the Veeam ONE server during the user session plus 30 days. Another purpose, besides the authentication, is to cache the information about VMware topology objects available for the Tenant user, so that during this 30-days inactive period, the Tenant user may quickly log in again.

Solution

The use of these aliases cannot be disabled, however, the retention period (30 days of inactivity after last user session) can be changed in the registry. It is controlled by the value HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam ONE Monitor\Service\InactiveLocalUserKeepIntervalSec (DWORD), which equals 2592000 seconds (30 days) by default.

Note that 0 value means that these users will not be deleted (no retention period), so for the immediate removal, the value must be set to 1 second.

To match the actual users and their temporary account aliases, Veeam ONE uses the "Veeam_<USER5><1A3B5C7D>" format , where "<USER5>" contains five first letters of the username used for authentication, and "<1A3B5C7D>" is a hash-code based on the username and password.

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 reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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 reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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.