How to change your expired passwords in OWA Exchange 2010 SP3

Exchange Server 2010 Service Pack 1 and Exchange Server 2007 Service Pack 3 (running on Windows Server 2008 or Windows Server 2008 R2) have a new feature that will allow users with expired passwords to change their password. This also works for users who have their accounts configured to change password on next logon (User must change password at next logon in ADUC).

Use this procedure to enable it on Exchange 2007 SP3 and Exchange 2010 SP1 Client Access servers:

Note: If you are using a CAS Array, you must perform these steps on each CAS in the array.

  1. On the Client Access Server (CAS), click Start > Run and type regedit.exe and click OK.
  2. Navigate to HKLM\SYSTEM\CurrentControlSet\Services\MSExchange OWA.
  3. Right click the MSExchange OWA key and click New > DWord (32-bit).
  4. The DWORD value name is ChangeExpiredPasswordEnabled and set the value to 1.
    Note: The values accepted are 1 (or any non-zero value) for “Enabled” or 0 or blank / not present for “Disabled”
  5. After you configure this DWORD value, you must reset IIS. The recommended method to reset IIS is to use IISReset /noforce from a command prompt.

Important: When changing passwords, users can’t use a UPN (for example, in the Domain\user name field in the Change Password window shown below, unless E2010 SP1 RU3 or later has been deployed on the Client Access servers.

How to put O365 mailbox on in-place hold using the Exchange Online powershell

In Exchange Server, In-Place Hold functionality is integrated with In-Place eDiscovery searches. You can use the In-Place eDiscovery & Hold wizard in the Exchange Administration Center (EAC) or the New-MailboxSearch and related cmdlets in Exchange Management Shell to place a mailbox on In-Place Hold.

Connect to Exchange online powershell and run the below command

New-MailboxSearch -Name “NameOfMailbox” -SourceMailboxes EmailAddress -ExcludeDuplicateMessages $True -InPlaceHoldEnabled $true -ItemHoldPeriod Number of Days -Description In-PlaceHoldDescription


Many organizations require that users be informed when they’re placed on hold. Additionally, when a mailbox is on hold, any retention policies applicable to the mailbox user don’t need to be suspended. Because messages continue to be deleted as expected, users may not notice they’re on hold. If your organization requires that users on hold be informed, you can add a notification message to the mailbox user’s Retention Comment property and use the RetentionUrl property to link to a web page for more information. Outlook 2010 and later displays the notification and URL in the backstage area. You must use the Shell to add and manage these properties for a mailbox.

Understanding Exchange 2010 server Roles

With Exchange Server Setup, you can deploy servers with specific roles through¬out the enterprise. Prior to setup and configuration, you need to decide how you will use Exchange Server 2010, what roles you will deploy, and where you will locate those roles. Afterward, you can plan for your deployment and then roll out Exchange Server.

Exchange Server 2010 implementations have three layers in their architecture: a network layer, a directory layer, and a messaging layer. The messaging layer is where you define and deploy the Exchange Server roles. The Exchange servers at the core of the messaging layer can operate in the following roles:

Mailbox Server This is a back-end server that hosts mailboxes, public folders, and related messaging data, such as address lists, resource scheduling, and meeting items. For high availability of mailbox databases, you can use database availability groups.

Client Access Server This is a middle-tier server that accepts connections to Exchange Server from a variety of clients. This server hosts the protocols used by all clients when checking messages. On the local network, Outlook MAPI clients are connected directly to the Client Access server to check mail. Remote users can check their mail over the Internet by using Outlook Anywhere, Outlook Web App, Exchange ActiveSync, POP3, or IMAP4.

Unified Messaging Server This is a middle-tier server that integrates a private branch exchange (PBX) system with Exchange Server 2010, allowing voice messages and faxes to be stored with e-mail in a user’s mailbox. Unified messaging supports call answering with automated greetings and message recording, fax receiving, and dial-in access. With dial-in access, users can use Outlook Voice Access to check voice mail, e-mail, and calendar informa¬tion; to review or dial contacts; and to configure preferences and personal options. Note that to receive faxes, you need an integrated solution from a Microsoft partner.

Hub Transport Server This is a mail routing server that handles mail flow, rout¬ing, and delivery within the Exchange organization. This server processes all mail that is sent inside the organization before it is delivered to a mailbox in the organization or routed to users outside the organization. Processing ensures that senders and recipients are resolved and filtered as appropriate, content is filtered and has its format converted if necessary, and attachments are screened. To meet any regulatory or organizational compliance require¬ments, the Hub Transport server can also record, or journal, messages and add disclaimers to them.

Edge Transport Server This serves as an additional mail routing server that routes mail into and out of the Exchange organization. This server is designed to be deployed in an organization’s perimeter network and is used to establish a secure boundary between the organization and the Internet. This server ac¬cepts mail coming into the organization from the Internet and from trusted servers in external organizations, processes the mail to protect against some types of spam messages and viruses, and routes all accepted messages to a Hub Transport server inside the organization.

These five roles are the building blocks of an Exchange organization. Note that you can combine all of the roles except for the Edge Transport server role on a single server. One of the most basic Exchange organizations you can create is one that includes a single Exchange server that provides the Mailbox server, Client Access server, and Hub Transport server roles. These three roles are the minimum required for routing and delivering messages to both local and remote messaging clients. For added security, you could deploy the Edge Transport server role in a perimeter network on one or more separate servers.

How to view current mailbox size, message count and last logon

You can use the Exchange Management Console to view who last logged on to a mailbox, the last logon date and time, the mailbox size, and the message count by completing these steps:

1. Expand the Recipient Configuration node and then select the Mailbox node.
2. Double-click the mailbox with which you want to work.
3. On the General tab, the Last Logged On By text box shows who last logged on to the mailbox, and the Modified entry shows the date and time the mailbox was last modified.
4. On the General tab, the Total Items and Size (KB) areas show the number of messages in the mailbox and the current mailbox size in kilobytes, respec¬tively.

If you want to view similar information for all mailboxes on a server, the easiest way is to use the Get-MailboxStatistics cmdlet. Here are some examples of using this cmdlet.

Get-MailboxStatistics -Server ‘corpsvr127’
Get-MailboxStatistics -Database ‘Engineering Primary’
Get-MailboxStatistics –Identity ‘cpandl\williams’

How to allow permissions on another user mailbox using powershell

Users need to access someone else’s mailbox, and in certain situations this is appropriate and preferable. You can grant permissions for a mailbox in two ways: grant access to a mailbox and its content or grant the right to send messages as the mailbox owner.

If you want to grant access to a mailbox and its contents but not grant Send As permissions, you can use the Manage Full Access Permission Wizard. In the Exchange Management Console, right-click the mailbox you want to work with and then select Manage Full Access Permission.

In the Manage Full Access Permission Wizard, click Add, and then use the Select User Or Group dialog box to choose the user or users who should have access to the mailbox. To revoke the authority to access the mailbox, select an existing user name in the Security Principal list box and then click Remove. Click Manage to set the desired access permissions.

In the Exchange Management Shell, you can use the Add-MailboxPermission and Remove-MailboxPermission cmdlets to manage full access permissions.

Adding full access permissions

Add-MailboxPermission -Identity UserWhoseMailboxIsBeingConfigured -User UserBeingGrantedPermission -AccessRights ‘FullAccess’

Add-MailboxPermission -Identity ‘’ -User ‘hiotechcandy\premr’ -AccessRights ‘FullAccess’

Removing full access permissions

Remove-MailboxPermission -Identity ‘UserBeingGrantedPermission’ -User ‘UserWhoseMailboxIsBeingConfigured’ -AccessRights ‘FullAccess’ -InheritanceType ‘All’

Remove-MailboxPermission -Identity ”’ -User ‘hiotechcandy\premr’ -AccessRights ‘FullAccess’ -InheritanceType ‘All’

If you want to grant Send As permissions, you can use the Manage Send As Permission Wizard. In the Exchange Management Console, right-click the mailbox you want to work with and then select Manage Send As Permission. In the Manage Send As Permission Wizard, click Add, and then use the Select Recipient dialog box to choose the user or users who should have this permission. To revoke this permission, select an existing user name in the Security Principal list box and then click Remove. Click Manage to set the desired Send As permissions.

In the Exchange Management Shell, you can use the Add-ADPermission and Remove-ADPermission cmdlets to manage Send As permissions.

Adding Send As permissions

Add-ADPermission -Identity UserBeingGrantedPermission -User UserWhoseMailboxIsBeingConfigured -ExtendedRights ‘Send-As’

Add-ADPermission -Identity ”’ -User ‘hiotechcandy\premr’ -ExtendedRights ‘Send-As’

Add-RecipientPermissions -identity ‘’ -Trustee ‘hiotechcandy\premr’ -AccessRights SendAs

Removing Send As permissions

Remove-ADPermission -Identity UserBeingRevokedPermission -User UserWhoseMailboxIsBeingConfigured -ExtendedRights ‘Send-As’ -InheritanceType ‘All’ -ChildObjectTypes $null -InheritedObjectType $null -Properties $null

Remove-ADPermission -Identity ”’ -User ‘hiotechcandy\premr’ -ExtendedRights ‘Send-As’ -InheritanceType ‘All’ -ChildObjectTypes $null -InheritedObjectTypes $null -Properties $null

How to hide mailbox from address book in exchange server 2010

you might want to hide a mailbox so that it doesn’t appear in the global address list or other address lists. One reason for doing this is if you have administrative mailboxes that you use only for special purposes.

To hide a mailbox from the address lists, follow these steps:

1. Open the Properties dialog box for the mailbox-enabled user account by double-clicking the user name in the Exchange Management Console.

2. On the General tab, select the Hide From Exchange Address Lists check box and then click OK.

How to Configure Auditing for exchange server

Auditing lets you track what’s happening with Exchange Server. You can collect information about logons and logoffs, permission use, and much more. Any time an action that you’ve configured for auditing occurs, it is written to the system’s security log, which you can access from Event Viewer.

You can audit Exchange activity by enabling auditing in a Group Policy object applied to your Exchange servers. This policy object can be a local Group Policy object or an Active Directory Group Policy object. You manage a server’s local Group Policy object using the Local Security Policy tool. You manage Active Directory Group Policy using the Group Policy Management Console (GPMC). GPMC is included as a Windows feature with Windows Vista and later versions of Windows. After you add GPMC as a feature, you can access it on the Administrative Tools menu.

You can enable Exchange auditing by completing the following steps:

1. Start the Group Policy Management Console by clicking Start, All Programs, Administrative Tools, Group Policy Management. You can now navigate through the forest and domains in the organization to view individual Group Policy objects.

2. To specifically audit users’ actions on Exchange Server, you should consider creating an organizational unit (OU) for Exchange servers and then define auditing policy for a Group Policy object applied to the OU. After you’ve created the OU or if you have an existing OU for Exchange servers, right-click the related policy object, and then select Edit to open the policy object for editing in Group Policy Management Editor.

3. You access the Audit Policy node by working your way down through the console tree. Expand Computer Configuration, Policies, Windows Settings, Security Settings, and Local Policies. Then select Audit Policy.

4. You should now see the following auditing options:

Audit Account Logon Events Tracks user account authentication during logon. Account logon events are generated on the authenticating computer when a user is authenticated.
Audit Account Management Tracks account management by means of Active Directory Users And Computers. Events are generated any time user, computer, or group accounts are created, modified, or deleted.
Audit Directory Service Access Tracks access to Active Directory. Events are generated any time users or computers access the directory.
Audit Logon Events Tracks local logon events for a server or workstation.
Audit Object Access Tracks system resource usage for mailboxes, information stores, and other types of objects.
Audit Policy Change Tracks changes to user rights, auditing, and trust relationships.
Audit Privilege Use Tracks the use of user rights and privileges, such as the right to create mailboxes.
Audit Process Tracking Tracks system processes and the resources they use.
Audit System Events Tracks system startup, shutdown, and restart, as well as actions that affect system security or the security log.

5. To configure an auditing policy, double-click or right-click its entry, and then select Properties. This opens a Properties dialog box for the policy.

6. Select the Define These Policy Settings check box, and then select the Success check box, the Failure check box, or both. Success logs successful events, such as successful logon attempts. Failure logs failed events, such as failed logon attempts.

7. Repeat steps 5 and 6 to enable other auditing policies. Note that the policy changes won’t be applied until the next time you start the Exchange server.

How to create a user account with a mailbox by using the New-Mailbox cmdlet in exchange 2010

Use below power shell in exchange shell to create a mailbox and account at the same time

New-Mailbox -Name “Prem Rana” -Alias “premr” -OrganizationalUnit “”
-Database “mbxDatabase1” -UserPrincipalName -SamAccountName “shanek” -FirstName “Prem”
-Initials “P” -LastName “Rana” -ResetPasswordOnNextLogon $true

How to create new mailbox in exchange 2010 using management console

To create a User Mailbox, follow the below steps:

1. Open Exchange Management Console (EMC) and expand the Recipient Configuration node

2. clip_image002


4. Right click on Mailbox and choose New Mailbox…

You can also create a new Mailbox by click on New Mailbox… from the right side pane under Actions


5. On the New Mailbox page, The available mailboxes are:

User Mailbox :
Select this button to create a mailbox that is owned by a user to send and receive e-mail messages. User mailboxes can’t be used for resource scheduling.

Room Mailbox :
Select this button to create a mailbox that will be used as a location resource for scheduling meetings. Room mailboxes can be included in meeting requests as resources and can be configured to automatically process incoming requests.
If you create a new user account for the room mailbox in Active Directory, it will be disabled. If you plan to associate the room mailbox with an existing account, you must select a disabled account.

Equipment Mailbox :
Select this button to create a mailbox that will be used as a resource for scheduling meetings. Equipment mailboxes can be included in meeting requests as resources and can be configured to automatically process incoming requests.

Linked Mailbox :
Select this button to create a user mailbox that is accessed by a user in a separate, trusted forest. You must still create a user account in the forest in which Exchange Server resides. This is required to create the necessary Active Directory object for storing the mailbox information.
Choose User Mailbox then click Next

6. On the User Type page, you can either create a new email for a new user or a new email for an existing user in Active Directory.
New User : Select this button to simultaneously create a new user in Active Directory and mail-enable the user.
Existing users : Select this button to mail-enable one or more existing users.
If you already have an Active Directory user wish to create for him/her a new email, then Select Existing User and then click Add to open the Select User dialog box. This dialog box displays a list of user accounts in the forest that aren’t mail-enabled or don’t have Exchange mailboxes. Select the user accounts you want to mail-enable, and then click OK to return to the wizard.
We will be creating a new user, so select New User and then click Next


7. On the User Information page, fill the user information and then click Next
If you want to create the user in a specific OU, then select the checkbox beside Specify the organization unit rather than using a default one and then click Browse, select the appropriate OU and click OK.
Fill User information and click Next

8. Type the Alias for your user mailbox, and then specify the mailbox database, retention policy, exchange ActiveSync mailbox policy and Address book policy ( if available )
I will be only selecting the mailbox database, as I didn’t create any policy yet.
To select a database, select Specify the mailbox database rather than using a database automatically selected, then click Browse
The available databases will be displayed. Select the mailbox database and then click OK
The selected database will be displayed, Click Next


9. Choose the Archive Settings.
You can have a local archive or a remote hosted archive for your user mailbox.
Items will be moved automatically from the primary user mailbox to the archive based on the retention settings.

10. Review the configuration settings and then click New

11. The wizard will be completed successfully. You can click on Finish to close the wizard.

12. Finally, you can see the new user created in the Mailbox node under Recipient Configuration

Interview Questions Exchange 2013

1. Question 1. What’s New In Exchange Server 2013?

Answer :

Below are the new features in Exchange Server 2013:

o New Unified Management console called Exchange Admin Center

o Server Roles architecture changed to two Server Roles – Mailbox Server Role and Client Access Server Role

o Public Folders are now in Mailbox Databases which can be replicated to other mailbox databases

o Site Mailbox introduced to allow the user to access the SharePoint sites and emails from Outlook 2013, using the same client interface

o Exchange 2013 Offers greater integration with SharePoint 2013 and Lync 2013

o Brand new Outlook Web App optimized for tablets and mobile devices and also for desktops and laptops

o Unified Messaging in Exchange 2013 comes with same voice mail features in Exchange 2010, but the architecture change to have only two server roles made all the UM related components, services and functionality are now available in Mailbox Server Role

o Users can Move Mailboxes in batches where it has an option to send mailbox move reports as emails

o Lot of enhancement in the Database Availability Group like Managed Availability and Managed Store etc

o Exchange work load is a new feature in Exchange 2013 defined for the purpose of Exchange System Resource Management

o Exchange 2013 is completely rewritten so deploying and keeping exchange 2013 to up to date is now easier

o Data Loss Preventions is a new feature which allows to protective the company sensitive data and inform user of internal compliance policies

2. Question 2. What Is Exchange Admin Center?

Answer :

Exchange Admin Center is the new web based Exchange Management Console for Exchange Server 2013, it allows for ease of use and is optimized for management of On-Premises, Online and hybrid Exchange deployments. EAC replaces Exchange Management Console and Exchange Control Panel, but ECP is still the url for Exchange Admin Center.

New features in Exchange Admin Center:

o List View – More than 20,000 objects can be viewed in EAC, where legacy ECP allows only 500 objects

o Add/Remove columns for recipients

o Public folders can be managed from Exchange Admin Center

o Long running process will be notified in the notification bar

o Role Based Access Control user editor can be done from EAC

o Unified Messaging tools like call statistics, and user call logs can be accessed from EAC

3. Question 3. Explain The Exchange 2013 Architecture?

Answer :

Legacy versions of Exchange 2007 and Exchange 2010 released with 5 server roles, ie, Mailbox, Client Access, Hub Transport, Unified Messaging and Edge Transport server. Server role architecture has been changed in Exchange 2013 which released with only two server roles.

Mailbox Server role: It holds the same function of Mailbox, the client access protocols, Hub Transport and Unified Messaging server role in Exchange 2010

Client Access Server role: work as the client access server role in Exchange 2010, Exchange 2010 work as  only stateless server, where it doesn’t do any data rendering,  and nothing will  be stored or queued in Client Access Server role. CAS offers all usual client access protocols: HTTP, POP and IMAP, and SMTP

4. Question 4. Why Exchange 2013 Architecture Has Been Changed With Two Server Roles?

Answer :

Exchange 2007 and 2010 were architect with certain technology constraint that existed at that time, where CPU performance was the Key constraint when Exchange 2007 was released and to alleviate the situation Server roles were introduced. However server roles in Exchange 2007 and Exchange 2010 are tightly coupled

Nowadays, CPU horse power is less expensive and it is not a constrain factor, with that constraint lifted, primary goal for Exchange 2013 is simplicity of scale, hardware utilization and failure isolation. So Microsoft reduced the number of server roles to two as Client Access Server Role and Mailbox Server Role

5. Question 5. What Are The Benefits On The Architecture Change By Having Two Server Roles In Exchange 2013?

Answer :

Having two server roles with Mailbox Server includes all the traditional components fount in Exchange 2010: the client access protocols, transport service, mailbox databases and unified messaging and the Client Access Server role to provide authentication, limited redirection and proxy services.

New architecture provides the below benefits:

o The Client Access Server and Mailbox Server become “Loosely Coupled”. All process and activity for a specific mailbox occurs on the mailbox server that holds the active database copy, eliminating concerns of version compatibility between CAS and Mailbox Server

o Version Upgrade flexibility – Client Access server can be upgraded independently and in any order.

o Session affinity to client access server role is not required – In Exchange 2013, Client access and mailbox components available on the same mailbox server, because the client access server simply proxies all connections to a specific mailbox server, no session affinity is required

o Only two namespace is required for Exchange 2013

6. Question 6. What Is Change Related To Mapi Access Using Outlook In Exchange 2013?

Answer :

Two server role architects changed the outlook client connectivity behaviour; RPC is no longer a supported direct access protocol. This means that all the outlook connectivity must take place using RPC over HTTP knows as Outlook Anywhere. Because of this behaviour, there is no need to have RPC client access service on CAS which reduces two name spaces that required for site-resilient solution.

7. Question 7. Explain The Change In Outlook Client Connection Behaviour When Compared With Exchange 2010?

Answer :

Outlook clients no longer connect to a server FQDN as they have done in all previous versions of Exchange. Outlook uses Autodiscover to create a new connection point comprised of mailbox GUID, @ symbol, and the domain portion of the user’s primary SMTP address. This change results in a near elimination of the unwelcome message of “Your administrator has made a change to your mailbox. Please restart.” Only Outlook 2007 and higher versions are supported with Exchange 2013.

8. Question 8. What Is Managed Store In Exchange 2013?

Answer :

Managed store is the name of the newly rewritten information store process, Microsoft.Exchange.Store.Service.exe and Microsoft.Exchange.Store.worker.exe, it is integrated with Microsoft Exchange replication server to provide higher availability through improve resiliency. Also the Managed store has been architected to enable more granular management of resource consumption and faster root cause analysis though improved diagnostics.

Managed Store works with replication service to manage mailbox databases, which continues to ESE as DB engine, Exchange 2013 includes change the mailbox database schema that provides many optimization over previous versions of Exchange and Replication Services is responsible for all availability related to Mailbox Servers. This change provides faster database failover and better disk failure handling.

9. Question 9. What Is A Site Mailbox?

Answer :

Site Mailbox is a new type of mailbox in Exchange 2013, where it improves collaboration and user productivity by allowing access to both documents in a SharePoint site and email messages in outlook 2013 using the same client interface.

10. Question 10. What Happened To Public Folders In Exchange 2013?

Answer :

Special type mailbox called Public folder mailbox introduced in Exchange Server 2013, which will store both the hierarchy and public folder content. This provides an advantage of the existing high availability and storage technologies of the mailbox store. Legacy Public folder database concept not in exchange 2013 and Public Folder replication now user the continuous replication model as like Mailbox Database.

11. Question 11. How The Mail Flow Occur In Exchange Server 2013?

Answer :

Due the architectural change, Mail flow in Exchange 2013 occurs via Transport Pipeline, it is collection of Transport services, connections, components and queues that work together to route the messages to the categorizer in the transport service on a mailbox server inside the organization.

Messages from outside organization enter the transport pipeline through a receive connector in the Front End Transport service on a client access server and then routed to the Transport Service on a Mailbox Server and the Mailbox Transport Delivery Service deliver the email to local mailbox database

Message from inside organization enter the Transport Service on a Mailbox Server in following ways, receive connector, Pick Up or Replay Directory, Mailbox Transport Service or Agent Submission. Those emails can be relayed to Front End transport service on Client Access Server using the Transport Service on Mailbox Server and sent outside

12. Question 12. Explain The New Transport Pipeline In Short?

Answer :

Front End Transport Service in Client Access Server acts as a stateless proxy for all inbound and outbound external SMTP traffic for Exchange 2013 organization. It won’t inspect message content, only communicates with the Transport Service on a Mailbox Server, and doesn’t queue any messages locally.

Transport Service in Mailbox server is identical to Hub Transport server, it handles all SMTP mail flow for the organization, perform message categorization, and performs content inspection. It won’t communicate directly with Mailbox Database that task will be handled by Mailbox Transport Service. So the Transport Service routes messages between the mailbox transport service, the transport service and the front end transport service.

Mailbox Transport Service running on Mailbox server consists of two separate services: the Mailbox Transport Submission Service and Mailbox Transport Delivery Service.

Mailbox Transport Delivery Service receives emails from Transport Service on the local or different mailbox server and connects to the local mailbox databases using Exchange RPC to deliver the message

Mailbox Transport Submission Service connects to local mailbox database using RPC to retrieve messages and submits the messages over SMTP to the Transport Service on the local Mailbox server or other Mailbox Servers.

13. Question 13. What Are The Enhancements In Batch Mailbox Move On Exchange 2013?

Answer :

Below are the enhancements on Exchange 2013 Batch Mailbox Moves:

o Multiple mailboxes move in large batches.

o Email notification during move with reporting.

o Automatic retry and automatic prioritization of moves.

o Primary and personal archive mailboxes can be moved together or separately.

o Option for manual move request finalization, which allows you to review a move before you complete it.

14. Question 14. What Are New Options Included In Exchange 2013 Related With High Availability And Site Resilience?

Answer :

Managed Availability – Internal Monitoring and recovery are integrated to prevent failures, proactively restore services, and initiate failovers automatically or alert admin to take action.

Managed Store – Integrated with Microsoft Exchange Replication Service to provide higher availability

Multiple Databases per disk – Exchange 2013 supports multiple databases both active and passive on same disk.

Automatic Reseed – If a disk fails, database copy stored on that disk is copied from the active database copy to a spare disk on the same server.

Automatic recovery from storage failures

Lagged copies can now care themselves to a certain using automatic log play down

Single copy alert task is removed and included in the managed availability component

DAG networks can be automatically configuration by the system bases on the configuration settings, DAG now can distinguish between MAPI and Replication networks and configure DAG network automatically.

15. Question 15. What Are The Features Discontinued In Exchange 2013 When Compared With Exchange 2010?

Answer :

Below are few features that are discontinued in Exchange 2013:

o Hub Transport Server Role and Unified Messaging Server

o Exchange Management Console and Exchange Control Panel

o Outlook 2003 support and RPC over TCP method of Mailbox access is removed

o S/MIME, Search folders and Spell check in OWA removed

o Linked Connectors are removed

o Anti-spam agents can be management only from Exchange Management Shell

o Connection filtering agent removed

o Managed Folder are removed

o Tools like Exchange Best Practice Analyzer, Mail flow troubleshooter, performance monitor, performance troubleshooter and routing log viewer are removed

16. Question 16. What Are The Features Discontinued In Exchange 2013 When Compared With Exchange 2007?

Answer :

Below are few features discontinued in Exchange 2013 that are available in Exchange Server 2007

o Storage Groups and Public Folder Databases

o Exchange WebDAV API and ESE streaming backup API

o High Availability concepts CCR, LCR, SCR & SCC are not available

o Export-Mailbox / Import-Mailbox Cmdlets and Move-Mailbox cmdlets set

o Managed folders

17. Question 17. What’s New In Outlook Web App 2013?

Answer :

Lot of new feature available in Outlook Web App 2013 below are few new features:

o Apps can be accessed from Outlook Web App

o Contacts can be linked to see all the data in a single view

o Ability to connect to user’s linkedIn account and add the contacts automatically to OWA

o Multiple calendars can be viewed in a Merged view

o Streamlined user interface for tablets and smartphones which supports use of touch

18. Question 18. Inform The Features That Are Not Available On Owa 2013?

Answer :

Below are the features that are available in previous versions but not available on Exchange Server 2013 Outlook Web APP:

o Shared Mail folders access is not available

o Distribution list moderation cannot be done from OWA

o S/MIME support

o Reading pane at the bottom of the window

o Ability to reply to email messages sent as attachments

o Search folders in not available

19. Question 19. What Are The Prerequisites Required To Install Exchange Server 2013?

Answer :

Below prerequisites are required to install Exchange Server 2013:

Operating System:

o Windows Server 2008 R2 Service Pack 1 or later

o Windows Server 2012

Additional Prerequisites:

o Microsoft .NET Framework 4.5 (pre install in Windows Server 2012)

o Windows Management Framework 3.0

o Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit

o Microsoft Office 2010 Filter Pack 64 bit

o Microsoft Office 2010 Filter Pack SP1 64 bit

o ADDS and few windows features

Domain Controller:

o Forest functional level has to Windows Server 2003

o Schema Master run on Windows Server 2003 SP2 or later

20. Question 20. On Which Operating System Database Availability Group Is Supported?

Answer :

DAG is supported on Windows Server 2012 Standard or Datacenter Editions or Windows Server 2008 R2 SP1 Enterprise Edition. Windows Server 2008 R2 Sp1 standard edition won’t support DAG

21. Question 21. On What Conditions Exchange 2013 Can Coexists With Previous Version Of Exchange Servers?

Answer :

Exchange 2003 and Earlier versions: Not Supported

Exchange 2007: Exchange 2007 SP3 with Update Rollup 10 on all Exchange 2007 servers and Exchange 2013 CU2 and later can coexist

Exchange 2010: Exchange 2010 SP3 on all Exchange 2010 Servers and Exchange 2013 CU2 or later can coexist

22. Question 22. What Are The Editions Available In Exchange Server 2013?

Answer :

Exchange 2013 available in two editions: Standard Edition and Enterprise Edition

Standard Edition allows only 5 databases to mounted (including active and passive copy) and Enterprise Edition allows 50 databases on RTM version of Exchange and 100 databases on CU2 and later versions. Recovery Database will not be counted on this.

23. Question 23. What Will Happen To Exchange 2013 Rtm Version When 120 Days Trial Period Expires?

Answer :

Exchange 2013 functionality will not loss when trial period expires, so you can maintain lab without having to reinstall the trial version.

24. Question 24. What The Supportable Clients That Can Access Exchange 2013 Mailbox?

Answer :

o Exchange 2013 mailbox can be access by the following clients

o Outlook 2013

o Outlook 2010 SP1 with Outlook 2010 November 2012 update

o Outlook 2007 SP3 with Outlook 2007 November 2010 update

o Entourage 2008 for Mac, Web Services Edition

o Outlook for Mac 2011

25. Question 25. Mention What Are The New Features In Ms Exchange 2013?

Answer :

Integration with Lync and SharePoint: With site mailboxes and in-place eDiscovery, it offers a greater integration with Microsoft Sharepoint and Lync

Provide a resilient solution: It built upon the exchange server 2010 and redesigned for simplicity of scale, feature isolation and hardware utilization

Supports a multigenerational workforce: From multiple sources users can merge contacts as well as smart search allows to search people in the network

Provide an engaging experience: MS web app focused on a streamlined user interface that supports the use of touch, enhancing the use of mobile devices

Meet the latest demand: With improved search and indexing, you can search across Lynch 2013, Exchange 2013, SharePoint 2013, etc.

DAG system: A new evolution of exchange 2010 DAG

26. Question 26. Mention What Is Recommended When You Are Using An Exchange Account For Your Work, When You Are Offline?

Answer :

It is suggested that you use Cached Exchange Mode when you are using an exchange account for your work, as it eliminates all the reason to work offline. With Cache Exchange Mode, you can keep continuing working even if you are disconnected with the network.  Cache Exchange Mode uses a folder file (.ost) and manages a synchronized copy of the items in all folder in the mailbox, when you are offline.  As soon as you are connected to the network, it syncs your data automatically to the server without losing any data.

27. Question 27. Mention What Are The Roles In Ms Exchange 2013?

Answer :

In MS exchange 2013, there are two roles Client Access Server and Mailbox Server.

28. Question 28. Mention What Is The Role Of Client Access Server?

Answer :

The Client Access Server gives connectivity to various services like:

o Microsoft Office Outlook

o Outlook Web App

o Mobile devices


o Accepts mail from delivers mail to other mail hosts on the internet

o Gives unified namespace, network security and authentication

o Handles all client requests for Exchange

o Routes requests to the correct mailbox server

o Allows the use of layer 4 (TCP affinity) routing

29. Question 29. Mention What Is The Role Of Mailbox Server?

Answer :

Mailbox servers help in:

o e-mail storage

o Host public folder databases

o Host mailbox databases

o Calculate e-mail address policies

o Performs multi-mailbox searches

o Provide high availability and site resiliency

o Provide messaging records management and retention policies

o Handle connectivity as clients don’t connect directly to the mailbox services

o For given mailbox, it provides all core exchange functionality

o When a database fails over, it also fails access to the mailbox

30. Question 30. Explain What Are The Important Features Of Transport Pipeline?

Answer :

Transport pipeline is made up of three different services:

Front end transport service: It does basic message filtering based on domains, connectors, senders and recipients. It only connects with the transport service on a mailbox server and does not backlog any messages locally

Transport service: It runs on all mailbox servers, and it handles SMTP mail flow. It helps in message categorization and content inspection. The transport services routes messages between the Mailbox Transport service, the Transport Service and Front End Transport service.  This service does not queue messages locally

Mailbox Transport: This system includes receiving and sending SMTP to the transport service from mailbox using RPC (Remote Procedure Call).

31. Question 31. Explain What Is The Role Of Categorizer?

Answer :

Categorizer performs following functions

Recipient Resolution: The e-mail address of the recipient is resolved to decide whether the recipient has got a mailbox in the Exchange Organization or an external e-mail address

Routing Resolution: Once the information regarding the recipient is resolved, the ultimate destination for the mail is routed, and the next hop are determined

Content Conversion: Once the mail has reached its determined address, the SMTP is converted into readable format like HTML, rich text format or plain text

32. Question 32. Explain The Term Dag (data Availability Group)?

Answer :

DAG or Data Availability Group is a framework build is MS Exchange 2013.  It is a group of upto 16 mailbox server that hosts a set of databases and provides automatic database level recovery due to failure of servers of databases.

33. Question 33. Mention How Many Types Of Delivery Groups Found In Ms Exchange 2013?

Answer :

In MS Exchange 2013, there are five types of delivery groups

o Routing DAG

o Mailbox delivery groups

o Connector source service

o AD site

o Server List

34. Question 34. Explain How Message Is Delivered To The Mailbox Database In Exchange 2013?

Answer :

In exchange 2013, after the message reaches the target mailbox server in the destination AD site, the transport service avails SMTP to carry the message to the mailbox.  After that, using RPC, Transport Service delivers the message to the local mailbox.

35. Question 35. What Action Does Front End Transport Service Does?

Answer :

Front end transport service does one of the following actions based on the number and type of the recipients

o For the message with a single mailbox recipient, choose a mail box server in the target delivery group and based on the proximity of the AD site, give preference to the mail box server

o For the message with multiple or several mailbox recipients, it uses the first 20 recipients to select a mailbox in a closest proximity or delivery group, based on the AD site proximity

o If the message has no mailbox recipients, it choose a random mailbox server in the local AD site

36. Question 36. Mention What Is The Function Of Mailbox Transport Submission Service?

Answer :

Mailbox Transport Submission service does one of the following actions based on the number and type of recipients.

For the message having only one mailbox recipient, it chooses a mailbox server in the target delivery group and give priority to the mailbox server based on the AD site proximity

With multiple mailbox recipients, it uses first 20 recipients to choose a Mailbox server in the closest delivery group, based on the AD site proximity

If there is no mailbox recipient, select a mailbox server in the local delivery group

37. Question 37. How The Flow Of The Mail Is Tracked In Ms Exchange 2013?

Answer :

To track message flow in MS Exchange 2013, Delivery Reports are used.  It is applicable for Outlook and Outlook web only.  However, Message Tracking Logs are also helpful to know the flow of the mail.