• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Fog Service MSI+MST

Scheduled Pinned Locked Moved
General
3
4
2.5k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N
    need2 Moderator
    last edited by May 7, 2014, 6:27 PM

    I am looking to deploy the Fog Service to Windows machines already running in our domain via a GPO and the Fog Service MSI. But I am having a hard time creating the MST that will tell the MSI what IP to use for the Fog server, and allow me to control the other options presented during a typical install. Anyone have anywhere for me to start?

    1 Reply Last reply Reply Quote 0
    • J
      Junkhacker Developer
      last edited by May 7, 2014, 9:07 PM

      not sure if the installer supports entering the IP, but you could just install with default settings with [CODE]setup.exe fog-defaults=true /qb[/CODE] and over write the config file with your customized one. it’s located at [CODE]program files\fog\etc\config.ini[/CODE] on a 32bit machine

      signature:
      Junkhacker
      We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

      1 Reply Last reply Reply Quote 0
      • T
        Tom Elliott
        last edited by May 7, 2014, 9:25 PM

        On a 64bit machine the location is:
        [code]program files (x86)\fog\etc\config.ini[/code]

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        1 Reply Last reply Reply Quote 0
        • N
          need2 Moderator
          last edited by May 9, 2014, 4:35 PM

          Perhaps I miscommunicated a bit. Typically an MSI is deployed through a domain rather than an EXE. This allows the domain to control what is done with the installer a bit more, including the use of an MST. The MST is a transform file that feeds the MSI commands and/or fills in options that the MSI usually contains. By default all domain managed MSI installs are silent, so in addition to not wanting to rely on the end user to know what buttons to push on an installer, an MST is necessary for anything other than a completely default install. I COULD replace the .ini files, but I would have to do this with another script, and I don’t know of a way to do this that is smart enough to run once per install, but also run again later if the install is marked as damaged or is somehow removed.

          I’ve dug into the MSI a bit, and I have found a section under _Validation where I can modify a Table AppID with Column RemoteServerName. I will do some testing and report back.

          1 Reply Last reply Reply Quote 0
          • 1 / 1
          1 / 1
          • First post
            1/4
            Last post

          167

          Online

          12.0k

          Users

          17.3k

          Topics

          155.2k

          Posts
          Copyright © 2012-2024 FOG Project