Boomerang

Version: 1.1.1 | File Size: 7 MB | Upload Date: 07/5/2011

This fling is covered under the Technical Preview License.

VMWARE, INC.

Notice to User:

Notice to User: This Technology Preview License Agreement is a CONTRACT between you (either an individual or a single entity) and VMware, Inc. (VMware), which covers your use of the VMware unreleased software that accompanies this Software Technology Preview License Agreement and related software components, which may include associated media, printed materials, and "online" or electronic documentation. All such software and materials are referred to herein as the "Technology Preview Software." If you do not agree to the terms of this Technology Preview License Agreement, then do not install or use the Technology Preview Software. By explicitly accepting this Technology Preview License Agreement, however, or by installing, copying, downloading, accessing, or otherwise using the Technology Preview Software, you are acknowledging and agreeing to be bound by the following terms.

1 DEFINITIONS

(a) “Technology Preview Software” shall mean the concept version of VMware’s software, in object form only, excluding any Open Source Software provided with the such software, and the media and Documentation provided by VMware to Licensee and for which Licensee is granted a use license pursuant to this Agreement. (b) “Documentation” shall mean the printed or online written reference material furnished to Licensee in conjunction with the Technology Preview Software, including, without limitation, instructions, testing guidelines, and end user guides. (c) “Intellectual Property Rights” shall mean all intellectual property rights, including, without limitation, patent, copyright, trademark, and trade secret. (d) “Open Source Software” means various open source software components provided with the Technology Preview Software that are licensed to you under the terms of the applicable license agreements included with such open source software components or other materials for the Technology Preview Software. (e) “Updates” shall mean a modification, error correction, bug fix, new release, or other update to or for the Technology Preview Software.

2. LICENSE GRANT, USE AND OWNERSHIP

(a) Limited License. Subject to the terms and conditions of this Agreement, VMware grants to Licensee a non-exclusive, non-transferable license (without the right to sublicense)

to use the Technology Preview Software in accordance with the Documentation solely for purposes of internal testing and evaluation,
to use the Documentation provided with the Technology Preview Software in support of Licensee’s authorized use of the Technology Preview Software, and
to copy Technology Preview Software for archival or backup purposes, provided that all titles and trademarks, copyright, and restricted rights notices are reproduced on such copies.

(b) Evaluation Feedback. The purpose of this limited license is the testing and evaluation of the Technology Preview Software and Documentation. In furtherance of this purpose, Licensee shall provide feedback, suggestions or ideas to VMware concerning the functionality and performance of the Technology Preview Software from time to time as reasonably requested by VMware, including, without limitation, identifying potential errors and improvements. Such feedback will be in a manner convenient to Licensee and will be subject to reasonable availability of Licensee’s personnel. Notwithstanding the foregoing, prior to Licensee disclosing to VMware any information in connection with this Agreement which Licensee considers proprietary or confidential, Licensee shall obtain VMware’s prior written approval to disclose such information to VMware, and without such prior written approval from VMware, Licensee shall not disclose any such information to VMware. Feedback, suggestions, ideas and other information which is provided by Licensee to VMware in connection with the Technology Preview Software or this Agreement will become the property of VMware and may be used by VMware to improve or enhance its products and, accordingly, VMware shall have a non-exclusive, perpetual, irrevocable, royalty-free, worldwide right and license to use, reproduce, disclose, sublicense, distribute, modify, and otherwise exploit such feedback, suggestions, ideas and information without restriction. No obligation is assumed or may be implied on the part of VMware by receipt or examination of the submission to use the feedback, suggestion or idea, compensate or otherwise enter into another agreement with Licensee. For avoidance of doubt, this section does not apply to any Open Source Software accompanying the Technology Preview Software.

(c) Restrictions. Licensee shall not copy or use the Technology Preview Software (including the Documentation) except as expressly permitted in this Agreement. Licensee will not, and will not permit any third party to, sublicense, rent, copy, modify, create derivative works of, translate, reverse engineer, decompile, disassemble, or otherwise reduce to human perceivable form any portion of the Technology Preview Software or accompanying Documentation. In no event shall Licensee use the Technology Preview Software for Licensee’s product development or any other commercial purpose. The Technology Preview Software and all performance data and test results, including without limitation, benchmark test results (collectively “Performance Data”), relating to the Technology Preview Software are the Confidential Information of VMware, and will be treated in accordance with the terms of Section 4 of this Agreement. Accordingly, Licensee shall not publish or disclose to any third party any Performance Data relating to the Technology Preview Software. (d) Ownership. VMware shall own and retain all right, title and interest in and to the Intellectual Property Rights in the Technology Preview Software and any derivative works thereof, subject only to the limited license expressly set forth in Section 2(a) hereof. Licensee does not acquire any other rights, express or implied, in the Technology Preview Software. ALL RIGHTS NOT EXPRESSLY GRANTED HEREUNDER ARE RESERVED TO VMWARE. (e) No Support Services. VMware is under no obligation to support the Technology Preview Software in any way or to provide any Updates to Licensee. In the event VMware, in its sole discretion, supplies any Update to Licensee via a designated website by VMware, such Update shall be deemed Technology Preview Software hereunder and shall be subject to the terms and conditions of this Agreement. (f) Third-Party Software. The Technology Preview Software enables a computer to run multiple instances of third-party guest operating systems and application programs. Licensee acknowledges that Licensee is responsible for obtaining any licenses necessary to operate any such third-party software, including guest operating systems. (g) Open Source Software. The terms and conditions of this Agreement shall not apply to any Open Source Software accompanying the Technology Preview Software. Any such Open Source Software is provided under the terms of the open source license agreement or copyright notice accompanying such Open Source Software or in the open source licenses file accompanying the Technology Preview Software.

3. TERM AND TERMINATION.

Licensee’s rights with respect to the Technology Preview Software will terminate upon the earlier of (a) automatic expiration of the Technology Preview Software based on the system date or (b) termination by VMware, in its sole discretion, of rights to Licensees with respect to the Technology Preview Software provided under this Agreement upon notice on the VMware website. Upon any expiration or termination of rights with respect to the Technology Preview Software under this Agreement, the rights and licenses granted to Licensee under this Agreement shall immediately terminate, and Licensee shall immediately cease using, and will return to VMware (or, at VMware’s request, destroy), the Technology Preview Software, Documentation, and all other tangible items in Licensee’s possession or control that are proprietary to or contain Confidential Information. The rights and obligations of the parties set forth in Sections 2(b) 2(c), 2(d), 2(e), 2(f), 3, 4, 5, 6 and 7 shall survive termination or expiration of this Agreement for any reason.

4. CONFIDENTIALITY.

"Confidential Information" shall mean all trade secrets, know-how, inventions, techniques, processes, algorithms, software programs, hardware, schematics, and software source documents relating to the Technology Preview Software, and other information provided by VMware, whether disclosed orally, in writing, or by examination or inspection, other than information which Licensee can demonstrate (i) was already known to Licensee, other than under an obligation of confidentiality, at the time of disclosure; (ii) was generally available in the public domain at the time of disclosure to Licensee; (iii) became generally available in the public domain after disclosure other than through any act or omission of Licensee; (iv) was subsequently lawfully disclosed to Licensee by a third party without any obligation of confidentiality; or (v) was independently developed by Licensee without use of or reference to any information or materials disclosed by VMware or its suppliers. Confidential Information shall include without limitation the Technology Preview Software, Documentation, Performance Data, and any Updates. Licensee shall not use any Confidential Information for any purpose other than as expressly authorized under this Agreement. In no event shall Licensee use the Technology Preview Software or any Confidential Information to develop, manufacture, market, sell, or distribute any product or service. Licensee shall limit dissemination of Confidential Information to its employees who have a need to know such Confidential Information for purposes expressly authorized under this Agreement. In no event shall Licensee disclose any Confidential Information to any third party. Without limiting the foregoing, Licensee shall use at least the same degree of care that it uses to prevent the disclosure of its own confidential information of like importance, but in no event less than reasonable care, to prevent the disclosure of Confidential Information.

5. LIMITATION OF LIABILITY

IT IS UNDERSTOOD THAT THE TECHNOLOGY PREVIEW SOFTWARE IS PROVIDED WITHOUT CHARGE FOR LIMITED EVALUATION PURPOSES. ACCORDINGLY, THE TOTAL LIABILITY OF VMWARE AND ITS SUPPLIERS ARISING OUT OF OR RELATED TO THIS AGREEMENT SHALL NOT EXCEED $100. IN NO EVENT SHALL VMWARE OR ITS SUPPLIERS HAVE LIABILITY FOR ANY INDIRECT, INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, OR LOSS OF BUSINESS INFORMATION), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, EVEN IF VMWARE AND ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THESE LIMITATIONS SHALL APPLY NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE OF ANY LIMITED REMEDY.

6. WARRANTY DISCLAIMER.

IT IS UNDERSTOOD THAT THE TECHNOLOGY PREVIEW SOFTWARE, DOCUMENTATION, AND ANY UPDATES MAY CONTAIN ERRORS AND ARE PROVIDED FOR LIMITED EVALUATION ONLY. THE TECHNOLOGY PREVIEW SOFTWARE, THE DOCUMENTATION, AND ANY UPDATES ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE. VMWARE AND ITS SUPPLIERS SPECIFICALLY DISCLAIM ALL IMPLIED WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE. Licensee acknowledges that VMware has not publicly announced the availability of the Technology Preview Software, that VMware has not promised or guaranteed to Licensee that such Technology Preview Software will be announced or made available to anyone in the future, that VMware has no express or implied obligation to Licensee to announce or introduce the Technology Preview Software, and that VMware may not introduce a product similar or compatible with the Technology Preview Software. Accordingly, Licensee acknowledges that any research or development that it performs regarding the Technology Preview Software or any product associated with the Technology Preview Software is done entirely at Licensee’s own risk. Specifically, the Technology Preview Software may contain features, functionality or modules that will not be included in the production version of the Technology Preview Software, if released, or that will be marketed separately for additional fees.

7. OTHER PROVISIONS

(a) Governing Law. This Agreement, and all disputes arising out of or related thereto, shall be governed by and construed under the laws of the State of California without reference to conflict of laws principles. All such disputes shall be subject to the exclusive jurisdiction of the state and federal courts located in Santa Clara County, California, and the parties agree and submit to the personal and exclusive jurisdiction and venue of these courts. (b) Assignment. Licensee shall not assign this Agreement or any rights or obligations hereunder, directly or indirectly, by operation of law, merger, acquisition of stock or assets, or otherwise, without the prior written consent of VMware. Subject to the foregoing, this Agreement shall inure to the benefit of and be binding upon the parties and their respective successors and permitted assigns. (c) Export Regulations. Licensee understands that VMware is subject to regulation by the U.S. government and its agencies, which prohibit export or diversion of certain technical products and information to certain countries and individuals. Licensee warrants that it will comply in all respects with all export and re-export restrictions applicable to the technology and documentation provided hereunder. (d) Modification. This is the entire agreement between the parties relating to the subject matter hereof and all other terms are rejected. No waiver or modification of this Agreement shall be valid unless in writing signed by each party. The waiver of a breach of any term hereof shall in no way be construed as a waiver of any term or other breach hereof. If any provision of this Agreement is held by a court of competent jurisdiction to be contrary to law the remaining provisions of this Agreement shall remain in full force and effect.

8. CONTACT INFORMATION.

If you have any questions about this Software Technology Preview Test Agreement, or if you want to contact VMware for any reason, please direct all correspondence to:

VMware, Inc.,
3401 Hillview Avenue,
Palo Alto, CA 94304,
United States of America
or email info@vmware.com.

VMware is a trademark of VMware, Inc.

57,799 views

(34 votes)

Tags: ESX, VC servers, VMRC, vmware, VMware Remote Console, vSphere

Summary
System Requirements
Instructions
Video
Change Log

VMware Boomerang is a radically simple client application that allows you to use multiple vSphere servers simultaneously. Simply select "Add a Server..." to connect and login to an ESX or VirtualCenter server and you will be presented with a list of all available virtual machines. You are able to perform power operations on the virtual machine or connect to it using the VMware Remote Console (VMRC), which is provided with vSphere Client. You can also easily add virtual machines as favorites so you can quickly view the subset of virtual machines that you are interested in.

Features

Supports connecting to multiple ESX and VC servers simultaneously.
Allows you to save your credentials for easy login to servers.
Favorites pane enables easy browsing through multiple virtual machines on different servers.
Simple user interface gives you quick access to connecting to a virtual machine or issuing power operations.
Keyboard navigation allows you to type the name of the virtual machine you want to use or to use directional keys to navigate.
Servers with large numbers of virtual machines are automatically collapsed into hyperlinks, which you can click to view subsets of the inventory or the entire thing.
Configurable automatic update checking.
See virtual machines you have recently connected to in the Recently Used section.
Search for virtual machines quickly across all your servers.

Users needing access to more than basic virtual machine power operations should use VMware vCenter Server to manage vSphere hosts and virtual machines. vCenter supports activities like vMotion, High Availability, storage configuration, host provisioning cloning, templates, monitoring, alerts and more.

VMware Boomerang does not support connecting directly to free ESXi servers.

