How to Fix Veeam Agent Installation Error

Veeam Backup & Replication agent installation errors with a disabled account message and ADMIN$ share connection issues typically indicate network security configuration or access management problems. This error often occurs due to incorrect security policy settings, firewall restrictions, or Windows administrative share access rights issues. The primary solution involves checking network settings, configuring accounts, and optimizing system security parameters.

---

Table of Contents

• Main Causes and Problem Diagnosis
• Network Access and Firewall Checking
• Account Configuration and Access Rights
• Additional Troubleshooting Methods
• Alternative Installation Approaches

---

Main Causes and Problem Diagnosis

Connection error to 0.0.0.0 with a disabled account message is typically caused by one of the following issues:

1. Incorrect RPC (Remote Procedure Call) configuration - despite opening ports, additional settings may be required
2. Restrictions on administrative share access - problems with access rights to ADMIN$ share
3. Authentication issues - the account may actually be disabled or have restrictions
4. Security policy conflicts - local or group policies blocking the installation

To diagnose the issue, perform the following checks:

1. Check account status:

   powershell

   net user | findstr "Active"
   

2. Check ADMIN$ share availability:

   powershell

   net share ADMIN$
   

3. Test connection to administrative share:

   cmd

   net use \\localhost\ADMIN$ /user:your_user password
   

Network Access and Firewall Checking

Your current RPC port opening settings are correct, but may require additions:

1. Add rules for SMB and WMI:

   cmd

   netsh advfirewall firewall add rule name="Open SMB In" dir=in protocol=TCP localport=445 action=allow
   netsh advfirewall firewall add rule name="Open WMI (DCOM)" dir=in protocol=TCP localport=135 action=allow
   netsh advfirewall firewall add rule name="Open RPC Endpoint Mapper" dir=in protocol=UDP localport=135 action=allow
   

2. Check and add rules for Veeam:

   cmd

   netsh advfirewall firewall add rule name="Veeam Backup" dir=in action=allow program="C:\Program Files\Veeam\Backup and Replication\Backup\Veeam.Backup.Service.exe" enable=yes
   

3. Temporarily disable firewall for testing:

   cmd

   netsh advfirewall set allprofiles state off
   

Important: Disabling the firewall is for diagnosis only. After resolving the issue, be sure to re-enable it.

Account Configuration and Access Rights

The “disabled account” issue is often related to incorrect access rights configuration:

1. Check and activate accounts:

   cmd

   net user administrator /active:yes
   

2. Assign necessary rights:

   cmd

   net localgroup administrators "your_user" /add
   net localgroup "Remote Desktop Users" "your_user" /add
   net localgroup "Performance Log Users" "your_user" /add
   

3. Configure local account security policy:

   cmd

   secpol.msc
   

   • Navigate: Local Policies → Security Options → Account Policies
   • Set “Access: User account control behavior of the internal administrator account” to “Disabled”

4. Check and modify registry parameters (if not done previously):

   cmd

   reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f
   reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v EnableLUA /t REG_DWORD /d 0 /f
   

Additional Troubleshooting Methods

If standard methods don’t work, try the following approaches:

1. Using the system account:

   cmd

   net user "NT AUTHORITY\SYSTEM" /add
   net localgroup administrators "NT AUTHORITY\SYSTEM" /add
   

2. Check RPC service:

   cmd

   sc query rpcss
   sc config rpcss start= auto
   net start rpcss
   

3. Reset security policies:

   cmd

   secedit /configure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verbose
   

4. Check registry for restrictions:

   cmd

   reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v LocalAccountTokenFilterPolicy
   reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v EnableLUA
   

5. Temporarily disable UAC:

   • Via registry:
     cmd

     reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v EnableLUA /t REG_DWORD /d 0 /f
     

   • Or via command prompt:
     cmd

     %windir%\System32\cmd.exe /k %windir%\System32\reg.exe add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v EnableLUA /t REG_DWORD /d 0 /f
     

Alternative Installation Approaches

If the issue persists, consider alternative agent installation methods:

1. Installation via Veeam Management Console:

   • Launch the Veeam console
   • Go to “File” → “Add server” → “Windows as a guest OS”
   • Follow the wizard instructions

2. Manual agent installation:

   • Copy the agent files from the Veeam server
   • Perform manual installation:
     cmd

     msiexec /i "Veeam Agent for Windows.msi" /quiet /norestart
     

3. Installation using Windows Management Instrumentation (WMI):

   • Ensure WMI service is running:
     cmd

     winmgmt /verifyrepository
     winmgmt /salvagerepository
     

   • Try installing via WMI:
     powershell

     Invoke-WmiMethod -Path "Win32_Product" -Name "Install" -ArgumentList "C:\path\to\veeam.msi"
     

4. Using a domain account:

   • If the server is domain-joined, use a domain administrator account
   • Ensure the account has “Full control” rights on the target server

5. Check version compatibility:

   • Ensure the agent version matches the Veeam server version
   • Verify Veeam agent 12.3.1 system requirements

---

Conclusion

The main solutions for the Veeam agent installation error with a disabled account message are:

1. Complete network settings check - ensure all required ports (135, 445, 49152-65535) are open and accessible
2. Proper account configuration - verify account activity and assign necessary rights
3. Security parameter optimization - configure LocalAccountTokenFilterPolicy and temporarily disable UAC for testing
4. Alternative installation methods - use the Veeam Management Console or manual installation if automatic installation doesn’t work

To prevent similar issues in the future, it’s recommended to:

• Regularly update Veeam to the latest version
• Use specialized Veeam accounts with minimal necessary rights
• Automate network configuration verification before installation

If the issue persists, contact Veeam technical support, providing installation logs and network diagnostic results.

Sources

1. Veeam Backup & Replication Documentation - Agent Installation
2. Microsoft TechNet - Windows Firewall Configuration
3. Veeam Community Forums - Installation Issues