Creating an MSI package that works with 64bit

[dgsmith]

Since the inception and our rapid conversion over to 64bit, we've found some self-created MSIs are problematic when assigned to x64 machines.

 

Having read a bit about how the folder variables have changed from this site, it seems that it's necessary to manually change the variable name where files are being copied to the Program files and system32 files, so as to not be dumped in Program Files (86) and SysWOW64 respectively.

 

Does anyone have experience with this and know of a better/more efficient way, other than having to manually edit an MSI to change these vars when you don't want it to treat the package as 32bit? For instance, I have an MSI that includes a collection of Paint.NET effects files that when assigned to a 64bit machine (which has a 64bit Paint.NET installed), it dumps them in Program Files (86) when the Paint.NET install is in the native Program Files.

It'd be good if an MSI could be created dual-purpose in that it can be made in such a way as to install to the respective native folders on a 32bit or 64bit install when it's known that is what is required.

 

Any advice that'd be useful?

[sparkeh]

How do you create your msi?

 

Advanced installer allows you to create mixed 32/64bit installers that puts file and registry entries in the right place. But you need the paid for version. Might be worth it if you do this a lot.

[dgsmith]

Still old school methods using ondemand and occasionally orca for extra stuff. Being an RM CC4 network we tend to use the provided tools that came with it, however we can only do a clean MSI install using a 32bit image (their ondemand doesn't support 64bit) and the ondemand software itself is now rather dated and extremely limited.

 

Are there any decent, free alternatives that offer a similar level functionality, or even as a compromise an easier way to make an MSI 64bit capable (whether instead of or as well as being 32bit? The prices on that advanced installer software we may struggle to justify, even just for the entry level one (and we wouldn't qualify for a free license)!

[Arthur]

Are there any decent, free alternatives that offer a similar level functionality

WiX Toolset (although it is slightly more complicated than Advanced Installer).

 

If your school has a Microsoft EES subscription you could use the App-V Sequencer to create .appv packages. The only other thing you would need to do is deploy the App-V client to your Windows 7 PCs.

[bossman]

All I can say is PDQ Deploy!

 

Excellent product and true value for money with a UK software distributor!

 

https://www.adminarsenal.com/

[dgsmith]

WiX Toolset (although it is slightly more complicated than Advanced Installer).

 

If your school has a Microsoft EES subscription you could use the App-V Sequencer to create .appv packages. The only other thing you would need to do is deploy the App-V client to your Windows 7 PCs.

 

Given we deploy via CC4 tools then the preference is to stick with that method (i.e. MSIs)

 

All I can say is PDQ Deploy!

 

Excellent product and true value for money with a UK software distributor!

 

https://www.adminarsenal.com/

 

But this is for deployment right, rather than creation of packages on an existing deployment platform?

[bossman]

@dgsmith

 

It does both, you can create a deployment package from exe's, msi's, batch file etc etc plus if you purchase the enterprise version £350.00 approx then you receive all the runtime packages free which are always kept up to date and its so easy to maintain your runtimes without having to go through the process of creating them from blue prints for CC4 or creating from scratch.

 

Its well worth the money from my experience, try it for free first and see, you get 3 free deployments to trial.

[Arthur]

Given we deploy via CC4 tools then the preference is to stick with that method (i.e. MSIs)

In addition to the .appv package, the App-V Sequencer also creates an MSI that can be used to install the .appv package using your existing CC4 tools.

[kellybrooks86]

True, we tried WiX and it turned out to be too complex. As for MS App-V Sequencer, in my opinion, it's also no the easiest tool to create this packages - PACE Suite or Advanced Installer both seem more intuitive to me (especially for the packaging newbies).