Requires Windows XP or later.

Download and run the installer. The application will automatically launch when installation is completed and add an icon to the system tray.

Updates in Version 1.1.1

Fixes a crash when a Favorite no longer exists on the server.
Fixes a rare crash when adding a vSphere server.

Updates in Version 1.1.0

Added a search box that allows you to enter a VM name.
Added a "Recently Used" section for VMs that you have recently connected to or performed power operations on. The number of days that the list encompasses is configurable in the preferences dialog.
Added a confirmation dialog when performing power operations.
Added logic to automatically append DNX suffixes when entering an unqualified server name.
Added support for high-DPI configurations.
Fixed a few rare crashes.
Added a better error message when attempting to add a free ESXi server (license check failure).

Comments

HP ESXI free server!
Tomaz Kavcic says:

Hello,

I was recently testing your Boomerang application for managing ESXI hosts. I am finding it pretty impressive as I can manage with it lots of different ESXI hosts at once, but there's a small... Show more

Hello,

I was recently testing your Boomerang application for managing ESXI hosts. I am finding it pretty impressive as I can manage with it lots of different ESXI hosts at once, but there's a small issue. I have plenty of Proliant DLxxx servers installed and some of them are running original ESXI 5.0 U1 (downloaded from vmware.com), but some of them also use HP customized ESXI 5.0 U1 (downloaded from HP.com repositories). Both ESXI instances are licensed (the one from HP has preinstalled key), but with boomerang I can only manage those hosts which run on original ESXI. Whenever I try to add a hosts which runs on HP customized ESXI 5.0 U1 I get the following error: "Login failed. Boomerang does not support unlicensed ESXI servers."
I find this error strange, as those hosts are also fully licensed. I would need support for those HP customized ESXI servers, as they have some special drivers/sensors/services added from HP for managing those servers which aren't available in original ESXI installations.
Would it be possible somehow to fix this error for this great application?

Thank you in advance, Tomaz Kavcic. Show less

May 14, 2012 at 1:59 am | Reply
- Adam Gross says:
  
  I'm not very familiar with ESXi licensing, but are you sure that you aren't mistaking your HP server being licensed with HP and your HP server being licensed with VMware?
  
  May 14, 2012 at 2:35 pm | Reply
  - Tomaz Kavcic says:
    
    Thanks for your answer. My text above was probably a bit disturbing, so I will try to make it short and clear this time. Here are two situations (on the same server):
    1. Latest ESXI 5.0 U1 downloaded... Show more
    
    Thanks for your answer. My text above was probably a bit disturbing, so I will try to make it short and clear this time. Here are two situations (on the same server):
    1. Latest ESXI 5.0 U1 downloaded from vmware.com, fresh install, added that new ESXI to Boomerang, works like a charm.
    2. Same latest ESXI 5.0 U1 downloaded from HP.com (this is a bit modified ESXI for HP servers - contains some additional drivers, sensors, etc.), fresh install on same server, same partition, added to Boomerang, got response "Login failed. Boomerang does not support unlicensed ESXI servers."
    I don't really know what you meant in your comment above about HP server being licensed with VMware, but there's really nothing I could do differently. The only thing that's different between those two installations is that the image downloaded from vmwware.com doesn't have any key installed (trial version), so I have to install my key which I was assigned when I registered my account at vmware.com. But the image which you can download from HP.com for HP servers already has "preinstalled" some kind of key for ESXI, so I don't have to enter my own. I also tried to replace it with my vmware.com assigned key, but I get same error each time.
    
    However, if you have an option, please try this yourself. I tried this on few different servers, and I always get same response...original ESXI from vmware.com works ok with boomerang, but HP build doesn't.
    
    Thanks again for you help! Tomaz... Show less
    
    May 15, 2012 at 11:39 am | Reply
    - Tomaz Kavcic says:
      
      One more thing I forgot to add. I can normally connect to all these servers using vSphere Client. Also the license Key which comes bundled with HP ESXI 5.0 U1 is: N4600-62JEJ-J8U49-0C3H6-CECN1. Also if I change that key with my own other key, Boomerang responds the same and it throws the error mentioned before...
      
      May 15, 2012 at 2:19 pm | Reply
      - Tomaz Kavcic says:
        
        Huh, sorry for all this mess. I have to correct myself a little. I logged in to my vmware account and that serial number I posted above is actually my own ESXI key assigned by Vmware.
        I tried to remo... Show more
        
        Huh, sorry for all this mess. I have to correct myself a little. I logged in to my vmware account and that serial number I posted above is actually my own ESXI key assigned by Vmware.
        I tried to remove that key in my ESXi server (put it to trial mode) and I tried to add it to Boomerang ...and it worked! Then I entered that key again to my ESXI server and Boomerang again refused to work with it.
        So, now I am wondering... Should I re-register at vmware to gey new ESXi key which would actually work with Boomerang OK or is there something else I should try? As I see it, the same ESXI installation works normally with Boomerang when in "trial mode", but as soon as I enter that key, it's impossible to add it to Boomerang as I always get that error: "Login failed. Boomerang does not support unlicensed ESXI servers."
        
        Lastly, please remove the key I posted above...it was clearly my mistake. Show less
        
        May 15, 2012 at 2:35 pm | Reply
        
        Tomaz Kavcic says:
        
        Ok, I hope this is my last reply. I made a huge mess, I'm sorry. I created a new test account at vmware and I got another free ESXI 5 license key. I entered it in my ESXi installation and the same thi... Show more
        
        Ok, I hope this is my last reply. I made a huge mess, I'm sorry. I created a new test account at vmware and I got another free ESXI 5 license key. I entered it in my ESXi installation and the same thing happens with boomerang which refuses to work with any of those free keys I have.
        So, if I got that right, Boomerang only works with non-free ESX servers? I mean, it is possible to use Boomerang also with ESXi, but only when in "trial" mode. As soon as you enter and valid free ESXi production key, it's impossible to use Boomerang anymore.
        Therefore I am wondering, is it possible to "fix" Boomerang somehow so it would also work with free ESXi servers? Show less
        
        May 15, 2012 at 3:03 pm | Reply
Pretty cool BUT . . .
Rootman says:

Doesn't support FREE licensed ESXi servers :(

I can use it at work but can't at home.

Also would be cool to HIDE certain guests, like Templates or servers that may be OFF for some reason or other.

May 11, 2012 at 2:09 pm | Reply
- Adam Gross says:
  
  Thanks for the feedback. Unfortunately these are all limitations of the API I use (VIX) but if I ever switch to a newer API I may be able to implement these.
  
  May 12, 2012 at 5:32 am | Reply
Command line launch?
Bryan Keadle says:

