Icacls "D:\Microsoft.NET" /grant:r "NT SERVICE\TrustedInstaller:(CI)(F)" Icacls "D:\Microsoft.NET" /grant:r "BUILTIN\Users:(OI)(CI)(RX)" Icacls "D:\Microsoft.NET" /grant:r "BUILTIN\IIS_IUSRS:(OI)(CI)(M,WDAC,DC)" Icacls "D:\Microsoft.NET" /grant:r "CREATOR OWNER:(OI)(CI)(IO)(F)" Icacls "D:\Microsoft.NET" /grant:r "NT AUTHORITY\SYSTEM:(OI)(CI)(F)" Icacls "D:\Microsoft.NET" /grant:r "BUILTIN\Administrators:(OI)(CI)(F)" The remaining commands grant the required permissions. Thus changes to the permissions of the drive (root directory) will not effect the new temporary directories. The first command removes the removes the inherited permissions and replaces them with a copy of the inherited permissions. Next we need to set the folder permissions to match the existing default directories. Md "D:\Microsoft.NET\Framework64\v9\Temporary ASP.NET Files" Md "D:\Microsoft.NET\Framework64\v7\Temporary ASP.NET Files" Md "D:\Microsoft.NET\Framework\v9\Temporary ASP.NET Files" Md "D:\Microsoft.NET\Framework\v7\Temporary ASP.NET Files" You can choose any location, I just followed the guide. These commands will create new directories for the ASP.NET 2.0 and 4.0 temporary files on the D drive. The first thing we need to do is to create new directories for the ASP.NET temporary files. The fix is to relocation the ASP.NET temp folder which is outside of the system state backup. Kudos to crutledge from Peer Wisdom who made this guide. Here for a detailed explanation of the issue along with a detailed guide to resolve it. I believe I have managed to fix my problem permanently without the use of daily scripts etc.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |