Virtually Jason

I've been working on an environment audit for one of my customers (expect to see some of those scripts popping up in the not-too-distant future).  In addition to auditing ESXi host configurations, I've been looking at their HP C7000 Chassis configurations and comparing them against enterprise standards.  Since there are a lot of chassis in this environment, I've been leveraging scripts to collect data via plink. It's not always easy to parse data from an SSH session into PowerShell objects, but HP gave us a great tool in their CLI (way better than adjusting column size, which is what I was looking for when I came across this).  It's already  well documented , but it saved me so much time that I figured that it was worth mentioning anyway... the HP CLI commands support this great option: -output=script2.  There's actually a couple of "script#" options, but I'm particularly fond of #2.  So, what's it do?  Well, it turns this style of human frie

I've been using the HTML 5 web client for the past couple of weeks now, and I wanted to post my impressions so far.  It's obviously not feature-complete yet, but most of the "day to day" functions are there.  I'm really impressed by what I've seen, it's snappy and intuitive; everything that we wanted the old web client to be. It kindof reminds me of the whole Windows 8 to 8.1 to 10 progression.  In Windows 8, Microsoft introduced a lot of new ideas... but they really changed the way people worked and they did so in ways people didn't want.  It was too new.  In 8.1, they scaled it back and then in 10 they scaled it back again, until I feel like Windows 10 has a nice balance of new features/philosophy while still respecting the way that we do our work. The Flash Client was too new; it was Windows 8.  We had completely new work flows that felt awkward and alien.  They weren't bad, but they didn't respect the way that we had all learnt to work.