<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Upgrade on Evan Hoffman</title><link>https://evan.wtf/tags/upgrade/</link><description>Recent content in Upgrade on Evan Hoffman</description><generator>Hugo</generator><language>en-US</language><copyright>Evan Hoffman</copyright><lastBuildDate>Sun, 29 Sep 2013 23:43:29 +0000</lastBuildDate><atom:link href="https://evan.wtf/tags/upgrade/index.xml" rel="self" type="application/rss+xml"/><item><title>iOS 7 has ruined my life</title><link>https://evan.wtf/2013/09/29/ios-7-has-ruined-my-life/</link><pubDate>Sun, 29 Sep 2013 23:43:29 +0000</pubDate><guid>https://evan.wtf/2013/09/29/ios-7-has-ruined-my-life/</guid><description>&lt;p&gt;I was looking forward to iOS 7 for a few reasons. I was glad to be rid of the skeumorphic design elements (stupid shit like the &amp;ldquo;Notes&amp;rdquo; app looking like a yellow notepad) but also glad to get the Control Center to turn off Wifi more easily - I only need Wifi to be on when I&amp;rsquo;m in my house or my office. It&amp;rsquo;s just a battery drain elsewhere. Ideally iPhone would just do this via geofencing, and the fact that it doesn&amp;rsquo;t is beyond retarded.&lt;/p&gt;</description></item><item><title>Upgrading ESX 4.0 to ESX 4.1 with Update Manager</title><link>https://evan.wtf/2010/10/21/upgrading-esx-4-0-to-esx-4-1-with-update-manager/</link><pubDate>Thu, 21 Oct 2010 23:57:54 +0000</pubDate><guid>https://evan.wtf/2010/10/21/upgrading-esx-4-0-to-esx-4-1-with-update-manager/</guid><description>&lt;p&gt;This turned out to be so ridiculously easy I probably shouldn&amp;rsquo;t even mention it, but only because I remembered that Update Manager exists. I thought I was going to have to burn an ISO, go to the datacenter, pop the disc in, etc. But with Update Manager this is all handled remotely. Just download the files from vmware.com and upload them to your vCenter server through the client. This YouTube video by VMware walks you through the procedure:&lt;/p&gt;</description></item><item><title>The bright side of Compellent</title><link>https://evan.wtf/2010/09/22/the-bright-side-of-compellent/</link><pubDate>Wed, 22 Sep 2010 16:07:46 +0000</pubDate><guid>https://evan.wtf/2010/09/22/the-bright-side-of-compellent/</guid><description>&lt;p&gt;Since I was bemoaning Compellent&amp;rsquo;s pricing recently I figured it would be unfair of me not to highlight the upside. Their tagline is (or was when we purchased it) &amp;ldquo;The only SAN so sophisticated it&amp;rsquo;s simple.&amp;rdquo; While I can&amp;rsquo;t say whether they&amp;rsquo;re the ONLY one, the idea is definitely true. This is the first SAN I&amp;rsquo;ve ever used, and aside from the learning curve for iSCSI itself (targets, spinup delay, etc.) it&amp;rsquo;s totally simple and intuitive. Create LUNs, map them to servers. Don&amp;rsquo;t worry about things like RAID levels or hot disks. We&amp;rsquo;re into our second year with Compellent and it&amp;rsquo;s definitely lived up to its promise of simplicity.&lt;/p&gt;</description></item><item><title>Exchange 2010 and Set-ActiveSyncVirtualDirectory Identity</title><link>https://evan.wtf/2010/07/12/exchange-2010-and-set-activesyncvirtualdirectory-identity/</link><pubDate>Mon, 12 Jul 2010 14:43:21 +0000</pubDate><guid>https://evan.wtf/2010/07/12/exchange-2010-and-set-activesyncvirtualdirectory-identity/</guid><description>&lt;p&gt;I don&amp;rsquo;t really know why I put this blog up, but generally I write stuff here after I muddle through some ridiculous problem that may have ended up being easily resolved, but whose solution was hard to find. That&amp;rsquo;s definitely the case with this post. Currently I&amp;rsquo;m in the middle of moving my company&amp;rsquo;s email from Exchange 2003 to Exchange 2010. Microsoft has provided some pretty good &lt;a href="http://technet.microsoft.com/en-us/library/aa998604.aspx"&gt;documentation&lt;/a&gt; on how to do this, but they do assume a certain level of familiarity with the product. For example, I probably spent 30 minutes trying to run Exchange cmdlets in Powershell before I realized there&amp;rsquo;s a special shell just for Exchange, the Exchange Management Shell.&lt;/p&gt;</description></item></channel></rss>