1. Microsoft Exchange Server 2007 SP1 Proof of Concept in a Box

2. Agenda Goals and Overview Execution Process Phase 1: Partner Sets up the POC Environment Phase 2: Customer Evaluates the Scenarios Phase 3: Partner Responds to the Customer Summary Q&A

3. Driving Successful Customer Engagements Exchange upgrade sales resources Solution Development Solution Briefing Architecture Design Session Proof of Concept Technical Decision Maker Business Decision Maker Messaging Specialists Generate Demands by Business and IT Needs Demonstrate Business Values Demonstrate Solutions & Technologies Drive Customer Trials (Hosted -> On-site) Hosted Trial On-Site POC BV Tool DemosDemos Scenario-Based Value Propositions and Resources

4. Project Goals What we are hearing: Show & Tell, POCs are the two most effective ways to accelerate opportunityShow & Tell, POCs are the two most effective ways to accelerate opportunity Continued feedback that “real value propositions” are needed to drive upgradeContinued feedback that “real value propositions” are needed to drive upgrade Many customers have just finished Exchange Server 2003* deploymentsMany customers have just finished Exchange Server 2003* deployments Project goals: Help our partners and field representatives to accelerate sales opportunities by delivering easy-to-use Proof of Concept toolkitHelp our partners and field representatives to accelerate sales opportunities by delivering easy-to-use Proof of Concept toolkit Deliver the POC in a Box to support end-to-end execution of Exchange upgrade campaign by focusing on key scenariosDeliver the POC in a Box to support end-to-end execution of Exchange upgrade campaign by focusing on key scenarios Note: Exchange 2003 mainstream support end of life coming in April 2009

5. Overview Scenario based modules Mobility and Anywhere Access Security Compliance and Governance Unified Messaging Office Communications Server 2007 R2 Integration (IM/Presence and Conferencing) What’s included Pre-configured VHD’s and Implementation Guide Customer Evaluation Guidance Documents Evaluation Completion Response Documents Architecture and Transition Recommendations Documents

6. Execution Process Field\PartnerField\Partner CustomerCustomer Transpose the customer responses into the Evaluation Completion Response Document and add a response where appropriate Complete Architecture and Transition Recommendations Document and Submit with Evaluation Completion Response Document to Customer Select Appropriate Customer for POC and explore scenarios of customer’s interests Deploy POC in customer environment using POC Implementation Guidance Approximately three to five weeks to complete Evaluates and answer questions following the Customer Evaluation Guidance Return the completed Customer Evaluation Guidance to the Partner \Field Team Approximately two weeks to complete 1 st Week 2 nd Week 3 rd Week 4 th Week 5 th Week Phase 1 Phase 2 Phase 3

7. Phase 1: Setting up the POC Environment

8. Phase 1 Steps 1 1 Customer prepares the hardware 2 2 Install the POC following Implementation Guide 3 3 Discuss integration into customer environment

9. Step 1: Customer Prepares the Hardware 1 1 Hardware What the Customer Needs One to four servers that meet configurations on next slide Windows Server 2008 EnterpriseWindows Server 2008 Enterprise Hyper-VHyper-V Both can be downloaded from http://www.microsoft.co m/virtualization/downlo ads.mspxBoth can be downloaded from http://www.microsoft.co m/virtualization/downlo ads.mspx http://www.microsoft.co m/virtualization/downlo ads.mspx http://www.microsoft.co m/virtualization/downlo ads.mspx Ability to make necessary internal and external DNS modificationsAbility to make necessary internal and external DNS modifications Minimum of two network connectionsMinimum of two network connections One on internal network and one on external networkOne on internal network and one on external network SoftwareNetwork

10. POC Host Server Configurations # Host Servers ProcessorRAMAvailable Hard Drive Space NIC 1Intel Pentium or compatible dual core 2GHz (Dual Processor Recommended) 12 GB140GBMinimum of Two NICs. 3 NICs recommended 2Intel Pentium or compatible dual core 2GHz (Dual Processor Recommended) 8 GB per Server *POCEX01 and POCOCS01 on separate servers 70GB per ServerTwo NICs per Server 3Intel Pentium or compatible dual core 2GHz 6GB per Server70GB on one server, 40GB on each of others Two NICs per Server 4Intel Pentium or compatible dual core 2GHz POCEX01 and POCOCS01 on 6GB servers Others on 4GB servers 40GB per ServerTwo NICs per Server

11. Logical POC Architecture DMZ Corporate Intranet POCEX02 Exchange 2007 Edge Server POCDC01 Active Directory Rights Management Server POCEX01 Exchange 2007 Client Access, Mailbox Hub Transport, UM POCOCS1 Office Communications Server 2007 R2 Internet Firewall POC Production Directory Server Other Production Servers Production Mail Server Production Directory Server Other Production Servers **Architecture for POC Deployment Only**

12. Step 2: Install the POC Implementation Guide Time to Complete: Approximately 1-2 Days Step by step process to configure server in customer environmentStep by step process to configure server in customer environment Step by step process for configuring customer environment to interact with POC systemStep by step process for configuring customer environment to interact with POC system Additional steps for configuring all necessary items required for features testingAdditional steps for configuring all necessary items required for features testing 2 2

