Hi Rehan, If my memory serves me right, this is a Windows restriction, where it will only allow one service to manage the wireless connections. I remember trying to get OAC working for the office, and Windows for home on both Windows XP Pro, and Windows 7, where I eventually just gave up, and used OAC for everything. I was actively switching between the 2 services at one point in this effort, but it did require local admin privileges on the laptop, and it was not something the average user would find simple.
Given that this was over a year ago that i gave up the effort, i wouldnt be able to tell you off the top of my head what exactly i was doing, but it did involve accessing the "Services" under Administrative Tools in the Control Panel of Windows every time i wanted to switch between OAC and Windows. Hope that helps, Mike On Wed, Oct 3, 2012 at 8:24 AM, Rehan Rafi <rrk....@gmail.com> wrote: > Dear All, > > Hopefully you all are doing fine. > > One of our customer has a wearied requirement related to Juniper Odyssey > Access Client that he don't want to use OAC at home wireless network and > want to use Widows wireless settings to connect. > > If above is do able, knowing client does not have permission to change OAC > settings. Can we force windows settings to take preference over OAC? > > -- > > Regards, > > Rehan Rafi > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp