I have been doing some testing with Veeam and our new 2016 deployments and I have noticed something that is causing us some issues.
We're wanting to rename the local admin account as is starting to become a security practice but with Veeam primarily it is causing us some issues.
I have renamed our local admin account to something not Administrator, when I do this with UAC enabled it fails, the SID should not have changed, it is the same account but with a different name, or does this alone change the SID even though none of the permissions have changed?
If I disable UAC it is fine.
Is there a hard coded logic in Veeam that says "Not named Administrator and UAC enabled just fail"? or is something actually changing in the rename that is breaking a permission Veeam needs?
Edit: I have confirmed the SID for the local admin account is still a 500 level account.
I have also read this applicable KB https://www.veeam.com/kb1788
But it seems to me if the SID is the same, it should work since the access hasn't changed.