Dear Team,
While the failed logon event itself is expected behavior, ensuring that Veeam ONE can successfully collect data requires proper configuration of WMI and DCOM permissions on the target Windows computers. If these are not set correctly, you will see persistent data collection failures in your Veeam ONE console in addition to the initial failed logon events.
To resolve this and ensure reliable data collection, you must grant the Veeam ONE service account the necessary permissions on each monitored Windows machine.
Here are the key permissions to configure:
- WMI Namespace Security: The Veeam ONE service account needs "Enable Account" and "Remote Enable" permissions for the "Root" WMI namespace and all its sub-namespaces.
- DCOM Permissions: The service account requires "Remote Launch" and "Remote Activation" permissions for DCOM.
- Membership in Local Groups: Adding the Veeam ONE service account to the "Performance Monitor Users" and "Event Log Readers" local groups on the target machine is also recommended for comprehensive data collection.
Step-by-Step Guide to a Quieter Logbook:
For detailed, step-by-step instructions on how to configure these permissions, refer to the official Veeam documentation
By following these instructions, you will ensure that while the initial (and expected) failed logon event may still be generated, Veeam ONE will have the necessary access to perform its monitoring tasks successfully, leading to a stable and reliable monitoring environment.
Best Regards,