Greg,
Thanks for updating on this. Meanwhile, I had another contact with an Adobe "Strategic Account Specialist", and according to that person, the ETA is within the next month. As a result, my support ticket has been closed, which I don't like very much, as the problem is not solved yet. We'll see where this is going.
On your proposal to just start explorer.exe after the MSI's have been executed, I used setup.exe so far. The package we're trying to create is huge, as it will have to install:
- Core Components
- Acrobat XI Pro
- Bridge CC
- Dreamweaver CC
- Fireworks CS6
- Flash Professional CC and Mobile…
- Illustrator CC
- InDesign CC
- Media Encoder CC
- Photoshop CC
If I understood correctly, I have to install Acrobat first for some reason, so my script would look something like:
AcroPro.msi TRANSFORMS=AcroPro.mst
CCforTeams.msi (that's how I called it)
ExceptionDeployer.exe" --workflow=install --mode=post
Explorer.exe
Is that what you had in mind? Do you see a problem in packaging so many applications in one package?
Thanks,
MTGCH