Search:

Microsoft Exchange Server(2007-2010) - ms-exchange-hosting.info

Exchange Server 2007 (v8, code name E12, or with SP1 v8.1) runs only on 64 bit x86-64 versions of Windows Server. This demand applies to supported production environments only; a 32-bit trial version is offered for download and testing. Hence, firms currently running Exchange Server on 32-bit hardware can be required to replace or migrate hardware if they want to upgrade to the new version. Companies that are currently running Exchange Server on 64-bit capable hardware are still required to migrate from their existing Exchange 2000/2003 servers to a replacement 2007 server since in-place upgrades don't seem to be supported in 2007.

The first beta of Exchange Server 2007 (then named "Exchange 12" or E12) was released in December 2005 to a terribly limited variety of beta testers. A wider beta was made obtainable via TechNet Plus and MSDN subscriptions in March 2006 according to the Microsoft Exchange team blog. Exchange Server 2007 is an integrated part of the Innovative Communications Alliance products.

New options

* Protection: anti-spam, antivirus, compliance, clustering with data, replication, improved security and encryption
* Improved Data Worker Access: improved calendaring, unified messaging, improved mobility, improved web access
* Improved IT Experience: 64 bit performance and scalability, command-line shell and simplified GUI, improved deployment, role separation, simplified routing
* Exchange Management Shell: a new command-line shell and scripting language for system administration (based on Windows PowerShell). Shell users will perform every task which will be performed within the Exchange Server graphical user interface plus further tasks, and can program often-used or complex tasks into scripts that may be saved, shared, and re-used. The Exchange Management Shell has over 375 unique commands to manage features of Microsoft Exchange Server 2007.
* "Unified Messaging" that lets users receive voice mail, e-mail, and faxes in their mailboxes, and lets them access their mailboxes from cell phones and other wireless devices. Voice commands will be given to control and hear e-mail over the phone (and conjointly send some basic messages, like "I am going to be late")
* Increased the database size limit. Database size is now restricted to 16TB per database
* Increased the utmost range of storage groups and mail databases per server, to 5 each for Customary Edition (from 1 every in Exchange Server 2003 Commonplace), and to fifty every for Enterprise Edition (from four groups and twenty databases in Exchange Server 2003 Enterprise).
* You can configure Outlook Anywhere (formerly called RPC over HTTP) to provide external access to Microsoft Exchange Server 2007 for your clients. If you wish Microsoft Workplace Outlook 2007 user profiles to be automatically configured to connect to Exchange 2007, configure the Autodiscover service. This also provides external URLs for Exchange services like the Availability service and offline address book.

Exchange Server 2010

