Symantec Management Platform (Notification Server)

Using 7, I've imported Adobe Reader 10 in Management Platform library, along with the MST to transform the MSI:

I'm having problems understanding how to deploy the acroread.msi along with the transform.  Below is what I'm currently trying with no success.  What am I missing?

Although not specific advice, I reocmmened against using any of the autogenerated command lines. You should test the command lines on a local box and when you are satisfied with how it's working edit an existing one or create a new one.

And try logging. I always put:

 /l*v "%temp%\acroread.log"

At the end of every msiexec command.

Check the {GUID}\cache directory on the client to make sure it's picked up all the package files.

We have been using Deployment 6.9 to manage our initial Adobe installs successfully (example below). We have also used Adobe's customization wizard to create the MST with no issues.  So this was my attempt to see if we could deploy Adobe Reader through the Symantec Manage Console.  My initial attempt was not using the autogenerated command lines and still it appears the job is timing out. 

start /wait msiexec /i "\\server\AdobeReader\Reader10.x\AcroRead.msi" ALLUSERS=TRUE TRANSFORMS="\\server\AdobeReader\Reader10.x\AcroReadFHLBI.mst" /qn /l*v "%windir%\Temp\AcroReader10.log"

So following the logic that this is now in the software library I should now be able to change the command line to read this:

start /wait msiexec /i "AcroRead.msi" ALLUSERS=TRUE TRANSFORMS="AcroReadFHLBI.mst" /qn /l*v "%windir%\Temp\AcroReader10.log"

Using a Deployment Server (6.9) you can see I simple pointing to the files on a server and running it. With SMP 7 I've imported this shared folder into the software library so the command line will change.  I'm wondering if I missed something since it doesn't appear to run?

When you used the adobe customization wizard it updates the setup.ini to include the transform.  Because we have always not had much luck with deploying adobe along with the msp file updates which is also in the setup.ini we no longer deploy with the msi.  Instead use the setup.exe file to deploy.

When creating transform we also set it to be a silent install so just running setup.exe works great.  Reads the setup.ini file and installs with transform information plus it installs all msp's in the ini file.

I discovered my issue.  When I imported the files to the software library I pointed it to the "reader10.x" folder so that it would capture all files under this folder.  Since I did this I now have to change my command line to include the folder which worked:

msiexec /i "Reader10.x\AcroRead.msi" ALLUSERS=TRUE TRANSFORMS="Reader10.x\AcroReadFHLBI.mst" /qn /l*v "%windir%\Temp\AcroReader10.log"

I am now curious what would happen if I create another package for reader 10 without the folder, just the files.  How does the command line know which package to run from? 

when creating a package there is a guid attached to the package and software resource.  Your quick delivery or managed delivery you choose a specific package and that package contains the specific command lines for that specific package and guid.  Then when you deploy the software resource for that guid is downloaded and the package runs the command line stored in the package which you selected to use.

Got it, thank you. 

I appreciate all the feedback.

Take ALLUSERS=1