TwistedHelixis

@Koldov thanks, ill take a look at those links

Yes I do have Authenticated Users The first GPO that I noticed not applying was the 'Local Users and Groups' policy. I have also just noticed the policy seems to not be applying to our pupil laptops / devices only, but is still applying to our teaching staff. Does that take us any closer to working out whats going on? I assumed all domain users (teachers and pupils) are automatically added to 'Authenticated users', perhaps this is not the case.

Have you noticed (or checked) any 'Computer' based polices that have recently stopped working? Wondering why I now need to add 'Domain computers' to get the policy applying.

removed

Just found this, so they both do the same thing, more or less.

I have no idea if that does the same thing, I just have 'authenticated users' listed there. Perhaps someone else can answer if they do the same job, or which I should be adding 'domain computers' onto.

So office 2013 pro got about 8 years, but Office 2019 gets about 4 years, is that correct? Some of my schools have already jumped to Google, this might push the other schools over.

I just noticed that some of my computer based policies are no longer applying on some computers. After a bit of hunting round, I fixed the issue by adding 'Domain computers' to the 'Delegations' tab in the GPO. So whats going on? Was 'Domain computers' there originally, but MS has been removed from the GPOs at some point. Did MS make a change that now requires 'Domain computers' under the delegation tab at some point?

Let me know how that goes [emoji3526]

I think Arbor has a plugin that can provision users in Google Workspace, so no need for Salamander in this case.

In the end I just created an email alias for that user in our Google system and used that alias as the ASM account.

I was told by Microsoft not to do this as it can cause some kind if island issue with the data. I have Primary DNS of DC1 set to the IP of DC2. Secondary DNS set to IP 127.0.0.1 Primary DNS of DC2 set to the IP of DC1. Secondary DNS set to IP 127.0.0.1

You should still have backups. Its a requirement from our insurance company that we have both offsite and offline backups, even though all our data is cloud based.

Well she typed her password into FMS today and it logged in. So all good now.

Just had our bursar email me saying she has locked herself out of FMS. I didn't think FMS had a password lockout. Does FMS have a password lockout?

Just been asked to allow Chat GPT through our filtering, so the Year 5 pupils can use it for writing prompts. Is this a good idea?

So, if I use Windows backup to take backups of my Hyper-V vms, In theory, after this update has applied to both the host and VMs, all backups after that should contain the new secure boot info and be restorable / bootable. Its only the backups taken before this months updates that will not be bootable. Is that correct??

Cubebackup will send you an email each night listing how much data was backed up and if there were any issues. I actually find Cubebackup more reliable than Spanning. Every once in a while I'll do a restore and its always been fine (touch wood). The only time I need to make any changes is when I add or remove a shared drive or add remove staff etc. EDITED

brilliant, thanks :-)

I am just trying to do the same, following the same guide - https://learn.microsoft.com/en-us/deployoffice/ltsc2021/deploy I cant even download the office 2021 deployment tool from their website- https://www.microsoft.com/en-us/download/details.aspx?id=49117 Is it a problem their end or am I doing something wrong?

Just taken a look at some of my computer OUs in AD and there are a load of computers listed, I am sure most are no longer even in service. Is there an easy way to workout which computers I can delete?

I recently went from Spanning to Wasabi & Cubebackup. Its more hands on but much cheaper. I also do a monthly onsite backup also using Cubebackup which gets turned off between backups.

Creating a scheduled task script that stops and starts the NLA service a few minutes after a reboot seems to be the simplest fix.

Lot of people with the same issue as me and also different ideas / solutions on this forum, so I will work through those. https://community.spiceworks.com/topic/2205082-new-server-2019-dc-keeps-setting-network-location-to-private-why

Sorry I was not very clear in my previous posts, the issue I am having is on my DC. After a reboot it connects to the network and internet through the Private firewall, not the Domain firewall. But if I restart the NLA service on the DC it then connects to the network and internet through the Domain firewall.