Configuration Guide
Table Of Contents
- ExtremeControl Guest and IoT Manager Configuration
- Extreme Networks® Software License Agreement
- Table of Contents
- About this Document
- New in this Document
- Guest and IoT Manager Overview
- Installing Guest and IoT Manager
- Administering Guest and IoT Manager
- Configuring Onboarding Template
- Creating an Onboarding Template
- Configuring the Common Details
- Configuring the Guest User Account Details
- Configuring Sponsor Approval
- Configuring the Device Record Details
- Configuring Device Type Groups
- Configuring the Account Notification Templates
- Configuring Advanced Details
- Configuring Guest User Provisioning Using Outlook Add-in
- Configuring Guest User Provisioning Using Vouchers
- Configuring Guest User and Device Provisioning Using CSV
- Configuring Device Record Details
- Configuring Zero Touch Guest User Provisioning
- Managing Onboarding Templates
- Configuring Custom Attributes
- Configuring Access Groups
- Creating an Onboarding Template
- Configuring Provisioners
- Configuring Self-Services
- Managing Guest Users
- Managing Devices
- Configuring Guest and Devices
- Using Self-Provisioning Services
- Guest and IoT Manager Add-In for Outlook
- Automated Login of the Guest User using the Login URL
- Troubleshooting and FAQs
- Testing RADIUS Connection Settings
- Restarting Guest and IoT Manager
- Problem: Virtual Appliance Troubleshooting
- Problem: Saving Access Control Engine Settings
- Problem: User Groups / End System Group Not Visible in Guest and IoT Manager
- Problem: Provisioner Cannot Login
- Problem: Guest and IoT Manager Email / SMS Notification Failed
- Problem: Unable to Access Guest and IoT Manager Application URL
- Problem: User and Device Troubleshooting
- Problem: Sponsor List is Not Available
- Problem: Modification in Network Interface settings does not reflect post dep...
- Problem: Outlook Add-in Issues
- Problem: Service Unavailable in Browser
- Problem: Time Zone Issues for Schedule Tasks
- Problem: Users/Devices are not getting cleaned up for Housekeeping Tasks
- Problem: Unable to Access GIM UI
- Problem: LDAP Provisioner login fails
- Problem: LDAP Sponsors are not populating in the Self-Service Page
- Problem: Server Error during bulk creation
- Problem: Unable to Renew Password
- Problem: Guest User account is not created post sending SMS
- Problem: Login URL redirects to Captive Portal
- Problem: “Server Error. Please contact Administrator Error message on clickin...
- Problem: FQDN not being used in URLs
- Problem: Unable to Customize Provisioner Login page
- Problem: Login failed. Invalid credentials/Account Expired” message on clicki...
- Problem: Outlook Add-in throws Security Exception post enabling FQDN
- Command Line Interface
Configuringthe Administrator Account
51 of 291
Setting Inactivity Timeouts
Use this procedure to modify the timeout values for Administration, Provisioner
and Outlook sessions.
Procedure
1. In the navigation pane, click Administration > Account tab.
2. In the Inactivity Timeout section, modify the duration and select the duration units
from the Idle Timeout and Outlook Idle Timeout drop-down list.
3. Click Save to save the configuration.
Field Descriptions
Use the data in the following table to use the Inactivity Timeout section.
Name Description
Admin Idle
Timeout
Displays the time-out configured in Extreme Management Center. The
timeout for administrator is from XMC but the rest are from the Guest
and IoT Manager (GIM) application.
Provisioner
Idle
Timeout
Configures the idle time-out period. The time-out period disconnects
the Provisioner Application after a period of inactivity that exceeds the
applicable threshold. You must log in again to use the application with
the new changes.
The default time-out period is 30 minutes and the maximum
period is 24 hrs.
Outlook
Idle
Timeout
Configures the idle time-out period for Outlook. The time-out period
disconnects the Outlook Application after a period of inactivity that
exceeds the applicable threshold. You must log in again to use the
application with the new changes.
The default time-out period and the maximum period is 24
hours.
Setting FQDN
Use this procedure to enable FQDN.