![]() Fill in General and Content tabs as you normally would.Manually specify the deployment type information.Manually specify the application information.Then you create the application as normal.Pushd \\your-sccm-server\sources$\Software\Minitab16 setup.exe /config %~dp0config.xml /qn popd \\ your-sccm-server \sources$\Software\Minitab16 So instead I created an install.cmd script with the following lines: Even if I spelled out the entire UNC path it did not like it and I’m not sure why. However, in testing the minitab installer did not like %~dp0 switch in place of the full path for the config file. ![]() The Minitab deployment guide states you should use setup.exe /config.The instructions below are for creating the application. I prefer applications to packages but either would work. Copy over the unpacked files to your SCCM sources dir.Save your xml file into your unpacked minitab files directory to reside alongside setup.exe.I turned the notifications since our users don’t have local admin rights, the notification would just be annoying. All other settings you can choose for yourself.Under install options be sure to tick the “I accept license agreement”.Specify your licensing server with port number. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |