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

Autoupdate communication

Hello all,

I'd like to know if a mgmt console server could listen on several IP addresses for autoupdate.

I'll explain you. I have one mgmt server who communicate on 2 IP Addresses (rms works between all clients and server). However the mgmt server asks to client to update through one server IP (configuration in iconn.cfg) and I would like that the mgmt server asks to client to update through both server IP addresses.


Here is current iconn.cfg
;[PPI.WebConfig_Primary]
ConnectionAddress = mgmt-server-ip1/.../ESXP
ConnectionType = HTTP

And here is that I would like to have :


;[PPI.WebConfig_Primary]
ConnectionAddress = mgmt-server-ip1/.../ESXP && mgmt-server-ip2/.../ESXP
ConnectionType = HTTP

or something like that. I guess this config is not possible but maybe there is something that comes close.

I hope I was clear. Do not hesitate to ask some information.

Thank you in advance.

Regards,

Wagab

:33865


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

    you can specify only one "address" for each update location (Primary or Secondary) in the policy. It can either be UNC or HTTP (in addition Sophos for the Secondary). Usually one would use a name (NetBIOS or FQDN) and not an IP-address. Normally DNS should provide the correct resolution depending on the client's location.

    Any reason why you put in an IP instead of a name?

    Christian

    :33869
Reply
  • Hello Wagab,

    you can specify only one "address" for each update location (Primary or Secondary) in the policy. It can either be UNC or HTTP (in addition Sophos for the Secondary). Usually one would use a name (NetBIOS or FQDN) and not an IP-address. Normally DNS should provide the correct resolution depending on the client's location.

    Any reason why you put in an IP instead of a name?

    Christian

    :33869
Children
No Data