Explore topic-wise InterviewSolutions in Current Affairs.

Move POLICY: automatically moves messages to the messages to the archive Mailbox with the options of 6 MONTHS, 1 year, 2 YEARS, 5 years and NEVER – 2 years is default. Move mailbox policies helps keep mailbox under quota. This works like outlook Auto Archive without creating PSTs 

Delete Policy: automatically deletes messages. Delete policies are global. REMOVES unwanted items 

Move + Delete policy: automatically moves messages to archive after X months and deletes from archive after Y Months. We can set policy priority: Explicit policies over default policies; longer policies apply over shorted policies 

Move Policy: automatically moves messages to the messages to the archive Mailbox with the options of 6 months, 1 year, 2 years, 5 years and never – 2 years is default. Move mailbox policies helps keep mailbox under quota. This works like outlook Auto Archive without creating PSTs 

Delete Policy: automatically deletes messages. Delete policies are global. Removes unwanted items 

Move + Delete policy: automatically moves messages to archive after X months and deletes from archive after Y Months. We can set policy priority: Explicit policies over default policies; longer policies apply over shorted policies 

RETENTION POLICY is an option to move/ delete certain mails by applying rules. We can set retention policies at Item or Folder level. Policies can be APPLIED directly WITHIN e-mail. We can set expiration date stamped directly on e-mail. Policies can be applied to all email within a folder.

We can configure delete policy to delete the mail after certain PERIOD and Archive policies to move certain mails with the certain period to archive mailbox.

Retention policy is an option to move/ delete certain mails by applying rules. We can set retention policies at Item or Folder level. Policies can be applied directly within e-mail. We can set expiration date stamped directly on e-mail. Policies can be applied to all email within a folder.

We can configure delete policy to delete the mail after certain period and Archive policies to move certain mails with the certain period to archive mailbox.

It is a SECONDARY mailbox that is CONFIGURED by the administrator, this APPEARS along with user’s primary mailbox in outlook or OWA, and the PST files can be dragged and dropped to personal ARCHIVE Mailbox.

Mails in Primary mailbox can be moved automatically using Retention policies. Archive quota can be SET separately from primary mailbox.

It is a Secondary mailbox that is configured by the administrator, this appears along with user’s primary mailbox in outlook or OWA, and the PST files can be dragged and dropped to personal archive Mailbox.

Mails in Primary mailbox can be moved automatically using Retention policies. Archive quota can be set separately from primary mailbox.

Personal Archive: secondary Mailbox Node, they are the PST files of primary Mailbox. 

Retention Policies: folder/item level and archive/delete policies.

Multi-Mailbox search: Role BASED GUI, admin can assign this permission to legal TEAM.

Legal Hold: MONITOR or control a user from delete a mail by legal hold and searchable with Multi Mailbox Search.

Journaling: Journal de-duplication (unwanted journaling on DISTRIBUTED mails). One copy of journal per database. 

Journal decryption: HT role will do the decryption and send the decrypted copy for journaling.

Personal Archive: secondary Mailbox Node, they are the PST files of primary Mailbox. 

Retention Policies: folder/item level and archive/delete policies.

Multi-Mailbox search: Role based GUI, admin can assign this permission to legal team.

Legal Hold: monitor or control a user from delete a mail by legal hold and searchable with Multi Mailbox Search.

Journaling: Journal de-duplication (unwanted journaling on distributed mails). One copy of journal per database. 

Journal decryption: HT role will do the decryption and send the decrypted copy for journaling.

1. Archiving improved by providing larger mailbox architecture, simple MIGRATION of PSTs back to server, discovery options, retention policies and LEGAL hold.
2. LARGE mailbox Architecture – maintains performance and provides OPTION for DAS-SATA storage to reduce costs
3. Archiving enables simple migration of PSTs back to server. If the archiving option sin enabled for a user, a new Mailbox will be created to the user NAME archive in which the user can set retention policies to move the mails to archive mailbox or the admin can set retention policies for the user mailbox.
4. Archiving simplifies discovery, retention and legal hold.

