Apply Schedules to an existing user profiles for one location (possible?)

  • 1
  • Question
  • Updated 3 years ago
  • Answered
We have added wireless to our school campus boarding hostels and I have been asked to add time schedules to this area  based on the current vlans and user profiles which are age specific.Basically Lights out at night, user profile switches off access till morning and set per age group.
Students are currently PPSK and  placed in separate user profiles assigned  to separate vlans by year group
I want to use the existing SSIDs and vlans  to avoid students having to much duplication.

My thinking has been to clone the network policy entirely
move the hostel APs to the new network policy.
clone the user profiles and add schedules to the newly created  clones only
but as soon as I edit the user profile list in the new hostel network policy it affects the original policy as well.
What am I misunderstanding? is this achievable at all without duplicating the SSIDS
the students need to be controlled by a schedule when connected to some APs and have no schedule when connect to others
Photo of Kevin Whelan

Kevin Whelan

  • 53 Posts
  • 2 Reply Likes

Posted 3 years ago

  • 1
Photo of Andrew Garcia

Andrew Garcia, Official Rep

  • 368 Posts
  • 120 Reply Likes
It sounds like you are using the same SSID profile in two different network policies.  Because the SSID object is the same, when you edit in one place, you are editing the shared SSID object in reality, which means you are changing it in both.

So, for what you are trying to do here, clone the original SSID object, give the object a different profile name, but reedit the SSID field to match that in the original SSID object (the SSID and Profile Name do not need to match in an SSID object, even though that is the default behavior).  Then you can apply the modified user profiles with time restrictions to your new SSID object.  

You can continue to use the existing Local User Groups you are using for PPSKs in the new SSID.  Just make sure the new user profiles in your new SSID are using the same user profile ID numbers as the user profiles from the original network policy.

From the student's perspective, everything appears the same.  Same SSID name to connect to, same PPSK.  But in the hostels, you would get the new time controls per user profile.

So, to sum up:

Network Policy 1
-- SSID1 ("MySSID")
-- Local User Groups (Name: Student10, Student11, Student12: UPID 10,11,12,etc)
-- User Profiles 10,11,12,etc

Network Policy 2
-- SSID2 ("MySSID")
-- Local User Groups 10,11,12,etc
-- User Profiles with Schedules (Name: StudentSched10, StudentSched11, StudentSched12: UPID 10,11,12,etc)

 
Photo of Kevin Whelan

Kevin Whelan

  • 53 Posts
  • 2 Reply Likes
thanks for the detailed answer,works perfectly in setup but need to test it with students to be sure, I would never have realised you could clone an SSID and have it work in tandem like that,That could be very useful in a lot of applications
Photo of Malcolm Snelgrove

Malcolm Snelgrove

  • 21 Posts
  • 2 Reply Likes
G'day,
I have tried doing this (two SSID objects with the same public SSID field), but scheduling SSID instead of User Profiles and at the one location. Basically I want to allow file-sharing like bittorrenting in the early hours while blocking it during the day. But it appears the clients don't see the new SSID as the same as the original no clients automatically authenticated. What went wrong?

I used schedules for the SSIDs in the same Network policy, with two User Profiles, one with a firewall to block bittorrenting and another to allow it. Same User group, (PPSK authentication) and no scheduling for the User Profiles as they are only active when the SSID is.
Photo of Malcolm Snelgrove

Malcolm Snelgrove

  • 21 Posts
  • 2 Reply Likes
G'day all,
An update that might help someone. I took a tip from a post on HM NG and created the User Profile and SSID from scratch instead of cloning them. Cloning a SSID or User Profile with other elements attached to them seems to be the problem.
Then I assign the firewall to the User profile and assign the users and user profile to the SSID. Then apply the schedule. I did have to rename the SSID to be the same name as the current one, and that allows the users to switch to the new SSID without intervention. The schedule on the current one does mean everyone gets logged off and a minute later the new SSID takes effect, but users seem to be able to log on to it.