Quirkiness of Excel 2011 for Mac, CSV's, and Powershell 3.0 import-csv

Work on Windows or a Mac, don't cross the streams unless you're up against Gozer.

I made a CSV file using Excel 2011 for Mac w/ that looked something like this:

HeaderName, HeaderName2, HeaderName3, HeaderName4
Meh, super.meh.local, space, heckling
Sigh, super.meh.local, space, bashing

Saving this as a "Comma Separated Values" file was my first mistake cause when I tried to import this in Powershell, I would get the following super helpful error:

import-csv : The member "super.meh.local" is already present

To boil it down, I needed to save the CSV as a "Windows Comma Separated" csv file type.  The other method was that I could have placed quotes around all comma separated values via a text editor.

vCenter Log Insight not receiving syslogs from ESXi hosts


This appears to occur under very specific circumstances. There is a KB and it is also noted Log Insight's troubleshooting section of their documentation.

Rather than regurgitate all the same information is here is the gist:
  1. Occurs when log insight services are restarted
  2. Affects ESXi 5.0.x/5.1.x when using TCP and 5.0 U1 and earlier over UDP.
  3. Does not affect 5.0 U2 and newer when using UDP.
Here is the table:

Communication ProtocolAffected ESXi Version

  • ESXi 5.0.x
  • ESXi 5.1.x
  • UDP
    • ESXi 5.0 and 5.0 U1