Are people installing VI 3.5 or going straight

to Vsphere 4 for new deployments? Have any of you been involved with the planning stages of recent deployments and had to go through this?

We are in purely "planning stages" where everyone is putting ideas together, and it's up to me to help come up with the virtualization parts.

My question is this, Do you deploy 3.5 ESX hosts and then migrate to 4 at a later date and deal with everything involved with that. Or do you go straight to 4 pick your flavors of it.

I do not know alot of 4 because it is new, and I have not seen alot of bad things said about 4 and problems of the new deployments, etc on the vmware forums.

Have any of you deployed 4 (production or lab), and if you did, did you like it? I downloaded it when it first came out, but never even got to install it on my lab server.

It looks great, but I am not sure if it's proven enough to put out yet. I have been concentrating so much on MS stuff lately, I kinda put the vmware news on the back burner.

Any thoughts and suggestions would be great.

Thanks

BreadFan

Find more posts tagged with

Comments

blargoe

I've got vSphere in the lab and I've been to training and I like it, in fact we're probably going to proceed with upgrading our small deployment of 3.5 to 4 before virtualizing the rest of the company.

Whatever you do just be sure to test, test, and test some more.

RTmarc

We were using vSphere in production at the company I just left. It's certainly an improvement over VI3.5.

astorrs

Go to 4 directly. For a fresh install it's perfect as you can design for the new features and not have to rework it later after an upgrade.

jibbajabba

astorrs wrote: »

Go to 4 directly. For a fresh install it's perfect as you can design for the new features and not have to rework it later after an upgrade.

Just make sure to check the CPU HCL in case you'd like to use FT ..