We have a lot of docked laptops in our environment where turning wireless off/on isn't possible.
We have ran a script on the workstations to correctly always prioritize ethernet over wireless, which works fine for clients.
The problem is when we try to remote into machines using PCanywhere in CMS, PCanywhere connects over wireless. I can see the wireless address it's trying to connect over right after accepting the cert.
We have much better success if I have technicians manually type in the ethernet address versus the given machine name that comes up, but this can be tedious sometimes to get from the client.
Is there any fix for this, how does PCAnywhere choose the address it's connecting to? When it just happened today, the IP address showing under computer name in the console was the ethernet address - not the wireless, so you'd think it'd pick that one?