Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 7 replies
  • Subscribers 1 subscriber
  • Views 2330 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

Autoupdate communication

Wagab

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.
  • 0

    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
  • 0

    Hello Christian,

    I said IP but I would like to say "name", the problem is the same. But you told me that we could specify a Secondary location, it's very interesting. How can I apply that config ?

    Thank you in advance

    Wagab

    :33951
  • 0

    Hello Wagab,

    so the server has actually two different names (apart from the IPs) on the two networks?

    In this case the IMO best solution is to assign the clients to different groups with appropriate policies.

    Christian

    :33957
  • 0

    Hello Christian,

    so the server has actually two different names (apart from the IPs) on the two networks?

    Yes

    In this case the IMO best solution is to assign the clients to different groups with appropriate policies.

    What do you want to say exactly ? What does IMO mean ^^ ? You want to say that I have to manage that only in the console and not with configuration file ?

    I will try. Thank you

    Wagab

    :34039
  • 0

    Christian,

    Thank you. I learn a lot of thing with you. ^^

    Regards,

    Wagab

    :34041
  • 0

    Hello Wagab,

    What does IMO mean

    :smileyvery-happy: In my opinion -  commonly it's IMH(umble)O but at my age I no longer see a need to pretend to be humble (and it is sometimes used ironically).

    I have to manage that only in the console

    Well, yes, it is often referred to as management console. And I'd say this is its main purpose. Furthermore, modifications to the config files on the client won't stick - they can alway be overwritten by the console (or a reinstall). Defining a policy in and assigning it from the console results in the corresponding config files written on the client. That's what it's about.

    Feel free to ask if you have more questions.

    Christian 

    :34045
  • 0

    Hello Christian,

    that works, thank you.

    Regards,

    Wagab

    :34293