I have seen this behavior in my environment before. My guess is that AutoDeploy is still sending the old image profile to the host. You can see if this is the case within vCenter Client...check the summary tab to see what image profile is loaded. I would try running a check compliance and repair on the host. A few times I have run apply-esximageprofile to assign the new image to that host.