Restore ACL

[jeromejas]

Does anyone know how to restore the ACL on C:\ProgramData\Veeam\ReverseProxy\Config\appsettings.json I modified the file to change the port from 443 to 8443 and now my upgrade keeps failing.

[vnikiforov]

Hello, Jerome,

The Config folder and appsettings.json each carry exactly two permission entries, SYSTEM and Administrators with Full Control, explicit with inheritance disabled, and the local Administrators group owns both. Editing the file by hand typically leaves a changed owner or an extra entry for your own account on one of them, and that is what the check trips on.
From an admin elevated command prompt:

Code: Select all

icacls "C:\ProgramData\Veeam\ReverseProxy\Config" /reset
icacls "C:\ProgramData\Veeam\ReverseProxy\Config" /inheritance:r /grant:r "NT AUTHORITY\SYSTEM:(OI)(CI)F" "BUILTIN\Administrators:(OI)(CI)F"
icacls "C:\ProgramData\Veeam\ReverseProxy\Config" /setowner "BUILTIN\Administrators"
icacls "C:\ProgramData\Veeam\ReverseProxy\Config\appsettings.json" /reset
icacls "C:\ProgramData\Veeam\ReverseProxy\Config\appsettings.json" /inheritance:r /grant:r "NT AUTHORITY\SYSTEM:(F)" "BUILTIN\Administrators:(F)"
icacls "C:\ProgramData\Veeam\ReverseProxy\Config\appsettings.json" /setowner "BUILTIN\Administrators"

The /reset first clears any extra entries, the second command applies the exact defaults.
If it is still flags other paths, restore the ReverseProxy root and Logs folders - additionally it should carry Authenticated Users with Read & Execute, and Routes matches Config.

If the above doesn't work please open a support case providing full Veeam logs in attachament.

As for the changing the port, I would not recommend doing that, until an official statement and KB article released, we identified some issues with that, so that is currently under investigation and as of yet we do not provide instructions or recommend doing that.