by Richard Jones | November 30, 2010 | Comments Off on Back on the Blogging Network
I guess one may call it a comedy of errors. Last August, I upgraded my Gartner laptop to Windows 7 from Windows XP. I like Windows 7, but during the transition, the VPN client that we Gartner Analysts use didn’t get configured correctly. Now fixing it requires being connected to the internal Gartner network so that IT can manage my machine without the VPN client loaded. Here’s the catch 22 – I work from a home office, so in order to fix my issue, I had to schedule time to travel to a Gartner office when I could meet with someone from IT to re-install and configure the client.
Travel travel travel – and just plain being busy made weeks turn into months and finally just before the US Thanksgiving break, I got a chance to meet up with IT in a Gartner office to get the reconfiguration done. Yahoo! Now I am able to get back into the blogging network (sorry for the silence so long.)
This is one of those examples when a heavy travel schedule prevented me from getting to needed maintenance, and things just had to wait.
Read Complimentary Relevant Research
100 Data and Analytics Predictions Through 2021
Over the next few years, data and analytics programs will become even more mission-critical throughout the business and across industries....
View Relevant Webinars
Will the Cloud Save Me Money? Or Am I About to Waste a Lot?
The cloud is often seen as a great way of saving money, but there is an emerging trend of organizations that cannot prove a ROI. We examine...
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.