Windows 10 and Remote UAC

[j-gray 37]

We're finding lately that remote agent deployment is failing on Windows 10 workstations due to Remote UAC.

Remote UAC issues are detailed here.

So if we add the 'LocalAccountTokenFilterPolicy' registry key with the specified value, we're able to successfully install the agent via ERA server.

This seems to be a recent development as we did not have this issue in the past.

Have there been any recent changes that would cause this change in behavior? Have others encountered this and is there a recommended solution?

Thanks much.

[MartinK 384]

We have actually described it in documentation as multiple users encountered this issue when deploying AGENT in non-domain environment, where using local administrator account is crucial. We have also prepared separate Deployment tool which should help in case ERA is not in domain and security configuration does not allow to access admin share from non-domain devices.

[j-gray 37]

Thanks for the reply. However, while I am using a local admin account to run the ERA task, these systems are all domain-joined.

[MartinK 384]

21 hours ago, j-gray said:

Thanks for the reply. However, while I am using a local admin account to run the ERA task, these systems are all domain-joined.

Is ERA (Server) in the same domain as clients? I Wrote it not very clear, but this was actual problem we encountered. It affected mostly ERA Appliances, which were not joined into domain.

[j-gray 37]

2 hours ago, MartinK said:

Is ERA (Server) in the same domain as clients? I Wrote it not very clear, but this was actual problem we encountered. It affected mostly ERA Appliances, which were not joined into domain.

Yes, we have just one domain and workstations and the ERA server are all on that single domain. The ERA server is a standard Windows 2012 install, not an appliance.