Exchange Server 2013 - License Cost and Product Support End Date

Exchange Server License Cost and Product support end date

Sometimes we try to find out the Microsoft product license cost and its expiration time period. The below url provides more detail …

For Example 

Exchange server 2013 License Cost

http://support.microsoft.com/lifecycle/search/

 

Exchange Server 2007 Product end date

http://support.microsoft.com/lifecycle/search/default.aspx?sort=PN&alpha=Exchange+Server+2013&Filter=FilterNO

Exchange Server 2013 email size restriction

Exchange Server 2013 email size restriction

Email size in Exchange server plays an important role for the organization since it acts important factor for bandwidth, storage limit, email queue, CPU utilization and mailbox size. The below article provide deeper stuff on how email size restriction plays in the Exchange server 2013.

The email message size value you are trying to configure should be 33% larger than the actual message sizes. For example if you want to allow 30 MB email size then the message size parameter should be 43 MB value. The reason behind is it uses Base64 encoding which increase the message size to 33% of the real message size.

The email size restriction for user mailbox will be applied in the following order

1. Global Transport configuration settings
2. Send connector size restriction
3. Receive connector size restriction
4. In the user mailbox properties of send and receive size limit

It’s also controlled in the configuration file of Exchange Server based upon the application

1. Exchange Web Service (EWS)
2. Outlook Web Access (OWA)
3. ActiveSync

Thumb Rule: If the upper order is more restrictive, then this will override the below order. For example if the Global Transport setting send receive size is 10 MB and Send connector size is 100MB. The user will not able to send more email more than 10 MB size.
Now let us understand in detail on how each component works

• Global Transport configuration settings

To verify global transport settings all Hub Transport servers in the Exchange Organization. The default of send and receive size is 10 MB. Complete global transport configuration setting can be displayed used the command Get-TransportConfig | fl
To check only the send and receive size of email
Get-TransportConfig | ft MaxSendSize, MaxReceiveSize
For example if you want to modify the sending and receiving email message size to 100 MB in the global Tranport configuration
Set-TransportConfig –MaxSendSize 20MB –MaxReceiveSize 100MB

• Send connector size restriction

Send connector are used to send emails out of the exchange organization and the default size is 10 MB. To verify and modify the send connector size
Get-SendConnector | ft name, MaxMessageSize
Set-SendConnector –MaxMessageSize 50MB

• Receive connector size restriction

Receive connector are used to receive emails from the internet or application and the default size is 10 MB. To verify and modify the receive connector size
Get-ReceiveConnector | ft name, MaxMessageSize
Set-ReceiveConnector –MaxMessageSize 50MB

• In the user mailbox properties of send and receive size limit

The send and receive email message size can be granular controlled in the user mailbox properties. To verify the and modify the size
Get-mailbox | ft Name, MaxSendSize, MaxReceiveSize
Set-Mailbox “test” –MaxSendSize 20MB –MaxReceiveSize 20MB
 Exchange Server Configuration File – Email Size Restriction

• 1.     Outlook Web Access

When email sent over the Outlook Web Access the email size is also verified in the web config file located in %ExchangeInstallPath%ClientAccess\Owa\web.config
Default Email message size in OWA:
maxAllowedContentLength="35000000" (value in bytes) = Approx 33 MB
maxReceivedMessageSize="35000000" (value in bytes) = Approx 33 MB
maxRequestLength="35000" (value in kilobytes) = Approx 34 MB
You can change this value to whatever size you need.

• 2.     Exchange Web Services (EWS)

Just like OWA, when email is sent using the EWS application (Mac Outlook, Entourage) the message size is justified with the parameter value located in the file ExchangeInstallPath%ClientAccess\exchweb\ews\web.config
Default Email message size in EWS:
maxAllowedContentLength="67108864" (value in bytes) = Approx 64 MB
maxReceivedMessageSize="67108864" (value in bytes) = Approx 64 MB
You can change this value to whatever size you need.

• 3.     ActiveSync

When email is sent using the ActiveSync handheld device the message size is justified with the value located in the file %ExchangeInstallPath%ClientAccess\Sync\web.config
Default Email message size in Activesync:
(value in bytes) Approx 9.7 MB
maxRequestLength="10240" (value in kilobytes ) = Approx 10 MB

Error Message and NDR

There are various error message which is listed below will occur if the value is not configured as per the above rule.

Error 1:
The following recipient(s) could not be reached:
raji@mail.com on 01/15/2014 3:54 PM
This message is larger than the current system limit or the recipient’s mailbox is full. Create a shorter message body or remove attachments and try sending it again.