Since vmware-rc isn't accepting -u -p option for an auto-authenticated connection, but Boomerang *IS* able to do this (presumably using the AcquireCloneTicket API?), might you be able to provide a com... Show more

Since vmware-rc isn't accepting -u -p option for an auto-authenticated connection, but Boomerang *IS* able to do this (presumably using the AcquireCloneTicket API?), might you be able to provide a command line way to connect to a named VM, passing through similar parameters, e.g.:

boomerang.exe -h (host) -M (vmid) -u (username) -P

Either that, or get your buddies at VMware to enable a -passthroughAuth command parameter for vmware-rc? Show less

April 28, 2012 at 4:35 pm | Reply
- Bryan Keadle says:
  
  Oh, and I should add - thanks for this GREAT TOOL!
  
  April 28, 2012 at 4:36 pm | Reply
- Adam Gross says:
  
  The way I pass credentials to vmware-vmrc.exe is by overriding its stdin and providing credentials securely through that method. I can't do any sort of login as current user mostly just because of th... Show more
  
  The way I pass credentials to vmware-vmrc.exe is by overriding its stdin and providing credentials securely through that method. I can't do any sort of login as current user mostly just because of the limitations of the VIX API, which require that I use a username/password and don't give me access to the underlying ticket. If I ever switch to use a different API, I will likely be able to clone the ticket and use that instead. Show less
  
  April 29, 2012 at 10:04 am | Reply
SnapShot Support
Matt Osburn says:

This is awesome! Any way it can support ability to revert snapshots?

March 21, 2012 at 8:00 am | Reply
- Adam Gross says:
  
  Thanks for the feedback! I am considering adding this functionality in a future release but haven't gotten around to it yet.
  
  March 21, 2012 at 8:56 am | Reply
Manual do console
FRANCISCO RODRIGUES says:

Good morning my friends, today I the company we are using the VMware vSphere Client 4.0, rse would like to know there is a manual in Portuguese Island, and have tried to find anything, if you guys can help me I appreciate it.

a great day everyone.

Francisco

February 13, 2012 at 5:20 am | Reply
Manual do VMware vSphere Clien
FRANCISCO RODRIGUES says:

bom dia meus amigos, hoje eu na empresa estamos usando o VMware vSphere Client 4.0, gostaria de sabe rse existe um manual em portugues do console, já tentei encontrar e nada, se vcs poderem me ajudar eu agradeço.

um ótimo dia a todos.

Francisco

February 13, 2012 at 5:19 am | Reply
Great work
Abdullah Abdullah says:

Salam,

Thank you :).

January 11, 2012 at 10:16 pm | Reply
ESXi support?
Max says:

Hi Adam,

I like the design of the tool and that it is very compact, exact what I was locking for.
Unfortunately it doesn't support ESXi and I get the very same message like Mathieu Bouffard
VMIte... Show more

Hi Adam,

I like the design of the tool and that it is very compact, exact what I was locking for.
Unfortunately it doesn't support ESXi and I get the very same message like Mathieu Bouffard
VMItem::OnVMOpenStateChanged: VM 'SERVERNAME' open state changed to STATE_OPEN_FAILED.
VixVM::OnVMOpened: Opening VM 'SERVERNAME' failed with asyncError 3014 (Insufficient permissions in host operating system).

Is there support for ESXi planned?

There is nothing more to say than great work! Keep it up! :)

Best regards,
Max Show less

January 11, 2012 at 9:09 am | Reply
- Adam Gross says:
  
  Sorry, no support for ESXi is planned. This is a licensing limitation that I have no control over.
  
  January 11, 2012 at 9:53 am | Reply
Something like this for OSx
Sumit Bansal says:

If it possible to get this for Apple mac osx ?

January 5, 2012 at 3:52 am | Reply
- Adam Gross says:
  
  Sorry, but I have no plans to port this to Linux or Mac.
  
  January 5, 2012 at 6:02 am | Reply
  - Jose Ocasio says:
    
    :( Sad comment! But anyhow thanks for this great app, running it on the vmwbox!
    
    May 7, 2012 at 5:35 am | Reply
Display vApp would be great
Jean-Marc says:

Great little utility... would be even better if it displayed vApps too.

December 7, 2011 at 11:30 am | Reply
Great Work!
Arihant Jain says:

Great Work!

December 6, 2011 at 12:04 am | Reply
Thanks
Danilo Recchia says:

Amazing job!

November 9, 2011 at 7:36 pm | Reply
VM Names, Folders & DNS name i
Anthony Larson says:

1) Is it possible to use the VM Names and folders found in the vi client, => Inventory => VMs and Templates ?
2) Also, could we have the folder names as well?
I am using vSphere v4.1 with vc... Show more

1) Is it possible to use the VM Names and folders found in the vi client, => Inventory => VMs and Templates ?
2) Also, could we have the folder names as well?
I am using vSphere v4.1 with vcenter v4.1.
3) Also, I've noticed that if vi Client is not installed, vmware boomerang will not connect to the vms.
4) An indicator to the right of the vm name, displaying if the vm is powered on or powered off would be great.
5) Boomerang does not seem to work with a DNS name, for the vcenter server, and only with IP Addressses when connecting to a specific vm, however does login/connect to the vcenter server. Show less

