Comments on: Partner Exchange 2010 Session TECHBC0320

By: Russell

Russell — Fri, 12 Feb 2010 18:58:51 +0000

I don’t buy the attack surface argument for a lot of reasons that really go outside the scope of this blog post commentary. Hopefully Scott can provide a post in which we can have a solid discussion; I don’t want to hijack his main point (VSS) but I do think its an important discussion.

By: stuart

stuart — Fri, 12 Feb 2010 17:29:21 +0000

Hi Scott , great article. I agree with the new VSphere APIs there will be alot a interest in moving towards Image based backups. I think it should be noted that as it stands toady you will see no application quiesce in Windows 2008 leveraging the Vmware Tools VSS provider, I blogged about this here http://virtualy-anything.blogspot.com/2010/02/understanding-vss-in-vmware-backups.html

By: Paul

Paul — Fri, 12 Feb 2010 00:21:47 +0000

Russell – I absolutely agree. Troubleshooting is much more cumbersome with ESXi….however, I can also appreciate VMware’s position with wanting to minimize the possible attack surface. Of course, with most security enhancements there are trade-offs. As for me, I’ll more than likely continue to use “classic”, and consider managing them as ESXi hosts.

By: brandon

brandon — Thu, 11 Feb 2010 21:48:50 +0000

Thanks for your reply Scott. Btw your Mastering VMware vSphere 4 book was great . I read it cover to cover. Odd how I can read technical stuff like that and enjoy it, while other ‘entertainment’ material dries out my eye sockets.

By: Russell

Russell — Thu, 11 Feb 2010 21:17:53 +0000

I have to say, troubleshooting ESX without a service console is among the most painful things I have ever attempted to do. I’m a little annoyed that I forgot to bring this up during PTAB since this is a hot button for myself and a couple fairly large customers.

By: Paul

Paul — Thu, 11 Feb 2010 15:57:55 +0000

Brandon,
I had the opportunity to attend a vSphere design workshop, and VMware’s stance for installation is now 1) ESXi embedded whenever possible 2) ESXi installable (choosing the hardware appropriate version for HP, Dell, or IBM) and a distant 3rd option is ESX “classic”.

That being said, there are a couple of factors that might prevent someone using ESXi such as hardware compatibility or an agent that is required to be installed on the ESX server such as a management or backup agent.

By: slowe

slowe — Wed, 10 Feb 2010 23:43:08 +0000

Brandon,

Without breaking any NDAs, I can tell you that it will be within your lifetime. Get prepared.

By: brandon

brandon — Wed, 10 Feb 2010 18:53:20 +0000

I’m very anxious to hear what was said about the service console end of life policy. We’re planning on moving to ESXi 4.0 with the upgrade to vSphere looming here soon. The biggest concerns aren’t coming from me or my partner in crime to support the environment, rather it comes from everyone else who has any say and some from management. Part of our justification for the move, aside from the security aspects alone, are that we need to learn to operate without the service console. We might as well start now. I don’t know if there is a time line or what it is that he said, but I’m extremely anxious to hear it, because if it confirms it is indeed going away in my lifetime, it will only add to the justifications for moving to ESXi.

By: uberVU - social comments

uberVU - social comments — Wed, 10 Feb 2010 06:20:07 +0000

Social comments and analytics for this post…

This post was mentioned on Twitter by PlanetV12n: Partner Exchange 2010 Session TECHBC0320 (blog.scottlowe.org) http://bit.ly/bfvKgY...