EXCHANGE Server 2010 can support the DAS and Also JBOD disks its because of the HA option DEPENDS only on the DATABASE level.

Exchange Server 2010 can support the DAS and Also JBOD disks its because of the HA option depends only on the Database level.

EXCHANGE Server 2010 provides simplified ADMINISTRATION by providing options like:

1. Compliance office can easily search for mailboxes 
2. HR can easily UPDATE the user information 
3. Help desk can easily manage mailbox quotas 
4. User can easily track the STATUS of the MESSAGE easily 
5. User can easily create own Distribution group 
6. User can modify the contact information

Exchange Server 2010 provides simplified administration by providing options like:

1. Compliance office can easily search for mailboxes 
2. HR can easily update the user information 
3. Help desk can easily manage mailbox quotas 
4. User can easily track the status of the message easily 
5. User can easily create own Distribution group 
6. User can modify the contact information

If a MAILBOX MOVE is HAPPENING, the USERS will be stay online and there wont be be any discontinuity in SENDING or receiving mails.

If a mailbox move is happening, the users will be stay online and there wont be be any discontinuity in sending or receiving mails.

In EXCHANGE Server 2007, we have server to server failover scenarios, and we need to use failover CLUSTERING to configure the HA options which is very difficult to manage

In Exchange Server 2010, HA modified to Database level which provides quick recoverability in disk and database failures. We can have multiple database copies up to 16 mailbox copies in a database availability group. Admin have replicate mailbox copies up to 16 replicated copies. Capabilities of having CCR and SCR into SINGLE platform.

In Exchange Server 2007, we have server to server failover scenarios, and we need to use failover clustering to configure the HA options which is very difficult to manage

In Exchange Server 2010, HA modified to Database level which provides quick recoverability in disk and database failures. We can have multiple database copies up to 16 mailbox copies in a database availability group. Admin have replicate mailbox copies up to 16 replicated copies. Capabilities of having CCR and SCR into single platform.

Its PROVIDES a solution to have ONE E-Mail INBOX for E—Mail, Text messages and Voice messages

Can have multiple E-Mail accounts in one OWA window

Its provides a solution to have one E-Mail inbox for E—Mail, Text messages and Voice messages

Can have multiple E-Mail accounts in one OWA window

Desktop: office 2007 and ENTOURAGE MAC

WEB: OWA, OFFICE outlook web ACCESS, IE, Firefox and safari

Mobile: office outlook mobile, windows mobile, and Exchange active sync for third party’s

Desktop: office 2007 and entourage MAC

WEB: OWA, OFFICE outlook web access, IE, Firefox and safari

Mobile: office outlook mobile, windows mobile, and Exchange active sync for third party’s

Exchange server 2010 comes up with the advance security feature of STOPPING malicious SOFTWARE and spam from enter into the message environment

We can have Forefront Security to have this advance security, which has Multiple scan engines throughout the corporate infrastructure Easy to use management CONSOLE provides CENTRAL CONFIGURATION and operation.

Exchange server 2010 comes up with the advance security feature of stopping malicious software and spam from enter into the message environment

We can have Forefront Security to have this advance security, which has Multiple scan engines throughout the corporate infrastructure Easy to use management console provides central configuration and operation.

Hub TRANSPORT Server provides:

1. AUTOMATICALLY protect Messages with the centralized Rights Management Service 
2. Automatic Content Based PROTECTION 
3. Transport rule action to apply template to E-Mail or Voice Mail 
4. Support for SCANNING of attachment 
5. Internet confidential and DO NOT Forward E-Mail Polices 
6. Information Protection Cross PC, Web and Mobile devices

Hub Transport Server provides:

1. Automatically protect Messages with the centralized Rights Management Service 
2. Automatic Content Based Protection 
3. Transport rule action to apply template to E-Mail or Voice Mail 
4. Support for scanning of attachment 
5. Internet confidential and DO NOT Forward E-Mail Polices 
6. Information Protection Cross PC, Web and Mobile devices

• We can set email retention mail policy from END user level
• Message expiration
• We can SEARCH for INDIVIDUAL or Multi user mailboxes from compliance OFFICER perspective

• Continuous Availability 
• SIMPLIFIED Administration 
• Flexible DEPLOYMENT of EXCHANGE SERVER 2010 

1. Manage Inbox OVERLOAD 
2. Enhanced Voice MAIL 
3. Collaborate EFFICIENTLY 

1. Manage Inbox Overload 
2. Enhanced Voice Mail 
3. Collaborate efficiently 

• EMAIL Archiving 
• PROTECT Communication 
• Advanced SECURITY 

1. PROTECTION and compliance 
2. Anywhere ACCESS 
3. Flexible and RELIABLE 

1. Protection and compliance 
2. Anywhere Access 
3. Flexible and reliable 

1. UM reporting The reports for Call Statistics and User Call Logs found in the Exchange Management Console are displayed in the Exchange Control Panel.
2. UM management in the Exchange Control Panel You can USE the ECP to manage UM components in a cross-premises environment.
3. Cross-Forest UM-enabled mailbox migration In Exchange 2010 SP1, you can use the New-MoveRequest cmdlet with the Mailbox Replication Service (MRS) to move a UM-enabled mailbox within a local forest and multiple forests in an enterprise.
4. Outlook Voice Access improvements Outlook Voice Access users can log on to their Exchange 2010 mailbox and choose the order to listen to unread voice mail messages, from the oldest message first or the newest message first.
5. Caller Name Display support Exchange 2010 SP1 includes support for enhanced caller ID resolution for displaying names for voice MAILS from unresolved numbers using Caller Name Display (CND).
6. Test-ExchangeUMCallFlow cmdlet With this Exchange 2010 SP1 cmdlet, you can test UM connectivity and call flow.
7. New UM DIAL Plan wizard An additional page has been added to the New UM Dial Plan wizard that allows you to add a UM server to the dial plan.
8. Lync Server 2010 Support Migrating SIP URI dial plans and Message Waiting Indicator (MWI) notifications in a cross-premises environment has been added.
9. Secondary UM dial plan support You can add a secondary UM dial plan for a UM-enabled user.
10. UM language packs added New UM language packs are now available in Exchange 2010 SP1. In addition, the Spanish (Spain) (es-ES) UM language pack available for Exchange 2010 SP1 now includes Voice Mail Preview, a feature that wasn’t available in the Exchange 2010 RTM release of that language pack.
11. Call answering rules improvements There are three updates to Call Answering Rules for UM-enabled users in SP1.
12. UNIFIED COMMUNICATIONS Managed API/speech platform improvements Beginning with Exchange 2010 SP1, the UM server relies on Unified Communications Managed API v. 2.0 (UCMA) for its underlying SIP signaling and speech processing.
13. UM auto attendant update In Exchange 2010 SP1, a UM auto attendant will play only the holiday greeting on a holiday.

In Outlook 2010 and Outlook 2007, Autodiscover automatically loads any mailbox for which a user has been granted FULL access permission. Users can’t control or disable this behavior.

• Calendar Repair Assistant supports more scenarios than were available in Exchange 2010 RTM.
• Mailbox Assistants are now all throttle-based (changed from time-based in Exchange 2010 RTM).
• Internet calendar PUBLISHING allows users in your Exchange organization to share their Outlook calendars with a broad Internet audience.
• IMPORTING and exporting .pst files now uses the Mailbox Replication service and doesn't require Outlook.
• Hierarchical address book support allows you to create and configure your address lists and offline address BOOKS in a hierarchical view.
• Distribution group naming policies allow you to configure string text that will be appended or prepended to a distribution group's name when it's created.
• Soft-delete of mailboxes after move completion

In Outlook 2010 and Outlook 2007, Autodiscover automatically loads any mailbox for which a user has been granted full access permission. Users can’t control or disable this behavior.

Below are the new features on the high availability:

• Continuous replication: block MODE: This mode will allow the passive mailbox copies are up to date, as the active database is updated; each update written to the database log file is also shipped to the passive mailbox copies. In the event of a failure, the passive database copy is updated with the latest log updates which minimizes DATA loss
• Improved client experience for cross-site failover: Admin can now control if Outlook will redirect cross-site or if it is automatically connected
• Improved support for 2-node DATACENTER resilient topologies ( Now supports Datacenter Activation Coordinator mode (DAC) Mode with two SERVERS in a DAG )
• Faster failovers with improved post-failover client experience (Failover drives the database to a clean shutdown by playing all logs. The mount process then simply brings database up, with no recovery required, which speeds up the failover time. )
• Mailbox database redistribution (New script which can move active mailbox databases back to the copy with the highest activation PREFERENCE)

Below are the new features on the high availability:

• New shell command New-MailboxRepairRequest to DETECT and repair mailbox and DATABASE corruption issues.
• New SCRIPT introduced to control excessive log growth of mailbox database MENTIONED as Troubleshoot-DatabaseSpace.ps1
• Public FOLDER client permissions support is added to EMC

Below are the new Transport functionality:

1. MailTips ACCESS control over organizational RELATIONSHIPS
2. Enhanced monitoring and troubleshooting features for MailTips and MESSAGE Tracking
3. Message throttling enhancements
4. Shadow REDUNDANCY promotion
5. SMTP failover and load balancing improvements
6. Support for EXTENDED protection on SMTP connections
7. Send connector changes to reduce NDRs over well-defined connections

Below are the new Transport functionality:

Client Access Server level improvements in Exchange Server 2010 Sp1

Federation certificates, Exchange ActiveSync, SMS Sync, Integrated Rights Management, Microsoft Office Outlook Web App, and virtual directories.

1. Federation certificates can be a self signed certificate instead of a certificate issued by a CA to establish federation trust.
2. Exchange Active sync devices can be managed USING Exchange Control Panel like manage default access level for all phones, set up and email alert when a device is quarantined and create and manage active sync device access rules
3. SMS sync is a new feature is exchange active sync that works with Windows mobile 6.1 with outlook mobile update and windows mobile 6.5, it will give an ability to synchronize messages between a mobile phone or a device and exchange 2010 inbox
4. New outlook feature like OWA themes (27) and an option to customize the themes. User will have an option to reset the EXPIRED password from OWA
5. Reset OWA Virtual directory wizard will resolve the DAMAGED file on a virtual directory
6. Client throttling POLICIES will help you manage performance of your Client Access servers. Only the policies to limit the number of concurrent client connections were ENABLED by default. Exchange 2010 SP1 all client throttling policies are enabled by default.

Client Access Server level improvements in Exchange Server 2010 Sp1

Federation certificates, Exchange ActiveSync, SMS Sync, Integrated Rights Management, Microsoft Office Outlook Web App, and virtual directories.

Let us assume the functional exchange SERVER 2010 server got crashed due to hardware failure, here are the STEPS that need to build the server again 

• Arrange a new Server with the same operating system as like the failed server and assign the same drive letter for the databases and the log files directory
• Reset the Active Directory Account for failed server
• Install and configure the perquisites that are needed to install Exchange Server 2010
• Ensure the network connectivity and configure the new computer with the correct IP address
• Join the new computer with the domain controller with the same computer name as a failed server
• Run the setup Mode:recoverserver
• RESTORE databases on the location of the new Disks
• If it is non mailbox servers, restore the configuration files from BACK backup or from other servers.

Let us assume the functional exchange server 2010 server got crashed due to hardware failure, here are the steps that need to build the server again 

Software:

• Windows Server 2008 SP2 or R2 with x64 bit version
• .Net framework 3.5 with SP1 
• Windows Remote Management Shell
• Power shell 2.0

Rest of the Windows components related to Exchange Server installation can be installed using the below COMMAND

Setup /mode:install /ROLES:"C,H,T" /InstallWindowsComponents

Software:

Rest of the Windows components related to Exchange Server installation can be installed using the below command

Setup /mode:install /roles:"C,H,T" /InstallWindowsComponents

Prepare Schema: After running the Prepare Schema switch, the Active directory will contain the classes and ATTRIBUTES required to support Exchange environment.

Prepare AD: after running the Prepare AD switch, new container will be created to hold the DETAILS of the information from server to databases to CONNECTORS. This process also created universal security groups to manage Exchange and sets appropriate permissions on objects to ALLOW them to be managed.

Prepare Schema: After running the Prepare Schema switch, the Active directory will contain the classes and attributes required to support Exchange environment.

Prepare AD: after running the Prepare AD switch, new container will be created to hold the details of the information from server to databases to connectors. This process also created universal security groups to manage Exchange and sets appropriate permissions on objects to allow them to be managed.

Single Forest: simplest design, both the AD account and mailbox resides on the same forest.

Multi Forest: TWO or more forest that operate independently from each other in terms of the accounts of application DEPLOYED in each forest.

Resource Forest: User accounts and GROUPS are deployed in root forest and applications like Exchange are deployed in special resource forest. Each mailbox exists in resource forest and use the disabled user accounts that BELONGS to root forest.

Single Forest: simplest design, both the AD account and mailbox resides on the same forest.

Multi Forest: Two or more forest that operate independently from each other in terms of the accounts of application deployed in each forest.

Resource Forest: User accounts and groups are deployed in root forest and applications like Exchange are deployed in special resource forest. Each mailbox exists in resource forest and use the disabled user accounts that belongs to root forest.

EXCHANGE Server stores the Exchange related information in Active Directory partitions, following are the details.

Domain Partition: Mail enable RECIPIENT, GROUPS and contact related to domain level are stored.

Configuration Partition: Stores the Exchange configuration information like, policies, GLOBAL settings, address list, connecters and it CONTAINS the information related to forest level.

Schema Partition: stores the Exchange specific classes and attributes.

Exchange Server stores the Exchange related information in Active Directory partitions, following are the details.

Domain Partition: Mail enable recipient, groups and contact related to domain level are stored.

Configuration Partition: Stores the Exchange configuration information like, policies, global settings, address list, connecters and it contains the information related to forest level.

Schema Partition: stores the Exchange specific classes and attributes.

We have two Edition introduced in Exchange Server 2010

Standard Edition: which PROVIDES the basic functionality of Exchange server, LIMITED to have 5 Databases, includes public folder database. Supports DAG and there is no limit for Database Size.

Enterprise Edition: Designed for LARGE organization with the 100 Database as the limit. Support DAG and there is no limit for database size.

We have two Edition introduced in Exchange Server 2010

Standard Edition: which provides the basic functionality of Exchange server, limited to have 5 Databases, includes public folder database. Supports DAG and there is no limit for Database Size.

Enterprise Edition: Designed for large organization with the 100 Database as the limit. Support DAG and there is no limit for database size.

No is the answers and it's not possible to install EXCHANGE Server 2007, if Exchange Server 2010 got INSTALLED at the first place.

If we plan to DEPLOY exchange Server 2007 on Exchange Server 2010 deployed ENVIRONMENT. We have to prepare the Exchange environment with Exchange Server 2007 INSTALLATION media and then if we install Exchange Server 2010, on the later, we have an option to introduce Exchange Server 2007.

No is the answers and it's not possible to install Exchange Server 2007, if Exchange Server 2010 got installed at the first place.

If we plan to deploy exchange Server 2007 on Exchange Server 2010 deployed environment. We have to prepare the Exchange environment with Exchange Server 2007 installation media and then if we install Exchange Server 2010, on the later, we have an option to introduce Exchange Server 2007.