Error 2:
The following recipient(s) could not be reached
raji@mail.com on 01/15/2014 3:54 PM
This message is larger than the current system limit or the recipient’s mailbox is full. Create a shorter message body or remove attachments and try sending it again.


Error 3:
Delivery has failed to these recipients or distribution lists:
administrator@mail.com
This message exceeds the maximum message size allowed. Microsoft Exchange will not try to redeliver this message for you. Please make the message smaller -- by removing attachments, for example -- and try sending it again, or provide the following diagnostic text to your system administrator.
Diagnostic information for administrators:
Generating server: MBX01.mail.com
administrator@mail.com
#550 5.2.3 RESOLVER.RST.SendSizeLimit; message too large for this sender ##

Error 4
OWA Error - The request filter module is configured to deny a request that exceeds the request content length”

Error 5
EWS Error -   Email is goes in drafts or never leaves the outbox and the client receives an “exceeded the size limit”
Reference:
http://technet.microsoft.com/en-us/library/hh529949%28v=exchg.150%29.aspx
http://technet.microsoft.com/en-us/library/bb124345(v=exchg.150).aspx

Exchange 2013 Outlook Anywhere

Exchange 2013 Outlook Anywhere – RPC Over HTTP

Exchange server 2013 Outlook Anywhere is used to connect the outlook internally and from the internet. Exchange server 2013 uses two EXHTTP nodes which get generated xml file automatically. Please find the below XML generated for the user account.

Output of Outlook AnyWhere in Exchange 2013 CAS Server

[PS] C:\Windows\system32>Get-OutlookAnywhere -Server CASSRV1

RunspaceId                                                           : 0a620a85-b852-46de-ab5c-f7396685e7d9

ServerName                                                         : CASSRV1

SSLOffloading                                                       : True

ExternalHostname                                                : webmail.mail.com

InternalHostname                                                 : webmail.mail.com

ExternalClientAuthenticationMethod                  : Ntlm

InternalClientAuthenticationMethod                    : Ntlm

IISAuthenticationMethods                                     : {Ntlm}

XropUrl                            :

ExternalClientsRequireSsl                                  : True

InternalClientsRequireSsl                                  : False

MetabasePath                                                   : IIS://CASSRV1.MAIL.COM/W3SVC/1/ROOT/Rpc

Path                                                                    : E:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc

ExtendedProtectionTokenChecking                 : None

ExtendedProtectionFlags                                   : {}

ExtendedProtectionSPNList                               : {}

AdminDisplayVersion                                       : Version 15.0 (Build 775.38)

Server                                                              : CASSRV1

AdminDisplayName                                          :

ExchangeVersion                                              : 0.20 (15.0.0.0)

Name                                                                : Rpc (Default Web Site)

DistinguishedName                                              : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=CASSRV1,CN=Servers,CN=Exchange Administrative   Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Mail,CN=Microsoft                                      Exchange,CN=Services,CN=Configuration,DC=AD,DC=MAIL,DC=COM

Identity                                                                  : CASSRV1\Rpc (Default Web Site)

Guid                                                                        : 101e738e-9dc5-48d1-9516-ff6ac7a01859

ObjectCategory                                                    : AD.MAIL.COM/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory

ObjectClass                                                           : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}

WhenChanged                                                     : 1/22/2014 10:38:54 AM

WhenCreated                                                       : 9/18/2013 11:39:02 AM

WhenChangedUTC                                              : 1/22/2014 5:08:54 AM

WhenCreatedUTC                                                : 9/18/2013 6:09:02 AM

New Feature in Exchange 2013 Outlook Anywhere

Inorder to achieve the HTTP connection for internal outlook client and HTTPS connections for the outlook client connection over the internet .Then we need to have follow the below rule.

§  Separate hostname for the internalhostname and externalhost should be different

§  The Internalhostname should not be published in the internet ISP DNS

§  The InternalClientsRequireSsl should be set as false and ExternalClientsRequireSsl should be set as true.

Powershell Command

Get-OutlookAnywhere | Set-OutlookAnywhere -InternalHostname "Outlook.mail.com" -InternalClientsRequireSsl $false -ExternalHostname "webmail.mail.com" -ExternalClientsRequireSsl $true

How it works ….

By default always the first HTTP part taken by the outlook to get the details of the url if it fails it goes to the next HTTP part of XML file. In the XML file under the protocol of EXHTTP you can able to view the SSL is off and internalhostname as Outlook.mail.com for the first part HTTP protocol used to connect the internal outlook client. If it fails then it moves to the next part of HTTP part to get connected for the internal outlook client

        EXHTTP

        Outlook.mail.com

        Off

        Ntlm

