use of the LocalAccountTokenFilterPolicy registry key

[karim]

Hello,
i have a question about the LocalAccountTokenFilterPolicy registry key
when i've installed for the first time my veeam infrastructure i added this registry key on my windows server 2016 proxies to permit the veeam services installation). theses servers were in WORKGROUP mode.
now they joined our Active Directory domain, so i deleted this key and recreated the proxies on veeam, but sometime they became unavailable. i recreated the key and now it's all good.

i thought that this key was mandatory only for servers in workgroup mode. does we have to always add this key for proxy installation ?

thank you for your replies.

[HannesK]

Hello,
no, in general this key is not required.

Best regards,
Hannes

[karim]

thank you for your reply,
but how can you explain that the managed server became more available when i added this key ?!
before that, servers were unavailable several times in a day

[Vitaliy S.]

This key does not make servers more available, so that might be a coincidence. What were the error messages you saw for these servers?

[karim]

there was no message, only the red cross
i will retry this

[Vitaliy S.]

Do you have Veeam ONE by any chance? If yes, then it can tell you the exact time and the error message observed for these servers.

[karim]

no sorry

[karim]

after deleting this key the 2 servers are unavailable after a certain time, if i rescan them they become available
https://ibb.co/KXMmtjn

[karim]

i got it, when one of the proxy was unavailable one of the backup has failed with this message : "failed to connect to the port proxy:2500"
i dont' know why i get this message, everything is ok on our firewalls.

[karim]

i deleted the registry key for the week-end and everything is ok...effectively a coincidence like you said. sorry for the noise.

[Vitaliy S.]

For the network related problem, try reviewing a Windows Event log to see if there are any error messages happening at the same time as the main error.