Security

last person joined: yesterday 

Forum to discuss Enterprise security using HPE Aruba Networking NAC solutions (ClearPass), Introspect, VIA, 360 Security Exchange, Extensions, and Policy Enforcement Firewall (PEF).
Back to discussions
Expand all | Collapse all

Quickconnect requires administrative privileges on Windows

This thread has been viewed 1 times

  • 1.  Quickconnect requires administrative privileges on Windows

    Posted Jan 13, 2014 04:04 PM

    We have a Quickconnect license that we planned ot use across our campus. However, I have just discovered that in order to run the downloaded application on a Windows device, it requires administrative privileges. How have folks worked around this? The cliente that will be running Quickconnect very likely do not have administrative credentials for their computer.

     

    Ideas?



  • 2.  RE: Quickconnect requires administrative privileges on Windows

    EMPLOYEE
    Posted Jan 13, 2014 04:09 PM
    QUICKconnect was designed for BYOD devices that users control themselves. We use group policy to push wireless settings for devices not in a users control.






    Sent from Windows Mail


  • 3.  RE: Quickconnect requires administrative privileges on Windows

    Posted Jan 13, 2014 04:42 PM

    There's an audience that doesn't fall into those two camps. It cannot be assumed that everyone falls within the same domain and could have group policy pushed. Visiting persons from other universities that are using Quickconnect here on campus could easily not have administrative access.

     

    Anyone else run into this?



  • 4.  RE: Quickconnect requires administrative privileges on Windows

    EMPLOYEE
    Posted Jan 13, 2014 04:45 PM
    Doesn't OSX require admin credentials to install profiles as well?


  • 5.  RE: Quickconnect requires administrative privileges on Windows

    Posted Jan 14, 2014 10:12 AM

    Looks like you're correct, Tim. Ulgh... not cool.



  • 6.  RE: Quickconnect requires administrative privileges on Windows

    EMPLOYEE
    Posted Jan 14, 2014 10:34 AM

    I believe to configure Windows it uses netsh commands which require elevation and for OS X, profile installs require elevation. I think XpressConnect and other competing products also face this issue as it lies with the OS.