VMware Cloud Community
Ludicrous09
Enthusiast
Enthusiast
Jump to solution

Auto Deploy questions.

I am having an issue with auto deploy and am not understanding if what is going on is by design or i am not doing something correctly.

So I have a two node cluster that I have booting from a copy of the default image ESXi-5.5.0-1331820-standard, my version is called ESXi_5.5 every things works as expected and i have the answer files and host profiles all working.  When I reboot a host and it comes back and gets it's image, adds itself to the cluster, applies its host profile, takes itself out of Maintenance mode and configures HA.  Ok everything is Peachy.

So now I have made a new Image with some additional Drivers that I needed (This Image is called ESX_5.5New) and killed my old  active deploy rules and deleted them, created new deploy rules and made them active. The New Deploy Rules work sort of.  

If I reboot the host it still gets the old image with out the new drivers.   Yet if i shut the host off and kick him out of vcenter and then boot him back up, he will get the new image.  Surely this is not what you have to do everytime you update the image.  am I missing something here?

I have run the get-Cluster DR-Test | Get-vmhost | Test-DeployRuleSetCompliance and both servers come back as compliant. 

Tags (1)
0 Kudos
1 Solution

Accepted Solutions
Ludicrous09
Enthusiast
Enthusiast
Jump to solution

I fixed my own issue.

Even though when i would run get-Cluster DR-Test | Get-vmhost | Test-DeployRuleSetCompliance and both servers come back as compliant.  The Auto deploy server was some how still caching the old image.  Once I ran Repair-DeployImageCache every thing worked with out me having to kick hosts out of vcenter.

View solution in original post

0 Kudos
1 Reply
Ludicrous09
Enthusiast
Enthusiast
Jump to solution

I fixed my own issue.

Even though when i would run get-Cluster DR-Test | Get-vmhost | Test-DeployRuleSetCompliance and both servers come back as compliant.  The Auto deploy server was some how still caching the old image.  Once I ran Repair-DeployImageCache every thing worked with out me having to kick hosts out of vcenter.

0 Kudos