Skip navigation

Tag Archives: Install


First of all, let me express my personal feeling to people actually visit my site day by day. I have been away for one week to get MCITP:EA certificate and haven’t updated my blog for one week. But I’m just surprised by how many people actually keen to come back my blog.

Now, I’m off MS for a while and finally can dive into VMware world again and hopefully, I can get practical and deep as well. With no further duo, please allow me to bring up this new series topic, Using ESXi to replace ESX.

Why would you to use ESXi to replace ESX in the production?

I’m pretty sure that’s the first question you would ask. That’s also first question my manager asked as well. In the old time, ESXi is a free product and not even get supported by Vmware. And what’s wrong with ESX?

Well, if we double check what vmware said recently.

§First choice is ESXi Embedded, whenever possible.

ESXi is the future.

VMware has announced its intention to eventually replace ESX with ESXi.

§Design the management infrastructure to support VMware® ESXi, even if deploying VMware ESX™.

Limit the use of service console–based command-line management and monitoring agents

Develop ESXi management techniques now because ESX will eventually be phased out.

This message is from a vSphere Design workshop and blogged in vFrank.

As far as I understand, Vmware had enough headache to fixing RedHat version of Service Console. More than 50% percentage of Updates are delivered for SC.Thousands Support call are related to this poor Management console and Vmware believes ESXi can work better, lighter, and easier. According to my personal experiences, I’m very troubled by ESX console ping dropping. I have 2 or 3 software monitoring SC via ping, SNMP and there are always issues.

Concerns about ESXi

It’s free product, do I get support?

Yes, you do. I just have Vmware License team shoot an official Email to me to prove ESXi is supported as long as you have full production support. You will get exactly same support as esxi.

Does ESXi support vMotion, HA, FT, DRS, blah,blah?

Yes, they are. ESXi support all those functions with no issues.  I would like to provide you a link which is comparison of ESX and ESXi. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1015000

So what kind of features does ESXi support?

I can show you a picture with most functions of ESX and ESXi supported. If you want to get full list, please follow this link. http://www.vmware.com/products/esxi/facts.html This page shows there are no functions ESX supports while ESXi doesn’t.

To be continued…….

Reference:

http://www.vfrank.org/2010/04/13/esx-will-be-phased-out-esxi-is-the-future/

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1015000

http://www.vmware.com/products/esxi/facts.html


Advertisements

I’m pretty new for Vmware View 4 system. Today, I have decided to install an evaluation View 4 into my test lab and see how it goes. But I have encountered few interesting mistakes on the way. I would like to share them with everyone so you don’t need to make same mistakes.

1. Windows 7 Support or not Support?

Well, basically, I want to install W7 into View so I can use it in our production system in the future. I have installed the first View template (Windows 7 64bit) and tried to install View Agent on it. But it failed. System told me View 4 doesn’t support 64bit windows 7 as template (but View Client runs fine on W764bit). So I wiped it out and installed the 32bit Windows 7. After I setup everything, I tried to connect View from my client (Windows 7 64bit Enterprise). Authentication to View Connection is fine. but My View Client gives me black (blank) screen.

Well, the reason for that is simple. View 4 is only supported Windows 7 32bit in TechView stage. Meaning you don’t get support for using W7. There are two solutions so far.

Solution A:  Using RDP protocol instead of PCOIP. Well, PCOIP is pretty new protocol which supports multimedia and 3D effect for your connection. But it doesn’t work well with W7.

so you need to choose correct protocol when you try to connect to your W7 pool.

Solution B: Change Windows 7 display drive and Video memory size. Basically, you can change default W7 driver (Vmware SVGA 3D) to VMWARE SVGA II. And also change the video memory to 40MB.

Please follow this link to see the detail.

http://thejeremykeen.com/2010/03/16/blank-screen-on-windows-7-vmware-view-desktop-using-pcoip/

2. View Desktop Source is not ready

Well, this is pretty common errors you will see when you try to connect to View from client. See as following picture.

The actual root cause could be vary. I can give you few common mistakes.

Mistake 1: Forgot to install View Agent

When I tried to build another pool (windows xp sp3), I forgot to install View Agent on the template windows. View Agent is critical for View and it helps Connection to understand whether this snapshot of template is occupied or not. It also helps redirect Printing and USB as well. If you made this mistakes, you need to reopen your template and installed agent. Then, refresh all snapshots after that.

Mistake 2: Tasks are not finished

Essentially, View Connection server will run lots of script directly to vCenter. If vCenter hasn’t finished the tasks (you can see from recent task bar), it won’t be ready.

Mistake 3: DHCP and DNS

View doesn’t do magic. It still relies on Windows DHCP and DNS to work. Basically, a new snapshot of your template need to be assigned an DHCP IP (when I tested in my lab, there is no DHCP, I have to manually assigned IP to snapshots) and DHCP needed to be registered in the DNS. If you are not able to ping your template from client computer, you won’t able to access your snapshot. So if you are hurry, you can run ipconfig /registerdns on snapshot and ipconfig /flushdns on client to manually refresh DNS record.

Those just some basic mistakes we may encounter. Please leave your comments if you run into more errors.

Thanks