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 requirement applies to supported production environments only; a 32-bit trial version is out there for download and testing. Hence, companies currently running Exchange Server on 32-bit hardware can be needed to replace or migrate hardware if they wish 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 new 2007 server since in-place upgrades are not supported in 2007. The primary beta of Exchange Server 2007 (then named "Exchange 12" or E12) was released in December 2005 to a very restricted variety of beta testers. A wider beta was made on the market 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 features * Protection: anti-spam, antivirus, compliance, clustering with data, replication, improved security and encryption * Improved Info Employee Access: improved calendaring, unified messaging, improved mobility, improved net access * Improved IT Experience: 64 bit performance & scalability, command-line shell & simplified GUI, improved deployment, role separation, simplified routing * Exchange Management Shell: a new command-line shell and scripting language for system administration (based mostly on Windows PowerShell). Shell users will perform each task which will be performed within the Exchange Server graphical user interface and 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 distinctive 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 different wireless devices. Voice commands can be given to manage and hear e-mail over the phone (and also send some basic messages, like "I am going to be late") * Increased the database size limit. Database size is currently limited to 16TB per database * Increased the maximum number of storage groups and mail databases per server, to five every for Standard Edition (from 1 each in Exchange Server 2003 Commonplace), and to 50 each for Enterprise Edition (from 4 teams and twenty databases in Exchange Server 2003 Enterprise). * You'll configure Outlook Anywhere (formerly referred to as RPC over HTTP) to produce external access to Microsoft Exchange Server 2007 for your clients. If you would like Microsoft Office Outlook 2007 user profiles to be automatically configured to attach to Exchange 2007, configure the Autodiscover service. This also provides external URLs for Exchange services such as 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 was released to producing (RTM'ed) on October 9, 2009. Exchange Server 2010 was officially launched on November nine, 2009 ; a month when hitting RTM. A one hundred twenty day trial is also downloadable from Microsoft. Preliminary changes include: 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 now not offered. CCR currently at Datastore level, not Server Level though the terminology has changed. Clustering functionality is now known as DAG (Database Availability Group). Exchange 2010 is additionally solely obtainable in 64-bit as half of Microsoft's drive for all its future products to be solely 64-bit based. Exchange 2010 will run on Windows Server 2003 with SP2 at least and Windows Server 2008 R2 (also only released in 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 additionally introduced active-active clustering, but for two-node clusters only. During this setup, each servers in the cluster are allowed to be active simultaneously. This is opposed to Exchange's additional common active-passive mode in which the failover servers in any cluster node can't be used in the slightest degree while their corresponding home servers are active. They need to wait, inactive, for the home servers in the node to fail. Subsequent performance problems with active-active mode have led Microsoft to recommend that it should no longer 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 requirement 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, but not for Exchange data. During this scenario, 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 built-in support for asynchronous replication modeled on SQL Server's "Log shipping" in CCR (Cluster Continuous Replication) clusters, that are built on MSCS MNS (Microsoft Cluster Service-Majority Node Set) clusters, which do not require shared storage. This type of cluster will be cheap and deployed in one, or "stretched" across two datacenters for defense against site-wide failures like natural disasters. The limitation of CCR clusters is the flexibility to have solely two nodes and therefore the third node known as "voter node" or file share witness that stops "split brain" situations, typically hosted as a file share on a Hub Transport Server. The second sort of cluster is that the ancient clustering that was out there in previous versions, and is currently being referred to as 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 during Exchange Server installation. LCR or Local Continuous Replication has been known as the "poor man's cluster". It's designed to allow for data replication to an alternative drive attached to the identical system and is meant to produce protection against native storage failures. It will not shield 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 referred to as SCR (Standby Continuous Replication). In contrast to CCR which requires that each 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, that are completely different from Windows CALs. Corporate license agreements, like the Enterprise Agreement, or EA, embrace Exchange Server CALs. It also comes as part of the Core CAL. Simply 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 enable a user to access Exchange e-mail from any device. User and Device CALs are the same value, however cannot be used interchangeably. For Service Providers trying to host Microsoft Exchange, there's an SPLA (Service Provider License Agreement) accessible whereby Microsoft receives a monthly service fee in the place of the traditional Client Access Licenses. Two types of Exchange CAL are obtainable: 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 variety of providers. You'll realize many 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 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 release of Mac OS X v10.6 (additionally called Mac OS X Snow Leopard), Mac computers running OS X embed native support for this technology, without having to use additional software such as 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, which is a feature that significantly reduces synchronization time between the server vs. WebDAV, that is employed by Exchange Server 2003. For Information, Queries 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 limited version of Outlook Web Access is offered to Mac users using a net browser. Entourage X, 2004 and 2008 don't support synchronizing tasks and notes with Exchange Servers 2000, 2003, 2007 or 2010. However Entourage 2008 "Web Services Edition", which could 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 (together with Exchange 2010). E-mail hosted on an Exchange Server will conjointly be accessed using POP3 and IMAP4 protocols, using clients like 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.). Varied Hosted Exchange Offers will be found at ms-exchange-hosting.information . Exchange Server mailboxes will conjointly be accessed through a internet browser, using Outlook Web Access (OWA). Exchange Server 2003 also featured a version of OWA for mobile devices, referred to as 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 different knowledge directly with the server - almost like BlackBerry devices. Apple, Nokia and alternative companies have licensed the software to enable their devices to sync with Exchange Server also . 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 . Several different devices currently support ActiveSync push e-mail, like the iPhone and devices that use the Android operating system . For More Details visit msdn.com / microsoft.com
Article Source: http://www.gambling-articles.org
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