Microsoft announced the Exchange 2010 to be offered from the second period of 2009, and it had been released to manufacturing (RTM'ed) on October nine, 2009. Exchange Server 2010 was officially launched on November 9, 2009 ; a month when hitting RTM. A one hundred twenty day trial is additionally downloadable from Microsoft.

Preliminary changes include: Storage Groups are being eliminated and incorporated into the Information Store. Clustering is now at the Database level, not Server level. LCR and SCC clustering now not offered. CCR now at Datastore level, not Server Level although the terminology has changed. Clustering functionality is currently called DAG (Database Availability Group). Exchange 2010 is additionally only offered in sixty four-bit as half of Microsoft's drive for all its future products to be solely 64-bit based. Exchange 2010 can run on Windows Server 2003 with SP2 at least and Windows Server 2008 R2 (additionally only released during a 64-bit edition).

Clustering and high availability

Exchange Server Enterprise Edition supports clustering of up to 4 nodes when using Windows 2000 Server, and up to 8 nodes with Windows Server 2003. Exchange Server 2003 conjointly introduced active-active clustering, but for two-node clusters only. In this setup, each servers within the cluster are allowed to be active simultaneously. This is opposition Exchange's more common active-passive mode in which the failover servers in any cluster node cannot be used in the least while their corresponding home servers are active. They need to wait, inactive, for the house servers in the node to fail. Subsequent performance problems with active-active mode have led Microsoft to recommend that it should not be used. After all, support for active-active mode clustering has been discontinued with Exchange Server 2007.

Exchange's clustering (active-active or active-passive mode) has been criticized as a result of of its demand for servers within the cluster nodes to share the same physical data. The clustering in Exchange Server provides redundancy for Exchange Server as an application, however not for Exchange data. In this situation, the data will be regarded as a single point of failure, despite Microsoft's description of this set up as a "Shared Nothing" model. This void has however been filled by ISV's and storage manufacturers, through "web site resilience" solutions, such as geo-clustering and asynchronous information replication. Exchange Server 2007 introduces new cluster terminology and configurations that address the shortcomings of the previous "shared data model".

Exchange Server 2007 provides designed-in support for asynchronous replication modeled on SQL Server's "Log shipping" in CCR (Cluster Continuous Replication) clusters, that are engineered on MSCS MNS (Microsoft Cluster Service-Majority Node Set) clusters, which do not require shared storage. This sort of cluster will be cheap and deployed in one, or "stretched" across 2 datacenters for protection against site-wide failures like natural disasters. The limitation of CCR clusters is the ability to have solely two nodes and also the third node known as "voter node" or file share witness that prevents "split brain" situations, typically hosted as a file share on a Hub Transport Server. The second sort of cluster is the traditional clustering that was obtainable in previous versions, and is now being called SCC (Single Copy Cluster). In Exchange Server 2007 deployment of each CCR and SCC clusters has been simplified and improved; the whole cluster install process takes place throughout Exchange Server installation. LCR or Local Continuous Replication has been referred to as the "poor man's cluster". It is designed to permit for knowledge replication to an alternate drive hooked up to the same system and is meant to supply protection against local storage failures. It will not defend against the case where the server itself fails.
For Questions,Answers,Videos visit ms-exchange-hosting.info

In November 2007, Microsoft released SP1 for Exchange Server 2007. This service pack includes an extra high-availability feature called SCR (Standby Continuous Replication). In contrast to CCR that needs that both servers belong to a Windows cluster, typically residing in the identical datacenter, SCR can replicate data to a non-clustered server, located during a separate datacenter.

Licensing

Like Windows Server products, Exchange Server requires Client Access Licenses, which are different from Windows CALs. Corporate license agreements, like the Enterprise Agreement, or EA, embody Exchange Server CALs. It also comes as part of the Core CAL. Just like Windows Server and other server merchandise from Microsoft, you'll select to use User or Device CALs. Device CALs are assigned to a device (workstation, laptop or PDA). User CALs, are assigned to a user or employee (not a mailbox). User CALs allow a user to access Exchange e-mail from any device. User and Device CALs are the identical value, but can not be used interchangeably. For Service Providers wanting to host Microsoft Exchange, there's an SPLA (Service Provider License Agreement) accessible whereby Microsoft receives a monthly service fee within the place of the ancient Client Access Licenses. Two sorts of Exchange CAL are offered: Exchange CAL Standard and Exchange CAL Enterprise. The Enterprise CAL is an add-on licence to the Standard CAL.

Exchange hosting

Microsoft Exchange Server can conjointly be purchased as a hosted service from a number of providers.
You'll realize several options for this at ms-exchange-hosting.info

Clients Program
Microsoft Exchange Server uses a proprietary RPC protocol, MAPI/RPC , that was designed to be used by the Microsoft Outlook client. Clients capable of using the proprietary features of Exchange Server embrace Microsoft Outlook, Novell Evolution, and the latest version of Microsoft Entourage for Mac. Additionally, since the discharge of Mac OS X v10.6 (conjointly known as Mac OS X Snow Leopard), Mac computers running OS X embed native support for this technology, without having to use extra software like of Microsoft Entourage. Designed in support with Mac OS X 10.6 needs the Exchange organization to be running Exchange Server 2007 SP1/SP2 or Exchange Server 2010. Apple depends on Exchange Web Services, that may be a feature that considerably reduces synchronization time between the server vs. WebDAV, which is utilized by Exchange Server 2003. For Information, Questions And Videos, check on ms-exchange-hosting.info .

Mac users wishing to access Exchange e-mail running on Exchange Server 2000 or 2003 should use Microsoft's Entourage client versions X, 2004 or 2008. Alternatively a restricted version of Outlook Web Access is obtainable to Mac users using a web browser. Entourage X, 2004 and 2008 don't support synchronizing tasks and notes with Exchange Servers 2000, 2003, 2007 or 2010. But Entourage 2008 "Net Services Edition", which could be a free download from Microsoft for users of Office 2008, does support synchronizing tasks and notes with Exchange Server 2007 SP1 roll up 4 or later (including Exchange 2010).

E-mail hosted on an Exchange Server can additionally be accessed using POP3 and IMAP4 protocols, using clients such as Outlook Specific, Mozilla Thunderbird, and Lotus Notes. (These protocols must be enabled on the server. Recent versions of Exchange Server turn them off by default.). Numerous Hosted Exchange Offers will be found at ms-exchange-hosting.data .

Exchange Server mailboxes can additionally be accessed through a internet browser, using Outlook Internet Access (OWA). Exchange Server 2003 additionally featured a version of OWA for mobile devices, called Outlook Mobile Access (OMA).

ActiveSync

Support for ActiveSync was added to Microsoft Exchange Server 2003. ActiveSync, in the context of Exchange Server, allows a compliant device such as a Windows Mobile device to sync mail, contacts and alternative data directly with the server - kind of like BlackBerry devices. Apple, Nokia and alternative firms have licensed the software to enable their devices to sync with Exchange Server similarly .

Support for Push E-mail was added to Exchange Server 2003 with Service Pack 2. Windows Mobile 5.0 needs the "Messaging and Security Feature Pack (MSFP)", later versions of the mobile operating system have the capability inbuilt . Many different devices now support ActiveSync push e-mail, like the iPhone and devices that use the Android operating system . For More Details visit msdn.com / microsoft.com