Michael

Yes - I've reported it to Microsoft via the 365 portal this morning. Users don't see any error, but the browser tab keeps on loading.

My only suggestion is try temporarily installing the Classroom.cloud App as a comparable Safeguarding App. I can't see what bearing the MDM would have, given other domestic browsers work as expected and I suspect you've tried different networks too. I realise keywords wouldn't be picked up, but it would test the browser rendering.

Thanks for confirming it is indeed a bug. 3.05's working fine for me otherwise using DHCP for Shared Ports.

Are any VOIP developers on here integrating with Bromcom as well as Arbor?

Afternoon all, Applying the latest iLO 5 3.05 firmware from 3.04, it's installed fine on most servers, however I've noticed servers with Shared Ports and static IPs thereafter are unable to connect. Servers with Dedicated Ports and static IPs continue to operate normally. By switching Shared Ports to DHCP, I'm able to connect, but back to an existing static IP or new static IP, I'm unable to connect. I've restarted iLO and tried toggling the adapter off/on within the Windows Configuration Utility. I've had some joy with this, but not in all cases. Any other suggestions, as right now it looks like a bug. Everything's been working fine on 3.04 and older firmware.

It's your O365 MX record, but this issue's now resolved with the patch.

That should do it. I untick Legacy Windows Discovery and enable SMB3 globally.

If you look at it from a historic point of view, how many times have you installed Windows 10 on devices that were only designed for XP, W7 or W8? We're all competent IT Professionals, so we make it work, even if it means searching for drivers manually online. Remember that LTSC 1809 is built on the same code as Windows Server 2019, just without the bells or whistles. Other options as mentioned already are Extended Support directly from Microsoft or of course, hardening your existing configurations with stricter software FW policies. Google Chrome will still receive continuous updates, regardless if Microsoft no longer decide to patch Edge on 22H2 for example.

I've been running/supporting LTSC 1809 for years now! Teams V2 is all going browser based, so will work in Chrome or Edge without any issues regardless of OS.

Have you upgraded the firmware on the Ricoh? Given other brands are OK, this would be my starting point. Various Papercut releases do require firmware to be upgraded for various functionality to continue working.

Similar for me - the issue was there for years too and had gone unnoticed, but only because the number of active devices on site have increased. It did completely throw me, as the errors the Windows client displays suggests it's a more major issue with the DC being offline or unavailable, with all other devices working normally, it does make you think it's a client issue.

Thanks both this makes sense now - /24 has 256 IPs and /22 has 1024 IPs, so effectively that's why the 257th IP couldn't see the DC.

Morning all, I have a query hopefully someone can clarify for me - I have a network on a /22 subnet with DHCP handled on the FW, however the DC was set to a /24 subnet, using the same IP range (static IP and gateway, just different subnet). Clients (all DHCP) were still able to authenticate against AD and for print services; everything else is in the cloud. The problem only came about whereby the first DHCP octet became full and clients couldn't contact the DC from within the second octet. With me so far? I corrected the problem by changing the DC to a /22 subnet and now DHCP clients in both the first and second octet can communicate with the DC fine. Question is, how were DHCP clients on a /22 able to communicate with a DC on a /24. This is on a flat network, single VLAN. TIA.

Possibly - just make sure it's on the latest firmware.

On the NAS, navigate to System > Settings > SMB, is SMB3 enabled globally? This is from Netgear ReadyNAS 214, so I'm guessing the 104 might be similar.

Yes - disabling the mailbox, but configuring it with permissions will still work.

Q4 2024 release, but looks promising.

That's absolutely fine. Just a case of following Google's guidelines, create a DNS record to approve the tenancy and that's it. If you're not using .sch.uk you may need to jump through a few hoops to prove you're a legal school/establishment.

This is possible if you've configured delegate printing in some form. I do exactly this for Staff > Pupil AD groups, but this means Staff can see any child's print jobs but not the other way round! I'd have a look at group memberships as a starting point.

It is a shame the DfE in the UK don't recognise this either, regardless of platform used to teach.

One issue not yet mentioned, is you can't deploy bespoke fonts. So for example every Primary teaches cursive writing.

Curious how this will sit with Safeguarding software. The more serious the keyword or phrase, the Safeguarding software generally sends a screenshot to the DSL as well the as keyword or phrased captured. It may still work, as it's running as a service rather than a key combination from the end user. The alternative is use a Smartphone or Tablet or another browser (as above). I don't see any real benefit to this new policy, as it's easy to workaround.

I can't answer your query, but have you considered WUfB? You can still stage groups of workstations to install updates at different times/days, all via GPO, on or off site.

The 2702 Fileset has now been published, so you can run Census in SIMS correctly.

I have found a small issue with NCSC's DKIM records in the following scenario - - Your DKIM key length is 1024 bit - You have Arbor CNAME selector records registered in your DNS editor - You upgrade O365 selector2 to 2048 bit and wait for keys to rotate - You then upgrade O365 selector1 to 2048 bit The end result, the NCSC portal reads O365 selector1 and one of the Arbor CNAME selector records. I'm hoping when the selector key rotation occurs a second time, the NCSC portal will correct itself to show O365 selector1 and selector2 as before. Anyone else observed this behaviour before?