Scripting Question

SOTI MobiControl 10.00

07/03/2015 2113 views
Has anyone worked on SOTI MobiControl 10.00?A single ".exe" file is provided as source, and this exe installs: 1. Crystal Reports 11.5.8 2. Crystal Report 2008 Runtime SP3 3. Microsoft SQL server 2008 R2 4. Microsoft SQL server 2008 R2 Native Client 10.52.4000.0 5. Microsoft SQL server 2008 R2 Setup (English) 10.52.4000.0 6. Microsoft SQL server 2008 R2 Setup Support Files 10.1.2731.0 7. Microsoft SQL Server Browser 10.52.4000.0 8. Microsoft SQL Server VSS Writer 10.52.4000.0 9. SOTI MobiControl 10.00 Tried extracting the files using Uniextractor but that didnt help. Any good suggestion on this will be helpful.
0 Comments   [ + ] Show comments


All Answers

There are so many items being installed that there must be individual installers in the .exe for each software title.

If they're not showing in %temp%, and you can't extract them - try looking in the uninstall key in the registry to see if the 'InstallSource' value points you in the right direction. Some installers put their stuff in %appdata%.

There are 9 items in your list, they *should* be 9 separate packages, as all but the MobiControl are reusable for other applications/purposes.
If you can't extract and grab the installers, then you might have to talk to the vendor about mass deployment strategies for their software and how they recommend it should be handled.

Answered 07/03/2015 by: dunnpy
Red Belt

  • Hi Dunnpy, Thanks for writing.
    And, Yes you are correct on the part that this application extracts files to different locations e.g.
    some of the files get extracted to %appdata%; and other gets extracted to root drive (in a permission restricted folder).
    And the MSIs extarcted are many in number..almost 9-10 in number.
    Yes, we can the lengthy path to call all of these MSI files in a batch file..but I was looking for any other alternate and feasible solution.
What exactly are you trying to achieve?  Your original posting is just a report on what the software installs, but apart from asking if anyone has installed this software, there appear to be no specific questions relating to what you want to achieve.
Calling a sequence of MSI files from a batch file or other wrapper script is a perfectly feasible solution, and probably quicker to implement than any other workaround unless your vendor can provide you with specific information.
Answered 07/04/2015 by: EdT
Red Belt

  • Yes, we can call all these extracted MSI files in a batch file as per install sequence but the exact problem is lies with the main application MSI file (MobiControl.msi) extraction, this .msi file extracts at:
    "C:\Program Files (x86)\SOTI\MobiControl\{12DDB8BE-AF8E-4004-B5D7-7738AEC7DEF4}\" and stays there for half second and disappears and the installation continues to progress. And, am not able to copy the extracted file because of this quick extract + installation process, any idea how do I copy this extracted msi file.
    Tried "Uniextractor" but this was unable to extract all the MSI files from setup.exe also in Eventviewer there is no more details of the "MobiControl.msi" execution path apart from the mentioned one above.
    Any help / suggestion how can I get this sorted?
The first thing I would try is to create the folder "C:\Program Files (x86)\SOTI\MobiControl\{12DDB8BE-AF8E-4004-B5D7-7738AEC7DEF4}\"  and then remove the delete permission from this folder for the account that is running the install. That should allow you to gain access to the file.
Also, bear in mind that MSI files are cached in c:\windows\installer, so if you take a directory listing of that (hidden) folder before installing the application, and then after, you will find out all the MSI files that have been cached. Starting with MSIEXEC.EXE version 5, the entire MSI is cached, not just the tables, since Microsoft found that signed MSIs would not uninstall if just the (modified) cached copy was used.
Answered 07/06/2015 by: EdT
Red Belt

I don't think that there any shortcuts to package/deploy this app and I would pursue the separate package per item - as they are software titles in their own right.

Chain the packages together if you need to deploy them together, but also have the option to install the individual items.
This will also assist in troubleshooting the deployment. If one item fails on a batch file install then you have to troubleshoot the whole batch chain. If one application that it is its own package fails, it is immediately obvious which has errored.

Answered 07/06/2015 by: dunnpy
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