its just a real shame that the "bug" has nothing to do with the functioning of ESX... it's all because of licensing and is why I am so critical of this particular error
Apprently you didn't read the posts either. It is an intrigal part of ESX, licensing or not, they ALL work TOGETHER. It doesn't matter which piece caused the problem, it's all part of the same CODE. It's not licensing, licensing is fine, it's within ESX itself. And how you can even say nothing to do with functioning..
you can't do DRS, vmotion, or power on VM's, that's pretty much ALL ESX does! It's 100% function.
If you change the date, and you have vm ware sync tools on, you have effectively made an entire environment useless. VM's can't login with AD unless time is within 5 minutes, some databases need time/date to be CRUCIAL to their updates.. this is a MAJOR hit, it's all about function, and nothing to do with licensing.
