Olliedawg

Put your domain name into here, will tell you if it's setup or not Network Tools: DNS,IP,Email (mxtoolbox.com)

+1 for Peasoup!

Yea i know. Running old hardware, which no longer gets security updates opens up a vector for cyber attacks. SLT in some schools don't realise this, or it isn't portrayed to them. There comes a point where things just need to be replaced. I don't think some schools realise how heavily IT is relied upon nowdays. It's effectively the backbone of 95% of daily operations I would be keen to show this to SLT - Would they want their school in the news for the wrong reasons? I highly doubt it Cyber attacks on London's hospitals affect 800 planned operations - BBC News Classes cancelled as 'sinister' school cyber-attacks rise - BBC News Cyber security breaches survey 2024: education institutions annex - GOV.UK (http://www.gov.uk)

Honestly i'd just pay for the extended support for the machines you can't upgrade in time, seems like the easiest option. If its only for one year, its not a big spend at 1$ per machine.

I believe the new teams does not support LTSC. If you are going to run LTSC, I suppose you could just run the web version of teams?

Correct answer : InTune (if you have licences for it). We're still on A1 so all of our staff laptops are Domain Joined (Hybrid). We do however use Senso so that allows for remote support / remote scripting to install software etc.

This is what SLT agreed on - Few different policies - One for 6 months, which will be the standard for majority, one for 18 months & one for 6 years (finance). I'd advised staff that they can also create new folders in their mailbox & set an individual retention policy on that folder, moving items into the folder they wish to keep for longer.

Gotcha - thank you

Ah lovely - that answers my question! When you say "new" style - do you mean 365 > Compliance > Policies > Retention

I'm looking at implementing a shorter forced retention period for all staff mailboxes (currently its 5 years - SLT have decided this is too long, which is fair enough). We currently have a single "Default Org Wide Policy" which applies to "All Mailboxes". This is set to 5 years, and set to delete when the time period is reached. My plan was to set the Default Org Wide Policy to the new agreed period of 6 months and create a second policy to explicitly include users which require a longer retention period (Finance for example). If the org wide policy is applying to all mailboxes, and I have a second policy which is explicitly targeting a user, which policy wins here? As the mailbox is technically under the scope of both of the policies. I would assume the explicit one would win? I have read conflicting answers. One being that the shortest retention period wins, another being that Explicit inclusion wins over "All Mailboxes". If anyone has any experience of this please let me know

Fantastic thank you - i will set up some users/folder structure to test this

I shall give your script a test, thank you

doh, no.. thank you

I would assume that this would work, however all of the folders I have checked do not have a .ini file (show hidden items checked in explorer)

Exactly how we do things. Works well but as you say not the best way to go about it security wise.

That would be great thank you

We have the single trunk & up to 8 concurrent calls. Are you with Gamma also?

Another +1 for 3CX. Paired with Yealink handsets, over the past 3 years zero issues really. Easy enough to manage through the web console. Over easter I moved our 3CX from a standalone aging PC running on bare windows 10, to a VM on one of our ESXi hosts. Very easy to do. Our 3CX licence costs us about £270 P/A Call costs average about £190 per month (Gamma)

We're still running 4th/5th gen intel machines here in our IT rooms, 8GB memory & a sata SSD. So not the newest hardware however these are ours on average Fresh login to generate local profile = Usually ~ 1 minute, longest I've seen was nearly 2 minutes, however this was on a crappy DFE laptop.. (yes we still have some of those "things") Login on machine student has used prior = Less than 30 seconds edit * Sorry completely overlooked that it said Windows 11. Our student machines arent on Windows 11 yet, only staff. Times above are for Windows 10

Local 100% We moved from all staff being on roaming profiles, and all students being on mandatory, to all being local. This sped up log-in times drastically & also ironed out other small issues

I'd imagine this would work as a login script, I cant see why not! Test it on a spare machine or a small group of users

Also used this. You need the bootstrapper & the msix Place them somewhere on the network accessible to users (read only perhaps) & run this (we used Senso to mass rollout) Installs the new teams, supposedly "upgrades" old teams to the new one if present, however this doesn't seem to work. I just uninstalled the old teams via GPO (we installed through GPO so was easy enough)

Good question - this is what I've inherited so I can't answer that one. Will have to wait until summer to have a look at it as i'm not overly confident with network stuff like this. Core only supports MSTP & RPVST & all of the edge switches are configured to RSTP. I believe you can mix MSTP & RSTP however not advisable?

I do have some spares (both HP and Netgear). When I get chance I i'll try one. It doesn't seem to be causing any other network issues at all - everything is normal (or seems to be). I might try disconnect both net gears at once and see what happens then

Thanks for the suggestions & yea I really do need to get them unpatched. Will be pain as I'm on my own!