Wednesday, 12 June 2013

Tools Link

Posted by at No comments:

Tuesday, 11 June 2013

Exchange 2013 Installation

Installing Exchange Server 2013



Hi all, 
Used this post for my test lab install.

Install Following
http://www.microsoft.com/en-gb/download/details.aspx?id=26604
http://www.microsoft.com/en-gb/download/details.aspx?id=30349
Ensure the account you are using is a member of Exchange Security group Delegated Setup

Exchange Server 2013 preview published , all server components can install on the newest server OS (Windows Server 2012) . If you hope to try it ,you can download it from : http://technet.microsoft.com/en-US/evalcenter/hh973395.aspx?wt.mc_id=TEC_116_1_6
    Today , I will to introduction how to installing Exchange Server 2013 preview .
    My test lab environment OS is all Windows Server 2012 datacenter RTM , forest and domain level are Windows Server 2012.
    The first phase is prepare AD , this phase need to running three commands :
     1.PrepareSchema :
      2.PrepareAD :
      3.PrepareDomain :
    When you finished AD preparation , now you will start to install Exchange Server 2013 preview . Because Exchange Server 2013 just have Mailbox and CAS roles , and Microsoft recommand first install Mailbox role .
    Now insert Exchange Server 2013 Preview image to starting install. 
    "STOP!!!!!!!"  I think you may to ask "You need to install Exchange requirements firstly".
    The answer is NO , Exchange Server 2013 more simplifying the installation process. When you start to install , you will into Check for Update ? dialog box :
    
      Check finished , will copy install file to local :
        Copy finished , will into Introduction dialog box :
    Click Next , will into License Agreement dialog box :
       Accept and click Next , will into Error Reporting dialog box :
     Select your option and click Next , will into Server Role Select dialog box , now you can select your need to installing Exchange role , Mailbox or CAS or both . By default , setup will automatically install Windows Server roles and features :
    Click Next , will into Installation Space and Location dialog box :
    Choose a location and click Next , will into Malware Protection Settings dialog box :
     Select your option and click Next , will into CEIP dialog box :
 
    Select your option and click Next will into Readiness Checks phase :
      Check if OK you can click install to start installing process , waiting some 10 minutes, install finished :
 
    Click complete , you can find Exchange Server 2013 preview shortcut in Start :
       The last , Exchange 2013 have not EMC (Exchange Management Console) mmc snap-in console , in 2013 they called EAC (Exchange Admin Center) , you can throw web browse to access , the address is : http(s)://CAS(FQDN)/ecp .
      Now you can build a test lab to testing more new features .
Posted by at No comments:

EXCHANGE 2013 ARCHITECTURE

Exchange 2013 Architecture:

Hi,

Microsoft Released Exchange 2013 which is latest release of the messaging and communications system
on the Windows operating system with the release of Exchange Server 2013, now the eighth major release of Exchange in the over 15-year history of the product, Microsoft has made significant improvements in the areas of global scalability, mobile and tablet client support, security, compliance, reliability, unified communications, and integration with SharePoint 2013 and Lync 2013.
As with Exchange Server 2010, the Exchange Server 2013 product only comes in an x64-bit version.
Exchange Server 2013 requires either Windows Server 2008 R2 or Windows Server 2012 (both x64-
bit only operating systems) to run as the core operating system.

