MSG212 Getting Started With Microsoft Exchange Server 2007: Simple Installation, Setup and Administration Scenarios

Key Takeaways and Objectives Exchange Server 2007 deployment is simple, flexible, and intuitive!!! Introduce core Exchange Server 2007 concepts Provide understanding of deployment requirements Deployments can be fully automated

Agenda Exchange Server 2007 Server Roles Exchange Server 2007 Requirements Topology requirements Server requirements Feature requirements Exchange Server 2007 Setup Automating Exchange Server 2007 Setup

DMZ Exchange 2007 Edge Server Windows Server Exchange 2007 Edge Transport Windows Server Exchange 2007 ClientAccess Hub Transport Mailbox UnifiedMessaging Intranet Exchange 2007 Server Roles

Exchange 2007 and the AD GC/DC Windows 2003 R2 AD Site MB,CA,HT,UM Roles Exchange 2007 GC/DC Windows 2003 SP1 Domain Functional Level All domains have to be "Windows 2000 Server native" or higher GCs/DCs Windows 2003 SP1 or higher All FSMO role holders and GCs need to run Windows 2003 SP1

Server Roles and AD Sites AD Site Mailbox Server Exchange 2007 GC Windows 2003 SP1/R2 Client Access Server Exchange 2007 Hub Transport Server Exchange 2007 AD Site Mailbox Server Exchange 2007 GC Windows 2003 SP1/R2 Client Access Server Exchange 2007 Hub Transport Server Exchange 2007

Required Permissions Extend the Schema for Exchange 2007 Setup.COM /PrepareSchema (1 time operation) Schema Administrators Create Exchange Organization Setup.COM /PrepareAD (1 time operation) Enterprise Administrators Prepare the Domain for Exchange 2007 Setup.COM /PrepareDomain Domain Administrators Install Server Exchange Organization or Exchange Server Permissions Local Administrators

Hardware Requirements 64-bit is required for production servers No in-place upgrade from Exchange bit Xeon processor or Pentiums with EM64T (NOT the Itanium or IA64) Any of the AMD64 processors (Opteron, Athlon and Turion) 32-bit is available for evaluation, but is not supported in production System and Exchange partitions have to be formatted with NTFS file system

Windows OS Configuration Exchange 2007 can be installed on Windows 2003 SP1 or Windows 2003 R2 Windows Components NNTP Service must not be installed SMTP Service does not have to be installed. (It will be disabled during Setup if found.) Mailbox and Client Access Roles require the World Wide Web Service Additional Components.NET Framework 2.0* Microsoft Management Console (MMC) 3.0* Windows PowerShell 1.0 (aka Monad) *These are included in Windows Server 2003 R2

Exchange Organization needs to be in Exchange Native Mode Routing Group Connector is required between Exchange Server 2003 and Exchange Server 2007 Exchange 2003 Front-ends cannot talk to Exchange Server 2007 Mailbox Server Roles Verify Recipients meet new validation requirements Exchange Server Interoperability Requirements

Feature Requirements Typical Installation - Smart Defaults (Mailbox, Client Access, and Hub Transport Roles) Mailboxes are ready to be created Users can login with OWA or Outlook Users can send mail within the Exchange Organization Unified Messaging Role Edge Server Role

Typical Exchange 2007 Setup Walkthrough

Automating Exchange 2007 Setup

Automating Exchange 2007 setup “The way it was” – a brief reminder Getting started with Exchange 2007 scripted setup Intro to the Exchange 2007 answer file Understanding success or failure of your scripted setup Putting it all together – extended configuration and “lights out” deployments

Hidden Agenda What I want you to remember about scripting Exchange 2007 setup: Easy to use Trustworthy Supported Everywhere Dovetail: To combine or interlock into a unified whole Exchange 2007 scripted setup combines seamlessly with other Exchange 2007 scripting concepts Dovetail

“The way it was” Exchange 2000/2003 unattend mode All about the unattend file Specific format created by setup itself Restrictions on allowed setup actions First server in an org: not supported Clustered server installs: not supported Installs in legacy environment (5.5): not supported Exchange 2000/2003 setup.exe return codes No meaningful return code Uneasy feeling from the end of the log… [15:20:02] !!!!!!!!!!Setup completed successfully! [15:20:03] CComBOIFacesFactory::QueryInterface (f:\tisp2\admin\src\udog\bo\bofactory.cxx:54) Error code 0X (16386): No interface. Error code 0X (16386): No interface.

