Wednesday, August 01, 2012

Office knows what you are doing, whether you've been... Office Telemetry for Office 2003, 2007, 2010, 2013...

Office IT Pro Blog - Introducing Office Telemetry in the new Office

"On July 16th 2012, we unveiled the next version of Office. One of the powerful features for IT Pros in the new Office is Office Telemetry, which we built to make IT Pros’ Office upgrade experience easier.

In a forthcoming series of blog postings, we will talk about Office Telemetry concepts and features designed to reduce migration costs.

Modern Office compatibility process

We started our work with one simple goal: Minimize the time IT Pros need to spend on Office compatibility before they deploy the new Office. (Past Office compatibility testing processes typically took more than a year for manual testing millions of documents and hundreds of add-ins). The new Office is designed to be compatible with existing Office documents, add-ins, and custom solutions. We know, however, that IT Pros still need to verify that the new Office will work with their users’ documents and add-ins with no compatibility and performance issues.
For the new Office, we studied the common issues that complicate deployments and developed a new Office compatibility approach:

Step 1 Collect data: Start with collecting actual document and solution usage and metadata from end users.
Step 2 Analyze data: Identify the business-critical documents and add-ins that need to be ready on the first day of Office deployment.
Step 3 Start a pilot deployment, focusing on the most critical solutions: Focus on testing documents and add-ins that are necessary to run the business. Proactively monitor how the business-critical documents and add-ins are behaving when they are tested. Quickly figure out resolutions to issues.
Step 4 Deploy Office and continue monitoring your solutions: Deploy the new Office, and look for cases of errors or poor performance to be addressed.
Identifying the truly important documents and add-ins and monitoring how well they run in the latest version of Office sounds like a gargantuan task. The new Office can gather this information for you automatically.

Sound promising? How can you know what is actually being used and how well it’s performing?

To help you answer these questions, we built Office Telemetry Dashboard. This is the tool that will give you access to the information that is necessary to follow the new compatibility approach.

What is Office Telemetry Dashboard?

Office Telemetry Dashboard is an Excel-based solution designed for IT Pros to view metrics of how frequently end users open specific Office documents, what issues that end users experience, and detailed information about their deployments, hardware, and documents. The aggregated telemetry data is collected from end users' PCs. Let's quickly take look at how you can view the data. As you can see in the screenshot below, the dashboard presents your company’s most frequently used documents and add-ins. ...


How is the data collected?

Data behind the dashboard is collected from end users with telemetry capabilities integrated in the new Office. It collects various kinds of events that are happening with Office client installations.

Also, IT pros can deploy the Telemetry Agent to Office 2003, 2007 and 2010. For these versions of Office, Telemetry Agent collects inventory information on actively used documents and registered add-ins so that IT pros can see the most frequently used documents and add-ins before deploying the new Office. This information is essential for scoping your enterprise’s business-critical documents and add-ins.



As a wanna-be IT guy, I think this is awesome. I love telemetry in our app's, the ability to easily gather usage stats, information, errors, etc from our applications. There's nothing worse than having to send out an email, "Are you guys using feature X/Y/Z?" "How often do you..." yada, yada. because you know the kind of data you're going to get (if you get any at all). Having runtime telemetry in our apps should be a fundamental requirement.

As a user this kind of freaks me out. lol. Knowing that my IT is getting this level of data from me, including file names, etc just seems a little, tiny bit icky. Yeah, I know they are already scanning my work HD, network shares, etc and know all about these documents already, but still.

I believe the key is clean, open, concise and transparent communication. If this telemetry agent just auto-magically appeared on my system, without communication or notice, I'd go out of my way to kill it. But if I were communicated with first, if the reason, usage and intent were clearly and openly communicated to me, then I'd likely let it live.

So remember, runtime telemetry and analysis is awesome, you MUST use it with care and clearly communicate with those provide the data. It's a matter of trust.

No comments: