Manually... was a bit nervious given a complete version change... On Wed, Oct 14, 2009 at 3:22 PM, Steven Peck <[email protected]> wrote:
> Did you script the hw upgrade or manually do it? > > On Wed, Oct 14, 2009 at 2:31 PM, Don Ely <[email protected]> wrote: > > I did my upgrade a couple of weeks ago... It was pretty flawless... A > > couple VM's lost their original NIC which in turn created some issues, > but > > not too bad otherwise... > > > > On Wed, Oct 14, 2009 at 2:00 PM, Steven Peck <[email protected]> wrote: > >> > >> We upgraded 15 hosts in one environment last week. > >> > >> Tonight we are doing the vmtools upgrade then the virtual hw upgrade > >> to a selection of guests. > >> 250 guest systems so it will be a long night. > >> > >> > >> > >> On Wed, Oct 14, 2009 at 12:16 PM, Eldridge, Dave <[email protected]> > >> wrote: > >> > We also purchased our hosts thru Dell and they are "OEM" licenses > which > >> > means first call to Dell. I have had to get them to up it to VMWare > >> > directly. It has worked out ok up til now. > >> > I don't have any issues with the esx cluster. It just runs. Now when > >> > it's time to upgrade to ver. 4... > >> > > >> > > >> > -----Original Message----- > >> > From: Michael Leone [mailto:[email protected]] > >> > Sent: Wednesday, October 14, 2009 12:49 PM > >> > To: NT System Admin Issues > >> > Subject: Re: OT: can't power off a VM on ESX 3.5 > >> > > >> > On Wed, Oct 14, 2009 at 2:22 PM, N Parr <[email protected]> > wrote: > >> >> Neither would I other than a last resort, I had this same issue with > a > >> >> guest > >> >> not shutting down a couple weeks ago and called tech support to > resolve > >> >> the > >> >> problem. That's the first solution, but I'm assuming he doesn't have > >> >> support or he wouldn't have been asking here. > >> > > >> > No, I have support. :-) But since we bought our VMware through HP, I > >> > have to call HP support, and go to their VMware support desk. That can > >> > be ... convoluted ... > >> > > >> > If it was an actual emergency, I would have done that. But since it > >> > wasn't critical, I figured I'd ask here. (and I knew it wasn't > >> > critical since no alarms triggered; no other hosts complained; no > >> > users complained they couldn't access various hosts; and the responses > >> > here weren't along the lines of "Wow, that's serious .."). > >> > > >> > :-) > >> > > >> > I wouldn't bounce an ESX host unless I had to, but in this case, this > >> > ESX hosts is (mostly) used by my private testing domain/subnet. So if > >> > I bounced this one particular host, it would be no big deal. I would > >> > just migrate any production VMs onto one of the other ESX hosts, and > >> > go on from there. I'm lucky, in that I have that capability. > >> > > >> > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > >> > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > >> > > >> > > >> > > >> > This message contains confidential information and is intended only > for > >> > the intended recipient(s). If you are not the named recipient you > should not > >> > read, distribute or copy this e-mail. Please notify the sender > immediately > >> > via e-mail if you have received this e-mail by mistake; then, delete > this > >> > e-mail from your system. > >> > > >> > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > >> > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > >> > > >> > > >> > >> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > >> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > >> > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
