Hello, I have quite an odd problem.

Okay, we have a the installs for the CS3 programs on the network and the program exe's are keyed to a keyserver, so I pulled the exe out of the MSI file, keyed it, and put it back into the MSI. Everything installs fine and works, except the installer doesn't put the shortcut into the start menu like it should. Any ideas?

FYI: I'm using the newest version of AdminStudio.

Let me know if you need any more details.

Edit: This problem occurs with all installs of any CS3 program.
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
anyone?
Answered 08/25/2008 by: cmarquar
Yellow Belt

Please log in to comment
0
my suggestion would be to use the native install, modify the requisite XML files not worry about repackaging it. That is what I did with DW9/CS3. The install actually consists of a string of MSIs & trying to keep them straight is a hassle... there is a KB for this product in the package KB.

but if you are feeling brave & want to do battle with Adobe's genius @ complicating everything...

Cheers!
Answered 08/25/2008 by: kiptek
Second Degree Green Belt

Please log in to comment
0
Thanks for the info, but I've already made the changes in the xml override file, that part is working greatly, it's just that we have a key server which handles licensing and tracks usage, in order for that to work we have to pull the executable out, key it, and stick it back into the MSI. After that, it would always prompt for a username and password before a user can use it. That all works fine, there just isn't a shortcut in the start menu.
Answered 08/25/2008 by: cmarquar
Yellow Belt

Please log in to comment
0
I know this isn't exactly what you want but what about putting the install in to a VB script and having the VB script make the shortcut?
Answered 08/28/2008 by: Heresy
Senior Yellow Belt

Please log in to comment
0
what about installing as is with the original media, then run a script to key the executable once it is on the machine? then login as a different user, launch & see if there is any self-healing that occurs, & if so, if it overwrites ur exe. As notorious as adobe is with their MSI structures, i would not be suprised if you can get away with this without a self-heal repairing the exe. worst comes to worst, open the 1033 MST & redo the component attributes so they are not overwritten on heal.

(i do not recommend my own advice, but if you are @ a wall...)
Answered 08/28/2008 by: kiptek
Second Degree Green Belt

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