Using the BYOD Onboarding Portal

The Onboarding Portal feature provides a series of intuitive option screens that allow mobile users to choose whether to connect to a Guest WLAN or to self-configure their mobile devices to authenticate to an internal WLAN using Zero-IT activation.
To enable the Onboarding Portal for mobile devices:
  1. Go to Services & Profiles > Guest Access.
  2. Click Edit or Create New to configure a guest access service.
  3. Enable the check box next to Onboarding Portal to enable Zero-IT device registration from the Guest Portal.
  4. Select one of the following options to display when connecting to the Onboarding Portal:
    • Guest Pass + Device Registration: Show both buttons.
    • Device Registration: Show Zero-IT Device Registration button only.
  5. If Guest Pass is enabled, configure Guest Pass options as described in Working with Guest Passes.
  6. Click Apply.

When a client connects to the Open Guest WLAN for the first time, the Ruckus Onboarding Portal page is displayed. The screen displays the following three options:

  • Guest Access
  • Register Device (download Zero-IT activation file)
  • Both

If the user clicks the Guest Access button, the process is the same as when connecting to a Guest WLAN and all settings on the Guest Access configuration page will be put into effect.

If the user clicks the Register Device button, the web page will be redirected to the WLAN Connection Activation page, from which the user can enter user name and password to activate this device. A Zero-IT activation file is generated for download once the client is registered with ZoneDirector.

After running the downloaded Zero-IT file, the device will be configured with the settings to automatically connect to the secure internal/corporate WLAN.

Note: You may need to manually switch from the guest WLAN to the secure WLAN after activation (on some mobile devices).
Note: You may need to manually delete any previously installed Zero-IT activation files before a new one can be run. On some devices (including some Android versions), the activation file will not run if an older an existing package of the same name with a conflicting signature is already installed.