Can someone please explain to me why a "FREE" product has a friggin expiration date? It just does NOT MAKE SENSE! Even worse, is a Licensed version one has paid for has this expiration "BUG...
See more...
Can someone please explain to me why a "FREE" product has a friggin expiration date? It just does NOT MAKE SENSE! Even worse, is a Licensed version one has paid for has this expiration "BUG". YES IT IS A BUG! QA missed the big fat cock roach in their process. Here's what I want. I want install Enterprise binaries that has NO expiration. If our agency paid in excess of $15,000.00 to license our servers (Enterprise version) the friggin thing should never ever expire. I feel like VMware does not trust it's customers eventhough they have already spent their thousands of dollars on their product. MS 2003 Server does not expire does it? NO. Enough with this garbage about software piracy and protecting your product, the same old boring played out song. If we paid for it it should never expire. VMWare's method is basically saying "you're all pirates and eventhough you paid up the a(insert letters here), I still don't trust you worth doodoo". That's why this issue is here. Hmmmm.... This scenario should sound familiar to VMware, remember the "FREE" vmware server release?....tick....tick....tick.... Edit Just to clarify becuase there seems to be some confusion on this. The license expiration issue has nothing to do with how VMware sells or licenses its products and the reason this happened on a "Free" product is because the time expiration was left in from the Update 2 beta code. VMware puts a hard expiration date into their beta products, this has nothing to do with preventing people from stealing the product, but to ensure beta products that have bugs and different features don't stick around and end up in production. So again, this was a huge mistake on their part to not take that code out, and we all have a right to be mad about it, but lets be mad for the right reasons. That being said, lets try to keep this thread to a technical discussion of the patch. So far our experiance has been mixed, we have a large environment with a variety of different hardware as well as ESX and ESXi embedded and installable all running. Most of the issues we have seen involve ESXi, standard ESX patching with UpdateManager appear to be working fine. I believe there is a problem with this patch and ESXi and UpdateManager, more info to follow. Don Pomeroy VMware Communities User Moderator