Software Deployment

Used the Adobe CW to create an MST, & am deploying with the 1033.MST also. Thought at first that it was the MST order but I can get it to manually install OK with variations of this command line:

%windir%\system32\msiexec.exe /i "%~dp0AcroPro.msi" TRANSFORMS=1033.mst;AcroPro90.mst /qb!- /l*v "%~dp0AcroPro90.log" REBOOT=ReallySuppress

I used advanced publishing without the local AIP. Looking in system explorer, I can see all relevant files and pertinent objects; Acropro.msi, Acropro90.mst, 1033.mst, data1.cab, msiacp.idx, install.cmd, uninstall.cmd. Looking on the worstation, I see all these files among others copied down to the install location including Radia.MST. My understanding is that Radia should merge my changes into this MST and use it for deployment, right?

My ZCREATE reads: ZCREATE RadiaMSI /i "/qb!- /l*v C:\installdir\AcroPro90.log" and kicks of the installation then fails as logged below. The error is indicative of the CA not finding a valid serial number which should be contained in Acropro90.MST. Any help would be appreciated...

MSI (s) (20:30) [16:55:38:327]: Looking for file transform: C:\PROGRA~1\Novadigm\Lib\SYSTEM\RADIA\SOFTWARE\ZSERVICE\ADOBE_~1\Radia.mst
MSI (s) (20:30) [16:55:38:358]: File will have security applied from OpCode.
MSI (s) (20:30) [16:55:38:358]: Original transform ==> C:\PROGRA~1\Novadigm\Lib\SYSTEM\RADIA\SOFTWARE\ZSERVICE\ADOBE_~1\Radia.mst
MSI (s) (20:30) [16:55:38:358]: Transform we're running from ==> C:\WINDOWS\Installer\41e90.mst
MSI (s) (20:30) [16:55:38:358]: SOFTWARE RESTRICTION POLICY: Verifying transform --> 'C:\PROGRA~1\Novadigm\Lib\SYSTEM\RADIA\SOFTWARE\ZSERVICE\ADOBE_~1\Radia.mst' against software restriction policy
MSI (s) (20:30) [16:55:38:358]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (s) (20:30) [16:55:38:358]: SOFTWARE RESTRICTION POLICY: C:\PROGRA~1\Novadigm\Lib\SYSTEM\RADIA\SOFTWARE\ZSERVICE\ADOBE_~1\Radia.mst is not digitally signed
MSI (s) (20:30) [16:55:38:368]: SOFTWARE RESTRICTION POLICY: C:\PROGRA~1\Novadigm\Lib\SYSTEM\RADIA\SOFTWARE\ZSERVICE\ADOBE_~1\Radia.mst is permitted to run at the 'unrestricted' authorization level.
MSI (s) (20:30) [16:55:38:368]: Validating transform 'C:\WINDOWS\Installer\41e90.mst' with validation bits 0
MSI (s) (20:30) [16:55:38:368]: Transform 'C:\WINDOWS\Installer\41e90.mst' is valid.

____________________________________________________

MSI (s) (20:30) [16:55:43:805]: Transforming table InstallExecuteSequence.

Action ended 16:55:43: CA_QV. Return value 3.
Action ended 16:55:43: INSTALL. Return value 3.

cross-posted on HP IT Resource center forums - CAE Management Applications (Radia) site

Hi Iam also facing the same issue with Acrobat 9.0 and publishing with Radia 4.1 with or without the local AIP in advanced mode. I too have posted at the HP forum and this site for assistance. Try to edit the zcreate as RadiaMSI /i "/qf" this will prompt for your action at each step and you can make out if your transform is being selected properly and at which step it fails. I get the error on the 2nd prompt for serial number and the error is "invalid serial number" though its the correct serial. If you would prefer to use without AIP (that means the source would be downloaded on to the client) then the basic publishing option will work with the transform. This is recommended only if the AIP option doesnt work.

yep. I can get it 2 work when publishing via basic. The whole point is that i was attempting to follow HP's best practices... After further research, it looks like the issue has to do with Radia & deploying multiple transforms. Their recommended work-around is to remove the connection to SOFTWARE.MSIFEATS.packageprefix_* from the application package instance, then using the Radia Packager in component selection mode, promote the MSTs, then connect the MSI PACKAGE instance to to each of the transforms file's instances, then create one application instance (ZSERVICE) 4 each of the transform packages then assign your subscribers...

(*are you still with me*)

Yep, needless to say I right clicked, deleted the package, & wernt back to my basic package running an install.cmd (because of the commandline character limitation)...