Jared Fowkes 0 Posted February 27 Share Posted February 27 We have an ESET network profile for our company with a single activator: "Windows profile: Domain". Users in branch offices get this profile correctly. However, remote employees, who are connected to company-provided gateways, do not - even though Windows shows that the connection profile is indeed "Domain". This was verified by running `Get-NetConnectionProfile`. The only thing that seems to link the affected systems is that they are on remote gateways in their home instead of a branch office. The DNS, hostname, and connection profiles are otherwise identical. Expected: Company network profile be applied by ESET. Actual: Public network profile is applied by ESET. Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,082 Posted February 27 Administrators Share Posted February 27 This will need to be checked by the technical support or developers. Please raise a support ticket. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.