October 26, 2011 at 1:34 pm | Reply
- Adam Gross says:
  
  Thanks for the comments Anthony. For #1, #2, and #4 I am unable to implement them as the vix API that I use does not allow operations like that without costly operations to "open" a VM so I can't off... Show more
  
  Thanks for the comments Anthony. For #1, #2, and #4 I am unable to implement them as the vix API that I use does not allow operations like that without costly operations to "open" a VM so I can't offer them to all VMs automatically. ESX 5.0 offers a better API that I may selectively use but that wouldn't be for a while.
  
  For #3, that is correct. I hope the error message that is shown is helpful enough. I depend on the VMware Remote Console, which is installed with the vSphere Client, to connect a console to a VM.
  
  For #5, this should work. Are you sure that your client machine is able to resolve the DNS name and the IP address that it resolves to matches the one you would expect? With 1.1 I also added the ability to automatically append default DNS suffixes to a request if it doesn't already include one, so all cases should work. Show less
  
  October 27, 2011 at 7:44 am | Reply
  - Anthony Larson says:
    
    For #4 , Is it possible to use the same code which highlights/depressed the Green PoweredOn or Red PoweredOff buttons, and create a indicator beside the VM name, to show that the VM is powered on or ... Show more
    
    For #4 , Is it possible to use the same code which highlights/depressed the Green PoweredOn or Red PoweredOff buttons, and create a indicator beside the VM name, to show that the VM is powered on or off?
    
    For #5, If I use the full FQDN boomerang works fine, if I use the shortened DNS name it will not connect. However if I use vi client v4.1, ping and tracert it works with both the FQDN & the DNS name.
    
    Also, is it possible I could have a copy of the code for boomerang?
    
    Thanks,
    Anthony Show less
    
    October 27, 2011 at 10:55 am | Reply
    - Adam Gross says:
      
      For #4, with the API I use, this is only possible if you have "opened" the VM which takes a few seconds (you can count the time when you select a VM to expand it). As a result, it isn't immediately a... Show more
      
      For #4, with the API I use, this is only possible if you have "opened" the VM which takes a few seconds (you can count the time when you select a VM to expand it). As a result, it isn't immediately available for all VMs so I am hesitant to put it on the main row.
      
      For #5, if you are using Boomerang 1.1 and the server name you entered doesn't have the "." character in it, I try to append each DNS suffix in HKLM\System\CurrentControlSet\services\Tcpip\Parameters\SearchList. If this still doesn't work, you may want to check the most recent log file in "%TEMP%\vmware-" to see which DNS suffixes I try to append. The log file would say something like "Retrying hostname as" then tell the new address it's trying. You may want to see if any match the one that you want it to match.
      
      Also, currently, Boomerang is not open-source. Show less
      
      October 27, 2011 at 12:04 pm | Reply
      - Anthony Larson says:
        
        For #4, then how about once a person clicks on the VM name, then when it's expanded, showing the start, stop, pause restart button, also have a status indicator to the right showing powered on/powered... Show more
        
        For #4, then how about once a person clicks on the VM name, then when it's expanded, showing the start, stop, pause restart button, also have a status indicator to the right showing powered on/powered off & paused?
        
        I know that a green/red (yellow for pause?) status indicator would only show for the VM that is currently selected, but it would be more noticeable than just the poweron/poweroff buttons being "depressed/ highlighted".
        
        The reason for this is my users don't look at the "highlighted/depressed" buttons and start powering on/powering off vms when they shouldn't.
        They claim not to not easily see the status on the buttons.
        
        What do you think of this though? Show less
        
        October 28, 2011 at 9:51 am | Reply
- tux says:
  
  It seems that the tool cannot search the VM's that are members of a vApp.
  
  May be a good idea to check that out for the next version :)
  
  Excellent APP, I like it a LOT !
  
  October 28, 2011 at 6:52 am | Reply
Share desktop
Eduardo says:

Hello Team!

Great App! :)

There is a way to share the desktop between the end user and support team?

Thanks.

Best,
Eduardo.

September 30, 2011 at 7:03 am | Reply
- Adam Gross says:
  
  Thanks! Are you referring to a VMware View desktop running over PCoIP?
  
  September 30, 2011 at 7:28 am | Reply
Thanks for the Tool
TWSS says:

Hello,
thanks for the tool, i search a long time for this.
It is possible to insert the notes from the virtuel machine when the mouse is over the Virtuell Machine button.

can i start a virtuell machine with boomerang in the comand line.

September 8, 2011 at 10:59 am | Reply
- Adam Gross says:
  
  Thanks for the feedback! It is not possible to start a virtual machine with boomerang in the command line. I will look into the notes thing, that's a good idea.
  
  September 9, 2011 at 6:21 am | Reply
Connecting to a different port
Brian says:

Very nice little app which is handy to do quick VM operations.

Alas when I was testing this fling to connect to a different port rather than the defaults for HTTP (80) and HTTPS (443), the applicat... Show more

Very nice little app which is handy to do quick VM operations.

Alas when I was testing this fling to connect to a different port rather than the defaults for HTTP (80) and HTTPS (443), the application fails to connect. The server is setup correctly on a different port since I can connect with other applications yet wire traces show that Boomerang, even though the port in the "Add Server" dialog is set to the server port, still tries to connect to the default 80/443.

Still, thumbs up for this handy project. Show less

August 29, 2011 at 12:25 am | Reply
- Adam Gross says:
  
  Thanks for the comment, I will look into this. It appears that my application is passing the correct values into the library I use so I will have to find out why it's not respecting those values.
  
  August 29, 2011 at 7:28 am | Reply
  - Brian says:
    
    I may have jumped the gun a little bit here but I did some little analysis with Process Monitor to see the VIX API and Boomerang log files to try and help if possible.
    
    I am currently assuming that ... Show more
    
    I may have jumped the gun a little bit here but I did some little analysis with Process Monitor to see the VIX API and Boomerang log files to try and help if possible.
    
    I am currently assuming that this Boomerang log:
    2011-08-30 07:31:59.294 [02C8] AddServerDlg::Connect: Attempting to connect to hostname '0.0.0.0'.
    maps to the VIX API log:
    Aug 30 07:31:59.544: app-712| VixHost_ConnectEx: version -1, hostType 10, hostName http://0.0.0.0/sdk, hostPort 8080, options 0
    
    With another custom VIX application which I use to connect to my server produces the following log:
    Aug 30 07:35:57.185: app-428| VixHost_ConnectEx: version -1, hostType 10, hostName http://0.0.0.0:8080/sdk, hostPort 0, options 0
    
    The hostPort is 0 and it is set as part of the hostName as requested by VixHost_Connect in the VIX API reference.
    
    Hope that those be of help. Show less
    
    August 29, 2011 at 10:58 pm | Reply
permissions
Sergey says:

I noticed that this tool requieres administrative permissions on Datacenter level. not good, not good...
Any fix? Thanx

