On XP, the share was created with Full Control. On 2003, the share was read-only. We can solve this by adding add /GRANT:Everyone, FULL to the NET SHARE command in the installation procedure, but this option is only recognised in Windows 2003, so we would have to perform something different, dependent upon the host operating system. We don't believe that we should be giving such permissions on a 2003 server - it is up to the individual administrator. Therefore this has been changed to a Knowledge Base article

 
Commented on 09 August 2007 09:49
--------------------------------------------------------------------------------
The Script file and Batch file Rule Actions allow the user to edit the script/batch file but saving the files fails because the ScriptFiles and BatchFiles shares are read-only.
On Windows 2000 shares were created with Everyone, Full Control by default. On Windows 2003/XP shares are created with Everyone, Read Only.

The installation needs to create the shares with Full Control granted to the Everyone group.