halbaradkenafin

How much permission do they need? Write? Modify? Read? No need to give them full control if they only need to be able to view the pupil work.

It's possible, I can probably put something together using Powershell to get the folder names. But why not apply the permissions at the parent folder that holds all the pupil folders? If you're granting permissions to almost all the folders the pupils have anyway then it seems like the quickest and easiest option, plus there are usually pupils who don't save things in the documents folder despite being told to (unless they don't have permissions to save there).

That's why I play Monk. I can heal and dps at the same time, which is pretty useful since my guild usually brings one too many healers anyway.

Try outputting to a csv on the test PC. It could be that it doesn't have permissions to access the drive on the DC.

Anything in the Event Log for the PC? Should be something showing up for start up GPOs and the scripts. Other option would be to throw in some output to a file on the C: to ensure the script is actually running and then you can figure out if it's the script or the startup process that is the problem.

We're currently using MDT for OS deployment but transitioning to SCCM as we use that for some packages (GPOs for others) and want to have it all managed centrally. SCCM can be a little slow to deploy things sometimes but it gets the job done and the reporting and logging is very good.

I came up with a script for this in Powershell a while back. I want to update it with some stuff from the NTFS Security module that was released after I created it but it works fine for this scenario. $Folders = Get-childItem -Path "" $InheritanceFlag = [system.Security.AccessControl.InheritanceFlags]::ContainerInherit -bor [system.Security.AccessControl.InheritanceFlags]::ObjectInherit $PropagationFlag = [system.Security.AccessControl.PropagationFlags]::None $objType = [system.Security.AccessControl.AccessControlType]::Allow foreach ($TempFolder in $Folders) { Write-Output -InputObject "Loop Iteration" $Folder = $TempFolder.FullName $UserFolder = $TempFolder $acl = Get-Acl -Path $Folder Write-Output -InputObject "\$UserFolder" $permission = "\$UserFolder","FullControl", $InheritanceFlag, $PropagationFlag, $objType $accessRule = New-Object System.Security.AccessControl.FileSystemAccessRule $permission $acl.SetAccessRule($accessRule) Set-Acl -Path $Folder -AclObject $acl } Drop it into a ps1 file on your file server, I'd suggest running it from a powershell prompt rather than just right clicking it (or from the Powershell ISE) and that way you'll see any errors (hopefully there aren't any).

You can do this with Powershell using the following code but needs to be run as admin: if ((Get-Service "ImperoClientSVC").Running -eq Stopped) { Start-Service "ImperoClientSVC" } Throw it into a ps1 file and set a scheduled task to run it every x minutes (not 100% sure how you'd set Powershell to run as admin like this but Google should tell you) and you should be sorted.

I'd advise that you just disable the computer accounts and move them to an OU for it. Then in a month or two when no one reports any issues you can delete them.

Remove-Item -Path $File.FullName -WhatIf Recursive searches always get me like that, need to make a big note of it and stick it to my desk to remind me.

That was me being an idiot with the script. The line should be: Remove-Item -Path ($Path + $File) -WhatIf And change $Path to include a \ at the end.

Sounds like a job for Powershell rather than VBScript as I'm not sure how easily VBScripts handles recursively checking folders. #Path to backup folder $Path = "D:\SUNSQLBackups" #Get every item in the folder and all sub folders foreach ($File in (Get-ChildItem -Path $Path -Recurse)) { #Check if age is older than 5 days if ($File.LastWriteTime -le (Get-Date).AddDays(-5)) { #Remove file Remove-Item $File -WhatIf } } I'd suggest running it once first with the -WhatIf set on Remove-Item to ensure that it's picking up the correct files you want to remove (replace it with -Confirm:$False so you don't have to hit enter each time it finds a file), you can adjust the (Get-Date).AddDays(-5) to scale the amount of days you want to limit it to.

That would have been sensible. I'll PM you with my email and name so you can match them up.

Submitted.

I'd suggest trying to restart the Impero service on an effected machine, if that doesn't fix it then try restarting the server service. I've seen that resolve most of the issues with the client, though the service can take a little while to restart properly and let you access the client. If that fails I'd check the access rights in the server, it's unlikely to have changed but you might want to double check anyway.

OnePlus One on EE but my contract is up soon and I'll be shopping around as I need more data than my previous plan and don't want to keep paying the top up cost for more data on EE.

That's pretty awesome of them. I might have to pick one of these up for a project I had in mind, it probably doesn't need the extra processing power compared to the B or A I already have but always useful to have it anyway.

Is this for the actual AD objects for the user or for their folders or for something else? Should be easy enough to do using ACLs

I've got a similar script which takes all the userfolders in a share and then applies the named users permissions to that folder and forces inheritance. I adapted it from a few other scripts I found after we had some issues following a migration. It loops over all the folders (actually all the items but the -Directory or something flag for Get-ChildItem will mean it ignores all the normal files in that area) in a directory. # Get all the child folders in the share $Folders = Get-childItem "" # Set Inheritance flags etc $InheritanceFlag = [system.Security.AccessControl.InheritanceFlags]::ContainerInherit -bor [system.Security.AccessControl.InheritanceFlags]::ObjectInherit $PropagationFlag = [system.Security.AccessControl.PropagationFlags]::None $objType = [system.Security.AccessControl.AccessControlType]::Allow # Loop over each folder in directory foreach ($TempFolder in $Folders) { # Get full path and username echo "Loop Iteration" $Folder = $TempFolder.FullName $UserFolder = $TempFolder # create ACL for named user and apply correct flags $acl = Get-Acl $Folder echo $UserFolder $permission = "\$UserFolder","FullControl", $InheritanceFlag, $PropagationFlag, $objType $accessRule = New-Object System.Security.AccessControl.FileSystemAccessRule $permission # Apply ACL to folder $acl.SetAccessRule($accessRule) Set-Acl $Folder $acl } You can probably use the Add-NTFSAccess cmdlet you've used already and just swap things around a little, I used this method as I didn't find that module so I might rework the code and give it a try using that module.

WinDirStat might be able to do this for you, or try Space Sniffer as that seems to produce some graphics with it's reporting.

Pass it up the line. At the end of the day it's not your job to manage pupils or other staff and if you lay it out to management that you're spending x amount per half term (or per term if you want to make the number more of an issue) just on mice and that almost all of that is from a specific classroom (perhaps start documenting when you replace mice there and how many) then they should take a closer look at it.

Any funding to buy a few Raspberry Pis? There are lots of resources on their site for primary school and onwards, you could probably adapt some of them for use without the Pis. The other option is to ask them what they'd like to do, they will probably come up with a bunch of things that aren't possible but you might get a few gems that are worth exploring.

You could install 7zip or another zipping application that has a GUI to do it that way. Or you could get the pupils to save the work on a shared drive that staff also have access to. Or you could give staff access to read from the Pupil home drives (we've just set it up as a mapped drive for staff and seems to work well).

Lucky for some. We had some overnight but not enough to close the school.

How about doing a quick look round the class every break time, noting any damage and then going to the Bursar or your SLT link and saying "This classroom has repeated vandalism and it's costing X amount every half term to replace equipment. We've narrowed it down to these Y classes who are the likely suspects, we know there is a supply teacher in at the moment but is there anything you can do from a Pastoral/Behavioural role to alleviate this a little?" You really need an SLT judgement that this will stop coming out of your budget and that the teachers will have more accountability for this stuff, it's worked well in the past from what I've seen but supply teachers make things harder unless it's the same person every day on long term supply. Once you get SLT backing then you can start finding the exact pupils who did it or likely did it (event viewer logs for the lessons) and then report that to their Head of Year or someone else in the Pastoral structure and move on from there. Edit: While it is a classroom management issue you also need to approach it in a way that makes it clear you are trying to provide a technical solution (cost of x mouses replaced per half term at current model plus these alternatives cost y but should reduce that cost) and therefore aren't just trying to pass the responsibility to someone else.