Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 12 replies
  • Subscribers 1 subscriber
  • Views 10313 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

Failed Sophos intall RMS intall issue

Fredk

I have an issue with a failed intall of Sophos v9.5 on a workstation.  The install is being pushed out from the enterprise console.

Here are the contents of the RMS Install log:

Install from:[D:\Program Files\Sophos\AutoUpdate\cache\rms]
Install to  :[(null)]
MsiPackagePath: [D:\Program Files\Sophos\AutoUpdate\cache\rms\Sophos Remote Management System.msi].
RMS: Current product is not installed.
RMS: Setup Plugin running MsiInstallProduct(D:\Program Files\Sophos\AutoUpdate\cache\rms\Sophos Remote Management System.msi,
                                            REBOOT=ReallySuppress ALLUSERS=1 SOPHOS_TP_TOKEN=1 TRANSFORMS=1033.mst)
!RMS: Setup Plugin failed to install product: Exit code [1603]

(null) does not look like a very promising install path.  Is this the issue?  This is the only computer on our network with this particular issue.

Any suggestions would be appreciated.

:10271


This thread was automatically locked due to age.
Parents
  • 0
    Hi,
    It looks like the machine was already managed before from a different SEC installation. That being said, you should be able to do as follows:
    1. Delete the cac value in the registry:
    HKEY_LOCAL_MACHINE\SOFTWARE\[Wow6432Node]\Sophos\Messaging System\cac
    2. Delete the pkc and pkp values under:
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sophos\Messaging System\Router\Private\pkc
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sophos\Messaging System\Router\Private\pkp
    and:
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sophos\Remote Management System\ManagementAgent\Private\pkc
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sophos\Remote Management System\ManagementAgent\Private\pkp
    should they exist.
    3. Delete a file called mrinit.conf.orig in:
    D:\Program Files\Sophos\Remote Management System\
    should it exist.
    4. Ensure the latest cac.pem and mrinit.conf files are in:
    D:\Program Files\Sophos\Remote Management System\
    and are correct for the current installation.  You should be able to browse back to the new server and access the SophosUpdate share, you'll find them under \CIDs\S000\<Product>\ I suspect.
    5. Call update now, this will start the install of the RMS package, during this install attempt, clientmrinit.exe will run, read in the cac.pem and mrinit.conf files and be able to update the registry keys.
    Note: If you have this problem on multiple machines, I wrote a HTA to generate a script you can run on a number to ensure they are correctly configured:
    /search?q= 8939
    Regards,
    Jak
    :10417
Reply
  • 0
    Hi,
    It looks like the machine was already managed before from a different SEC installation. That being said, you should be able to do as follows:
    1. Delete the cac value in the registry:
    HKEY_LOCAL_MACHINE\SOFTWARE\[Wow6432Node]\Sophos\Messaging System\cac
    2. Delete the pkc and pkp values under:
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sophos\Messaging System\Router\Private\pkc
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sophos\Messaging System\Router\Private\pkp
    and:
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sophos\Remote Management System\ManagementAgent\Private\pkc
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sophos\Remote Management System\ManagementAgent\Private\pkp
    should they exist.
    3. Delete a file called mrinit.conf.orig in:
    D:\Program Files\Sophos\Remote Management System\
    should it exist.
    4. Ensure the latest cac.pem and mrinit.conf files are in:
    D:\Program Files\Sophos\Remote Management System\
    and are correct for the current installation.  You should be able to browse back to the new server and access the SophosUpdate share, you'll find them under \CIDs\S000\<Product>\ I suspect.
    5. Call update now, this will start the install of the RMS package, during this install attempt, clientmrinit.exe will run, read in the cac.pem and mrinit.conf files and be able to update the registry keys.
    Note: If you have this problem on multiple machines, I wrote a HTA to generate a script you can run on a number to ensure they are correctly configured:
    /search?q= 8939
    Regards,
    Jak
    :10417
Children
No Data
Unfiltered HTML