While scanning a ESXi 4.1.0 (build 348481) host from the host update manger tab to see if the host is still compliant. I got a error : The host returns esxupdate error code: 10. check the update log file and esxupdate.log files for more details
A couple of days ago, the PepperCrew had his monthly meeting. There was a little discussion about the new vSphere 5 release from VMWare. In the release notes there is mentioned that it will support OSX installations. I’m not convinced that that would work. There is a big community in the world who wants to install OSX in a sandboxed environment or even native on not Apple hardware. (Hackintosh or OSx86 etc etc). So, lets try some different scenario’s.
Apple supports only virtualized OSX Server installations on Apple hardware. Normal OSX installations aren’t supported or possible.
First Test: Install OSX Snow Leopard (10.6) in VMWare Fusion (On an iMac)
This is not allowed. The installer stops with the following error: 
Second Test: Install OSX Snow Leopard Server (10.6) in VMWare Fusion (On an iMac)
For the project where i worked on lately i documented the BIOS settings i have made with the reason why. These are the BIOS settings i use for a HP BL 460c G6 blade where vSphere ESXi 4.1 will be installed on. The bold words in the left column are the options to be adjust. the location is written above in the same column but may vary between BIOS version.
When you want to replace the old virtual network card for a VMXNET3 network card of a Domain controller (DC) and when the DC is also DNS server (AD integrated) and the only one in the domain you may encounter some problems. Yesterday i replace the old network card for a VMXNET3 adapter in a DC that was the only DC in the Domain (yes i hear you 1 DC = no DC ) and i encounter the following errors on the server:
Lab manager is a product that is not been made for a WAN connection and the security that you want for safety. But it can work. Don get me wrong. Yes the connection of lab manager is secure because it is over port 443. Is it?
For internal use we have build a playground for testing new products and to use for demo’s. But as small as it is (2 ESX hosts) we like it to be secure and be able to use it at a customer site ( for the demo part ). And when you work at a company where most of the employees adore Citrix product the choice of a Citrix Access Gateway (CAG) was easily made. So the setup for the environment in it simplistic form is looking like the drawing below
I am building a scripted installation for a customer. The last time i did this it was for ESX4.0 and i have never done a scripted install with the ESXi implementation until now. When I made a scripted install for ESX i always customize the partitions for the installation like this in the KS.CFG file:
My vSphere ESXi 4.1 stopped during booting form the ISO file : Booting: MBI-0×00010128, entry=0x0040024a. I had made a ISO with a custom KS.CFG file for scripted installation.
I havened seen this message before but i did some digging and found out the the ISO file was corrupted. I build a new one and it the problem was gone.
This error looks very simulate to Booting: MBI=0x00100d8, entry=0×00100212 this error indicates that the hardware you are trying to use is not on the HCL list of VMware
Loading ...