EMC Virtual Storage Integrator (VSI) 3.0.1.5 the, what I hope to be, easy explanation

Summary:
Everywhere I read and hear “oh it’s easy”.  Yes, it is, but it is so poorly implemented and explained.  The reason is that you need two pieces to make it work, Solutions Enabler and VSI itself.  Here are the steps in nutshell:
Recommended Install Steps:
  1. Install Solutions Enabler on Windows Server (Linux Server and running this locally is also an option)
    • Can be a VM, but there are some caveats if your ESX hosts connect to vMax/Symmetrix arrays.
    • Choose Complete and leave the rest of options default on install.
    • Open a cmd prompt to the install directory. (Normally C:\Program Files\EMC\SYMCLI\BIN)
    • Run the following commands:
      • stordaemon install storsrvd –autostart
      • stordaemon start storsrvd
        • The VSI 3.1.0 install guide has the above command backwards.
  2. Install Solutions Enabler on a system that will be running the vSphere Client (normally your desktop/laptop)
    • Choose Complete and leave the rest of options default on install.
  3. Install VSI on the same system running the vSphere Client and Solutions Enabler
  4. Open the vSphere Client and go to management –> EMC Storage
  5. In the Remote Server Name box, type in the name of the Windows server running Solutions Enabler in Step 1.  If all steps have been performed correctly up to this point clicking the Test Connection link will result in a ‘Passed’ as pictured below:
    • vSphereEMCVSI-Settings
  6. Next click on the array tab and plug in IP’s or DNS names for Clariion array SP’s and a username/password w/ proper rights that are appropriate.
    • Username and Password must be made on the SAN side.
    • Read-only (Monitoring) is suggested, but full admin is possible if you want to create/delete lun’s from the vSphere client.
    • Celerra is the same, but only one IP or name of Celerra Control Station is required.
    • EMC-VSI-ArrayConfig
  7. If you have Symmetrix/vMax arrays connected to your vmware environment, the version described here requires that a single LUN, for every array that your vmware environment is connected to, must be mapped to the Solutions Enabler server created in Step 1.
    • This majorly sucks if your Solutions Enabler server is a VM, this means mapping an RDM to your VM, but on a bigger scale, mapping to every ESX host that your VM is hosted on.
    • Directly from the installation guide:
      • Symmetrix arrays can only be discovered in-band; this means that at least one LUN must be accessible for that Symmetrix array.

View 4.5 Post-Synchronization Script not running?

Summary:

I have a post synchronization and power-off script that clears some McAfee reg keys, starts App-V services, and other misc. stuff (workaround from 4.0.1) that I’ve ported over to 4.5.  Essentially, I noticed when logging into my View 4.5 systems, this script was not being run for some reason.  Below is what I was seeing in my View pool settings:

ViewPostSyncGuestCustom

Notice the Yen symbols?  This likely happened when I recreated these pools and I was typing in “Romaji” instead of “US” on my Mac.  The Yen symbol is the equivalent of backslash(‘\’) on the keyboard and translates fine for most applications, not for View 4.5 apparently though.  This is likely a rare occurrence in which my Japa-cheesyness isn’t so cool.

Resolution:

Replace the Yen symbol w/ a good ‘ol US backslash(‘\’) as picture below:

ViewPostSyncGuestCustomAfter

The good news is that after making this change any new VM’s that spin-up will run the batch files correctly.

API version '4' for vCenter Server '<vCenterName>' is not supported.

Summary:
This helpful message appears when you attempt to use a VUM 4.1 PowerCLI cmdlet against a 4.0 vCenter / Update Manager version.
Resolution:
Uninstall VUM 4.1 PowerCLI and install VUM 4.0U1 PowerCLI.
Takeaway:
Read the release notes and hope that VMWare has right download link posted on their site, which as of this posting is wrong.  The link posted above is correct.
vmwaresite