Mike's Realm chown -R us ./base


vShield Manager 5.5 Upgrade Fails: Invalid file

So your kicking off your vSphere 5.5 upgrade and your starting off with vShield Manager and what should be a real easy upgrade you instantly get this error when you upload the Upgrade Bundle:

vshield failure


Fortunately the fix is super simple, just rename to ensure the file extension is .tar.gz e.g.:

Downloaded file: VMware-vShield-Manager-upgrade-bundle-5.5.0-1317534.gz
Renamed file: VMware-vShield-Manager-upgrade-bundle-5.5.0-1317534.tar.gz

It's worth noting that this was also an issue with vShield Manager 5.1 as well if you were performing an upgrade...


List/Export Installed Windows Updates Including Windows Server 2012


Previously I had written about this for Windows Server 2008 and prior versions.  I just wanted to mention that this works on Windows Server 2012 via wmic as well.

So if your running Windows Server 2012 and want to export a list of updates use WMIs Command-line interface (WMIC) to generate the list.

Launch a command prompt and type:

 wmic qfe get /format:csv >C:\updates.csv

Also note that instead of a csv you can use these other format options:


LIST is Tab Delimited



Orchestrator: Error: Not published webview error The webview ‘weboperator’ is not published.

Working with vCenter Orchestrator and getting "Error: Not published webview error The webview 'weboperator' is not published." when you try to approve a user interaction in your workflow?

Navigate to Web Views and right click weboperator and ensure it's published!


vCenter Orchestrator Plugin Updates!


These updates were posted on the vCenter Orchestrator forums recently, if you aren't keeping tabs over there you should be.

Links for each plugins release notes can be found on the thread @ http://communities.vmware.com/thread/405928?tstart=0


Cook your own VMware AppBlast


Wrote this article almost 6 months ago...finally got around to finishing it--Let me know what you think!

"Project AppBlast will provide the universal delivery of any application, including Windows-based applications, to any off-the-shelf browser or device supporting HTML 5, enabling instant remote access to non-HTML based applications."

We discussed this at work the other day and we were excited at the possibilities with AppBlast, but since it's not here now we'll have to wait for a released product.  One of my co-workers Chad Wintzer said well why wait?  We dug around and came up with a working solution--and a damn good one after a few evenings grinding away at this.  Having a fair amount of RDS experience already this is what we came up with:


The backend infrastructure is provided by Microsoft's Remote Desktop Services: RemoteApp.  This feature was introduced in Windows Server 2008 and was improved upon even more in the R2 release.  What RemoteApp allows you to do is run applications on backend RDS (TS) servers, and establish an RDP session from a user to just that app.  The user is presented with a window over their local desktop and functions just about as if it was actually installed and running off the local desktop.  Users can run multiple applications in parallel and so long as the app behaves well in a RDS environment you can host 1 installation with multiple users.  The servers that run RemoteApps are called RD Session Hosts, to scale you can simply throw a bunch of RD Session Hosts together and strap a load balancer on top, however you will want to use RD Connection Broker(s) in place of a traditional load balancer to keep track of user sessions.  The Connection Broker(s) manage session information such as RD Session Host server, session state, session ID, and the user associated with the aforementioned bits.  For the security junkies it's worth noting that RemoteApp is AD integrated so you can restrict access to various apps via Security Groups.  This was something added in R2 I believe as many folks were complaining about this when RemoteApp first came out.

If you don't want to go that route you can look at Citrix's XenApp offering, but we found RDS: RemoteApp performed exactly as we needed it to.


Howto Reboot/Shutdown Windows Server 8


I can't believe I am actually writing this...with all the major changes Win8/Win8 Server are bringing one would never think they would change how you shutdown or restart, right?  Well we are wrong...

You can't just click Start->Shutdown anymore, old schoolers might remember this one:


Focus needs to be on the desktop (minimize all other windows, or click on the wallpaper so focus is on the desktop) then hit Alt+F4 to see a familiar window:

Windows Key+C

This is the "Charms" shortcut key.  Charms is a Microsoft term for these icons that appear when you hit Windows Key+C:

Then Click Settings:

Now you can click Power & select Restart or Shutdown.



Howto Install VIB Patches on ESXi Hosts Without Update Manager

So you find yourself in a position where you need to update one (or more) of your hosts but don't have vCenter Update Manager around to assist.  In my case trying to get Windows Server 8 CP working....It's not terribly difficult, you simply:

  1. Download the patch - you can download patches direct from VMware @ the Patch Portal
  2. Open a datastore with enough freespace to store the patch via your vSphere Client (Right-Click->Browse on a datastore)
  3. Upload the patch you downloaded (should be a .zip file)
  4. SSH into the host
  5. Execute the command "esxcli software vib install /vmfs/volumes/<DATASTORE-NAME>/<PATCH-NAME>.zip"  - replacing the <DATASTORE-NAME> and <PATCH-NAME> appropriately.

This command can take some time to execute for large patches.

When it's done you should get some text like below, remember to pay attention to this text so you know if you need to reboot your host or not.

Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: VMware_bootbank_esx-base_5.0.0-0.7.515841, VMware_bootbank_mi sc-drivers_5.0.0-0.7.515841, VMware_bootbank_net-be2net_4.0.88.0-1vmw.500.0.7.51 5841, VMware_bootbank_net-e1000_8.0.3.1-2vmw.500.0.7.515841, VMware_bootbank_net -e1000e_1.1.2-3vmw.500.0.7.515841, VMware_locker_tools-light_5.0.0-0.7.515841
VIBs Removed: VMware_bootbank_esx-base_5.0.0-0.0.469512, VMware_bootbank_misc -drivers_5.0.0-0.0.469512, VMware_bootbank_net-be2net_4.0.88.0-1vmw.500.0.0.4695 12, VMware_bootbank_net-e1000_8.0.3.1-2vmw.500.0.0.469512, VMware_bootbank_net-e 1000e_1.1.2-3vmw.500.0.0.469512, VMware_locker_tools-light_5.0.0-0.0.469512
VIBs Skipped: VMware_bootbank_ata-pata-amd_0.3.10-3vmw.500.0.0.469512, VMware _bootbank_ata-pata-atiixp_0.4.6-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-cm d64x_0.2.5-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-hpt3x2n_0.3.4-3vmw.500. 0.0.469512, VMware_bootbank_ata-pata-pdc2027x_1.0-3vmw.500.0.0.469512, VMware_bo otbank_ata-pata-serverworks_0.4.3-3vmw.500.0.0.469512, VMware_bootbank_ata-pata- sil680_0.4.8-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-via_0.3.3-2vmw.500.0. 0.469512, VMware_bootbank_block-cciss_3.6.14-10vmw.500.0.0.469512, VMware_bootba nk_ehci-ehci-hcd_1.0-3vmw.500.0.0.469512, VMware_bootbank_esx-tboot_5.0.0-0.0.46 9512, VMware_bootbank_ima-qla4xxx_2.01.07-1vmw.500.0.0.469512, VMware_bootbank_i pmi-ipmi-devintf_39.1-4vmw.500.0.0.469512, VMware_bootbank_ipmi-ipmi-msghandler_ 39.1-4vmw.500.0.0.469512, VMware_bootbank_ipmi-ipmi-si-drv_39.1-4vmw.500.0.0.469 512, VMware_bootbank_misc-cnic-register_1.1-1vmw.500.0.0.469512, VMware_bootbank _net-bnx2_2.0.15g.v50.11-5vmw.500.0.0.469512, VMware_bootbank_net-bnx2x_1.61.15. v50.1-1vmw.500.0.0.469512, VMware_bootbank_net-cnic_1.10.2j.v50.7-2vmw.500.0.0.4 69512, VMware_bootbank_net-enic_1.4.2.15a-1vmw.500.0.0.469512, VMware_bootbank_n et-forcedeth_0.61-2vmw.500.0.0.469512, VMware_bootbank_net-igb_2.1.11.1-3vmw.500 .0.0.469512, VMware_bootbank_net-ixgbe_2., VMware_b ootbank_net-nx-nic_4.0.557-3vmw.500.0.0.469512, VMware_bootbank_net-r8168_8.013. 00-3vmw.500.0.0.469512, VMware_bootbank_net-r8169_6.011.00-2vmw.500.0.0.469512, VMware_bootbank_net-s2io_2.1.4.13427-3vmw.500.0.0.469512, VMware_bootbank_net-sk y2_1.20-2vmw.500.0.0.469512, VMware_bootbank_net-tg3_3.110h.v50.4-4vmw.500.0.0.4 69512, VMware_bootbank_ohci-usb-ohci_1.0-3vmw.500.0.0.469512, VMware_bootbank_sa ta-ahci_3.0-6vmw.500.0.0.469512, VMware_bootbank_sata-ata-piix_2.12-4vmw.500.0.0 .469512, VMware_bootbank_sata-sata-nv_3.5-3vmw.500.0.0.469512, VMware_bootbank_s ata-sata-promise_2.12-3vmw.500.0.0.469512, VMware_bootbank_sata-sata-sil_2.3-3vm w.500.0.0.469512, VMware_bootbank_sata-sata-svw_2.3-3vmw.500.0.0.469512, VMware_ bootbank_scsi-aacraid_1.1.5.1-9vmw.500.0.0.469512, VMware_bootbank_scsi-adp94xx_, VMware_bootbank_scsi-aic79xx_3.1-5vmw.500.0.0.4695 12, VMware_bootbank_scsi-bnx2i_1.9.1d.v50.1-3vmw.500.0.0.469512, VMware_bootbank _scsi-fnic_1.5.0.3-1vmw.500.0.0.469512, VMware_bootbank_scsi-hpsa_5.0.0-17vmw.50, VMware_bootbank_scsi-ips_7.12.05-4vmw.500.0.0.469512, VMware_bootb ank_scsi-lpfc820_8.2.2.1-18vmw.500.0.0.469512, VMware_bootbank_scsi-megaraid-mbo x_2.20.5.1-6vmw.500.0.0.469512, VMware_bootbank_scsi-megaraid-sas_4.32-1vmw.500. 0.0.469512, VMware_bootbank_scsi-megaraid2_2.00.4-9vmw.500.0.0.469512, VMware_bo otbank_scsi-mpt2sas_06.00.00.00-5vmw.500.0.0.469512, VMware_bootbank_scsi-mptsas _4.23.01.00-5vmw.500.0.0.469512, VMware_bootbank_scsi-mptspi_4.23.01.00-5vmw.500 .0.0.469512, VMware_bootbank_scsi-qla2xxx_901.k1.1-14vmw.500.0.0.469512, VMware_ bootbank_scsi-qla4xxx_5.01.03.2-3vmw.500.0.0.469512, VMware_bootbank_uhci-usb-uh ci_1.0-3vmw.500.0.0.469512

Dell Management Center Plugin for vCenter Overview/Install Guide


Dell introduced this plugin awhile back, it's actually a Virtual Appliance you import into vCenter.  The plugin inside vCenter is actually an Adobe Flex (Flash-based) app that gets embedded into your vSphere Client, so ensure you have Flash installed on the machine(s) you wish to use this plugin from.

Overview of Features

  • Update BIOS/Firmware on Dell ESXi hosts from vCenter
  • Checks for updates automatically and alerts you when there are updates available
  • Can leverage an established Dell Repository to avoid data duplication--if you are a heavy Dell shop you should know what this is
  • New vCenter Alarms for Dell Hardware
    • These Alarms can even trigger hosts to go into maintence mode to evacuate VMs from that particular host if the hardware event is critical (in a DRS enabled cluster of course)
  • Supports Dell's Proactive Systems Management
    • Works without (the God-awful) SilverStreak to automatically create support cases with Dell when issues arise
  • View Warranty information of your Dell hosts
    • Allows you to configure a proxy, if your environment requires one
  • Bare metal deployment of ESX/ESXi servers
    • This leverages Dell Lifecycle Controllers and iDRACs to provision Dell servers somewhat auto-magically.
    • First you create a Hardware Profile from a Reference Server--(configures boot order, BIOS settings, iDRAC settings, RAID config)
    • Then you create a Hypervisor profile--You point at an ISO, and configure the vCenter, destination container (data center or cluster), and even a host profile for you enterprise plus users.
    • Note you can "white-list" service tags so only those hosts you define can be used by the plugin to deploy against.
  • OSMA Launcher
    • So you can launch directly to your OSMA web console to connect to an OSMA agent on an ESXi host
  • Appliance Upgradable
    • Does not require replacement by deploying a new OVF when a new version comes out


    WhatsUp: Dell Server Hardware Status Monitor

    WhatsUp v14 added some nice new active monitors to monitor fans, power supply and temperature for Dell Servers.  However that doesn’t cover everything else, Memory, CPU, Chassis Intrusion, HDD, RAID Controllers, etc.  We found the simplest way was to simply monitor for the LCD color of the Dell server.  Yes, we are sure the OID that we are looking at isn’t actually LCD color, but we like to think that it is.  The OID is actually for drsGlobalSystemStatus--which if it's not 3, then there is a problem and the LCD is amber to reflect that.  Below is how you can setup this active monitor for WhatsUp:

    First you need to configure SNMP on your DRAC, this screenshot shows the steps:

    Once you have SNMP configured on your DRAC you can setup the SNMP Active monitor in WhatsUp as follows:

    Tagged as: , No Comments

    vCenter Orchestrator Trouble: Server service fails to start – service terminated with service-specific error Incorrect function


    I was setting up a new instance of Orchestrator inside my lab and came across this issue.  the Orchestrator Server service would not start, andi nside the vCenter Orchestrator Configuration webpage, we don't have any output in the log--so we investigate the Windows logs...

    In the system log all you see is Error: The VMware vCenter Orchestrator Server service terminated with service-specific error Incorrect function..

    Poking around we come across a log file @ C:\Program Files\VMware\Infrastructure\Orchestrator\app-server\bin\wrapper.log which sheds some light on the problem:

    C:\Program Files\VMware\Infrastructure\Orchestrator\app-server\bin\wrapper.log
    1. STATUS | wrapper  | 2011/11/26 18:02:35 | --> Wrapper Started as Console
    2. STATUS | wrapper  | 2011/11/26 18:02:35 | Java Service Wrapper Professional Edition 64-bit 3.3.9
    3. STATUS | wrapper  | 2011/11/26 18:02:35 |   Copyright (C) 1999-2009 Tanuki Software, Ltd.  All Rights Reserved.
    4. STATUS | wrapper  | 2011/11/26 18:02:35 |     http://wrapper.tanukisoftware.org
    5. STATUS | wrapper  | 2011/11/26 18:02:35 |   Licensed to VMware Global, Inc. for VMware vCenter Orchestrator
    6. STATUS | wrapper  | 2011/11/26 18:02:35 |
    7. STATUS | wrapper  | 2011/11/26 18:02:35 | Launching a JVM...
    8. INFO   | jvm 1    | 2011/11/26 18:02:35 | Error occurred during initialization of VM
    9. INFO   | jvm 1    | 2011/11/26 18:02:35 | Could not reserve enough space for object heap
    10. ERROR  | wrapper  | 2011/11/26 18:02:35 | JVM exited while loading the application.
    11. STATUS | wrapper  | 2011/11/26 18:02:40 | Launching a JVM...
    12. INFO   | jvm 2    | 2011/11/26 18:02:40 | Error occurred during initialization of VM
    13. INFO   | jvm 2    | 2011/11/26 18:02:40 | Could not reserve enough space for object heap
    14. ERROR  | wrapper  | 2011/11/26 18:02:40 | JVM exited while loading the application.
    15. STATUS | wrapper  | 2011/11/26 18:02:45 | Launching a JVM...
    16. INFO   | jvm 3    | 2011/11/26 18:02:45 | Error occurred during initialization of VM
    17. INFO   | jvm 3    | 2011/11/26 18:02:45 | Could not reserve enough space for object heap
    18. ERROR  | wrapper  | 2011/11/26 18:02:45 | JVM exited while loading the application.
    19. STATUS | wrapper  | 2011/11/26 18:02:50 | Launching a JVM...
    20. INFO   | jvm 4    | 2011/11/26 18:02:57 | Error occurred during initialization of VM
    21. INFO   | jvm 4    | 2011/11/26 18:02:57 | Could not reserve enough space for object heap
    22. ERROR  | wrapper  | 2011/11/26 18:02:57 | JVM exited while loading the application.
    23. STATUS | wrapper  | 2011/11/26 18:03:01 | Launching a JVM...
    24. INFO   | jvm 5    | 2011/11/26 18:03:01 | Error occurred during initialization of VM
    25. INFO   | jvm 5    | 2011/11/26 18:03:01 | Could not reserve enough space for object heap
    26. ERROR  | wrapper  | 2011/11/26 18:03:01 | JVM exited while loading the application.
    27. FATAL  | wrapper  | 2011/11/26 18:03:02 | There were 5 failed launches in a row, each lasting less than 300 seconds.  Giving up.
    28. FATAL  | wrapper  | 2011/11/26 18:03:02 |   There may be a configuration problem: please check the logs.
    29. STATUS | wrapper  | 2011/11/26 18:03:02 |

    Your first thought might be disk space, did a log run away? No that isn't the case--Java Heap refers to memory, looking inside the wrapper.conf from the command above we find more information.

    C:\Program Files\VMware\Infrastructure\Orchestrator\app-server\bin\wrapper.conf
    1. # Initial Java Heap Size (in MB)
    2. wrapper.java.initmemory=2048
    4. # Maximum Java Heap Size (in MB)
    5. wrapper.java.maxmemory=2048

    Java has to allocate 2Gb of RAM on startup. My VM only had 1.5Gb, that looks like the issue--this is what you get for ignoring the Minimum System Requirements (assuming your running Orchestrator on same server as your vCenter).  Increase the RAM on your VM and this error should be gone. vCenter Server should have a minimum of 3Gb of RAM.