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
Problem: Users/Devices are not getting cleaned up for Housekeeping Tasks
272 of 291
Solution
1. Log into the GIM console and check the time zone using the show time zone
command. By default, time zone setting for GIM is in GMT.
2. Change the time zone using the timezone command in the console.
Problem: Users/Devices are not getting cleaned up
for Housekeeping Tasks
Problem
Housekeeping task is used to delete Guest Users/Devices that have their first
login pending.
For Devices/Guest Users with First login pending to be deleted before 'x' days,
the scheduled tasks considers the period of 24 hours as 1 day. Therefore, for 'x'
days the period will be 'x' * 24 hours before running the task.
For example, a scheduled task that is configured as, Delete all First Login
Pending Guest User created before 1 day but when the task is executed, the
Guest Users that were created a day before and meet this criteria are not
removed.
Solution
The time period used to identify the eligible Guest Users/Devices is calculated
from the time the task is executed. Therefore, ensure that the identification of
eligible Guest Users/Devices is calculated keeping in mind the time at which the
task executes.
For example,
If the task is defined as Delete all First Login Pending Guest Users created before
1 day. Where, the task is executed at 10 AM on the 4th June. Then all the Guest
Users created before 10 AM 3rd June are eligible for this clean up.
Similarly, if the Guest User was created on 11 AM on the 3rd June and may seem
to fit the created before one day criteria, this Guest User is not eligible for clean
up.