Installing MSI as admin but distributing icons to user profile
I am attempting to deploy an MSI via LANDesk. If I install the application as an administrator account (local system), then I get all the icons put into either the system profile folder or the All Users folder (such as the All Users\Start up) folder. I need to install as the local system since the user doesn't have sufficient user rights. How can I add icons to the user's profile director instead of all users (so the application will run on startup for the USER not for EVERYONE)?
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
anonymous_9363
12 years ago
>write a script
Er....no. Use either an advertised entry-point (e.g. a shortcut) to trigger self-healing, having moved the user-level components to a new feature and making the feature containing the advertised entry-point a child of this new feature or, at worst, use Active Setup.
Both are documented ad nauseam here at IT Ninja.
Er....no. Use either an advertised entry-point (e.g. a shortcut) to trigger self-healing, having moved the user-level components to a new feature and making the feature containing the advertised entry-point a child of this new feature or, at worst, use Active Setup.
Both are documented ad nauseam here at IT Ninja.
Posted by:
dchristian
12 years ago
What i would do is write a script:
-Delete the icons created in the all users icon
-Determine the logged on user
-Create the links myself where i want them
-Delete the icons created in the all users icon
-Determine the logged on user
-Create the links myself where i want them
Posted by:
dj_xest
12 years ago
Could be of use with ALLUSERS property. Check this out and see what OS you have and use appropriately. http://msdn.microsoft.com/en-us/library/windows/desktop/aa367559%28v=vs.85%29.aspx
Comments:
-
If it is run as local system and a user is NOT logged in, then the msi log says it runs with ALLUSERS=1 and the icons go under all users. If a user IS logged in, the log says it runs, but does NOT include the ALLUSERS property and then everything goes into the system profile folder (in the windows folder) and the icons aren't seen. I've experimented with ALLUSERS=1 and =2 in the command line, neither work as desired above. - yougotiger 12 years ago
-
OK tiger, here it is. Follow what VBcab said or knight below. if you don´t have any shortcut but only on that startup folder, then use active setup, otherwise you can use the other way around that VBscab has mentioned if you dont want the user to log off and initiate that AS.
if you require someone logged in prior to the installs of you app, then maybe you can delay the installation until they are logged in by checking some process in task manager. - dj_xest 12 years ago
Posted by:
dandirk
12 years ago
VBScab has mentioned the more proper/useful ways to do something like this... leverage advertised short-cuts/self-healing or repair via active setup.
dj_xest also mentioned installing per user, but I have always had horrible issues trying to deploy software per user like that. Usually having to do with later upgrades, even run into issues where tech's can't uninstall the app unless they login to the customers account, which isn't very handy. Not only that but you have to install the app for every user, so they have to wait for installation even though it may have been installed on that computer many times. Not an issue for small apps but larger ones it's a pain.
If you wanted you could do a hybrid... Install per machine, then have LANDesk (if you are using their app launcher even better) run a repair for each user. Essentially doing what VBScab mentioned but using LANDesk to control it...
dj_xest also mentioned installing per user, but I have always had horrible issues trying to deploy software per user like that. Usually having to do with later upgrades, even run into issues where tech's can't uninstall the app unless they login to the customers account, which isn't very handy. Not only that but you have to install the app for every user, so they have to wait for installation even though it may have been installed on that computer many times. Not an issue for small apps but larger ones it's a pain.
If you wanted you could do a hybrid... Install per machine, then have LANDesk (if you are using their app launcher even better) run a repair for each user. Essentially doing what VBScab mentioned but using LANDesk to control it...
