We currently have the OAC client installed on all of our corporate laptops for using 802.1X wireless in the office and for connecting to outside non-802.1X access points as well. It works very well and the user is presented with a blue taskbar icon whenever there is a good connection whether it talks to the UAC or not. The end users have basically trained that the blue icon is a sure sign they have a good connection.
Now we want to use Odyssey to also manage their wired connections when in the office with 802.1X authentication. I was able to create a custom update installer that does this and it works well. The thing that has changed is that when someone is on a wireless connection and not connected via ethernet the taskbar icon is black even though they have a good wireless connection because it knows the wired one is disconnected. This doesn't happen in the reverse situation because we use wireless suppression so whenever there is a good wired connection the wireless is disabled. I had opened a case with JTAC that got escalated to engineering and even through my SE to development requesting an option that allows me to have the taskbar icon stay blue as long as there is at least one connection. The response from everyone was that this is as designed and my request could not be accommodated.
So my question to fellow users of OAC who use it both wired and wireless is how did you handle this in your organization? Did you simply tell your users that a black icon doesn't necessarily mean there is a problem?
Solved! Go to Solution.
We had the same situation with the same response. We also filed a PR through our SE. We basically had to tell our users to look at the GUI to determine status.
I, too, am dismayed by the supposed "Solution" label on this thread. A status should be just that, a true status. With the tray icon displaying "Connecting", this is an erroneous message which needs to be fixed by Juniper.