Well, because we need to write to the file.
Will Premiere let you save the project to a local location?
Adobe was never designed to run off networks.
I have no problems saving to a network drive and running off a network drive (albeit at lower speed than local projects) and no problem in using networked assets, so the most likely cause is in your permissions, so ask your SA.
Premiere will let me save to local location or a network location that has "Full Control" permissions.
Of course the file needs permissions to be written but Write DAC is not required to write a file it is the permission to modify the DACL of a file. http://msdn.microsoft.com/en-us/library/aa379607(VS.85).aspx describes the Write_DAC permission as "The right to modify the discretionary access control list (DACL) in the object's security descriptor." This is a permisison that I intentionally do not grant to users on a shared network drive.
I'm looking to understand why premiere needs to modify the DACL.
The best way to use PR is with full administrative rights.
I'm experiencing the same issue in my environment with creative cloud applications, both prelude and premiere, and have been unable to find any further information regarding why the application requires specific DAC rights or whether a work around exists. From a security perspective it is irresponsible to grant such rights on a home directory or to elevate everyone's rights to administrator.
Currently are your users home directories sitting on a standard windows share or are you using another vendor to provide the storage?
Any help would be much appreciated, thanks.
I was unable to find any information why the Write DAC permission is required. We still run Adobe CS5 but I’m disappointed to hear this hasn’t been addressed in later versions!
The work around we use is to grant “Full Control” share permissions but not allow “Change Permissions” file permission. It seems that premiere requests the Write DAC but never uses it.
Our user directories sit on standard windows shares. I also tested using Linux and samba shares but did not experience the issue. I think this is due to the much simpler Linux permissions model.
Hope this helps,