Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 2254 views
  • Users 0 members are here
Options
Suggested
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

Can't Install SAV v.9 using push/pull installation.

rlc 
hi,

Anyone who knows how to solve this issue?
Please kindly assist me on this.
The problem is no matter how I try through push/pull installation from the
SEC v. 4 won't install the SAV on the machines. I already tried the
following:

   1. Ensure that the Remote Registry, Server, Computer Browser, and Task
Scheduler services are started.
   2. Ensure that the C$ admin share is enabled.
   3. Ensure that Simple File Sharing is turned off.
   4. Enable File and Printer Sharing for Microsoft Networks.
   5. Ensure that TCP ports 8192, 8193, and 8194 are open.
   6. Restart the computer to make the changes effective.

The above won't help solve the isue.


Pull installation works but it appears in grayed color in the SEC v.4.
Have check the services and sees that it lacks two(services). I tried so
many time already and same things happened.


Another problem with the other machines is  this: through push
installation after I put the username/password and hit finish, nothing
happens, no green/orange arrow shows. But I can ping them and doubled
check that theyre alive.

Thank you.

~rechie
:2950


This thread was automatically locked due to age.
  • 0

    Hi,

    You say the client is missing 2 services.  Which ones are they, I would assume as the machine is greyed out in SEC that they are:

    "Sophos Message Router" and "Sophos Agent" as these form the Remote Management System package?

    If so it would suggest this package failed to install can you confirm this?

    Thanks

    JAK

    :2953
  • 0

    yeah you're right that two were the missing services, I tried already reprotecting it but same thing happened. How come it failed? Its the same directory I used to managed the 1050 machines.

    Thank you.

    ~rechie

    :2954
  • 0

    Hello rechie,

    just saw that you didn't get an answer to your post , sorry.

    It looks like a SEC3 to SEC4 migration and some RMS configuration problem. Have these clients been previously protected? If so, is the server running SEC4 a new one (i.e. not the one used before)? Has it been set up as recommended in Enterprise Console: upgrading to the latest version, and migrating the console and configuration to a new 32-bit server?

    If it's "only" a reinstall/upgrade on the clients they probably (try to) contact the old server. If the keys have been copied but the server name/address have changed then the correct mrinit.conf should be put into the RMS folder (like described here) on the CID. This usually resolves the issue. 

    Please check the Sophos network communications report on one of the updated clients.

    Christian

    :2955
  • 0

    If the services of RMS don't exist that would suggest the RMS component is failing to be installed so it should be generating an MSI error.  If you can locate the MSI log file of the RMS install that should help.  It should be in the \windows\temp\ directory as AutoUpdate is installing this package under the System context.  The file name is: "Sophos RMS install log.txt"

    One of the main causes for failure to install this package is if the files mrinit.conf and cac.pem that are typically copied to the client's directory:

    %Programfiles%\Sophos\Remote Management System\
    by setup fail to be copied as when AutoUpdate installs the RMS package it is dependant on finding these 2 files in the mentioned location.

    So I would check on one of these clients that the directory:

    %Programfiles%\Sophos\Remote Management System\

    exists and in it are the 2 files mentioned above.  on a working machine you should be able to see setup.exe eriting these 2 files to that location.

    As a bit more information. the MSI has a custom action which runs this part of the installer and this action logs to the file:

    ClientMRInit-<timestamp>.log

    So that might also be worth checking if this seems to be the right area.

    Thanks

    Jak

    :2963
Unfiltered HTML