DavidTomic

It shouldn't be hard to get it working properly, but it really just depends on exactly what you're actually trying to achieve. I have something fairly similar configured, which I've basically got setup as follows: Students - Read & Execute (This Folder Only) (Which means that the root folder is essentially read only as far as the students are concerned. They can't create/modify/delete anything at the root level.) Students - Read, Write & Execute (Subfolders only) (The idea being that the teacher creates a (sub)folder [iE: English Assignment], which the students then have permissions to save/write to as needed. NOTE: They can write INTO the folder, but they can't actually modify/delete the folder itself, which is basically what you want, right?) Creator Owner - Modify (Students can modify/delete their OWN files, but not the files of any other users) I'm not sure how well that meshes with what you're actually trying to achieve, but it might at least help set you on the right path ...

Sorry ... I understand EXACTLY what you're saying, and you're absolutely correct. When I read your post I had you mixed up with the OP who was actually having the problem to begin with.

Which is exactly why you *DON'T* grant Full Control permissions in the first place ... EDIT - I just updated my last post to (hopefully) make things a little bit clearer. Does that help at all?

No ... The normal hierarchy for NTFS permissions is: Explicit Deny Explicit Allow Inherited Deny Inherited Allow Those rules are checked (from top to bottom) and the first match it finds are the permissions that get applied to the affected object(s). The *ONE* exception to normal behaviour, is if they've been granted FULL CONTROL of the parent folder, which is where your problem is stemming from. (Since they've been given full control of the (parent) directory, any child permissions are basically irrelevant because they've got full access to modify the underlying permissions anyway) You don't want students being able to modify/change security permissions (which Full Control obviously allows them to do) so should *NEVER* grant students Full Control of *ANYTHING* ... Granting them MODIFY access gives them full control over everything *EXCEPT* changing security permissions, which is what you should be setting instead. It also solves the problem you're having with them being able to delete things which they're not supposed to.

It could be the result of any number of things happening, but there will more than likely be some clues about what's going on in the event viewer logs of your domain controller(s). That's where I'd be starting my troubleshooting from ...

The motherboard only supports 4GB [2x2GB DIMMS]. If you ever want to find out the memory requirements/capacity of a particular machine, the crucial system scanner is my favourite tool for the job.

I'm currently in the processing of building up an image for ~60 new staff laptops that are going to be running Windows 8, and we've made the decision that we need to try and ease them into the transition as gently as possible so I'm looking at all of these options as well. At the moment I'm actually leaning towards Classic Shell, not least of all because it's completely free. It also seems to tick all the boxes in terms of design/functionality, so are there really any compelling enhancements in any of the paid versions that are going to be worth spending money on?

Obvious question (I hope) ... but it's not ending up getting infected by some type of malware/virus is it? I assume that would be one of the first things that you'd look into?

I've come across the same problem, and I honestly never figured out what was actually causing it. In the end I actually just setup a new print server and migrated everything onto that (same printers, same drivers, etc), and it's been working fine ever since. Go figure ...

It does in Server 2012. In 2008/R2 you needed to have the Enterprise/Datacenter versions if you wanted to use clustering, but in Server 2012 that's now all included in the Standard license.

Open the Remote Access Management console on your DirectAccess server, click on the "OPERATIONS STATUS" link on the left hand side and see if there are any problems/errors being reported.