Thanks Yes I do have some VM's on the DMZ, I make sure I'll have the proper IP's and yes there are multiple re-boots needed.
Thanks On Tue, Jun 15, 2010 at 2:27 PM, Steven Peck <sep...@gmail.com> wrote: > Just make sure you inventory the IP addresses on any system where you > have multiple nic's. While not common, we had several systems with > issues wehre we had to redo the NIC settings after this. It ends up > being about 3 reboots all told. > > Steven Peck > http://www.blkmtn.org > > On Tue, Jun 15, 2010 at 11:12 AM, Damien Solodow > <damien.solo...@harrison.edu> wrote: > > What you’re seeing is the VM hardware version. You need to be running > VMware > > Tools from ESX 4.x before you upgrade them to v7. > > > > Here’s how: > > > > Shutdown the VM. > > > > Right click and choose “Upgrade Hardware” > > > > Turn on VM > > > > Let Windows detect assorted new hardware > > > > Reboot. > > > > Rejoice. > > > > > > > > You can actually have Update Manager take care of this for you as well… > > > > > > > > From: Stefan Jafs [mailto:stefan.j...@gmail.com] > > Sent: Tuesday, June 15, 2010 2:11 PM > > To: NT System Admin Issues > > Subject: VSphere Clients at v4 > > > > > > > > I upgraded to VSphere quit a while ago but just today applied all > Critical > > and Non-critical patches. I notices that "old" VM's still show v4 after > > updating the VMware tools, I even tried to remove re--boot and re-install > > still v 4. However all "new" VM's show v 7! Should they not all just be v > 7 > > after update? > > > > > > > > Should I worry about it or just ignore it? > > > > -- > > Stefan Jafs > > > > > > > > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > -- Stefan Jafs ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
