24027 Update remediation of AgentServer <Server Name> timed out.
The Remediation task with a time-out value of 40 minutes.
When you have updates from more then a month, it will take more then 40 minutes to complete the task.
I never seen remediation task been successful, because of this and other issues with the remediation feature.
Please help to update this value or change the behavior so this error does not occur.29 votes
Request you to please connect with support team and raise the same as production ticket. Support Team can work and perform detailed investigation and identify the root cause.
- create a new vm
- create a checkpoint of the new vm
- attach a second disk to the vm
- restore the checkpoint
all versions below UR3:
- the file of the 2nd disk remains on the csv and can be attached later
- the agent removes the file of the second disk3 votes
When LM a VM to a different cluster using VSM, and if the VM has more than one VHDX attached and I want to place each disk on a different CSV. migration fails with an access denied error. Migrating the same VM to one CSV succeeds.1 vote
Add custom pre/post update remediation script for each host to make firmware updates possible during remediation cycle.
I suggest that you add possibility for pre and post powershell scripts for what to do before and after update remediation.
That way it would be possible to do hardware firmware upgrades during the remediation phase. Perhaps with configurable timeout before the host is supposed to be back online again?
Possible parameters to the pre and post scripts could be hostname, BMC address/BMC credentials.0 votes
- Don't see your idea?