why chen is criticizing so much?
why don't he think virtualization has reduced the load of physical server and thereby power consumpton and VMware has gurnatee that they will fix all the issue without any data loss.
As you know mistakes often happen...
if you buy any software it should have some bug...
but always think that how this software has made us task easy.
I know it is frustrating...
In this modern world nothing is perfect.
so please don't try to criticize so much.
if you can't handle then don't buy no software and do it everythingmanual....
|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary 
[1,407]
Women 4 times more likely than men to cough up personal info [589]
Japan's 10 funniest tech-related commercials [Videos] [407]
Throwing away a promo CD is "unauthorized distribution"? [1,265]
Adults too quick to dismiss educational video games [682]
Attack of the iPhone clones [Slideshow] [578]
10 things IT needs to know about AJAX [1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow] [409]
|
|
Latest != Greatest. You've all been "Microsofted" if you think
Latest != Greatest.
You've all been "Microsofted" if you think you should put a patch on production servers, because one exists. This particular patch doesn't even address any security issues, it's expanding upon feature sets.
Please report for re-assignment and leave your geek badge on my desk.
so some customers were advised and others not?
We were proactively notified by VMware Monday
hmmmmmmmm
I'm calling BS...
"We were proactively notified by VMware Monday. They told us these are the symptoms and what would happen if you powered down your virtual machines,"
Riiight...
I was advised Tuesday ( by 9pm Monday US PST time)
Yeah I got an email advising me. this is because I am in Australia, I was experienceing it by 9:30am our time AND Vmware aust confirmed it with me by 2pm which is some 15-18 hrs ahead of the USA, (actually 9pm PST Monday night in the USA) we had already experienced the bug. so don't quickly calling BS, because technically VMware USA did find out about it on Monday. I'm tipping their priority was to inform their large scale enterprise clients first.
Only Large Scale Customers..
We run a small ESX shop and have a current support agreement in place.
We did not receive any notification about this bug, First we knew of it was in the news. Luckily we were going to update next week.
I guess only the really big boys get told and us little fish get hung out to dry.
Patch Available
http://kb.vmware.com/selfservice/dynamickc.do?externalId=1006721&sliceId=1&command=show&forward=nonthreadedKC&kcId=1006721
-Gilson Soares
why is it always pro VM ware
Why do you post pro VM Ware articles and never any negative. In my dealings , I have come across too many shops that will not run their critical data on VM Ware. So they keep some physical servers. I womnder outloud as to the agenda of the authors of the articles, as to why they are so pro VMWare and not objective. Do they research befoe they write? If so I have never been asked. Bottom line... VM Ware came at an extreme expense, it locked us in to only their add ons. and it is always extremely difficult to get answers when there are problems. I would liek to see an objective article oncwe in a while. Get off the VM ware payroll.
Problem was caused by VMware....
but if fairness, it is us that uses third party software to run our buisne$$es. Seems much easier to blame to software company than our own short-sightedness about relying on others to support our business. People should just write their own software for their critical business functions. No one to blame then.
zzz
zzz
Poor Judgement
This isn't as major an issue as it's made out to be as anyone in a large shop should know not to install the latest patches without having some real production use under their belt.
If they experienced an outage then it's somewhat their own fault.
Face it in todays day and age everything related with IT is bug ridden. Thus, it's up to us to test patches and ensure functionality isn't damaged prior to placing patches, firmware, etc... on critical systems.
Post new comment