I've been asked to tailor MS ActiveSync 4.1 but I can't get my head around this package.

o The package places files and a shortcut I can't find in the package.
o A custom action to start wcescomm.exe won't run, wherever I place it.
o After installation wcesmgr.exe will be started and will show a screen whenever someone logs on.
On the PC it's in the Run regkey but it can't, however, be found in the registry inside the package

I guess the MSI contains other MSI's but I can't find them.

I need to place the shortcut in another folder, start wcescomm.exe directly after install and remove wcesmgr.exe from the Run regkey.

Can someone help me out here?

Marcel
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
The answer is to recondition the "CA_Nt5_PrimeInf" custom action in the "InstallExecuteSequnce" table, by adding "AND ( NOT REINSTALL )" to the condition. Remember to use a transform for this.

This will take care of all the shortcuts for users and the wcomm.exe running one.

Giz
Answered 01/16/2006 by: gizmolala
Third Degree Blue Belt

Please log in to comment
0
I did that already but I need to have control over it.

Since I can't find the shortcut and the wcescomm.exe in the package and since my custom actions won't run there's nothing I can do to tailor it to the customers wishes.
I will try to repackage it and see what comes from that.

Marcel
Answered 01/16/2006 by: ZhuBaJie
Orange Belt

Please log in to comment
0
for u to see the wcescomm.exe , u need to import it from the system to ur package.

check ur shortcut table and u'll see that the file is there but hidden.
Answered 01/16/2006 by: gizmolala
Third Degree Blue Belt

Please log in to comment
0
Thanks, this helps.

I also found the Run entry and deleted it.

Do you have any idea why my custom actions won't run?
I tried them on several places and with several different custom actions like ruin from destination and a script.

----------------
a little later...

Changing the folder in the MSI doesn't help; it installs the shortcut in the same place as before.
Removing the Run key doesn't help either; it's still there when I install it.

Weird...
Answered 01/16/2006 by: ZhuBaJie
Orange Belt

Please log in to comment
0
wcescomm.exe in the package is within the [INSTALLDIR] folder (if you are opening it with Installshield). Is this what you meant by your query??
Sorry if this doesnot make any sense for your query[X(]
Answered 01/16/2006 by: slb
Purple Belt

Please log in to comment
0
I found out that all the time my transform wasn't used because /t was used and not TRANSFORMS=.
Damn! This way you can try till you die! Monday morning, I wasn't wide awake yet I guess.

Anyway, this is how I did it.

- I made a clean .MST
- Made the Randapparatuur folder to put the shortcut in
- Removed the Run registry key from the ActiveSyncCore feature
- Changed the Shortcut table to install to the new directory
- Changed the InstallExecuteSequence table by adding 'AND (NOT REINSTALL)' to the CA_Nt5_PrimeInf condition
- Changed the InstallExecuteSequence table by adding 'AND (NOT RunAs_ISTALL)' to the CA_InstalllinkNotes condition
- Changed the property ISCHECKFORPRODUCTUPDATES=0
- Changed the property RebootYesNo=No
- Added the property RunAs_INSTALL=1
- Added the property ROOTDRIVE=C:\

That's all folks!
Answered 01/16/2006 by: ZhuBaJie
Orange Belt

Please log in to comment
0
Zhu,

The Shortcut us a Generated Shortcut with a GUID in it. im a WISE user and the shortcut is hidden in a seperate feature.
In WISE i needed to turn on some switches before i could see it. but its there.

When you delete is from the MST file you created it wil not be placed.

But to remind you the GUID behind is there for e reason, if you want to create your own Shortcut just chang the name or the location of the Existing one in the MST file. this will work.

For your custom Actions not running : What are you deploying with? and maybe you can run a Logfile with your MSI by using : msiexec /i /L* <location of Logfile> <yourMSI> TRANSFORMS=<yourMST> /qb-
This way you log your Entire MSI into a TXT file. This way i used to get the errors back into the log and it will show you why this isnt working.

Try this under your Deployment rights ( the Deployment userid that For example Altiris uses ) and the administrator Rights

Good luck!

Regards,

The Packeteer.
Answered 01/16/2006 by: The Packeteer
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: ZhuBaJie

I found out that all the time my transform wasn't used because /t was used and not TRANSFORMS=.
Damn! This way you can try till you die! Monday morning, I wasn't wide awake yet I guess.

Anyway, this is how I did it.

- I made a clean .MST
- Made the Randapparatuur folder to put the shortcut in
- Removed the Run registry key from the ActiveSyncCore feature
- Changed the Shortcut table to install to the new directory
- Changed the InstallExecuteSequence table by adding 'AND (NOT REINSTALL)' to the CA_Nt5_PrimeInf condition
- Changed the InstallExecuteSequence table by adding 'AND (NOT RunAs_ISTALL)' to the CA_InstalllinkNotes condition
- Changed the property ISCHECKFORPRODUCTUPDATES=0
- Changed the property RebootYesNo=No
- Added the property RunAs_INSTALL=1
- Added the property ROOTDRIVE=C:\

That's all folks!


Haha, Well that happens Zhu.
Answered 01/16/2006 by: The Packeteer
Senior Yellow Belt

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