Lab Manager v3 license question

Similar Questions

• The NAC Manager/Server license question

  I use a pair of NAC Manager failover with 5 games of CAS servers. Each set of CAS servers is authorized to perform the different amounts of users. (i.e. 1500 or 3500) I loaded all the licences in the Manager. (All Coses PAK have been validly submitted by using the MAC address of the Senior Manager.) Is it possible to assign... or... How will I know which set of servers will be assigned the appropriate license for a specific set of users max?

  It was only from pak or was it separate paks... because he's going like that with a pak u generate license for cam (this is the license for the number of servers it can handle)... for that you must provide the mac cam address. then for each server FO u can use even PAK or a new and mentions the mac address of the server here and makes the exact differenc... If you had separate Pak. each PAK is given based on the license you requested from...

• Lab Manager licensing during the merger of vSphere environments

  Is there a small vSphere environment that is available for Lab Manager and a great environment vSphere and both are now completely separated (different vcenter servers, groups separated from ESX, etc.), and they are merged into one, what happens to the Lab Manager licenses?  Should be updated to take account of the increase in the number of ESX host in the new environment?  Environments can be merged without buying additional licenses?  If so, would be half the environment allowed for lab manager and others are not allowed?  How would the lab manager-under license, and lab-manager-without sections allowed environmental stands / separated?

  Thanks for your comments

  "Prepared" you went in in the section resources, hosts tab and see that the host is ready (green check mark), this means that there has been a 'prepare' to the host.  Prepare installs the agent LM, then she will deduct your license (settings > license).

  Kind regards

  Jon Hemming, b.SC., RHCT, VMware vExpert 2009
  http://Twitter.com/vJonHemming

  If your question or problem has been resolved, please click the "right answer".  If someone helped him, please click "useful answer.

• Lab Manager 4 will not release the license after the removal of host.

  Hey there,

  I am running Lab Manager 4 in my infrastructure.  I recently added a lot of CPU 2 and licensed.  Shortly after, I removed the host of Lab Manager, but he has not published the 2CPUs of licensing - which means that I am able to use my license 2CPU part to add new hosts.

  No idea how I can get the license for free?

  Thank you!

  You must "unprepare" this ESX host in the laboratory Manager.

  The 'prepare' function consumes your license, and similarly "unprepare" frees.

  This ESX host appears in the overall organization > resources > Hosts?

  Best regards

  Jon Hemming

• Question about Lab Manager and ESX Resource Pools

  Hello world

  I was wondering if I can get feedback from some of the members of the community.  We used Lab Manager very strongly in our support organizations and it has proved to be a valuable tool.  Recently, we collaborated with the Department of technical training and started hosting online seminars and classes for them using Lab Manager.  Last week we had a fairly large class of users (approx. 45), each duty deploy 2 rather Beefy VMs that were very intensive resources (Jboss, SQL, Mail to name a few).  My colleague and I went through a lot of trials and planning to ensure that our infrastructure can handle the load while allowing our users to date at the same speed and reliability, so that they are used.

  Our Lab Manager ESX server pools made up of the following:

  5 HP DL380 G5 servers with 2 x Quad Core 2.8 GHZ processors (8 cores each) with 32 GB of RAM each

  2 HP DL580 G5 servers with 4 x Quad Core 2.8 GHZ processors (16 cores each) with 128 GB of RAM each

  When the class is running and everyone has made their 2 machines, we noticed for some reason, he was all on ESX2 and 3 deployment (380 s).  Then came the ESX alarms, use of 90% of memory, then more than 100% bringing the disk page.  The CPU usage was at a all time high.

  I look at the 2 580 s and there are about 4 virtual machines deployed on them.

  So my question is...

  How does he know where to launch a Virtual Lab Manager machine?  There's no sense 2 servers have been brought to the red zone, and almost overloaded when the 2 most powerful servers in my farm are nearly dormant.  I noticed sometimes in the past, but not this bad.  Normally, we have about 45-50 computers deployed at some point and it seems to spread them out properly.

  This group of training has access to the same LUN and ESX server with Betclick as any other organization that we have.

  We have decided hosting several sessions of training may be greater than this one and would like to know that the virtual machines will be distributed properly.

  I would like to know your opinion on this

  First to answer your question, then make guess what happens.

  As indicated in response Ilya, LM distributed VMs differently with active DRS resource pools and pools of resources without active DRS.

  LM place VMs when the DRS is not used.

  When DRS is used, we use the DRS admission control to select the host to place virtual machines.

  DRS is turned off, LM uses its own placement routine:

  For each virtual machine, LM filter all managed servers that cannot run the virtual machine. A complete list of patterns are:

  • The managed server has not enough memory or quota for virtual machine to run the virtual machine.

  • The host is not connected to the data store that is the virtual machine.

  • The virtual machine has active state (suspended) and the CPU of the server managed by the waking state has been captured is not compatible with the managed server currently considered.

  • The virtual machine has been a guest on 64-bit and the managed server is not 64-bit capable.

  • The virtual machine has more processors than the managed server.

  • The managed server is not accessible or is set to "prohibit deployments." Not reachable may mean that the lm-agent or its not to ping queries is not answer (this is visible in the list of managed server page).

  Once we have the complete list of eligible servers, we place the virtual machines on the host including the smallest (MemoryReservation % + CPUReservation %). By default, we reserve not CPU on LM VMs, this internship will be largely due to the memory on the host computers if you have not changed the settings of reservation of CPU on your virtual machines.

  For closed deploy to the PF3, force us all virtual machines to go on the same host, so if any virtual machines have any special data store / CPU type specification, all virtual machines is forced to go on this host. If there are conflicting requirements between different virtual machines in the same configuration, deployment will fail. Closed VMs also have another condition to check that is rarely achieved in practice: number of closed networks available on the managed server. By default, this is 20 and you will need more than 20 different configurations closed running on a managed server before you who will strike.  (LM4 allows Cross fencing host, so this does not apply in LM4).

  To make a guess blind because of your distribution problem - if you use the saved state and fencing, it's probably the type of processor.  Processor type can be checked on the host properties page.

  If you not are not I would check that the images can deploy on the 580 s by disabling the 380s and trying to deploy them.

  If you use DRS (which you're not), it could be due to deployment of virtual machines too fast for the algorithm of control for the entrance of VC.  An easy solution for this is to extinguish the DRS on the cluster manager of laboratory.

  We tested load internal repeatedly, the product QA in different laboratories, we run (LM has been used in VMworld Labs for the past couple years and internal systems of training and demonstration for our Organization implemented SE), so no need to worry about this.  I assure you that the first 'real' performance problem you will encounter will be almost certainly due to an overload of your storage array (too many IOPS / s)... and for that you have to distribute content in data warehouses and use techniques of creating paths to balance the load.

  Kind regards

  Steven

  Another thread on this: http://communities.vmware.com/message/1258902.

• Lab Manager acceleration kits / required licenses?

  Hello!

  We are currently using ESXi and plan to move to centralized test Lab Manager lab. The estimates are based on the acceleration kit that used to be available at about 4-5 k €, which seemed to include VI 3 licenses that are required for the Lab Manager to run on top of ESXi (or if whatever the basis ESXi does not support).

  Now I can't find the acceleration kits more 'Buy Lab Manager', instead I find licenses for Lab Manager only.

  Now I read everywhere that the vCenter is necessary and even messages that describe that vCenter foundation is not sufficient to run the laboratory Manager. However no official 'that's what you need to do if you want to get Lab Manager' running.

  To be honest, if the acceleration kits were gone for good, licensing begins to be as clear as some States large company in their regulatory policy, "must be this version of the database server", but do not worry to mention what license you need for the said server or background Windows server...

  I would like to know the price of 'minimum' (to continue) Lab Manager on top of bare metal, start-up costs and maintenance renewals when the initial support runs.

  With regard to reading, 2 or 4 processors as it seems to count.

  BR,

  Kalle

  Sorry, that seems so difficult.  To sort through all of this:

  • Lab Manager requires ESX Standard or Enterprise.  It does not currently run on ESXi, but it's on the Roadmap (cannot discuss dates here).

  • Lab Manager 3 requires vCenter (Lab Manager 2 does not work).

  • vCenter Foundation is untested, but should work (but can only manage up to 3 knots).

  • ESX Foundation is not supported by the Lab Manager.

  • The laboratory director is authorized by the node (the server Lab Manager is free).

  • Lab Manager Server runs on Windows Server 2003 and can run on a virtual machine

  • VirtualCenter runs on Windows 2000, Windows XP Professional, or Windows Server 2003 and can also run on a virtual machine.

  Thus, the minimum subscription is:

  • ESX Standard for two processors

  • Lab Manager for two processors

  • vCenter Foundation

  • Windows licenses you need for the Lab Manager server and VirtualCenter Management Server.

  Installing vCenter Management Server and server Lab Manager on the two virtual machines on this host ESX and use their local drive to store the virtual computer images.

  Such a system doesn't scale well, of course.  When you size, you will need to add the following:

  • Shared storage (NFS, iSCSI, or FC)

  • More ESX and Lab Manager licenses

  • vCenter Standard or Premium, instead of Foundation.

  Hope this helps,

  Steven

• Question of curiosity - why doesn't support Lab Manager 4 Nexus

  I suspect it has to do with the 'helper' VMs deployed to help manage the host spanning networks, but I didn't know why it wouldn't work with the Nexus.  Thanks in advance.

  I think that it is because with the Nexus, virtual network configuration is managed side Nexus instead of by the bias of the vSphere API.  Lab Manager actually requires a more direct control of the network in the vSphere API configuration and interface of the ESX host.

  ~ P

  Don't forget if the answers help you, award points

• Issues of Configuration Lab Manager

  Hey,.

  So I tried to read documents about lab manager that we try to implement. Our lab environment has been previously implemented, and we had not considered using Lab Manager so far.

  Our installation is as follows: 3 data centers with two VM hosts in each and of course several VMS under.

  Our license is currently only 4 cpu, if he had to get a permit of expansion that I would be able to have the Director of the laboratory, managing multiple data centers? The current installation is on a virtual machine inside a data center and currently manages another data center.

  My second question is: our vsphere hosts is a physical machine, would it be better to install the Manager of laboratory on it instead of a virtual machine inside a data center?

  And then there at - it a good way to put the virtual machines already created and executed in Lab Manager without having to reproduce or copy on our data store?

  Thank you!

  First, Lab Manager supports only a single data center object from inside of vCenter.  It would be possible to do the following:

  1. use multiple clusters in a single datacenter (easier)

  2. do you have multiple facilities of Lab Manager who manage different data centers. (overhead much more)... different installs... splitting the licenses.

  I highly suggest option 1, if possible.

  My second question is: our vsphere hosts is a physical machine, would it be better to install the Manager of laboratory on it instead of a virtual machine inside a data center?

  It would be much better to provide a simple Windows 2003 Server virtual machine to be the Lab Manager server.  You cannot install Lab Manager on the same system as vCenter or a domain controller.

  And then there at - it a good way to put the virtual machines already created and executed in Lab Manager without having to reproduce or copy on our data store?

  You can "resume" a model, but not a VM.  If you import a virtual machine, Lab Manager will make a copy to have an independent set of files to manage.

  Kind regards

  Jonathan

  B.SC., RHCT, VMware vExpert 2009
  http://Twitter.com/vJonHemming

  If your question or problem has been resolved, please click the "right answer".  If someone helped him, please click "useful answer.

• Requirements of VMWare Lab Manager

  Hello!

  I'm trying to put together a proof of concept for my business help to reach an agreement to buy and implement of Lab Manager, but am having a hard time getting real answers on a licence!  Maybe I'm reading just the documents wrong or something, but here are my questions:

  (1) VMWare Lab Manager does support ESXi?  If so, why do I use instead of ESXi ESX when all management is made by the end before (Lab Manager or vCenter Server)?  ... I have no need of HA or VMotion.

  (2) do I need for 3 products license?  For example, Lab Manager, vCenter Server, and ESX server?

  I read in a PDF document that vCenter Server is not a must but could take no ESXi, but a person in chat support told me that Lab Manager backed ESXi but necessary vCenter Server.  I'm a bit confused.

  What is the deployment scenario recommended for an environment with 1 physical host (to start) but plans to expand to 3-5 in the year?

  Thanks for your help!  Sorry to ask what I am sure is answered somewhere on the website, I just couldn't find where and it seems that the name of the product seems to be different depending on what you're looking at (ESX Server Infrastructure =?)

  -Jesse Reinhart

  Hi Jesse

  (1) lab Manager does not support ESXi.

  (2) Yes Lab Manager 3.0.2 requires the current version VC, it does not work on stand-alone host. Director of the laboratory 2.5.x support stand-alone host.

  You need a configuration that Lab Manager-->--> ESX VC even for single host currently.

  Hope that helps

  John Shao

• Can I use Lab Manager with VirtualCenter Server Foundation

  Hi, now I'm choosing the license type for my gateway.

  Regarding now I can't manage through Virtual Center more than 3 knots.

  But I have a question. Can I use VirtualCenter Server Foundation License with VMware Lab Manager 3.0?

  You can use vCenter Server Foundation with PF3. We currently have 3 standard ESX licenses and a vCenter Server Foundation and it works very well. The only limitation is that you cannot manage more than 3 guests, but in your case it does not appear that it will be a problem.

• vCenter Lab Manager 4.0.4 5?

  I know that there is no support for Lab Manager 4.0.4 and vCenter 5, but it's going to work? Or when it will be supported? I see no reason why there would be a problem if I leave my host ESX 4.1 cluster.

  Has anyone tried this before?

  vCenter 5 + Lab Manager 4.0.4 won't work.  There, questions that I saw people who did the upgrade without checking compatibility.  Since Lab Manager is abandoned, I'm not expecting a major update to support vCenter 5.0.

  One option is to divide it into 2 environments... 1 specially for vCenter to LabManager and then a 2nd which will vCenter 5 which is a new installation you can grow out.

  Best regards

  Jon Hemming

• Shutdown for Lab Manager

  We are conducting a data center power down and I would like to confirm my judgment for Lab Manager procedure:

  Stop order:

  1. Shutdown VMs LM
  2. Virtual routers (for closed configurations) stop by VC
  3. Stop VMwareLM-ServiceVM (by distributed switch) by VC
  4. Stop LM Server (VM, but not running on the ESX host cluster managed LM)
  5. Shutdown LM managed ESX host
  6. Shutdown VC Server

  Boot order:

  1. Power on server VC
  2. Power on managed LM of the ESX host
  3. Power on LM Server
  4. Power on virtual LM VMs, routers & VMwareLM-ServiceVM by VC

  My questions:

  Are the steps in the proper order?

  What I have to cancel the deployment of my configurations or they may just be in an engine out of State? I like to keep the configurations deployed to maintain external if possible IP addresses.

  just closed down going also to extend the process of closing, it would be: ESX hosts SAN switch SAN storage reverse order to start upward.

• Relationship of Lab Manager and vSphere

  My shop starts to think about his Lab Manager architecture design, and we have some questions about the relationship between vSphere and Lab Manager.

  (1) can Lab Manager leverage of resources defined outside its host vSphere environment?

  (2) must LM be hosted in a specific vSphere environment to effectively exploit the scene-to-production in this environment vSphere features?  In other words, what is the impact to the staging functionality when you move a virtual machine from a workspace of LM to a VSphere environment that does not host the environment of LM?

  The reason we ask is because we already have production environment vSphere, and we plan to install vCenter Lab Manager within this environment or install LM in a separate vSphere environment.

  Thank you.

  Tim

  (1) the laboratory director can leverage resources defined outside its host vSphere environment?

  All used 'resources' must be inside a vCenter server, and all objects must be contained within a single "Data center" object in the hierarchy.

  > LM (2) done must be hosted in a specific vSphere environment to effectively exploit the scene-to-production in this environment vSphere features? In other words, what is the impact to the staging functionality when you move a virtual machine from a workspace of LM to a VSphere environment that does not host the environment of LM?

  If the vCenter for production is not the same as Lab Manager, you must export the Configuration of LM in an SMB share (requires a classic ESX host in the middle of LM), and then import it to the appropriate location.

  I did not notice problems with Lab Manager VMs-by-side with use of regular production.  Just separate the ESX hosts in a dedicated Cluster or a Pool of resources.

  Kind regards

  Jon Hemming, b.SC., RHCT, VMware vExpert 2009
  http://Twitter.com/vJonHemming

  If your question or problem has been resolved, please click the "right answer".  If someone helped him, please click "useful answer.

• I can point my Lab Manager 4.0.2 to point to another new vCenter Server?

  Hi guys,.

  I have a client with a LM4.0.2 production and we are considering moving to one another new/a vCenter server.

  It is important to note that the new vCenter will NOT have the same DB or FULL of the old domain name. It's a completely different vCenter with other ESX hosts.

  Now the questions:

  Can I redirect my Lab Manager (VM) at the new vcenter without any problem?

  What of the ESX (resource) on the old vcenter?

  Is it possible to do this without downtime for laboratories? If this is not the case, how can I minimize downtime? cancel the deployment will be enough?

  Does anyone have this done successfully?

  Any comments would be much appreciated.

  Eyal

  etamir,

  There are some excellent discussions within this forum on the same topic.  I strongly suggest to read first, and I'll see if I can find an example.

  Before going further, data warehouses used in the new vCenter/ESX environment will be exactly the same as the current one?  If you want to keep all of your configurations, I need to know that the UUID of the LUN does not change during this process.

  Can I redirect my Lab Manager (VM) at the new vcenter without any problem?

  You can change the IP/domain FULL name vCenter in the settings section of the Lab Manager site... now on the problems that could result.

  You will need to remove anything from the GUI of Lab Manager that has to do with the current vCenter (unedploy, unprepare host esx, resource pools, configurations etc.).  There will be more on this in the dedicated thread

  What of the ESX (resource) on the old vcenter?

  ESX doesn't really matter, it's the data UUID store that matters.  ESX is just virtual machines.  Note: you'll want to throw all States/suspend points on the VMS where processors are different on the ESX hosts.

  > Is it possible to do this without downtime for laboratories?

  No, there will be a form any downtime.  Either that LM site will be useless (no resources with Betclic, consoles will does not work until the guests are prepared, etc.).

  > If not, how can I reduce downtime? cancel the deployment will be enough?

  Yes, to cancel the deployment of will help... but there will be some lag as you reconfigure Manager of laboratory to use the new vCenter.

  > Has anyone successfully done this?

  Yes.  I saw others to do this.

  Subjects in the sample: http://communities.vmware.com/message/1592762

  Kind regards

  Jon Hemming, b.SC., RHCT, VMware vExpert 2009
  http://Twitter.com/vJonHemming

  If your question or problem has been resolved, please click the "right answer".  If someone helped him, please click "useful answer.

• Lab Manager dependencies on vCenter and terminology

  I just Lab Manager, of course with ESX and vCenter.  I know very little about Virtualization, as this issue will prove.  What are the activities of configuration required on vCenter for Lab Manager able to build models, installation configurations and share library configurations?

  Also, I'm trying to get my head around the difference between the data store, data center and media store.  My current knowledge are:

  A data store has a one-way relationship to one or more hosts.  If storage is on a specific host (physical hard disk for example) then the data store has a relationship one of exlclusively with a single host.  Any file a host or a virtual machine can read/write can be read/written on this data store.

  A data center is a logical collection (non-brique and mortar) hosts, data warehouses and virtual machines.  A data center can aggregate various data stores in a single logical storage available to all virtual machines area?  Or another flavor of physical storage can same issue on a Server Windows 2008 physical logically be conifgured such as NFS, and can share NFS join a data center?

  A media store is a special part of a data store managed by the Manager of laboratory exclusively for the storage of files ISO for the construction of models in the laboratory Manager.  Is a media store part of a data store or part of a data center?

  Is a model of vCenter the same model Lab Manager?

  Any clarification on these questions would be more useful.

  Kind regards

  Rick

  Good questions! Welcome to the Forums as well!

  Your description data store is pretty right on. With the exception of the now for the storage of the local host, new technologies progressed to virtualize in the shared storage by the use of devices to Vritual Server.  Companies like HP lefthand and Openfiler to name a few.

  With regard to the issues of data center

  > A datacenter can aggregate various data warehouses into a single logical storage available to all virtual machines area?

  No, he learn better to keep data warehouses between HA/DRS separate clusters.  Now between the host in a cluster you "will share stroage" for the use of the DRS, HA or Storage vMotion.

  > can physical storage on a Server Windows 2008 physical logically be conifgured such as NFS, and can share NFS join a data center?

  Yes you can - use Openfiler VSA to connect the two iSCSI LUNS and NFS for ESX. As long as the ESX host can access the virtual machine through the network.

  For your other questions have a good read on a couple of things well:

  http://bsmith9999.blogspot.com/2010/02/Lab-Manager-40-Setup-and-best-practices.html

  This webcast was just as informative as well:

  http://www.VMware.com/a/webcasts/details/284

  See you soon,.

  Chad King

  VCP-410. Server +.

  Twitter: http://twitter.com/cwjking

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful