Software Deployment

I find it hard to believe that the All Users folder requires permissioning on ALL your workstations. If it does, there's something seriously wrong with your build.

Find out which package/process altered the permissions and fix that. Otherwise, you could potentially find that all of your packages will need to have a permissioning Custom Action added.

Which OS are you working on?
On Windows Vista, I had to give permissions to allusersprofile/pdf folder in pdf 995 application.
and I have worked for 1 client where, we had to give permissions to allusersprofile/application folders, in windows xp.

Hi Ian,

Thanks for your reply.

I am using a clean Windows XP SP3 build for packaging. Hence I can assume that there is nothing wrong with the build. However I think its is this package. I am currently working on Lotus Notes 7.03.

The problem is created by files that are installed to the AllUsers profile.The files in contention is in the Help directory and gives a prompt when launched by the users. The prompt explicitly points at permissions for the users to the said file. I provided permission to the file and it works (ProcMon confirmed the same).

As i have never done such a thing, so I checked the other directories in the AllUsers profile folder like "C:\Documents and Settings\All Users\Application Data\Microsoft\HTML Help" which also has permission provided to it. This is the default folder present on the build and Microsoft itself has provided permissions to it.

I take it back! I just checked my VMs and the 'Application Data' folder excludes write access to 'Users'.

Rather than assign permissions, I'd include the file which is being written in your package. That file is almost certainly a Help contents (.CNT) file, given that the error occurs when the Help is launched...

Open all the HLPs which are in the package and include the resulting CNTs.

Just a note:
If the .CNT file doesn't exist it will be created in the same folder however, if the user does not have permissions to do so it will be created under the users profile instead.

It think it sounds more like inherited rights from the Application Data folder which prevents the user for read access.
Fire up procmon and see which permissions it requires.

Once we had the same issue with one of the app (dont remember the app name). tried doing so manythings but it didnt work so till that time we also thought the same that we dont need to give permissions to ALLUSERS\Application Data\ App Folder, but to launch the application in users we have given persmission and it worked, if i am wrong then please suggest.