We recently completed a migration of our SQL Server from SBS 2003 (& SQL 2003) over to Win Server 2008 R2 & SQL Server 2008. Our system is a little screwy currently - Our AD DC is still the SBS 2003 machine, while the 2k8R2 machine is running SQL Server and hosting a large shared folder for storing our business-critical files.
I've run into a sporadic issue where users (using a shared Admin login ATM) will lose write access to the shared folder. I can fix it by logging into the server and manually changing the "read-only" flag on the folder (It's actually our entire second partition - just one shared subfolder for our files). This has happened 3 times in the couple months we've had this rigged up, and I can't find a source for the change each time - event logs don't show anything different than usual.
I've read a lot about Server 2008+ having "User Account Control (UAC)" and being a bear in just these situations. I know I could disable UAC and wait to see if the problem persists, but I'd like to actually FIX the issue properly. I also haven't seen any sort of explicitly UAC-related prompts - we come in one day and try to copy/paste to the folder like usual, and we're given the old "Access is Denied - check in-use/write-protection". Can anyone point me in the direction of what might be causing these permission failures?
EDIT (3/12): I dug through File & Sharing Manager on the server and discovered that I have two share names for the same folder. One share entity has full permissions while the other entity has only "Read" - obviously, my workstation was linking to the limited share name. I've corrected the permissions in the second entity and restored access for now. Will most likely remove the second entity, but not until I set up permission auditing to figure out just what is changing the permissions of that share.