jthompson

Seen that as a caching issue here, too. It feels like it's more likely to occur in shared drives that have a very large number of files and folders (i.e. a particularly hefty directory structure for the browser to have to cache). This might be why some staff/device combinations are appearing to be affected more than others.

Whiskonsin The Furoe Islands Purris Stroke-on-Trent

It's an idea ahead of its time. Or at least it was back in the early 90's, when Craig Charles was presenting CyberZone on BBC2, in the Def II slot after Neighbours.

If you have to post a gallery of some screenshots of some words that you've written to encourage high-quality content, you have to wonder whether the platfrom you've just bought is actually conducive to said high quality content.

Exactly correct! (I missed your anwser at first). I used to enjoy writing little programs on it. It's still my goto calculator on Android too, thanks to an emulator.

Let's try another button...

I think it can run Doom, but that doesn't narrow it down much, so here's a 2nd clue...

I found myself being charmed less with each series tbh, but will still watch series 5 when it arrives. I feel like it was getting cranked up to the "only you can save the whole world" thing that I don't really go for. What I do really like about Stranger Things is how it's a melting pot of influences, which is switched to a different cocktail with each series to give them a distinct feel. Lots of Goonies and E.T. in the first series, then Gremlins, Breakfast Club, The Thing, etc. for other series.

This was thing that probably most sparked my interest in computing.

Hey, early 1980's is still young. YOUNG!!

We've been using WisePay for a few years. I'm pretty sure it gets used for all parent payments. Certainly cashless catering, school trips and uniform, but I think we're also using it for school event tickets, too.

The spaces in those PowerShell paths will have been added automatically by EduGeek upon submission of the post. There'll be no spaces in those paths. If you're not already using AppLocker, I can recommend exploring that, as it will take care of a whole bunch of stuff for you on this front, including blocking any batch scripts other than those that you specifically allow. You'll want to take your time to get all your various rules in place first before making them all active, however. It'll block executables by default, so you'll need to add to the default allow rules as required for your environment before you start enforcing them. In AppLocker, one of the default rules is to allow everyone to run anything within %WINDIR%\*. You can block PowerShell by adding exceptions to that rule, so that the paths to the various PowerShell exes aren't allowed. As a more immediate, temporary fix, you could use Group Policy to create a little Software Restritction Policy (Computer Config > Policies > Windows Settings > Security Settings > Software Restriction Policy), set to allow by default, with rules to block the PowerShell exes. That then wouldn't interfere with anything else in the meantime.

In Group Policy being applied to your student users, "User Config > Policies > Administrative Templates > System > Prevent access to the command prompt". If that's not already enabled, enable it, but leave its option "Disable the command prompt script processing also?" set to "No" if you want to allow any logon/logoff scripts to be able to continue to work. You might also want to check whether students are able to launch any of the various PowerShell prompts. To block those, "User Config > Policies > Administrative Templates > System > Don't run specified Windows applications", adding: %SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe %SystemRoot%\system32\WindowsPowerShell\v1.0\powershell_ise.exe %SystemRoot%\SysWOW64\WindowsPowerShell\v1.0\powershell.exe %SystemRoot%\SysWOW64\WindowsPowerShell\v1.0\powershell_ise.exe If the students are using a batch script or some other script/executable to initiate those remote shutdowns, rather than doing directly from a prompt, that'd be a job for application allowlisting (i.e. AppLocker).

I did think Viewmaster, too! That and those 80's games that worked like sci-fi binoculars, that you hung around your neck. One had sharks that you had to shoot at.

If your immutable storage is being hosted by an always online on-site system, and that system gets compromised, then your immutable storage is at risk. If your immutable storage is being hosted by a cloud storage provider, then it's a different story: a compromise of your own on-site systems is not going to be posing the same level of risk.

Just upgraded GCDS to v5.0.20, and all still appears to be working okay after performing the the above steps (post #19).

The recent update to allow shared drives to be placed into OUs was really handy, as that allows for individual shared drives to be shared externally whilst keeping the defaults elsewhere to internal only.

By default we don't allow external sharing, but we allow for exemptions for certain individual staff members. This would be for things like inter-school colaboration projects where actual collaboration on files is involved. We make them agree to a discalimer type thing first (single tickbox Google Form) before adding them to group that gives them the extra privileges. Students, never.

Yes. Too easy, I think.

It's not a PlayStation.

Here's another one...

Not as such, no. You'd bascially be creating new accounts on a new domain, that just happen to have the same names, usernames, etc. There will be GUIDs and things in the background which will necessarily end up different between respective accounts on both domains. To get a usable CSV list of your users exported from your old domain, have a look at WiseSoft BulkADUsers. The attributes you want to export will just be all the obvious ones like first name, last name, job title, department, email, etc but the vast majority of user AD attribues you'll be leaving behind. With a suitable CSV export to hand, you can then look at using WiseSoft Account Management Spreadsheet to create accounts accordingly in your shiny new domain. Users will need to start off with new passwords: you won't be able to carry those across. --- Don't forget to note down which AD groups you're going to need to recreate. The tools above won't really help you with that, but with only ~40 users, that's not likely to be too onerous to rebuild by hand.

Out of interest, what sort of integration with 365 are you after?

A new from-scratch domain build is the ideal, but that that does mean having to sort out getting all your computers joined to the new domain or reimaged. If you've got more than a handful of computers, that's going to be annoying. The recreation of user accounts would be reasonably straightforward compared to that, since they lend themselves to being done in bulk. I suppose you could do a phased approach rather than a hard cutover. Build a new domain on the new server, create user accounts for everyone, and then work through the computers over a period of time, moving them to the new domain. The rest of the users/computers continue on on the 2000 domain until it's their turn to be migrated.

SharePoint list spring to mind. That would allow to you structure your data quite a bit so as to be able to include serial numbers and other asset details. There's almost certainly an asset register template that you could start it up with.