I'm going to strive to keep this short since I'm sure that most readers who've been drawn to this post by the inclusion of "iPad" in the title have a long line of stories and reviews to read about Apple's newest device; there's clearly no shortage.
Some of you may have seen me tweeting recently about a little experiment that I have going on where I'm using a small PC (perhaps we can call it a netbook, but that's a semantics issue) — the Nokia Booklet 3G — as my primary computing device outside of the office.
Following my colleague Andrew Jaquith's eloquent post, I thought it fitting that I add a post about changes in coverage and how they'll affect me. Before I do, however, I want to lend my voice to wish Natalie all the best in her new endeavor, it will be fun to run into her on the "opposite side of the table" in briefings in the future, and I'm thrilled that I'll be able to maintain professional ties with Natalie as she moves into the next phase of her career.
So, what's going to change for me and my coverage at Forrester as a result of Natalie's move? Well, as some of you know due to some communication I had with you last week, as a result of coverage shifting around, I'm very happy to announce that I am taking over Enterprise Mobile Device research for the Infrastructure and Operations team at Forrester to provide Ben Gray with some bandwidth to take on some of Natalie's virtualization coverage, details of which I'll leave best shared by Ben.
Here at Forrester, we spend a good deal of time talking about the future of the mobile enterprise. Whether that's an emerging standard for a faster, more capable mobile network or a future of all-out mobile connectivity with applications and devices ready to tap into it.
I recently took part in my first Wi-Fi enabled flight (AA 387 STL — SAN) and, in addition to raving about the experience, I found it one of the better ways to make productive use of otherwise lost time. While the speed was reasonable, and better than I'd expected, there was a separate tier of experience that I encountered as a result of being a mobile user accessing Forrester's services and applications from 30,000 feet.
The answer, based on research recently completed by Doug Washburn and I, entirely. With the help of Christine Perkett, President and founder of PerkettPR — an organization of all virtual employees — we studied the IT infrastructure, productivity, and green benefits of PerkettPR's last ten years as an organization reliant on geographically scattered workers and reliable remote access to systems and information.
True to the topic's virtual focus, the entire idea began with a virtual exchange. I was initially intrigued by a Tweet that Christine submitted to her 12,000+ user following on Twitter, pondering the green effects and savings her company had garnered over the past ten years as a virtual organization.
Some of the findings in the document center on what seem, in Perkett's opinion, like common sense, but aren't always readily apparent to workers or to organizations:
I've put together another video blog this time getting into the detail on the various models I see for branch office server and infrastructure consolidation, based on the findings of my recent TechRadar.
Forrester IT Operations Blog Branch Office Consolidation
In the first IT Infrastructure & Operations video podcast, I discuss trends in branch office consolidation as presented at Forrester's recent IT Forum US event, with a lovely backdrop of the Las Vegas strip. Read the accompanying report here.
Writing on technologies for the branch office often times places me across the domains of mobility and non-mobile network infrastructure. Increasingly, in client inquiry calls, the question of "how do I optimize my branch office infrastructure" comes up and takes many forms. I'll attempt to address the most common of these branch office optimization scenarios in a series of posts. This being the first of such posts, I'll tackle one of the more basic optimization questions; connectivity for the small branch office.
Last week, Blue Coat gathered analysts in New York City for its Application Delivery Network Briefing Event to showcase its newest offerings, some of which are not yet released, and give the analyst community an update on where things stand following the company’s acquisition of Packeteer, completed in June of 2008.
Long story short? The vendors’ roadmaps have merged and it seems Blue Coat is doing a solid job of integrating the visibility and deep traffic inspection messages of the PacketShaper products with its caching, optimization, and security messages. Prior to the Packeteer acquisition, while Blue Coat offered a solid secure gateway and caching story, the true level of traffic visibility and optimization it could provide was limited.
Interesting for IT Operations and Security Professionals, the two product lines remain separate, though branding will merge in the second half of 2009. This could create either a dilemma or an opportunity for Blue Coat in the current economy when companies are being forced to show faster ROI with less investment upfront. The PacketShaper/ProxySG product split means that an organization can adopt one element of the solution at a time, dialing up investment as need dictates.