What’s the Same Between Exchange Server 2007/2010 and Exchange Server 2013?
The core infrastructure of Exchange Server 2013 is basically the same as Exchange Server 2007 and
2010. Microsoft continues to use the Jet EDB database as the main database store. Some time ago, it
was rumored that Microsoft would rewrite Exchange to run off SQL Server; however, neither
Exchange Server 2013 nor versions coming out from Microsoft in the foreseeable future will change
the basic EDB database structure.
Exchange Server 2013 still has the concept of a Mailbox server where EDBs are stored, and where
user mailbox data resides. An Exchange server can have multiple Exchange databases running on the
system, and multiple Exchange servers can reside in an environment for both scalability as well as
redundancy.
What’s Missing in Exchange Server 2013 That Was in Previous Versions?
For administrators, the biggest change is the Exchange Management Console (EMC) is completely
gone. No more graphical user interface (GUI)–based administration; however, that doesn’t mean that
administrators are stuck with just PowerShell in the Exchange Management Shell (EMS) environment.
What Microsoft has done is expand the Exchange Control Panel (ECP) from Exchange Server 2010
into the new Exchange Administration Center (EAC).
The Exchange Administration Center allows the administrator a web-based access to everything the
administrator used EMC for before. The administrator can create and manage user mailboxes, manage
Exchange servers, manage public folders, create send and receive connectors, perform eDiscovery
tasks.
Architectural Changes in Exchange Server 2013

  • With Exchange Server 2013, Microsoft eliminated the Hub Transport role and the Unified Messaging role, so the core roles are now the Client Access server and the Mailbox server (MBX) roles. 
  • The Client Access server (CAS) no longer does data rendering; the role just focuses on authentication, redirection, and proxy. 
  • The Mailbox server role now includes Client Access protocols, Hub Transport services, mailbox databases, and Unified Messaging services.
  • Because the Client Access server role is drastically simplified to just support HTTP, HTTPS, POP,and IMAP client protocols with no requirement for session affinity between the CAS and MBX roles,Exchange Server 2013 now has better failover and the ability to do simple Level 4 load balancing.
  •  CAS and MBX servers no longer need to be geographically close to one another, whereas in the past, the two roles needed to be on the same subnet with high-speed connectivity because of the amount of data transferred between the two servers and the dependence on split roles shared between the two servers. As such, the CAS role can now be geo-centralized with MBX servers distributed to various sites in the enterprise. In addition, with the elimination of integrated components between the CAS and the MBX servers, the requirement of identical patch levels between CAS and MBX servers is no longer a dependency. Organizations can patch and update CAS and MBX servers in a pattern and manner that makes sense to the organization, greatly providing better flexibility in updating an Exchange environment, and greatly improving the uptime of Exchange. 
Architecture Benefits
Building block architecture - for all sizes orgs
Deploying a 2013 CAS enabled you to serve previous & future Exchange versions
Now Layer 4 load balancer - Session affinity no longer required - Entire session state takes place on the active copy hosting the mailbox
CAS now just a protocol proxy.
Functional Layering
CAS now just a protocol proxy
All protocols now hosted as Services on mailbox role.
Changes CAS Role
Still domain joined machine. Comprised of three components
CAS protocols- Http - IMAP - POP,SMTP,UM
Basically its an Exchange aware proxy server - Has all logic - knows where to proxy requests
CAS Array in 2013 - no mapi over tcp - only outlook anywhere - https
No need to layer 7 - designed to work with TCP affinity - layer 4
Image 1
Mailbox to be first one installed as all config is on mailbox server
  
Client Access Service runs on the mbx server, acting as endpoint for CAS protocols such as pop / imap
Transport stack and mail queue previous on hub transport run by the transport service on mailbox server
UM service runs on mbx server
Image 2 Proxying protocols - Note SMTP only for Send / Receive external
 

Benefits of no longer supporting RPC/TCP
Reliable stable model - manages network latency better.
Session always on the mailbox server
No more administrator made a change message to users.
Outlook Connectivity in 2013
1.Recieves HTTP request - AD lookup to retrieve user information / auth user
2.Active manager lookup of the mailbox GUID to identify users database location
3.Proxies request to the mailbox server
Legacy Coexistence - N-2 support - Legacy name space only required is migrating from 2007
Can proxy requests or Cross site redirect to legacy load balancer 37:11
 

Above shows legacy Proxy and cross site proxy request - no legacy name space.
Namespace simplified
Any CAS can now answer to the namespace , no requirement to load balance namespace layer 7
Example of Single Common Namespace.
 

