This is a two part question.
1. I've just uninstalled version 1736 installed version 1833 of the full web/data endpoint client on my system to test with. When creating the 1833 endpoint package from the Triton policy server I specifically added the alternant port 80 URL for the PAC file. It seemed to be working fine over port 80 while on our internal LAN but when I connected to an external open wifi connection the auto configuration script changed the PAC file URL back to the Default port 8082 URL. I then connected back to our internal LAN and tried to change the PAC URL back to port 80 but now it will automatically change back to the default port 8082 URL. Has anyone had this problem and is there a way to force it to always use the alternate port 80 PAC file URL regardless of connection?
2. Earlier this year my user ID was moved from one OU in active directory to a new OU. When I am on the internal LAN my authentication is fine and I am authenticated as myself in the new correct OU so I receive the correct filtering policy. When I connected to an external connection to be remote filtered by the endpoint client, it is authenticating me as myself but in the old OU so it is giving me default policy access. Even the Active Directory hybrid context in Triton shows my user ID in the new correct location and I've synced it multiple times but it still filters me in the old location. Has anyone else ran into this issue?