In the XML file under the protocol of EXHTTP you can able to view the SSL is off and externalhostname as webmail.mail.com. Since the first name is unable to resolve fqdn over the internet hence it gets connected to second part of the EXHTTP part. Hence it move to SSL connection

       EXHTTP

        webmail.mail.com

        On

        Ntlm

In Exchange server 2013 public folder will be get connected by using the below piece of XML file

              PFHierarchy@mail.com

Note: On performing the above change in co-existence mode of Exchange 2007/2010 with Exchange 2013 there will no impact for the legacy exchange user mailbox. Since it connect using RPC/TCP for MAPI connectivity

XML File - Generated on Email Test Configuration in Outlook

      Raji S

      /o=Mail/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Raji_S

      Raji_S@mail.com

      19fbc7b1-2b71-42c6-b399-6d5465ff93c8

      email settings     False

       EXCH

        5719c3f9-d590-44ea-9e21-ff6fe7b304cd@mail.com

        /o=Mail/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=5719c3f9-d590-44ea-9e21-ff6fe7b304cd@mail.com

        73C08307

        /o=Mail/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=5719c3f9-d590-44ea-9e21-ff6fe7b304cd@mail.com/cn=Microsoft Private MDB

        webmail.mail.com

        AD.MAIL.COM

        https://webmail.mail.com/EWS/Exchange.asmx

        https://webmail.mail.com/EWS/Exchange.asmx

        https://webmail.mail.com/EWS/Exchange.asmx

        https://CASSRV1.mail.com/ecp/

        ?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=AD.MAIL.COM

        ?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=AD.MAIL.COM

        PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=AD.MAIL.COM

        ?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=AD.MAIL.COM

        ?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=AD.MAIL.COM

        PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=AD.MAIL.COM

        Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=AD.MAIL.COM

        https://webmail.mail.com/EWS/Exchange.asmx

        https://webmail.mail.com/EWS/UM2007Legacy.asmx

        https://webmail.mail.com/OAB/322aa0e9-256a-4886-bbcb-62e7aaf4cb80/

        off

        none

EXPR

        webmail.mail.com

        On

        Ntlm

        https://webmail.mail.com/EWS/Exchange.asmx

        https://webmail.mail.com/EWS/UM2007Legacy.asmx

        https://webmail.mail.com/OAB/322aa0e9-256a-4886-bbcb-62e7aaf4cb80/

        on

        none

        https://webmail.mail.com/EWS/Exchange.asmx

       APAC

WEB

        https://webmail.mail.com/OWA/

EXCH

            https://webmail.mail.com/EWS/Exchange.asmx

            https://webmail.mail.com/OWA/

EXPR

            https://webmail.mail.com/EWS/Exchange.asmx

            

EXHTTP

        Outlook.mail.com

        Off

        Ntlm

        https://webmail.mail.com/EWS/Exchange.asmx

        https://webmail.mail.com/EWS/Exchange.asmx

        https://webmail.mail.com/EWS/Exchange.asmx

        https://gurcasv01.ad.mail.com/ecp/

        ?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=AD.MAIL.COM

        ?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=AD.MAIL.COM

        PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=AD.MAIL.COM

        ?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=AD.MAIL.COM

        ?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=AD.MAIL.COM

        PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=AD.MAIL.COM

        Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=AD.MAIL.COM

        https://webmail.mail.com/EWS/Exchange.asmx

        https://webmail.mail.com/EWS/UM2007Legacy.asmx

        https://webmail.mail.com/OAB/322aa0e9-256a-4886-bbcb-62e7aaf4cb80/

        On

        None

EXHTTP

        webmail.mail.com

        On

        Ntlm

        https://webmail.mail.com/EWS/Exchange.asmx

        https://webmail.mail.com/EWS/UM2007Legacy.asmx

        https://webmail.mail.com/OAB/322aa0e9-256a-4886-bbcb-62e7aaf4cb80/

        On

        none

PFHierarchy@mail.com

Reference:

http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-2-step-by-step-exchange-2007-to-2013-migration.aspx

http://channel9.msdn.com/Events/TechEd/NorthAmerica/2013/OUC-B313#fbid=

http://technet.microsoft.com/en-us/library/hh529912(v=exchg.150).aspx

http://support.microsoft.com/kb/2834139/en-us?sd=rss&spid=16662