We have a very simple new deployment server, hosts file services and runs WDS and VMAT thats it, not a DC or anything just a member server.
We have a dedicated D drive (Since this server is a VM on an ESX host its drives are SAN based) One folder called software, which is our software repo.
I was having difficulties making changes to some sub folders, and reviewing the permissions and owners of each file was a little skewed. Some folders where owner of Administrators class, while many others where my admin account as the owner.
So I went to work to clean up all permissions in the parent and all child folders. On the Parent folder, the primary shared folder. I changed owner to Administrators class (as it was my admin account originally) and pushed it to all children folders, I then went into the Security Tab, and set all permissions i wanted accordingly, Everyone have read and list, Staff group have read and list, Domain Computers have Read and List, Domain admins have full control, system has full control, administrators have full control, three standard accounts (including my standard account) have Read, write, list, and modify control. Then I pushed it to all child folders. I tested it with my standard account and everything was working fine.
I came into work today to find that the software repo hadn't mapped according to our logon script. I attempted to connect to the share, and it fails... until i map the drive with my admin account, and then it works again...
Any ideas as to what I managed to screw up?