Getting Started Exchange 2007 setup on the console Simple setups have simple usage Usage is complete and available on the command line A wealth of options = flexibility

Exchange 2007 Setup on the Command Line

Intro to the Exchange 2007 Answer File [gfn_mid microsoft exchange\gfn_mid microsoft exchange system management tools] gfn_pid stockprop suitebaseline=0 gfn_pid stockprop scenariobaseline=0 gfn_pid stockprop shared=0 gfn_pid stockprop required=0 gfn_pid stockprop hidden=0 gfn_pid microsoft exchange install type= gfn_pid microsoft exchange organization name= {CDC92A5E-3E10-448C-A609-9E0D41943F00}={599AD9B5-707B-4CC1-A4E A619F2B}= gfn_pid microsoft exchange 5.5 server name (in site)= gfn_pid microsoft exchange admin group= {0EF92510-DB5E-45F3-8F02-815CE7B79A06}= gfn_pid microsoft exchange ag containing routing group= gfn_pid microsoft exchange routing group= gfn_pid microsoft exchange accept licensing= gfn_pid microsoft exchange show custom actions=0 gfn_pid microsoft exchange show licensing=0 {907EA70F-F59B-424F-A422-C358C1F0E55F}={ }{E03A1AEB-BAB5-424C-ABAD-EBA67BE1E358}={ } gfn_pid microsoft exchange use specific mpc=0 gfn_pid microsoft exchange mpc value= {27AD2AB2-DA F5496A039CA}=0{862C EE CEC-F6687CA89593}=0InstallActionInteger=61953

Intro to the Exchange 2007 Answer File What it looks like Suspiciously like a simple text file Format is parameter=value; or simply parameter for boolean params How to create one Notepad Why you might need an answer file Chances are you don’t Used for advanced setup parameters, like cluster or Edge Transport role settings Consider the “many clusters” scenario Cmsname=<name>Cmsipaddress=<ipaddress>CmssharedstorageCmsdatapath=<datapath>

Understanding success or failure Learning to trust setup Simple return codes 0 for success 1 for failure The right data in the log ExchangeSetup.log, found in the ExchangeSetupLogs directory of your system drive Errors and Warnings are uniformly annotated Success/Failure messages are unambiguous [5/25/2006 3:32:05 PM] [0] The Microsoft Exchange Server setup operation completed successfully. [5/25/2006 3:32:05 PM] [0] End of Setup

Putting it all together Exchange 2007 setup can be scripted in any and every scenario First server install? Supported Cluster install? Supported Uninstall, Add/Remove, RecoverServer? Supported “Lights out” deployment: end-to-end scripted installation and configuration Dovetail Where Exchange setup ends, Exchange Management Shell begins…

Exchange 2007 “lights out” Deployment

Automated Setup Summary Easy to use Simple usage for simple setups Simple answer file, if you need to use it Trustworthy Success or failure at the command line The right data in the log Supported Everywhere Every install action, from /prepareAD to cluster install All modes of setup Dovetails powerfully with Exchange Management Shell scripting concepts for “lights out” deployments

Takeaway Exchange Server 2007 deployment is simple, flexible, and intuitive!!! Exchange Server 2007 built on Server Roles Windows AD only needs to be upgraded Deployments can be fully automated

Register for the Microsoft Exchange Server 2007 Public Beta! Register for the Microsoft Exchange Server 2007 Public Beta! Sign-Up for Free Pre-Launch E-Learning Sign-Up for Free Pre-Launch E-Learning Win a Trip to the Exchange Server 2007 Launch! Submit your line of Windows PowerShell script to: Win a Trip to the Exchange Server 2007 Launch! Submit your line of Windows PowerShell script to: /default.mspx /default.mspx What’s Next?

Resources Technical Chats and Webcasts Microsoft Learning and Certification MSDN & TechNet Virtual Labs Newsgroups communities/newsgroups/en-us/default.aspx Technical Community Sites User Groups

session evaluation