Veeam Support Knowledge Base
Failed logon event generated by Veeam ONE on Windows computers

Failed logon event generated by Veeam ONE on Windows computers

KB ID:	2276
Product:	Veeam ONE
Published:	2017-04-14
Last Modified:	2023-01-12

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

Repeated audit events for failed logon with bad username or password occur on Hyper V hosts and in Veeam Backup & Replication environment. The events appear to be initiated by Veeam ONE service account.

Cause

The behavior is described in this Microsoft KB article.

Solution

Behavior by Microsoft design.

More Information

If you have any questions, contact Veeam Support.

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 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:

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.