13. POC Virtual Machine Configurations Guest Server Guest OSServer RolesProcessorRAMHard DriveVirtual NIC Timebomb Expiration POCDC01 Windows Server 2003 R2 Standard 64-bit Active Directory RMS 2.8GHz Pentium D (Dual Core) 2GB30 GB Dynamic Hard Disk One NIC 5/31/2010 POCEX01 Windows Server 2003 R2 Standard 64-bit Hub Transport Mailbox Client Access Unified Messaging Forefront Security for Exchange 2.8GHz Pentium D (Dual Core) 4GB30 GB Dynamic Hard Disk One NIC 5/31/2010 POCEX02 Windows Server 2003 R2 Standard 64-bit Edge Transport Forefront Security for Exchange 2.8GHz Pentium D (Dual Core) 2GB30 GB Dynamic Hard Disk Dual NICs 5/31/2010 POCOCS01 Windows Server 2003 R2 Standard 64-bit Office Communications Server 2007 R2 Enterprise 2.8GHz Pentium D (Dual Core) 4GB30 GB Dynamic Hard Disk One NIC 5/31/2010

14. POC Client Software 60 day trial version of Microsoft Office 2007 Professional is available on 60 day trial version of Microsoft Office 2007 Professional is available on http://www.microsoft.com/office http://www.microsoft.com/office 60 day trial version of Microsoft Office Communicator 2007 R2 is available on 60 day trial version of Microsoft Office Communicator 2007 R2 is available on http://www.microsoft.com/dow nloads/details.aspx?familyid=5 35637AF-D92F-41B1-BF0C- 54A526A88247&displaylang=e n http://www.microsoft.com/dow nloads/details.aspx?familyid=5 35637AF-D92F-41B1-BF0C- 54A526A88247&displaylang=e n Installers for the Microsoft Office Live Meeting 2007 Client and the Conferencing Add- in for Microsoft Office Outlook are included on DVD1

15. Step 3: Discuss Integration into Customer Environment 3 3 Discuss Sample AccountsDiscuss Sample Accounts Fifteen (15) sample accountsFifteen (15) sample accounts Pre-created for all servicesPre-created for all services Pre-populated with email and voicemailPre-populated with email and voicemail Customer can use sample accounts or create their own for truer “Day in the Life” experienceCustomer can use sample accounts or create their own for truer “Day in the Life” experience Mail flow is enabled between environments using mail contacts and DNS records End-user mail will exist on production and POC environments No PBX integration necessary

16. Phase 2: Customer evaluates the Scenarios

17. Phase 2 Steps 1 1 Partner Prepares Documents 2 2 Customer Evaluates Scenarios

18. Step 1: Partner Prepares Documents Provide only appropriate scenario items to the customer Discuss the importance of the responses in the documents Discuss the length of the document They really do not take as long as they look! 1 1

19. Step 2: Customer Evaluates the Scenarios Evaluation Guide Time to Complete: Approximately 3-5 Weeks 2 2

20. Phase 3: Responding to Your Customers

21. Phase 3 Steps 1 1 Transpose the customer feedback into the Evaluation Completion Responses Document 2 2 Architect the Solution 3 3 Deliver the documents to the client

22. Step 1: Transpose the Customer Feedback 1 1 Copy the customer responses from the Customer Evaluation Guidance documents into the corresponding Customer Evaluation Completion Responses Document Add a response to all customer feedbackAdd a response to all customer feedback Responses may include things likeResponses may include things like Third party solution to enable capabilityThird party solution to enable capability No solution for any product for capabilityNo solution for any product for capability May be an issue with way it was testedMay be an issue with way it was tested We are pleased you liked the featureWe are pleased you liked the feature EtcEtc This step is optional. Many customers prefer an in person meeting to address their feedback. 2 2 3 3 1 1

23. Customer Evaluation Completion Responses Sample Page Time to Complete: Approximately 3-5 Days

24. Step 2: Architect the Solution Select the appropriate Architecture and Transition Recommendations documents All customers should receive the Base Exchange 2007 SP1 Architecture and Transition Recommendations Select from Anywhere Access, Security, Governance and Compliance, Unified Messaging, OCS Integration Follow the provided coaching notes to complete the documents 2 2

25. Architecture and Transition Recommendations Sample Page Time to Complete: Approximately 1-2 Weeks

26. Step 3: Deliver the Documents Remove the coaching notes from the Architecture and Transition Recommendations documents Run provided macro to remove all notes with single click Meet with the client to hand off the documents in person Look at the scenario based content in the UC FastStart Guides to assist with the follow on conversations 3 3

27. What we have heard Customer reactions Customers really appreciated the hands-on evaluation more than high- level demos The POC helped the customers over the initial learning curve for both products Customers became much more confident about using the products This is a tested model for delivering a POC

28. Next Steps Start thinking about which of your accounts would be a good fit for this solution Use the POC in your customer engagements Deploy the POC internally to test the process Allow more customer experience testing with UC Hosted Trial.

29. FAQs What is the impact to the customer’s production network? Every effort has been made to minimize the impact. The changes to the production network are limited primarily to a few DNS entries and contact additions in the messaging server Do we have to install a gateway to integrate with the client’s PBX? No. All functionality for testing UM will be handled using the OCS virtual machine and communicator Can we use older version of client software instead? Yes, the end user experience will be somewhat different but Outlook 2002 or later can be used to connect to Exchange Server 2007 and Office Communicator 2007 can be used to connect to Office Communications Server 2007 R2. That being said, we strongly recommend that the new version of client software be used to fully test these scenarios How do I remove the POC from the customer environment? Simply shut down the four virtual machines and roll back the DNS modifications and contact entries Why is this better than the hosted product trials? This is a turn-key solution that allows the customers to experience what a “Day in the Life” of an Exchange 2007 administrator and user is really like. The simplified deployments and detailed content that accompanies the machines truly helps ensure a successful POC delivery and minimize risk to the POC, the customer, and our partners

30. © 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.