Software Deployment Question

Packaging Access Runtime 2013

05/21/2015 3832 views
Hello I'm trying to package Access Runtime 2013. I have downloaded the source .exe and extracted the Setup.exe and the MSI as usual. I'm running the following command and everything works fine.

setup.exe /config accessrt.ww\Config.xml

However as soon as I edit the MSI in any way the install will fail. I need to change the usual properites in the MSI like Company, Contact info, Disable uninstall add registry keys in a new component etc.

How can this be achieved? Has anyone else achieved this? Why cant I change the MSI (I'm not even renaming it?)
0 Comments   [ + ] Show comments


Community Chosen Answer


It does get a bit upset if you edit the MSI.

As noted above, do your modifications in an MSP by running setup.exe  /admin.
Most of what you want to do can be done from the Config.xml. Reg keys are a bit different, add them using the /admin (they will be in the MSP) but they don't get un installed.

Most places add (and remove) reg keys using a script in the config.xml (create a 2nd XML for removal)

Answered 05/25/2015 by: Badger
Red Belt

All Answers


You need to create an MSP using the Office Customization Tool, which is accessed by adding the '/admin' argument to SETUP.EXE.

I'm sure there are reasons why Microsoft chose to use this "Let's abandon transforms" route but I've never been able to find any documentation explaining them. I'd be interested to read it, if it's out there.

And thank you, yes, I *know* patches are effectively embedded transforms but why the complication?

Oh and by "disable uninstall", I presume you mean removing the ARP entry?

Answered 05/22/2015 by: VBScab
Red Belt

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