1 post tagged “chkdsk”

After spending considerable time with Microsoft on the phone and an ezassist session on the server in question this is what I found out.  There are two hotfixes available.  One for W23k servers with SP1 and one for W23k servers with SP2.  You must apply these hot fixes and reboot the server BEFORE you run chkdsk on any volumes.  There are no easy ways to replace the permissions on the user folders once the damage is done.  Option A is the GUI routine where you right click on the user folder and readd the users or global groups and then select to push to all files and folders.  Option 2 is to use a xcacls.vbs script to run lcacls.exe and associated commands to push the permissions out to each file and folder.  If you need to apply global changes only to a group of folders you can go to the top root folder and make your changes and then select inheritance for all sub folders and files under the root.  That will not work for individual folder security permission needs which is much more granular. 

I dodged a bullet with regards to replacing the security permissions on my file server today. Since the office is closed and no one is accessing the server or making changes to data I was able to revert the E volume back to 12/26/07 at 5 am via the Volume Shadow Copy.  It took some time for this to happen but once it was complete and I rebooted the server I spot checked several folders and everything was back to where it was before I ran chkdsk and accidentally stripped out the permissions.  If this had been a normal work day and all the users had been making changes to their data or adding data to their user directories then I would have been forced to go the lcacls.vbs route or the manual point and click GUI routine to replace the permissions.  I can not begin to tell you how much fun that is.