When upgrading the above is displayed, would be really good to have more information, much like vROps which displays the progress on each node. Currently it just sits there even with upgrade failures.
I would like to see the ability to force agents in a Group to copy the config from the agent Group into their liagent.ini file as startup config. After doing a mass deploy of agents i found that all agents come With auto_update=yes commented out, and if I use the option to change it in the agent Groups, it will not work as the agent obviously reads the local file at the time where the auto update is triggered. For me ...more »
We have a technical requirement to deploy vRLI nodes across L2 subnets within the same datacenter. Today, this is not a supported/certified configuration. Ideally, the internal balancer could be leveraged, but it is understood that an external load balancer may be necessary. We're looking to get this configuration certified and supported.
Could somebody tell me whether Log Insight 2.5 or 3.0 will work with a certificate using key size 4096? The admin guides only mention 2048 but I was wondering if other values could be used?
When I update Log Insight (f.eks. to the new 2.5 TP) I would love to just go to the "Management\Agents" view and choose "Update all agents" or similar.
I prefer self-contained solutions (like updating VMware Tools) instead of having to rely on 3'rd party deployment tools for maintenance.
Have a small download, less than 50MB, which then downloads the OVA/OVF in a reliable, restartable fashion.