`
Leveraging the clients ability to get multiple DNS IP addresses back for the single name space
User gets IP for VIP1 and second IP for VIP2
Sue will round robin across these, may even bounce between array - has no impact on users
Same server to service the session is no longer required because the session is only located on the mailbox
Server, so any CAS  / load balancer can service the request
CAS Front End Transport Service / Architecture
Handles in inbound and outbound SMTP traffic - NOT the same as hub transport
Does not queue mail - is stateless - is a layer7 proxy - enough routing logic inside of service to allow
Use of layer 4
Listens on 25 and 587
SMTP Receive - Protocol Agents (Not content filtering) just connection filtering recipient and sender filtering
Hub Selector - Choose which mailbox server that contains the hub transport mailbox service that it can send the message to. Via SMTP not RPC
 

From a Mailbox goes to the SMTP receive and then to SMTP to outside world.
Delivery Groups - aka where are we going to send the message to next.
AKA - DAG or AD Site or mailbox

Mailbox Server hosts the components that process, render and store Exchange data.
Includes components previously found in separate roles - mail.que
Only CAS connects directly to the Mailbox Server - All clients connect to the CAS
DAG still the same regards to 16 mailbox server - boundary for replication and DAG members can be in different sites
MAILBOX RELATED CHANGES
Managed Store -
 Store.exe as in previous version has now gone, replaced with Managed Store that’s using a worker model
Store.Service.exe controller process that’s equivalent to store.exe
Manages mounts/dismounts starts or shutdown are worker process - logs failures when store.service detects problems
Manages the life cycle of the worker processes
Store.worker proceess - One per database - RPC endpoint is database guid
Responsible for block mode replication for passive database
Reads against DB, writes to log stream, ESE cache
Replication Service - Hosting Active Manager - Detecting DB failures - Issues Mount/dismount to store - Initiates failovers and failures reported by ESE & Managed Availability
ESE Cache Management
Memory allocated for ESE cache now per database as there is a store.worker process per database
ESE Cache allocated depends on number of local DB copies and number of Active DBs
20% of max cache allocated to passive copies
Max cache calculated at start-up time.
IOPs reductions - Improvements in the logical store schema - Several Messages per page
Large sequential IO used
Support for large mailboxes 100Gb+ / slider bar in Outlook 2013 to manage OST file size
Elimination of Scheduled Maintenance
Now ran within time based assistants - when there's time and resources they will run
Background maintenance can be completed over a longer period of time.
Quota notifications generated at logon time
Modern Public Folders - Public folder database no longer exists
If you want pubic folders you create a PF mailbox - first one called the hierarchy mailbox that stores a writable copy of the public folder tree.
Each subsequent content mailbox add content - when size limited you want its created  - create another. Each once has a copy of the hierarchy mailbox to be able to direct requests
Only one writeable copy of the date - public folder therefore uses continuous replication
New Search Infrastructure
 - FAST - CTS - Content Transformation Service & IMS Interaction Management Service
CTS - Incoming Docs - Parse docs / filter / word break and put into FAST core
IMS - Incoming Queries - Parse query - send back results
 

In Exchange 2013 as messages come in a Transport Layer with are sent to CTS - indexing only once
Mailbox server updates and ExSearch updates and Mailbox CTS reads changes from Transport CTS
If it went to another copy in the DAG the message is not re-indexed as the replicated site reads from the CTS - Transport and copies it across
Transport Related Changes - On mailbox Server is 3 services
Exchange Transport - State full service handling SMTP mail flow and content inspection
Exchange Mailbox Transport Delivery - Receives mail from the transport service and delivers to db
Exchange Mailbox Transport Submission - Takes mail from DB and submits to Transport service
Transport Service Responsible for inbound / outbound mail - transport rules AV , routing. Queuing message mail.que
Transport Pipeline





  Exchange 2013 Poster Download
Posted by at 3 comments:
Subscribe to: Posts (Atom)