https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyMzU5IiwiaGFzaCI6ImI1MmViNzg3LTk2MjMtNDVhNi1iNzQyLTk5YTA0OGJmYTEwMCJ9
1-800-691-1991 | 9am - 8pm ET
EN

Bad Hyper-V Username Logon Attempt

Challenge

Veeam ONE raises the following event-based alarm: Bad Hyper-V username logon attempt.

Cause

The Bad Host Username alert suggests that someone is attempting to access the host with an invalid username or password.

Solution

Veeam ONE raises the Bad Hyper-V username logon attempt alarm based on the Hyper-V event that is received from the MS Hyper-V host:
 
4625 Microsoft-Windows-Security-Auditing

The further issue troubleshooting should be performed on the MS Hyper-V server side.

If you would like to find out the root cause of the event, investigate the Security log on your Hyper-V host > Computer Management > Event Viewer > Windows Logs. Find the event record mentioned above and see the details.
 

More information

In case you cannot find the event record or the record details refer to Veeam ONE server, please contact Veeam Support for further assistance.
KB ID:
2359
Product:
Veeam ONE
Version:
9.x
Published:
2017-10-12
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later