Showing posts from September, 2010

EMC Virtual Storage Integrator (VSI) 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: 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. 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. Install VSI on the same system running

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: 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: 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.