MAIN REASON is, while update EXCHANGE Server 2007 with SP2 will modify the Active DIRECTORY Schema to allow Exchange Server 2007 and Exchange Server 2010 to co exists in same Exchange organization.

Main reason is, while update Exchange Server 2007 with SP2 will modify the Active Directory Schema to allow Exchange Server 2007 and Exchange Server 2010 to co exists in same Exchange organization.

WINDOWS Server 2008 SP2 or R2 VERSION was the only supported version of Windows Servers to Install Exchange Server 2010.

Note: Windows Server 2008 DATACENTER Edition was not certified to install Exchange Server 2010 and also the Windows Server 2008, core edition and WEB editions are also not supported.

Windows Server 2008 SP2 or R2 version was the only supported version of Windows Servers to Install Exchange Server 2010.

Note: Windows Server 2008 Datacenter Edition was not certified to install Exchange Server 2010 and also the Windows Server 2008, core edition and web editions are also not supported.

If we are going to install an NEW installation or a TRANSITION from earlier version, we have to follow the below STEPS in preparing an Exchange Server 2010 installation.

• Run the EXBPA to identify the problems
• Check whether all the perquisites and the hot fixes are installed
• Active directory to be raised to Windows Server 2003 forest functional level, better to have Active Directory and Global Catalog Server on 64 bit server with Windows Sever 2003 Sp1 or later
• REMOVE any Exchange Server 2000 or earlier version prior to the Exchange 2010 installation
• If we have Exchange Server 2007 in place, that need to be update with Exchange Server 2007 SP2
• Decide which versionedition of Exchange Server 2010 we are going to install BASED on the business requirement.

If we are going to install an new installation or a transition from earlier version, we have to follow the below steps in preparing an Exchange Server 2010 installation.

Three IMPORTANT focuses on the release of Exchange Server 2010 are:

1. Increase operational flexibility through easier deployment, HIGH AVAILABILITY and simplified administration.
2. Support to larger and better organized mailboxes using Archive mailbox, Discovery Mailboxes etc.
3. Provides control with protected communication, BUILT in compliance and archiving functionality like Retention and Legal hold.

Three important focuses on the release of Exchange Server 2010 are:

• An INCOMING message from the Internet first goes to the Edge Transport server.
• The Edge Transport server performs first-level recipient validation, as well as spam and virus filtering. The message is then passed on to the Hub Transport server.
• The Hub Transport server performs compliance content assessment and then looks at the internal routing for messages and forwards the message to another Hub Transport server or directly to a Mailbox server.
• The Mailbox server places the incoming message into the user's mailbox and notifies the user that a message has arrived.
• The user LAUNCHES OUTLOOK, OWA, their Windows Mobile device, or another client system and connects to the client access server. The client access server confirms the DESTINATION point of the user's mailbox and provides the user access to their mailbox data.
• In parallel, if a voice mail message COMES in for a user, the Unified Messaging server processes the incoming voice message, and then takes the message and places the voice message into the user's mailbox residing on the Mailbox server for the recipient

Mailbox SERVER: This server hosts mailboxes and public folders.

Client ACCESS Server: This is the server that hosts the client protocols, such as POP3, IMAP4, HTTPS, Outlook Anywhere, Availability service and Autodiscover service. The Client Access Server also hosts Web services.

Unified Messaging Server: This is the server that connects a Private BRANCH eXchange (PBX) system to Exchange 2010.

Hub Transport Server: This is the MAIL routing server that routes mail within the Exchange organization.

Edge Transport Server: This is the mail routing server that typically sits at the perimeter of the topology and routes mail in to and out of the Exchange organization.

Mailbox Server: This server hosts mailboxes and public folders.

Client Access Server: This is the server that hosts the client protocols, such as POP3, IMAP4, HTTPS, Outlook Anywhere, Availability service and Autodiscover service. The Client Access Server also hosts Web services.

