As a follow up to my earlier post about W2K8 Std R2 with SP1 Problem using VMware Customization it turns out that SP1 is not the problem it is actually a Windows Update that caused the issue. We fired up another VM without SP1 and well... we thought we found the problem and that we were done becasue when we fired up the VM we tested it with a plain W2K8 R2 install with no SP1 and no Windows Updates.
Well... we quickly found that was not the issue becasue we then patched and the same problem blue scree reboot problem came up. The problem is we don't knwo which one of the 67 updates it is.
OK so here is what we did to get around this problem and back to firing up VM's in minutes rather than hours. We installed W2K8 R2 with no patches at all and no SP1. We created a W2K8 VM template and used the VMware Custimization and all was well -no BSOD's and no reboots. We then patched each machine with no issues. The trick is don't add the Windows updates and you won't beat your head against the wall like I did.
We called VMware support after we found the problem and they told that after testing the fix is to update your ESXi server to 4.1 update. Our server was 4.1.
I have not tested nor verified that Update1 fixes the problem. I hope this info helps someone out and you do not lose all of the time that we did tracking down the problem.
Well... we quickly found that was not the issue becasue we then patched and the same problem blue scree reboot problem came up. The problem is we don't knwo which one of the 67 updates it is.
OK so here is what we did to get around this problem and back to firing up VM's in minutes rather than hours. We installed W2K8 R2 with no patches at all and no SP1. We created a W2K8 VM template and used the VMware Custimization and all was well -no BSOD's and no reboots. We then patched each machine with no issues. The trick is don't add the Windows updates and you won't beat your head against the wall like I did.
We called VMware support after we found the problem and they told that after testing the fix is to update your ESXi server to 4.1 update. Our server was 4.1.
I have not tested nor verified that Update1 fixes the problem. I hope this info helps someone out and you do not lose all of the time that we did tracking down the problem.
No comments:
Post a Comment