In my last post, The Migration From ESX to ESXi is Happening. Moving Configurations, I talked about the need to move from ESX to ESXi and some of the options that came along with it. Here we are, almost a month later, and I have started to take my production environment from ESX to ESXi. Here's what I've learned in the process.
Forget keeping your current ESX profile. It doesn't matter if you have Host Profiles, or if you had an old kickstart script. Toss them out the window. Host Profiles based on ESX are going to take into account security profiles which are no longer necessary, and with 4.1 adding new features, they won't be a part of the new host. I've built a sample ESXi 4.1 kickstart script and found out first hand alot of things that were possible with ESX aren't there with ESXi.
As of vSphere 4.1, ESXi now has the ability to perform a kickstart installation, whereby you create a script to configure your ESXi host during the install. Using a kickstart script, you can get an ESXi host up and functional within a matter of a few minutes. The fact that it's functional, doesn't mean it's fully configured. Kickstart scripts are still very limited and can't completely configure your ESXi host with all that vSphere 4.1 offers. Some features that can't be scripted (atleast in my own testing) are Local Active Directory integration, prompting a user for input to create a dynamic script, simply adding a host to vCenter, configuring a Distributed Virtual Switch (dVS) because it's not a part of vCenter, and more. This might be only temporary because Justin Guidroz has created a script to add your ESXi Host to vCenter Using MOB as part of a kickstart.Add a comment