Unified Messaging Server: This is the server that connects a Private Branch eXchange (PBX) system to Exchange 2010.

Hub Transport Server: This is the mail routing server that routes mail within the Exchange organization.

Edge Transport Server: This is the mail routing server that typically sits at the perimeter of the topology and routes mail in to and out of the Exchange organization.

A few of the missing features that are available in Exchange Server 2003 or 2007 are:

• Storage Groups and Recovery Storage Groups are removed and the concept of mailbox database and Recovery mailbox database is available
• STM database has been removed, so it's just moved to EDB database as like exchange 2000 and the STM database concept is incorporated with EDB database
• ADMINISTRATIVE Group and Routing Groups is been completely removed. Routing Groups are replaced with Active Directory SITES and services to define organizational Sites and routing of messages to those sites
• EXOLEDB, WEBDAV, CDOEX and the Store Events are gone; exchange 2010 uses the new Exchange Web Services as the primary method to provide web services to client system
• Public Folders are still announced in a de emphasized state
• Other features like front and BACK end architecture has been removed, New Management tools EMC and Exchange Management Shell are introduced.
• Normal Permission Model is replaced with powerful or granular permission model named Role Based Access Control

A few of the missing features that are available in Exchange Server 2003 or 2007 are:

1. Core Infrastructure of Exchange Server 2003 or 2007 versus Exchange server 2010 in same, Microsoft continued to use the JET EDB database as the main database ENGINE
2. Exchange 2010 still use the concept of mailbox servers to hold US the user mailboxes and public folders
3. Users can access their email using Outlook, OWA and Active Sync Clients
4. Exchange 2010 uses the VSS API to freeze the exchange database to perform a backup of exchange server database.
5. Even if transition of mailbox from exchange server 20032007 occurs, older CLIENT access emails using outlook or OWA won't FEEL much difference on their client perspective, there is no compulsion of upgrading to Exchange 2010.
6. Exchange Server 2007 5 roles architecture is not changed in Exchange Server 2010. But the MAPI endpoint on Mail Server role is moved to client access server role, where in Exchange Server 2010, All the Exchange Server clients will connect CAS to access the mailbox and the public folders access will be directly threw or to Mailbox Database.

We have to editions introduced in EXCHANGE 2010, STANDARD and Enterprise Edition.

1 Standard Edition: limited to have 5 databases, can be installed in Windows server 2008 Sp2 X64 Machine and Supports DAG (Standard edition exchange 2010 can be a member of DAG) if it is installed in Windows Server 2008 SP2 X64 enterprise edition operating system. No size limit for database, limited only by the HARDWARE

2 Enterprise Edition: Limited to have 100 databases, installed on Windows server 2008 Sp2 X64 Machine and Support DAG. Only be installed in Windows Server 2008 SP2 X64 enterprise edition operating system. No size limit for database, limited only by the hardware.

We have to editions introduced in Exchange 2010, Standard and Enterprise Edition.

1 Standard Edition: limited to have 5 databases, can be installed in Windows server 2008 Sp2 X64 Machine and Supports DAG (Standard edition exchange 2010 can be a member of DAG) if it is installed in Windows Server 2008 SP2 X64 enterprise edition operating system. No size limit for database, limited only by the hardware

2 Enterprise Edition: Limited to have 100 databases, installed on Windows server 2008 Sp2 X64 Machine and Support DAG. Only be installed in Windows Server 2008 SP2 X64 enterprise edition operating system. No size limit for database, limited only by the hardware.

Exchange Server is an email, calendaring and ADDRESS book systemapplication that runs on WINDOWS Server 2008 operating system. In Exchange 2010, Microsoft focus on security, scalability, reliability, MOBILITY and unified COMMUNICATION.

Exchange Server is an email, calendaring and address book systemapplication that runs on Windows Server 2008 operating system. In Exchange 2010, Microsoft focus on security, scalability, reliability, mobility and unified communication.