August 8, 2011 at 6:13 am | Reply
- Alex says:
  
  I am seeing a similar issue. We want this for some of our admins who should have minimal access.
  
  August 8, 2011 at 10:04 am | Reply
  - Adam Gross says:
    
    This may be a bug in the API I use. Can you guys e-mail me the Boomerang log and the VIX log where this happens? My e-mail address is grossag @AT@ vmware .DOT. com. You can find the Boomerang log in %TEMP%\vmware-. You should be able to find the VIX log either in that same directory or in a similarly named folder of the form %TEMP%\vmware--.
    
    August 8, 2011 at 11:23 am | Reply
    - Sergey says:
      
      Sent you the logs. Check it, please
      
      August 8, 2011 at 11:26 pm | Reply
      - Mathieu Bouffard says:
        
        Same thing here.
        When trying to add permissions for a user at a VM level, it gives me "Failed to open the VM" if I try to connect through Boomerang.
        If I add the user on the Datacenter permissions l... Show more
        
        Same thing here.
        When trying to add permissions for a user at a VM level, it gives me "Failed to open the VM" if I try to connect through Boomerang.
        If I add the user on the Datacenter permissions level, it works.
        But I want to limit the user to manage only a bunch of VMs, not all VMs.
        
        Little request: It will be good if this little soft could support Linked-Mode Vcenters. A user could easily access to all VMs he has access through all Vcenters, using only one connection. Show less
        
        August 10, 2011 at 4:04 am  |  Reply
        
        Mathieu Bouffard says:
        
        These are the errors that I've got in the boomerang log:
        
        2011-08-10 12:56:26.020 [0110] VMItem::OnVMOpenStateChanged: VM 'SERVERNAME' open state changed to STATE_OPEN_FAILED.
        
        2011-08-10 12:56:26.020 [0110] VixVM::OnVMOpened: Opening VM 'SERVERNAME' failed with asyncError 3014 (Insufficient permissions in host operating system).
        
        August 10, 2011 at 4:17 am  |  Reply
        
        Adam Gross says:
        
        When vSphere 5.0 is released, I would be interested in seeing whether it has the same problem. It may be a permissions issue with vSphere that I would need to file internally.
        
        August 23, 2011 at 9:53 am  |  Reply
        
        Alex says:
        
        same issue with 5, let me know if you still want logs. This is an amazing fling (my personal fav) and want to get it out to more users!
        
        September 4, 2011 at 8:08 pm  |  Reply
        
        JW says:
        
        Assigning permissions to folders works
        
        October 12, 2011 at 12:04 pm  |  Reply
        
        Adam Gross says:
        
        I talked to someone on the VIX team and they said that you could do 1 of the following 2 things to remedy this:
        
        1. Provide backup operator administrator privileges on the Datacenter that hosts the ESX, or
        2. Create a Role that just has "System.View" privilege. Assign backup operator this role at Datacenter level and administrator privileges on the ESX.
        
        February 23, 2012 at 6:53 am  |
        
        Alex says:
        
        Adam,
        
        For some reason I can't reply to your latest message on Feb 23rd, however when you said provide "backup operator" administrator privileges or in option 2 you said to create a new role with sy... Show more
        
        Adam,
        
        For some reason I can't reply to your latest message on Feb 23rd, however when you said provide "backup operator" administrator privileges or in option 2 you said to create a new role with system.view.
        
        first, what "backup operator" do you mean? Is this the server's builtin group "Backup Operators", or something special?
        Second, as far as creating a new role with just "System.View", I assume this would need to be done via the SDK, any way you can shed some light on the specific command(s) to run? Show less
        
        March 12, 2012 at 1:45 pm  |  Reply
        
        Neha says:
        
        >> first, what "backup operator" do you mean? Is this the server's builtin group "Backup Operators", or something special?
        
        The backup operator is not a built-in group or any existing role. It... Show more
        
        >> first, what "backup operator" do you mean? Is this the server's builtin group "Backup Operators", or something special?
        
        The backup operator is not a built-in group or any existing role. It was a specific role that other customer has created for performing backup operation with selective privileges.
        
        >> Second, as far as creating a new role with just "System.View", I assume this would need to be done via the SDK, any way you can shed some light on the specific command(s) to run?
        
        This can be done by connecting vSphere client to vCenter too. The "System.View" privilege is available by default to all Roles. Thus, to create a custom role with "System.View" privilege, click Home > Administration > Roles > Add Role, and give a name to the role. You do not need to add any other privilege. The following privileges are created by default for this role:
        "System.Anonymous"
        "System.Read"
        "System.View" Show less
        
        March 14, 2012 at 10:02 pm  |  Reply
vLand
Fantom says:

Thanks dude, keep it rocking. Definitely come out with a new version with any tweaks and new ideas. Great program and thanks for sharing.

July 27, 2011 at 10:16 am | Reply
Power Operations
RAMESH GEDDAM says:

It would be helpful, if we have Green arrow icons, if the VM is running. After looking at the video, The tool doesnt show, whether the VM is powered on or off or suspended, which is really dangerous for production environments, before we even click connect, we should know, whether the VM is running or not.
Apart from this, I see this as a helpful tool,. Nice work,,,,

July 25, 2011 at 8:49 am | Reply
- Adam Gross says:
  
  Thanks for the feedback. Unfortunately, the API I use doesn't offer me a scalable way to get the power state of all VMs so I am hesitant to put a power icon next to the VMs. However, when you click ... Show more
  
  Thanks for the feedback. Unfortunately, the API I use doesn't offer me a scalable way to get the power state of all VMs so I am hesitant to put a power icon next to the VMs. However, when you click a VM to open it, you should be able to tell the power state based on the state of the power controls. The VM's current state should be shown as a depressed button that cannot be pressed again, which will indicate whether the VM is suspended or powered off. Show less
  
  July 25, 2011 at 10:08 am | Reply
Searching
Kevin Foster says:

First off great app!

We have multiple VC's and one of them is for a labmanager setup. We have a lot of hosts flying up and down and we need to troubleshoot some of them. It would be great if you could at a filter/search bar at the top so we could quickly locate the vm and connect.

Great work!

Kevin

July 14, 2011 at 12:16 pm | Reply
- Adam Gross says:
  
  Thanks for the recommendation! I am working on exactly that and am hoping to have an update released in the next few weeks.
  
  July 15, 2011 at 12:06 pm | Reply
  - Peter Smith says:
    
    This will be great.
    
    July 18, 2011 at 11:27 am | Reply
    - Adam Gross says:
      
      Just wanted to let you know that the new version that is available now includes this functionality. Let me know if you find any problems with it.
      
      August 14, 2011 at 6:37 am | Reply
Permissions
Roey Azroel says:

Hi Adam,

First, Cool App! and very useful!

I have one question - I want my developer to use this application for the same reason as you... less application are open in the same time.

but if i... Show more

Hi Adam,

First, Cool App! and very useful!

I have one question - I want my developer to use this application for the same reason as you... less application are open in the same time.

but if i give two different developers to use Boomerang, and they both have different permissions, Boomerang will know how to show them the VMs that they have permission to control in the vCenter?

Thanks!

Roey Show less

July 8, 2011 at 12:37 pm | Reply
- Adam Gross says:
  
  I am not too familiar with setting up permissions for users in vCenter, but I believe that it is fairly easy to do. You can test whether this works on Boomerang by adding a server for a specific user. Then you can remove the server using the red "-" icon and then re-add it with another user's info. Pete confirmed below that this is possible.
  
  July 10, 2011 at 8:45 pm | Reply
What about Android?
Eps says:

Hi,

Whay about porting Boomerang to Android for free? :D

Eps.

July 8, 2011 at 8:12 am | Reply
suggestions
Hal Rottenberg says:

Great little tool. Here's some suggestions that I have:
- have preference setting (THAT DEFAULTS TO ON) to prompt before performing the power operations. This is a pretty dangerous thing to not have ... Show more

