Business Collaboration Dont over discover Discover Rationalize Business

• Business Collaboration • Don’t over discover Discover Rationalize • Business Impact • Large Scale • Day 1 requirements • On demand Validate Manage • Obtain Value • Future Planning

What I have Discovery; not inventory Finding what you need Discovery leads to testing/validation Telemetry Dashboard can help usage Is discovery optional? What I need

Discovery Collaborate Telemetry is a Starting Point Not an end-to-end discovery solution Business areas must be engaged (Rationalization) Discovery drives Testing Drive Testing Get Started Discovery = “looking for solutions” Discovery <> “looking for problems” 1 st Step: Telemetry Infrastructure Must be implemented/configured TD Infrastructure lives beyond Discovery

Manage Change

What does “Compatibility” mean? How to you prove it’s compatible? An app/document has… You do your work …no bugs… The only ones who how to do the work are …in the environment you want… which stop you from getting work done the people who do the work User testing = “The only test that matters”

UAT Environment VDI provides reach, scale, reuse Goals: Make it Production-like Make it easy* Where/How to test? Requires administration, infrastructure Remove testing barriers Increase participation * The hardest part of UAT… …is getting people to UAT

Testing Piloing ” ! t e N y t e f a S Click-to-Run and Side-by-Side (Sx. S) h t Sx. S i w Office 365 Pro. Plus can run with other versions w o Eliminates impact (and fear) of change “N What UAT Environment? Side-by-Side unlocks new testing scenarios All the benefits of testing in production… …without all the risk! Telemetry Dashboard can Validate Pilot Data provides reassurance IT can offer more than just deployment status Dashboard Testing “Barrier free UAT!” Reassurance

Critical? Track Only Test critical solutions What’s in your Disaster Recovery Plan? C 2 R allows “No Fear” Testing driven by Discovery Be bold!is. Save time/money Just-in-time discovery/validation Telemetry Dashboard = Reactive Data Measure Just Do it! Shows discovery “what happened” Moves & validation from pre-deployment to Not always indicative of “Does it work? For me? ” deployment phase Use TD to pinpoint issues & measure impact

“I don’t have time to test” Previous versions of Office transition state Un-side-by-siding

To prevent most file association issues: Office 2007: http: //support. microsoft. com/KB/2596620 http: //support. microsoft. com/KB/2767916 Office 2010: Previous versions of Office Service Pack 2

Office 365 Pro. Plus

Office Deployment Tool

Deployment

Option Install from “here” Details Use Office Deployment Tool (setup. exe) Deploy like any other software Command line: Setup. exe /configure here. xml Deploy the entire source Leverage existing deployment methods No Source. Path attribute defined in the config XML

Option Details Use Office Deployment Tool (setup. exe) Install from “there” Command line: Setup. exe /configure there. xml Separates setup. exe (1 MB) from source files (1 GB) Facilitates “pre-staging” of source files Source. Path attribute is defined Allows source files to be updated independent of deployment package

Option Details Use Office Deployment Tool (setup. exe) Command line: Setup. exe /configure everywhere. xml Install from cloud “Outsources” distribution infrastructure Great for internet connected clients, branch offices No Source. Path attribute defined in config XML Always deploys latest build

Do you have an adoption plan? Technology is easy; Human behavior is hard People learn differently; have different motivations Training? One approach – Identify/train Office “champions” Champions become your advocates; drive demand Resources http: //success. office. com http: //aka. ms/officetraining

Cumulative calculated Manage change automation

Internal or Cloud source? Outsource your update infrastructure Multiple languages can lead to lots of content Binary delta replication reduces bandwidth needs Network infrastructure can impact decision Automatic Updates or controlled updates? Update management – can it be justified? Hybrid approaches provide flexibility/control Group Policy provides granular control Eg, automatically have “some” people get automatic updates

Updates

http: //myignite. microsoft. com