Thursday, June 19, 2014

Deploy Minitab 17 via SCCM

Minitab has released a new version. Here is my method for packaging Minitab 17 for deployment via SCCM.
  1. I download the executable mtben1710.mu.exe from Minitab. When run this executable will extract all its files into a directory in C:\Windows. So I run this on a test computer and at the "Welcome to the Minitab 17 Setup" window, I stop and go to "C:\Windows\Downloaded Installations\Minitab 17 English MU" and copy the files to another directory or my Source on my SCCM Distribution point.
  2. When the Setup.exe from the unpacked Minitab setup folder is run, it will extract an MSI to C:\Windows\Installer with what appears to be a random name. I want this MSI. I can get the GUID from it for my detection method when I make it an application deployment in SCCM. So on my test machine, I run Setup and go through the whole process of installing Minitab. I then do a hardware inventory on the test machine and use Resource Explorer to find out what MSI installed Minitab 17. Looking at the Installed Software table under the entry for Minitab17 (not the entry for Minitab 17, don't ask me why its listed twice), I see that the local package that installed Minitab was C:\Windows\Installer\266403.msi. I copy this MSI to my Minitab 17 source folder. When I build the Application Deployment Type in SCCM, for my detection method I choose this MSI to get the GUID and version number. Alternatively you can dig around in this folder examining each MSI to find the right one.
  3. Now that you have the source files. Next you need to create a config.xml file. Open a command prompt in the directory with your source files and type "setup /admin" This will open the Minitab 17 Customization Tool. Here you will specify your license server, install options like whether to install the desktop icon, accept the EULA, make it a silent install and disable or enable the Software Update Manager. Create and save a config.xml to your source folder with the rest of the installation files.
  4.  Once you have created and saved your config.xml file, you need the command line for installation. The command line I use for installing Minitab 17 is simply: "setup.exe /config config.xml". My config.xml file takes care of the license server name, no desktop shortcut, accepts the EULA, disabled the Minitab update manager and installs silently.

Deploying without a license server

Ok so what about laptops or computers that may need to use Minitab without a license server, possibly because they wont be online when the user wants to use Minitab or maybe you don't have a license server.
Steps 1 and 2 are the same. At Step 3, enter localhost for the server name and save the new configuration file, possibly naming it config-standalone.xml if you already have config.xml for your license server settings in your source.
4. Next create a txt file called "MultiUserLicense.ini" with the following in it:
[Minitab 17.0]
License File=C:\Program Files (x86)\Minitab\Minitab 17\minitab.lic
Heartbeat=
Retries=
Put this file in your source, you are going to copy it to C:\ProgramData\Minitab\ during deployment. It tells Minitab where the license file is instead of prompting the user.
5. Now create a script to do all of this:
  1. Run the setup command with the appropriate switches
  2. Copy the minitab.lic file to the appropriate folder.
  3. Copy the MultiUserLicense.ini to the appropriate folder.
 I put the following code into a txt file called "install-standalone.cmd"
@ECHO OFF
:Location
Set loc=%~dp0
:Install
"%loc%Setup.exe" /config config-standalone.xml
:Copy License File
copy "%loc%minitab.lic" "C:\Program Files (x86)\Minitab\Minitab 17\minitab.lic"
copy "%loc%MultiUserLicense.ini" "C:\ProgramData\Minitab\MultiUserLicense.ini"
GOTO END
:END
Generally I package both of these into SCCM 2012 as 2 deployment types, the server license type is targeted to desktops, the stand alone is targeted to laptops.


1 comment: