Anyone have luck in packaging Dynamics AX?

Was wondrin if anyone have had any experience by packaging Dynamics AX 4.X client?
If so how did you do it

The installation files contains a native msi file which i was able to get installed by deleting all content under LauncCondtionStatement. But if i now run the program it says somethinh about a missing active x component

0 Comments   [ + ] Show comments

Answers (1)

Posted by: anonymous_9363 13 years ago
Red Belt
Whenever I re-package, I ALWAYS do a test install using this procedure:

- run my MSI
- start a lightweight snapshotting tool (I use Ziff-Davis's In Control)
- remove any file or registry data that indicates to the original installer that the product is installed
- run the vendor install again
- you *may* want to start the app so that you capture any configuration that it might make
- complete the snapshot
- add any relevant file or registry data to my package
- repeat

This way, I know that my package exactly reproduces the vendor's installation. In your case, I'm willing to bet that the vendor's set-up stub performs a bunch of DLL/OCX registrations.

Lastly, deleting stuff from a vendor-supplied MSI - or making changes of any kind - isn't a good idea. Always use a transform.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