Home | Computer | Software
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, companies currently running Exchange Server on 32-bit hardware will be required to replace or migrate hardware if they would like to upgrade to the new version. Firms 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 brand new 2007 server since in-place upgrades aren't supported in 2007. The first beta of Exchange Server 2007 (then named "Exchange 12" or E12) was released in December 2005 to a very limited range of beta testers. A wider beta was created available via TechNet Plus and MSDN subscriptions in March 2006 in line with the Microsoft Exchange team blog. Exchange Server 2007 is an integrated part of the Innovative Communications Alliance products. New features * Protection: anti-spam, antivirus, compliance, clustering with data, replication, improved security and encryption * Improved Information Employee Access: improved calendaring, unified messaging, improved mobility, improved web access * Improved IT Expertise: 64 bit performance & scalability, command-line shell & simplified GUI, improved deployment, role separation, simplified routing * Exchange Management Shell: a replacement command-line shell and scripting language for system administration (based mostly on Windows PowerShell). Shell users can perform every task which will be performed within the Exchange Server graphical user interface plus further tasks, and can program often-used or advanced tasks into scripts that may be saved, shared, and re-used. The Exchange Management Shell has over 375 unique commands to manage options 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 alternative wireless devices. Voice commands can be given to regulate and hear e-mail over the phone (and also send some basic messages, like "I will be late") * Increased the database size limit. Database size is now limited to 16TB per database * Increased the maximum variety of storage groups and mail databases per server, to 5 every for Normal Edition (from 1 every in Exchange Server 2003 Standard), and to 50 each for Enterprise Edition (from four teams and twenty databases in Exchange Server 2003 Enterprise). * You'll be able to configure Outlook Anywhere (formerly referred to as RPC over HTTP) to supply external access to Microsoft Exchange Server 2007 for your clients. If you wish Microsoft Office Outlook 2007 user profiles to be automatically configured to attach to Exchange 2007, configure the Autodiscover service. This additionally provides external URLs for Exchange services like the Availability service and offline address book. Exchange Server 2010 Microsoft announced the Exchange 2010 to be obtainable from the second period of 2009, and it absolutely was released to producing (RTM'ed) on October nine, 2009. Exchange Server 2010 was officially launched on November 9, 2009 ; a month when hitting RTM. A a hundred and twenty day trial is also downloadable from Microsoft. Preliminary changes embrace: Storage Teams are being eliminated and incorporated into the Info Store. Clustering is now at the Database level, not Server level. LCR and SCC clustering not offered. CCR now at Datastore level, not Server Level though the terminology has changed. Clustering functionality is now referred to as DAG (Database Availability Group). Exchange 2010 is additionally only available in 64-bit as part 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 (conjointly only released in a very 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, except for two-node clusters only. In this setup, both servers within the cluster are allowed to be active simultaneously. This can be opposed to Exchange's additional common active-passive mode in which the failover servers in any cluster node can't be used at all while their corresponding home servers are active. They have to wait, inactive, for the house servers in the node to fail. Subsequent performance problems with active-active mode have led Microsoft to advocate that it should now 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 because of its demand for servers in the cluster nodes to share the same physical data. The clustering in Exchange Server provides redundancy for Exchange Server as an application, but not for Exchange data. During this state of affairs, the info will be regarded as a single purpose of failure, despite Microsoft's description of this founded as a "Shared Nothing" model. This void has however been stuffed by ISV's and storage manufacturers, through "site resilience" solutions, like geo-clustering and asynchronous knowledge replication. Exchange Server 2007 introduces new cluster terminology and configurations that address the shortcomings of the previous "shared knowledge 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 designed on MSCS MNS (Microsoft Cluster Service-Majority Node Set) clusters, that don't require shared storage. This kind of cluster can be inexpensive and deployed in one, or "stretched" across two datacenters for cover against site-wide failures such as natural disasters. The limitation of CCR clusters is the power to own solely two nodes and the third node known as "voter node" or file share witness that prevents "split brain" scenarios, generally hosted as a file share on a Hub Transport Server. The second sort of cluster is the traditional clustering that was accessible in previous versions, and is currently being known as SCC (Single Copy Cluster). In Exchange Server 2007 deployment of each CCR and SCC clusters has been simplified and improved; the entire cluster install process takes place during Exchange Server installation. LCR or Local Continuous Replication has been called the "poor man's cluster". It is designed to allow for knowledge replication to an alternate drive attached to the same system and is meant to provide protection against native 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 additional high-availability feature known as SCR (Standby Continuous Replication). Not like CCR which requires that each servers belong to a Windows cluster, sometimes residing in the identical datacenter, SCR can replicate data to a non-clustered server, located in an exceedingly separate datacenter. Licensing Like Windows Server products, Exchange Server requires Client Access Licenses, which are totally different from Windows CALs. Company license agreements, like the Enterprise Agreement, or EA, embody Exchange Server CALs. It additionally comes as part of the Core CAL. Simply like Windows Server and different server merchandise from Microsoft, you'll be able to opt for to use User or Device CALs. Device CALs are assigned to a tool (workstation, laptop or PDA). User CALs, are assigned to a user or employee (not a mailbox). User CALs enable 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 is an SPLA (Service Provider License Agreement) accessible whereby Microsoft receives a monthly service fee in the place of the ancient Client Access Licenses. Two sorts of Exchange CAL are available: 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 additionally be purchased as a hosted service from a range of providers. You'll be able to realize many choices for this at ms-exchange-hosting.info Clients Program Microsoft Exchange Server uses a proprietary RPC protocol, MAPI/RPC , that was designed to be utilized by the Microsoft Outlook client. Clients capable of using the proprietary options of Exchange Server embrace Microsoft Outlook, Novell Evolution, and the newest version of Microsoft Entourage for Mac. Also, since the discharge of Mac OS X v10.6 (conjointly called 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. Engineered in support with Mac OS X 10.6 requires 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 used 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 on the market to Mac users using a net browser. Entourage X, 2004 and 2008 do not support synchronizing tasks and notes with Exchange Servers 2000, 2003, 2007 or 2010. However Entourage 2008 "Web Services Edition", that may be a free download from Microsoft for users of Workplace 2008, will 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 also be accessed using POP3 and IMAP4 protocols, using clients like Outlook Categorical, Mozilla Thunderbird, and Lotus Notes. (These protocols must be enabled on the server. Recent versions of Exchange Server turn them off by default.). Varied Hosted Exchange Offers can be found at ms-exchange-hosting.data . Exchange Server mailboxes can additionally be accessed through a net browser, using Outlook Web Access (OWA). Exchange Server 2003 also 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, within the context of Exchange Server, allows a compliant device like a Windows Mobile device to sync mail, contacts and other information directly with the server - the same as BlackBerry devices. Apple, Nokia and other companies have licensed the software to enable their devices to sync with Exchange Server likewise . Support for Push E-mail was added to Exchange Server 2003 with Service Pack 2. Windows Mobile 5.0 requires the "Messaging and Security Feature Pack (MSFP)", later versions of the mobile operating system have the potential inbuilt . Many other devices currently support ActiveSync push e-mail, such as the iPhone and devices that use the Android operating system . For More Details visit msdn.com / microsoft.com
Article Source: http://www.gamblingarticlessite.net
www.ms-exchange-hosting.info
Please Rate this Article
5 out of 54 out of 53 out of 52 out of 51 out of 5
Not yet Rated
