Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 3 subscribers
  • Views 13706 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

ParentAddress key incorrect for newly Endpoint installation

Phutapong Suanyim

Hi there

I have build up my own sophos installer with Sophos Deploy Packager via command:

.\DeploymentPackager.exe -cli -mng yes -cidpath "C:\ProgramData\Sophos\Update Manager\Update Manager\CIDs\S000\SAVSCFXP" -updp http://XXX.YYY.ZZZ:1777/CIDs/S000/SAVSCFXP/ -sfxpath D:\Sophos_src\sav_107_custom.no.silient.exe -crt R

After it's installation to Windows 7 computer and check registry but the ParentAddress key is incorrect server name as shown below.

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sophos\Messaging System\Router]
"ServiceDescription"="Message router for Sophos applications"
"ServiceHomeDir"="C:\\Program Files (x86)\\Sophos\\Remote Management System\\"
"ParentAddress"="WIN-PKJ3IHORP4C,WIN-PKJ3IHORP4C"
"ParentPort"=dword:00002000
"ConnectionCache"=dword:0000000a
"NumSenderThreads"=dword:00000003
"NumORBThreads"=dword:00000004
"IORSenderPort"=dword:00002000
"ServiceArgs"="-ORBListenEndpoints iiop://:8193/ssl_port=8194"
"NotifyRouterUpdate"="EM"

anyone know why it shown as "WIN-PKJ3IHORP4C" instead of Enterprise Server name "XXX.YYY.ZZZ" and how to fix it ??



This thread was automatically locked due to age.
Parents
  • 0

    Hello Phutapong Suanyim,

    why do you think this is the incorrect server name (and why did you check this particular registry value)? Admittedly that is just lists two instances of the same NetBIOS name is unusual but it suggests that a) the management server is configured to obtain its IP via DHCP and b) there's no FQDN assigned.

    The ParentAddress is set upon RMS initialization from the ParentRouterAddress in mrinit.conf the CIDs root (...\CIDs\S000\SAVSCFXP\). mrinit.conf in turn is created on the management server during SEC installation.

    Christian

  • 0 in reply to QC

    Hi Christian

    Thank you to quick reply.

    No I don't know what exactly issue on this but per my observed the ParentAddress is not set properly and the mrinit.conf from %temp%\cid_packager_temp\SAVSCFXP\ doesn't copy to C:\Program Files\Sophos\Remote Management System\ like usual installation for other 1400 Windows 7 computers.

    It would be great if you please explain how installation mechanism for Sophos installer.

     

    Bests,

    Pond

  • 0 in reply to Phutapong Suanyim

    Hello Pond,

    do I understand correctly that just this one out of 1400 computers doesn't have the expected ParentAddress? Again the question - what gave you the idea to check this registry value, it's usually not something you use to verify that the installation is ok.
    It's still not clear what the observed problem is: Endpoint not "appearing" in the console? Endpoint failing to update? Or?

    So you say that mrinit.conf in the S000 CID is correct (containing XXX.YYY.ZZZ in the ParentRouterAddress)? And the mrinit.conf in C:\Program Files (x86)\Sophos\Remote Management System\ isn't the one from the CID (or installation package)?

    Christian

  • 0 in reply to QC

    Hi Christian

    Yes, you understand corectly, this one out of 1400 computers doesn't have the expected ParentAddress value.

    As I have no idea how to verify that the installation is ok or not and I just suppose the expected ParentAddress value is needful. that why I keep check this registry value.

    the main problem are this endpoint not "appearing" in the console and it failing to update as well.

     

    So you say that mrinit.conf in the S000 CID is correct (containing XXX.YYY.ZZZ in the ParentRouterAddress)? And the mrinit.conf inC:\Program Files (x86)\Sophos\Remote Management System\isn't the one from the CID (or installation package)?

     

    Yes , that's correct.

     

    Bests.

    Pond

     

  • +1 in reply to Phutapong Suanyim

    Hello Pond,

    if Sophos has never been installed on this endpoint and the package works on other machines I don't see from where it could pick up the incorrect mrinit.conf.
    Hm, I'd uninstall what is there, afterwards (just to make sure there aren't any leftovers) remove any remaining Sophos folder from Program Files, Program Files (x86), and ProgramData. Then run the package again. The install should create a Sophos ES setup.log in the user's %TEMP%. Check for other logs in this %TEMP% and \Windows\Temp\.

    Is the WIN-PKJ3IHORP4C name completely unfamiliar?

    Christian 

Reply
  • +1 in reply to Phutapong Suanyim

    Hello Pond,

    if Sophos has never been installed on this endpoint and the package works on other machines I don't see from where it could pick up the incorrect mrinit.conf.
    Hm, I'd uninstall what is there, afterwards (just to make sure there aren't any leftovers) remove any remaining Sophos folder from Program Files, Program Files (x86), and ProgramData. Then run the package again. The install should create a Sophos ES setup.log in the user's %TEMP%. Check for other logs in this %TEMP% and \Windows\Temp\.

    Is the WIN-PKJ3IHORP4C name completely unfamiliar?

    Christian 

Children
No Data
Unfiltered HTML