User Experience With Outlook 2013 and Outlook Web App 2013

User Experience With Outlook 2013 and Outlook Web App 2013

Common user experience present in both Outlook and Outlook Web App 2013

1. Conversation Actions & View
2. Modification of server side junk email allow/block list
3. Modification of server side inbox rules
4. Management of memberships of Exchange Distribution Groups
5. Set external/internal message and from/to date range
6. Integration to allow access to remote calendar, share local calendar
7. Combine Multiple Calendars in One View
8. Fast searching using pre-built search index
9. Integrated E-Mail Archive
10. View of MailTips
11. GAL Photos and UM Name along with availability
12. Allows viewing of compatible attachments without leaving Outlook
13. Policy Management Set and view retention policy for folders
14. Message preview shown to the right of messages
15. Stored Nicknames on the server
16. Real time calendar view for meeting and room bookings
17. AD Rights Management Services

Additional User Experience Features Outlook have where Outlook Web apps doesn't get user experience

1. Export and Import of Contacts
2. Export and Import to PST
3. Ability to add Macros
4. Resend the email message
5. Ability to reply to embedded email messages
6. Calendar Preview in Meeting Requests
7. Expanding distribution groups to see all members
8. Adding multiple Exchange account accross different server and domain
9. Ability to moderate distribution list
10. Subscribe to RSS feeds
11. Reading pane at the bottom of the window

Ref: http://blogs.technet.com/b/mconeill/archive/2013/08/29/outlook-2013-vs-owa-2013.aspx

Combining Muliple DAG and MAPI networks - Exchange 2010 DAG Network

Combining Muliple DAG and MAPI networks - Exchange 2010 DAG Network

When you have Primary Site and secondary site hosting Exchange 2010 Mailbox server and configuring DAG network. You can able to view four network under DAG network

 2 MAPI network one in Primary Site (170.0.0,x/16) and one in secondary site (170.1.0,x/16).
 2 Replication network one in Primary Site (30.0.1.0/24) and one in secondary site (30.0.2.0/24).

This can be collasped easily using the following Exchange Powershell Command

Set-DatabaseAvailabilityGroupNetwork DAG1DAGNetwork01 -Subnets 170.0.0,0/16,170.1.0,0/16

Set-DatabaseAvailabilityGroupNetwork DAG1DAGNetwork02 -Subnets 30.0.1.0/24,30.0.2.0/24

Still the network holds the default name inorder to have proper nomenclature run the following command

Set-DatabaseAvailabilityGroupNetwork DAG1DAGNetwork01 -Name MAPI_Network

Set-DatabaseAvailabilityGroupNetwork DAG1DAGNetwork02 -Name Replication_Networ

The following command will disable replication traffic through the MAPI network.

Set-DatabaseAvailabilityGroupNetwork MAPI_Network –ReplicationEnabled $false

In Exchange Server 2013 we don't need to perform the collapsing of DAG Network since it does automatically Ref: http://technet.microsoft.com/en-us/library/dd297927%28v=exchg.150%29.aspx

Outlook Error - The name cannot be resolved. The name cannot be matched to a name in the address list.

Outlook Error - The name cannot be resolved. The name cannot be matched to a name in the address list.

Solution:

• Check you can able to access the user mailbox using Outlook Web Access. 
• Verify the user object is getting listed in the Global Address list
• Check whether user is configured Hidden from Exchange address lists
• Open Adsiedit- Go to Domain partion - Select the user object - Right Click on the user and select Properties - check the value of LegacyExchangeDN 
• Also verify the below attribute value which plays vital role in Exchange

homeMDB
homeMTA
legacyExchangeDN
mail
mailNickname
msExchHomeServerName
msExchMailboxGuid
msExchMailboxSecurityDescriptor
proxyAddresses

Outlook Error - The name cannot be resolved. The name cannot be matched to a name in the address list.

Outlook Error - The name cannot be resolved. The name cannot be matched to a name in the address list.

Solution:

• Check you can able to access the user mailbox using Outlook Web Access. 
• Verify the user object is getting listed in the Global Address list
• Check whether user is configured Hidden from Exchange address lists
• Open Adsiedit- Go to Domain partion - Select the user object - Right Click on the user and select Properties - check the value of LegacyExchangeDN 
• Also verify the below attribute value which plays vital role in Exchange

homeMDB
homeMTA
legacyExchangeDN
mail
mailNickname
msExchHomeServerName
msExchMailboxGuid
msExchMailboxSecurityDescriptor
proxyAddresses