Ok so I am a packaging piglet, slowly learning as I go.

I have repackaged PalmOne 4.1.4 based on recomendations in the KB, that and everything else via MST kinda went over my head.

My repackaged MSI works great, it automatically heals when a new user logs in etc Yes I know I broke the cardinal rule, don't repackage an MSI. Others suggested it in the KB and it seems to work fine. I did this with AdminStudio and performed a snapshot.

1 problem I am having is that all the shortcuts install in the All Users profile and I can't seem to figure out how to put them in seprate user profiles. My hope was to have the shortcuts in the user profile, make them keys and have them installed in the new user start menu when they first start the app (through Novell Zenworks)

I have tried changing the ALLUSERS property to "", but this seems to be ignored. I even changed the custom actions, setAllUsersProfile2k property value to [%USERPROFILE] (from [ALLUSERSPROFILE]) and virtually any/every directory/property table reference that seems to refer to ALLUSERS...


I assume there is somewhere in the AdminStudio ism that sets where the start menu shortcuts are installed, a property of some sort... Can anyone shed some light and where I can look?

My enviroment:

WindowsXP
All users have local Admin rights
Delivered via Novell Zenworks

Thanks

Oh... by the way if anyone happens to know... Where the heck does the Palm Quick Install desktop icon show up in the editor.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
It's an inescapable conclusion that your issue isn't helped one iota by having re-packaged the application. Transforms/MST are simple: they're essentially a difference database. AdminStudio has a neat utility/tool (whose name escapes me!) for creating them, whereby you just click through a "dummy" installation (so that AS can pick up your dialog choices) and end up with an MST. One of those choices, of course, would be 'All users of this computer' or 'Just for me', the latter being what you want.

Changing the setAllUsersProfile2k Custom Action is foolish and may have repercussions elsewhere in the MSI.

Lastly, GroupWise may override the ALLUSERS setting: is there a means to specify a per-machine/per-user installation in GW?
Answered 04/07/2008 by: VBScab
Red Belt

Please log in to comment
0
I have tried the simple MSI methods that generally work for me but these failed. Yes I tried a response transform made by AdminStudio's Tuner app and this failed as well, the Palm msi does NOT prompt to install All Users or Just Me. Funny though I do see the dialogs setup for it in the Direct Editor. Maybe there is an advanced dialog I can enable somehow. Will have to look at

With Palm, the app installs fine but then fails when run on a different account on same machine. Reinstall does not work. Reading the Packaging KB on this site, Palm is a know poor package with multi-user issues. A few repackaged the app a few others worked it out in the MST. I could not follow the changes in the MST so I went with the repackaging and got 90% of the results I was looking for.

The ONLY success I have had is with a snap shot, the MSI properly repairs itself when started by a different user. But the advertised shortcuts are created in the All Users profile which is a issue for our enviroment.

Yep I am very new to packaging, I was just playing with any table entry then may net the results I was looking for... thus the change to setAllUsersProfile2k. I appreciate the warning, just wanted to show I was working on it and trying everything I could to fix this issue my self.


GroupWise?: I must be dense, is the ALLUSERS setting on the PC/workstation? If so where can I check this? I thought ALLUSERS just a standard used by MSI internal in conjunction with XP enviro varibles?
Answered 04/07/2008 by: dandirk
Third Degree Green Belt

Please log in to comment
0
VBScab - thanks for the idea...

I ended up looking through the dialogs in the AS editor.

Found the dialog regarding all users or single user. Found the property and proper value from the dialog. Odd how you cannot access this dialog through the standard install...

Well I changed the property and it installed to the specific user... Performing testing to see if my repackage still repairs itself like the other one.

Note: Property table. ApplicationUsers= AllUsers or OnlyCurrentUser

Thanks
Answered 04/07/2008 by: dandirk
Third Degree Green Belt

Please log in to comment
0
ORIGINAL: dandirk
GroupWise?: I must be dense, is the ALLUSERS setting on the PC/workstation? If so where can I check this? I thought ALLUSERS just a standard used by MSI internal in conjunction with XP enviro varibles?
You're right, ALLUSERS is an MSI property. I know diddly-squat about GW, but I was figuring that since every other deployment system I've encountered has a means to specify whether a package is be installed per-machine or per-user, there must be a way for GW to do that, too.
Answered 04/08/2008 by: VBScab
Red Belt

Please log in to comment
0
VBScab - thanks for the hint again. I have reworked the package and figured out some ways AdminStudio/msi deals with Allusers properties.

I have gotten the original msi/mst to work well enough by itself except for an issue with a weird type of short cut. Its called the PalmOne Quick Install. It is not a file as it doesn't even show up if I do a dir of all of the possible locations (allusers, userprofile, default user etc)...

I will have to do a search and post to see if anyone knows how to get rid of this icon outside of manual deletion...
Answered 04/08/2008 by: dandirk
Third Degree Green Belt

Please log in to comment
0
It may well be created by a Custom Action...run the package through your authoring tool's debugger and watch for the shortcut creation, then refer back to the last action executed.
Answered 04/09/2008 by: VBScab
Red Belt

Please log in to comment
0
Yeah that would be a neat trick to learn. AdminStudio doesn't have what I would call an obviously named debugger.

So I just elevated the install level of the feature. Don't think our users use the quick install app.

Poof problem gone.
Answered 04/09/2008 by: dandirk
Third Degree Green Belt

Please log in to comment
0
To remove the PalmOne Quick Install desktop shortcut:
Remove the Property:
InstallAppV2DesktopIconName=palmOne Quick Install (this removes the text below the icon)

Remove the registry key:
HKLM\Software\Windows\CurrentVersion\Explorer\Desktop\NameSpace\%Palm Desktop GUID%

Gizsha
Answered 07/01/2009 by: gizsha
Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity