

Here are a few steps I have taken to be able to install the application as well as activate it, for me this is the best solution, you or others may require or want a different solution but here goes anyway…

Licensing is a major issue here, during deployment SCCM will use SYSTEM to install the application, this means that when it runs the script, installs MapInfo and runs the command to activate the license, it will fail because it does not have access to the internet.

If you’re deploying MapInfo via SCCM I would suggest you add each prereq as separate packages, otherwise I would write into the bat file to install all of the prereqs before installation of MapInfo.Īlthough I will be deploying via SCCM and I can use the command, I will still be creating a bat file script because there are quite a few issues with things like licensing etc.
#MAPINFO 10 SERIAL 64 BIT#
If you’re using the 86 or 64 bit version of MapInfo you need to install the corresponding versions of the prerequisites. Oh and as per Pitney Bowes support, they officially do not support SCCM. I wouldn’t recommend creating a MST and deploying the MSI with the MST, from previous experience this misses components out like File Type Associations and other little bits like that. There is no packaging involved with MapInfo Pro due to the fact everything can be done via the command line or a bat script.
