broadld

Yes sorry an oversight on my part we are up in North Yorkshire.

I presume if they have done this for some devices then BYOD might be affected next on Microsoft's quest for zero trust everywhere. It potentially might be a server side update that blocks this rather than a client side one.

We are in exactly the same position. For managed devices it isn't a problem but for BYOD it looks like a real pain. You have to get users to enrol for user certificates and then they use the certificate to authenticate to the wireless. Currently students struggle to install the HTTPS filtering certificate onto their devices. The other route we are looking at is using Intune Cloud PKI but all devices need to be managed by intune for this. So all BYOD devices would need to be enrolled. But then user certificates should then auto enrol for users. All early days yet but if anyone finds anything out about this and has any further ideas I would be glad to hear them.

When you say you transitioned to full 802.1X what exactly do you mean? How does this work for BYOD devices? Do users have to enrol for a certificate then use this certificate to then authenticate? What RADIUS server are you using?

If they are managed devices you can use PSK and issue device based certificates. What are people's plans for BYOD devices? We like to use RADIUS so that when a user joins the wireless with username and password they are put on the correct VLAN based on their year group. This authentication is also passed to our web filter to filter the device appropriately. Is there any like for like replacement for this? If we had one SSID for students that they connected to using a wpa key this would be quite large. We would then have to have say a captive portal that students then had to log into for authenticating them on the filter side.

Good morning everyone, Just wondering if any schools work with any 3rd party IT support companies to get support from them. Such as a yearly contract for 3rd / 4th line support for your IT team to lean on if they are unsure of anything? I would be interested if anyone has any recommendations of companies. Thanks Dave

@SIMS_Customer_Support Is this an update that will take SIMS offline to apply a database patch? I feel quite uncomfortable rushing through a patch which will have had little testing done on it in the middle of a school day. Have ESS been in touch with the DFE regarding the CENSUS return?

I have organised a trial for this so we will see if it works any better than last time we tried it.

The safeguarding side seemed to just work in v1. But the broadcast of screens and locking screens was very hit and miss. Like other have said if they got this sorted it would be great. Hoping someone can test and see if it works any better in v2.

If you can let me know if this improves the deadlocks that would be great.

Has anyone applied Patch 20352 yet and has it improved the lockouts?

That's great so literally we can get rid of the open port and the connector does it all. I suppose the good thing about doing it this way, is the user is authenticated before they even get to your system!

I presume after it is configured you have to configure your firewall to only accept traffic from Azure? Otherwise someone would still be able to access the RDWeb server directly if they got your external IP address and browsed to it.

Do you need any additional licensing in Office 365 to run an app proxy?

Hope you got this sorted. If not you need to put the vhdx file on shared storage. Shared storage in a HyperV Failocver Cluster should display in c:\clusterstorage\. There may be multiple volumes if you have different tiers of storage setup. You need to create a VM in Failocver Cluster Manager and attach the disk. If you have already created the VM in HyperV you can protect it with Cluster Manager after. Have a look at this guide from Papercut which covers quite a lot of it. It will also explain it a lot better! https://www.papercut.com/help/manuals/ng-mf/common/cluster-server-2012-2016/#:~:text=In%20the%20Failover%20Cluster%20Manager,the%20virtual%20machine%20up%20on.