Great little tool. Here's some suggestions that I have:
- have preference setting (THAT DEFAULTS TO ON) to prompt before performing the power operations. This is a pretty dangerous thing to not have that reminder
- How about a MRU (most recently used) list? This would work in addition to favorites, but it is automatic. In other words, if I just rebooted a VM, it would be nice for that VM to float to the top of a list so that I can know to check its power state or console later. Combine that with the other suggestions of showing power state inline and this would be very powerful.
- How about adding a pushpin icon that would turn the window into a real 'tooltip' window? Then we could move it over to a second monitor or unused part of the screen and have that quick access without going to the tray each time. Show less

July 8, 2011 at 6:57 am | Reply
- Adam Gross says:
  
  Thanks for the feedback; those are all great ideas I agree about the importance confirming before power operations; I'm not quite sure how I forgot to do that. MRU also sounds good and so does a pushpin icon. I have implemented a pushpin icon in previous applications that I have used but wasn't sure whether people would actually use it.
  
  July 10, 2011 at 8:43 pm | Reply
Great app!
Hal Rottenberg says:

Very cool app! I love the favorites feature.

July 8, 2011 at 6:50 am | Reply
- Fabian says:
  
  Yes, it is very great. I entered the adress of the vcenter server and it works. only bad think is, that i must enter the credentials at opening the remote console. i hope this will fix very fast!
  
  July 11, 2011 at 1:24 am | Reply
A useful tool
Yong says:

It's quite useful and convenient to do basic VM management. I got two questions after a quick trial:
1. It doesn't accept short hostname (full FQDN and IP address work fine), it's better to do a name resolution first.
2. The main window is fixed, it's better to support drag and zoom to customize the window size.

July 8, 2011 at 12:13 am | Reply
- Adam Gross says:
  
  Thanks for the feedback. I will look into implementing the features you requested.
  
  July 10, 2011 at 8:41 pm | Reply
Search
Ammesiah says:

Nice tool.
It could be very nice to implement some search when dealing with large/multiple infrastructure.

July 8, 2011 at 12:08 am | Reply
- hhmz says:
  
  I totaly agree with Ammesiah...nice app but you must add search in the next release.
  
  July 11, 2011 at 6:17 am | Reply
  - Adam Gross says:
    
    As long as a VM is not collapsed into a hyperlink, you are able to type the name of the VM to navigate over to it. Just try select one VM with the mouse then typing the name of another one. Is this what you're looking for or are you looking for something more powerful?
    
    July 11, 2011 at 6:31 am | Reply
