Posts Tagged ‘Lab Manager’

Lab Manager Customization

August 1st, 2009

Although VMware does not support much along the lines of Lab Manager web interface customization, feature requests from VMware Partners and end users are likely to see the light of day in future versions as discussed in this thread by VMware employee Steve Kishi.

Through the examples of Hany Michael over at, there are a few changes that can be made that I think are pretty safe. I noticed in Hany’s Lab Manager 4 video (located at the link above), he had modified Lab Manager branding in a few places by dropping in his own artwork. Rather than modifying the web interface code, he merely located the image files and replaced them with his own.

At the login screen,

VMware’s generic Lab Manager branding:

8-1-2009 9-42-25 AM

Becomes Hany’s own creation by replacing the .gif file at C:\Program Files\VMware\VMware vCenter Lab Manager\WebSrvr\Resources\Default\Images\Login\Login.gif:

8-1-2009 9-40-05 AM

Once inside,

The logo in upper left corner:

8-1-2009 9-42-57 AM

Is replaced by Hany’s brand by modifying the .gif file at C:\Program Files\VMware\VMware vCenter Lab Manager\WebSrvr\Resources\LM\Images\LeftNav\logo.gif

8-1-2009 9-40-58 AM

In Lab Manager 3, we can add a MOTD or splash screen message for end users or developers by modifying the image at C:\Program Files\VMware\VMware Lab Manager\WebSrvr\Resources\LM\Images\Common\login_back.gif:

8-1-2009 10-20-26 AM

Look for MOTD and branding features, as well as others mentioned in the thread above, to be implemented in future versions of Lab Manager.

Lab Manager “Valid NIC Requirement” prerequisite check fails

May 17th, 2009

If you’re installing Lab Manager 3.x and the Valid NIC Requirement prerequisite check fails, verify your Lab Manager server has a static IP address configuration and not a configuration that is assigned by DHCP.

For other Lab Manager requirements, be sure to check out the Installation and Upgrade Guide.

5-17-2009 12-32-11 PM

Lab Manager Network Port Requirements

May 13th, 2009

I need to become a VMware Lab Manager expert and so it begins.  From what I’ve seen so far, Lab Manager 3.x has made great progress since I last kicked the tires 15 months ago on Lab Manager 2.x.  The biggest news by far is that ESX hosts can be managed both by Lab Manager Server and vCenter Server with all the fixins (DRS, HA, VMotion).  Although I’ve already found that VMs connected to an internal only vSwitch remain pinned to the host due to VMotion rules.

Nothing too Earth shattering here; this information comes straight from page 20 of the Lab Manager Installation and Upgrade Guide.

Systems TCP Port UDP Port
Client browser to access Lab Manager Server system 443
Client browser to access ESX hosts 902, 903
Lab Manager Server system and ESX hosts to access SMB share

(import and export operations only)

139, 445 137, 138
ESX hosts to access NFS media datastores or NFS virtual machine datastores 2049
Lab Manager Server system to access Lab Manager agent on ESX hosts 5212
Lab Manager Server system to access ESX host agent on ESX hosts 443
Lab Manager Server system to access the VirtualCenter Server system 443
Lab Manager Server system to communicate with virtual router on some ESX hosts

(for fenced configurations)

Lab Manager Server system to access LDAP Server 389 LDAP


Before the installation of Lab Manager, be sure that ports above won’t conflict with an existing configuration by running the netstat -b command from the Windows command line.

VMware product name changes

December 3rd, 2008

Quick update on a news item you may have already heard about. Remember those VMware product/component decoder rings you might have started working on after the VMworld 2008 announcements? It’s time for an update. VMware announced a handful of product name changes on Monday:

  1. VMware VirtualCenter is now VMware vCenter Server
  2. VMware vCenter is the family name for all management products
  3. VMware Lab Manager is now VMware vCenter Lab Manager (since it is in the management products family)
  4. The VMware vCenter prefix applies to the other products in the management products family as well
  5. VMware View is the family name for all VDI/VDM products
  6. VMware VDI is now VMware View
  7. VMware VDM is now VMware View Manager

I’m not real fond of name changes unless there is a good reason behind it. I’ll give VMware the benefit of the doubt that there was good reason to make these changes, although not knowing myself 100% what is up VMware’s sleeve, the timing is somewhat debatable. Couldn’t they have waited until the next generation of Virtual Infrastructure to align the products and components? Citrix did this with Presentation Server when they instantly re-branded it to XenApp. It confused a lot of people, especially the newcomers. I hope confusion among VMware customers is minimized. It’s going to take a little while for these new names to become second nature for me.

What do you think of the name changes? Feedback is always welcomed here.