[ad_1]
Utilization Meter 4.5.0.1 patch launch rolled out on Might twenty third. This new launch addresses a significant situation present in Utilization Meter 4.5.
Why is Utilization Meter 4.5.0.1 wanted?
The brand new Utilization Meter 4.5.0.1 fixes a consumer permission situation with Utilization Meter 4.5. The issue that it solves is said to the umscheduler account, which doesn’t have sufficient permissions to run the next Utilization Meter cron jobs: umhealth, logarchive, umlogs, umlogsize, and umarchive. In consequence, these cron jobs can’t run robotically, and the Utilization Meter logging is stopped.
Because of the lack of consumer permissions, the umscheduler consumer can’t write and delete log recordsdata in /op/vmware/cloudusagemetering/var/logs listing and begin or cease Utilization Meter processes with begin.sh, and cease.sh. The latter can have an effect on the metering in case there is a matter with any of the information collectors. The issue received’t be detected, and the companies can’t be restarted.
One other situation that stems from the issue is that some log recordsdata older than 90 days are usually not robotically deleted. Additionally, outdated utilization knowledge recordsdata from /choose/vmware/umdata/, relying on Utilization Meter working mode, are usually not cleaned, e.g., after 90 days for on-line mode. This can influence the consumed storage capability in your Utilization Meter equipment however received’t affect the reported utilization knowledge as solely new knowledge goes to Utilization Perception.
What is going to occur with Utilization Meter 4.5?
Utilization Meter 4.5 will not be downloaded after the discharge of Utilization Meter 4.5.0.1. It is going to be faraway from Buyer Join, and shortly after that can be out of help.
What to do after Utilization Meter 4.5.0.1 is out?Â
To keep away from any incorrect metering and compliance points, we extremely suggest that you simply take motion to improve to Utilization Meter 4.5.0.1! That is very true for companions operating Utilization Meter 3.6.1, 4.1, 4.2, and 4.5. Try the next info per a Utilization Meter model.
Companions operating Utilization Meter 4.5
If you’re a accomplice operating Utilization Meter 4.5, you might want to improve instantly to Utilization Meter 4.5.0.1. You may both carry out an in-place improve or set up Utilization Meter 4.5.0.1 and add your VMware merchandise anew.
The next info will enable you to carry out an in-place improve or contemporary set up.
Companions operating Utilization Meter 4.X
Companions operating Utilization Meter 4.x situations ought to take into account that a few of them will quickly be out of help. That signifies that upgrading to Utilization Meter 4.5.0.1 is very really helpful!
Try this info on the way to improve from Utilization Meter 4.x to Utilization Meter 4.5.0.1.
Companions operating Utilization Meter 3.6.1
If you’re nonetheless operating Utilization Meter 3.6.1, you have to to improve to Utilization Meter 4.X by deploying 4.5.0.1 as a brand new equipment. To avoid wasting effort and time, migrate your product configuration to Utilization Meter 4.5.0.1. You should utilize a migration script that can switch the main points of your VMware merchandise, reminiscent of endpoint IP or hostname, consumer credentials, and product model, to a pre-deployed Utilization Meter 4.5.0.1 occasion.
Test these procedural steps to learn to do it.
Be aware: Remember the fact that merchandise metered by Utilization Meter 3.6.1 can differ from these supported by Utilization Meter 4.5.0.1. Test the VMware Interoperability Matrix earlier than migrating your product configuration to keep away from confusion. The migration script will solely migrate these merchandise supported by Utilization Meter 4.5.0.1
Abstract
Whereas we acknowledge the inconvenience that this situation introduces to you, we’ll make an additional effort to reduce the danger of getting such unplanned releases sooner or later. We’ll proceed with our try to supply clear and handy VCPP utilization metering to you.
When you have extra questions on switching to Utilization Meter 4.5.0.1, e-mail us at usagemeter@vmware.com or go away a remark.
 Assets
[ad_2]
