This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Enterprise Console 5.0 Remote Management Console Installer

Hi,

Older versions (4.5, 4.7) allowed us to install a "remote management console" to manage the central server from another machine (IT staff desktop, etc.)

Can't seem to find the installer for 5.0, and when I run the main installer it tries to install a full new management server instance (which is not what I want.)

Any ideas how to do this?

Regards,

Jon.

:20675


This thread was automatically locked due to age.
  • Hello Jon,

    use the same installer as for your central server. It should prompt you with a Components Selection page. Quoting from the Advanced Startup Guide chapter 7.5: On the Components Selection page, make sure that Management Console is selected and Management Server and Database are not selected. It is the same procedure as before (the exact behaviour depends on the components - i.e. a previous version - already installed on this computer). 

    Christian

    :20685
  • Hi Christian,

    Perversely, these options were not presented to me when running from the self-extracting installer. I had to navigate to the extracted files and run setup.exe from there, after which the options were available. Now, even the self extractor is providing those options, so I am confused, but able to do what I want, so... yeah. I guess that's a win?

    Cheers,

    Jon.

    :20803
  • Hello Jon,

    Perversely, these options were not presented to me when running from the self-extracting installer

    I'm too lazy to check this but you're probably right (I vaguely remember it being the case) . If this is so, then I'd say it is either a defect or a documentation error as according to the Startup Guides you should be presented with the Components Selection. Since aeons I'm in the habit of just downloading the installer, extracting the files to some shared location and then cancelling the installer. To install I connect to this location and run setup.exe.

    Thanks for your report

    Christian

    :20809
  • I do not see any option to allow me to install just the remote management feature. Can you point me to the exact file I need to install?

    :21747
  • HI,

    EDIT:

    I've just realised this thead is about remote Sophos Enterprise Consoles (SEC), not the Remote Management System (RMS).  

    Regarding the remote SEC.  As of SEC 5.x there is now:

    1. The setup.exe ("\sec_50\ServerIinstaller\setup.exe" )

    2. The various MSI installers (database, console, server)

    You should run setup.exe ("\sec_50\ServerIinstaller\setup.exe"), which gathers the components you want and based on those chosen the options for the install, accounts, ports, etc... These are gathered and passed to the MSI files as properties.

    You can see these in the bootstrap log file as written by setup.exe (%temp%\Sophos_bootstrapper [timestamp].log) this going on.

    So in theory you could run a silent install of the components once you know you have all the pre-reqs and all the properties you need to pass to the MSIs.  Having performed one install you can use the log file to gather this information if you so wish.  Having said that, unless you need to do many installs, it's best to run the setup.exe as this performs all the up-front checks to ensure install is a success and has all the pre-reqs.

    Just for completeness, if I look in my bootstrap log from when I installed in a workgroup, I see to install the console:
     

    "C:\sec_51b\ServerInstaller\Console64.msi" SERVER_PORT="85" SERVER_COMPUTERNAME="SECSERVERNAME" INSTALLDIR="C:\Program Files\Sophos" INSTALLDIR32="C:\Program Files (x86)\Sophos" ADDLOCAL="Core" REBOOT="ReallySuppress" 

    Note: this doesn't have the account property set so this wouldn't work in a domain environment.

    Regards,

    Jak

    RMS stuff

    ========

    You can't really or at least you shouldn't need to.  As a quick run down:

    1. When you run Setup.exe (the one from the distribution share) it copies cac.pem and mrinit.conf to the client.

    They are placed in the "\Program files\Remote management system\" directory.  

    These are really the configuration of the RMS component.

    2. AutoUpdate is installed.

    3. AutoUpdate pulls down the packages, RMS is always pulled down as is SAV.  SCF, Patch, Compliance Agent are all optional packages.

    4. AutoUpdate, then kicks of the MSI files for each package. So in the case of the RMS package, the MSI is run from the cache directory of AutoUpdate.  

    One of the actions in the RMS installer is to run the comand line tool ClientMRInit.exe, this reads in the mrinit.conf and cac.pem and puts this info into the registry.

    The MSIs are actually controlled by the setup plugin of each package as this has additional logic to assist with installing each package, for this reason you shouldn't run the individual MSI files to install the individual packages, AutoUpdate needs to install them.

    So, you can re-configure RMS, if you think that is the problem by ensuring that the cac.pem and mrinit.conf in the RMS program files directory are correct and run ClientMRInit.exe.  This will re-write out the configuration to the registry but you might have to restart the service to re-read the config.  This is the basis of the tool I wrote which you mafy find useful to reinit the clients.

    http://community.sophos.com/t5/Sophos-Endpoint-Protection/Enterprise-console4-5-client9-5-all-PCs-greyed-out-and-won-t/m-p/8939#M4482

    Hope this explains a few things.

    Regards,

    Jak

    :21749
  • Hello EchelonAdmin,

    if you run setup.exe from the \sec_50 folder (or wherever you extracted the files to) it should present the selection - note as Jon said you have to run setup.exe explicitely, when it's run by the self-extractor it does not ask.

    Christian
    :21767