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,

    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
Reply
  • 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
Children
No Data