Auth errors on esxi 4.1 U1(fre
Matteo Saitta says:

All my free esxi hosts do not authenticate with boomerang(while my production vcenter does) either in ssl or plain connections. Any special requirements to make it work with free esx?

July 7, 2011 at 11:39 pm | Reply
- Giovanni Uccio says:
  
  Is the same for me with my ESXi Host, I received back the message: "Login failed" when I try the autenthication.
  
  info:
  
  VMware ESXi Version 4.1.0 Build 381591
  
  License: Product: vSphere 4 Hypervisor Licensed for 1 physical CPUs (1-6 cores per CPU)
  
  Someone else has tried ?
  
  Kind Regards
  
  July 8, 2011 at 12:25 am | Reply
  - Giuseppe says:
    
    Same problem also for me.
    
    July 8, 2011 at 5:26 am | Reply
    - Adam Gross says:
      
      You should be able to get more information from the Boomerang log. Open up the %TEMP%/vmware- directory and find the most recently modified log with "boomerang" in the file name. There should be an entry for the login error detailing the error code and a description string. Can you post it? Thanks!
      
      July 10, 2011 at 2:14 pm | Reply
      - Adam Gross says:
        
        Nevermind, it looks like VIX doesn't support free ESXi. I will have someone update this page to make this clearer and will try to change the app to make it clearer as well in a future version. I apologize for the confusion.
        
        July 11, 2011 at 7:36 pm | Reply
        
        Giovanni Uccio says:
        
        ok, thank you adam for the notification.
        
        Regards,
        Govanni
        
        July 18, 2011 at 5:07 am | Reply
RFC's
SchulieBug says:

A few wishes:
- detect the proxy used when checking for updates
- the ability to use SSON (like vSphere client itself also does)

July 7, 2011 at 11:25 pm | Reply
- Adam Gross says:
  
  Thanks for the feedback. The application should be able to auto-detect the proxy that you have set. How did you set your proxy in Start > Control Panel > Internet Options > Connections > LAN Settings?
  
  July 10, 2011 at 8:39 pm | Reply
  - SchulieBug says:
    
    Proxy settings are autodetect. We're using a MS proxy server, so maybe there is an issue with ports?
    
    July 11, 2011 at 4:37 am | Reply
    - Adam Gross says:
      
      The expected behavior is that the application automatically uses the current Windows proxy settings. So to confirm, you are clicking the "Check For Updates" button but it is saying that the check for... Show more
      
      The expected behavior is that the application automatically uses the current Windows proxy settings. So to confirm, you are clicking the "Check For Updates" button but it is saying that the check for updates failed? If so, can you try clicking the button again then opening the log by going to %TEMP%\vmware- then finding the most recently modified log file with "boomerang" in the title. There should be a few lines at the end that will say something like:
      
      2011-07-11 06:32:55.324 [11FC] utils::HttpOpenUrl: InternetOpenUrl() failed: http://www.vmware.com/info?id=1047 (12007).
      2011-07-11 06:32:55.334 [11FC] utils::ReadURL: InternetOpen failed for direct connection. Checking for proxy.
      2011-07-11 06:32:57.897 [11FC] utils::HttpGetHostProxySettings: Failed to get winhttp proxy info with error 0x2f94.
      2011-07-11 06:32:57.897 [11FC] utils::ReadURL: Unable to open url at 'http://www.vmware.com/info?id=1047'.
      
      Can you post those? Thanks! Show less
      
      July 11, 2011 at 6:38 am | Reply
Nice work
Hersey Cartwright says:

Very nice, very handy. I added my production vCenter server and tested it with a free ESXi server I have in my lab and it seems to work just fine for both.

Couple of things that would be nice - fil... Show more

Very nice, very handy. I added my production vCenter server and tested it with a free ESXi server I have in my lab and it seems to work just fine for both.

Couple of things that would be nice - filter out templates and make it easier to tell if a VM is powered on or off (change the link color, add a icon to indicate the VM is running).

I did a quick write up on it here http://www.vhersey.com/2011/07/boomerang-fling-handy-little-app/

Thanks for the fling.
Hersey Show less

July 7, 2011 at 6:26 pm | Reply
- Adam Gross says:
  
  Thanks for the feedback! I agree with you and will look at those requests for a future release.
  
  July 7, 2011 at 9:19 pm | Reply
- Adam Gross says:
  
  I looked into this further and unfortunately it appears that I can't implement either. The VIX API that I use requires that I "open" a VM (which takes 5 seconds per VM) to get any power information o... Show more
  
  I looked into this further and unfortunately it appears that I can't implement either. The VIX API that I use requires that I "open" a VM (which takes 5 seconds per VM) to get any power information or determine whether it's a template. It doesn't scale to open each VM so I just have to parse the VMX path (which is all I get) to determine the VM name and not do anything else until the user selects the VM. Show less
  
  July 10, 2011 at 8:41 pm | Reply
very interesting....
Pete Koehler says:

I'm looking to see if this addresses one specific use case we have. We have several linux VM's for our development team. Our internal build processes require these systems to be logged in as a parti... Show more

I'm looking to see if this addresses one specific use case we have. We have several linux VM's for our development team. Our internal build processes require these systems to be logged in as a particular user, and "xhost +" run so that X windows can be released to other remote displays. In order for Xhost + to work, it has to be run on the local console. (and no, this cannot be automatically started at boot). Not a big deal when these were physical boxes, but definately something to be concerned about when they are VMs. I'm reluctant to give any of our developers access to a vcenter console just so they can do this, so I'm considering to see if I can make this work for that purpose. The specific VM's they would need access to are already in a designated folder inside of vsphere, and I added a special user that would just have permission to that folder, but if I add any permission setting minus administrator, it fails to work. Any thoughts? Show less

July 7, 2011 at 2:56 pm | Reply
- Pete Koehler says:
  
  Sorry... spoke to soon. Just a little top-level permissions issue with my in regards to my earlier comment. All seems to be working well. Very very interesting little app. Nice work.
  
  July 7, 2011 at 6:40 pm | Reply
  - Adam Gross says:
    
    Glad to hear it worked out, and thanks for the compliment! Let me know if you have any further feedback or questions.
    
    July 7, 2011 at 9:24 pm | Reply
Flings not supporting Free ESX
AB says:

Why are these flings not supporting Free Hypervisors.

July 7, 2011 at 12:02 pm | Reply
- Adam Gross says:
  
  Have you tried it? I haven't tested it but I wouldn't be surprised if it works. This fling uses VIX ( https://www.vmware.com/support/developer/vix-api/ ) so if it supports free ESX then the fling should as well.
  
  July 7, 2011 at 12:35 pm | Reply
  - Giovanni Uccio says:
    
    Hi Adam,
    I tried to login into my ESXi server and I also have installed the 1.10.3 version of VIX API but I'm unable to complete my login getting back the "login failed" message.
    
    Kind regards
    
    info: VMware ESXi Version 4.1.0 Build 381591
    
    July 8, 2011 at 12:45 am | Reply
    - Dino Sousa says:
      
      Hi,
      I got the same error...
      
      Thanks
      
      July 8, 2011 at 2:14 am | Reply
      - Andrew says:
        
        +1
        
        ESXi 4.1.0 build 260247
        Login failed with correct account
        
        anyone handle with that?
        
        July 8, 2011 at 5:47 am  |  Reply
        
        Raimo says:
        
        Same error. I have VIX for Windows 64-bit installed and ESXi 4.1 with free licence applied.
        
        July 8, 2011 at 12:54 pm  |  Reply
        
        Adam Gross says:
        
        You should be able to get more information from the Boomerang log. Open up the %TEMP%/vmware- directory and find the most recently modified log with "boomerang" in the file name. There should be an entry for the login error detailing the error code and a description string. Can you post it? Thanks!
        
        July 10, 2011 at 2:16 pm  |  Reply
        
        Raimo says:
        
        vmware-boomerang-....txt:
        2011-07-11 08:40:26.967 [1A24] State::AddServer: Adding ESX/VC server failed with error 32 (This operation is not supported with the current license).
        
        vmware-vix....log:
        Jul 11 08:40:26.967: app-5856| Vix: [5856 vixVIMProxy.c:1023]: Error VIX_E_LICENSE in VixVIMHostOnLicenseManagerLoaded(): host has basic license and does not support remote management
        
        July 10, 2011 at 10:10 pm  |  Reply
        
        Adam Gross says:
        
        Thanks for the info. I talked to some developers of the VIX API and confirmed that they do not support free ESXi. I will make this clearer on the web page and in the application in a future version. I apologize for the confusion.
        
        July 11, 2011 at 7:37 pm  |  Reply
        
        Raimo says:
        
        Could you add support for free licenced ESXi?
        
        July 10, 2011 at 10:11 pm  |  Reply
  - William Lam says:
    
    Actually VIX API does not support Free ESXi, it requires that ESX(i) is licensed
    
    May want to put that in the requirements section
    
    July 9, 2011 at 8:34 am | Reply
    - Raimo says:
      
      It's licenced with free licence
      
      July 10, 2011 at 5:59 am | Reply
      - River.Hog says:
        
        I have same problem with ESXi, it does not work, Same complain about license, but if you check another log in temp vmware-vix-.... you can see similar to mine:
        ---
        Jul 11 10:29:27.160: app-18292| Vi... Show more
        
        I have same problem with ESXi, it does not work, Same complain about license, but if you check another log in temp vmware-vix-.... you can see similar to mine:
        ---
        Jul 11 10:29:27.160: app-18292| Vix: [18292 vixVIMProxy.c:1023]: Error VIX_E_LIC
        ENSE in VixVIMHostOnLicenseManagerLoaded(): host has basic license and does not
        support remote management
        ---
        so it seems that ESXi does not support remote management and this is ESXi limitation not this tool so cannot be "fixed" or added to Boomerang. Show less
        
        July 10, 2011 at 11:41 pm | Reply

Boomerang

Comments

HP ESXI free server!

Pretty cool BUT . . .

Command line launch?

SnapShot Support

Manual do console

Manual do VMware vSphere Clien

Great work

ESXi support?

Something like this for OSx

Display vApp would be great

Great Work!

Thanks

VM Names, Folders & DNS name i

Share desktop

Thanks for the Tool

Connecting to a different port

permissions

vLand

Power Operations

Searching

Permissions

What about Android?

suggestions

Great app!

A useful tool

Search

Auth errors on esxi 4.1 U1(fre

RFC's

Nice work

very interesting....

Flings not supporting Free ESX

Leave a Reply Cancel reply

Flings

Like

Engineers

Adam Gross

Tags

VMware Labs Updates

Follow VMware Labs

Links

Terms of Use