Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 214415

Re: Best Practice for keeping ESXi up-to date

$
0
0

http://imagicon.info/cat/5-59/vbsmile.png NeuroJava wrote:

 

Hi,

I was wondering what's the best practice for keeping the ESXi image (with driver packages) upto-date.

We are planning on using stateless ESXi deployment using Auto Deploy and wondering:

1. Use Power CLI as indicated here http://www.gabesvirtualworld.com/updating-your-esxi-host-using-vmware-vsphere-5-auto-deploy/

2. Use VMWare Update Manager (VUM) and allow users to download the packages they want to update and then update the auto deploy image so it gets picked up in subsequent boots.

 

It seems to me there is a certain gap in Auto Deploy or I'm missing something...

but how does one plan on using Auto Deploy and keeping the images upto date? Is there some way to use VUM and also update the Auto Deploy images?

 

 

 

NeuroJava wrote:

 

Hi,

I was wondering what's the best practice for keeping the ESXi image (with driver packages) upto-date.

We are planning on using stateless ESXi deployment using Auto Deploy and wondering:

1. Use Power CLI as indicated here http://www.gabesvirtualworld.com/updating-your-esxi-host-using-vmware-vsphere-5-auto-deploy/

2. Use VMWare Update Manager (VUM) and allow users to download the packages they want to update and then update the auto deploy image so it gets picked up in subsequent boots.

 

It seems to me there is a certain gap in Auto Deploy or I'm missing something...

but how does one plan on using Auto Deploy and keeping the images upto date? Is there some way to use VUM and also update the Auto Deploy images?

hi first check related service are running automatically like WS-Management service .

 

for more follow this link

 

www.vmware.com/pdf/vsphere4/r40/vsp_40_esxupdate.pdf

 

Yours,

Satya


Viewing all articles
Browse latest Browse all 214415

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>