290 likes | 564 Views
Getting Started with Exchange Server 2007. Simple Installation, Setup and Administration Scenarios. Johann Kruse: 2 nd November 2006. Key Takeaways and Objectives. Exchange Server 2007 deployment is simple , flexible , and intuitive !!! Introduce core Exchange Server 2007 concepts
E N D
Getting Started with Exchange Server 2007 Simple Installation, Setup and Administration Scenarios Johann Kruse: 2nd November 2006
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 • Unified Messaging configuration
Exchange 2007 Exchange 2007 Edge Server Intranet DMZ Windows Server Exchange 2007 Windows Server Client Access HubTransport Exchange 2007 Edge Transport Unified Messaging Mailbox Server Roles
Exchange 2007 Windows 2003 R2 Windows 2003 SP1 GC/DC GC/DC MB,CA,HT,UM Roles Exchange 2007 and the AD AD Site • 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
Windows 2003 SP1/R2 GC Exchange 2007 Exchange 2007 Exchange 2007 Exchange 2007 Exchange 2007 Mailbox Server Hub Transport Server Hub Transport Server Client Access Server Client Access Server Server Roles and AD Sites AD Site AD Site Windows 2003 SP1/R2 GC Exchange 2007 Mailbox Server
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
PrepareX Parameters • PrepareAD – Prepares for Exchange 2007 installations • PrepareLegacyExchangePermissions – Grants permission the EES and EDS groups permission to the ExchangeInfo property set • PrepareSchema – Extends the Exchange 2007 schema • PrepareDomain – Creates local domain group and grants permissions to the EDS and EES groups • Required for multi-domain/multi-AD site topologies
Hardware Requirements • 64-bit is required for production servers • No in-place upgrade from Exchange 2003 • 64-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 onWindows 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 Server Interoperability Requirements • Exchange Organisation 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
Demo Typical Exchange 2007 Setup Walkthrough
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
“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 0X80004002 (16386): No interface.
Getting StartedExchange 2007 setup on the console • Simple setups have simple usage • Usage is complete and available on the command line • A wealth of options = flexibility
Demo Exchange 2007 Setup on the Command Line
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> Cmssharedstorage Cmsdatapath=<datapath>
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
Automated Setup Summary • Easy to use • Simple usage for simple setups • Simple answer file, if you decide 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 • Fully integrated with Exchange Management Shell scripting concepts for “lights out” deployments
Exchange 2007 Unified Messaging Architecture and setup
Exchange Server 2007 UM Problems being addressed • Voice and e-mail exist as separate inboxes hosted on separate servers accessed through the desktop for e-mail and the phone for voicemail • Fax messages come to stand-alone fax machines and require personnel to monitor • Users and administrators have to manage their communications from multiple locations with multiple sets of tools
Unified Messaging Feature Summary • Voice Messaging and Fax Services • Call Answering – a seamless part of Exchange and completely integrated with Microsoft Office Outlook 2007 and Outlook Web Access (no touching the desktop required) • Fax Receiving – Direct to your inbox just like voicemails. • Outlook Voice Access – You can call in and hear everything in your inbox. Touch-tone or hands free speech recognition based! • E-mail, voice mail, calendar, contacts, corporate directory • Phone in, have your e-mail read to you, act on it, listen to your calendar, tell your next appointment you will be late, call one of your Outlook business contacts, listen to your voicemail, call someone in the corporate directory. All hands free. • Auto Attendant • Creates a professional automated receptionist to route calls to departments or employees at your company • Also speech recognition enabled!
Exchange Serve 2007 UM Architecture • Simple to deploy and manage • Consistent with Exchange Server 2007 site consolidation • Reasonable price point • Right set of features rather than all features • Highly reliable
PBX Connectivity Using VoIPGateways Circuit-switched telephony protocols Mailbox Server Phone company’s Central Office VoIP Gateway Hub Transport Server Unified Messaging Server Traditional PBX External phone Internal phone Active Directory SIP/RTP/T38 protocols
IP PBX Connectivity Mailbox Server Phone company’s Central Office Hub Transport Server Unified Messaging Server IP PBX External phone Internal phone Active Directory SIP/RTP/T38 protocols
Demo Unified Messaging Configuration
Takeaway 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