MSI installation - All Users folder is creating under logged in user id
Hi,
I prepared an MSI from setup capture in WPS. It has folders and files copied under All Users folder but when we install thru MSI, it is creating All Users folder under logged in user id ( in user context), c:\winnt\system32 (in system context).
Destination of the folder should be
c:\documents and settings\all users\abc\xyz\a1.txt
but it is going under
c:\documents and settings\user id\all users\abc\xyz\a1.txt (in user context)
c:\winnt\system32\all users\abc\xyz\a1.txt (in System context).
Tried the following options but no use.
1. Pass the parameter ALL_USERS="%ALLUSERSPROFILE%"
2. Used custom action to set All_Users property to c:\documents and settings\all users
When I looked in the verbose log,
All_users property is changing to %ProfilesFolder%\All Users and value of the ProfilesFolders is c:\winnt\system32 (in sys context), c:\documents and settings\user id\ (in user context).
Any help would be highly appreciated!!!
I prepared an MSI from setup capture in WPS. It has folders and files copied under All Users folder but when we install thru MSI, it is creating All Users folder under logged in user id ( in user context), c:\winnt\system32 (in system context).
Destination of the folder should be
c:\documents and settings\all users\abc\xyz\a1.txt
but it is going under
c:\documents and settings\user id\all users\abc\xyz\a1.txt (in user context)
c:\winnt\system32\all users\abc\xyz\a1.txt (in System context).
Tried the following options but no use.
1. Pass the parameter ALL_USERS="%ALLUSERSPROFILE%"
2. Used custom action to set All_Users property to c:\documents and settings\all users
When I looked in the verbose log,
All_users property is changing to %ProfilesFolder%\All Users and value of the ProfilesFolders is c:\winnt\system32 (in sys context), c:\documents and settings\user id\ (in user context).
Any help would be highly appreciated!!!
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
mekaywe
13 years ago
i have faced the same problem but dint find the right solution at that time.
How I came out of this issue is, created a wisescript which will install the files/folders and added it as a custom action.
Anyone who has solution to this problem are welcome.
Rgds
Arjun
How I came out of this issue is, created a wisescript which will install the files/folders and added it as a custom action.
Anyone who has solution to this problem are welcome.
Rgds
Arjun
Posted by:
anonymous_9363
13 years ago
I think you are confused.
There is a public property - ALLUSERS - which controls whether the package is installed per-machine or per-user.
As for the destination, check the directory structure in the 'Setup Editor' view, selecting 'Tables' tab and then selecting the 'Directory' table. I suspect you have a rogue entry in that table.
There is a public property - ALLUSERS - which controls whether the package is installed per-machine or per-user.
As for the destination, check the directory structure in the 'Setup Editor' view, selecting 'Tables' tab and then selecting the 'Directory' table. I suspect you have a rogue entry in that table.
Posted by:
WSPPackager
13 years ago
I did verified the directory structure and everything looks good.
I am not using ALLUSERS property in the command line. I used All_Users property to set the value.
Still it is going under logged in user id.
I am not using ALLUSERS property in the command line. I used All_Users property to set the value.
Still it is going under logged in user id.
Posted by:
WSPPackager
13 years ago
Hi All,
I found the solution to fix this issue.
Use Set Directory CA in Execute Differed section. (This should be immediately after Set Property ARPINSTALLLOCATION.
Regards,
I found the solution to fix this issue.
Use Set Directory CA in Execute Differed section. (This should be immediately after Set Property ARPINSTALLLOCATION.
Regards,
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.