Monday, July 6, 2015

Unable to send message with Attachment even though Proper Message size limits 15 MB has been set on Receive, Send and at Transport Level which also includes MIME overhead of 37% still not able to send/receive message

Exchange 2010, Unable to send message with Attachment even though Proper Message size limits 15 MB has been set on Receive, Send and at Transport Level which also includes MIME overhead of 37% still not able to send/receive message.


then try this command 

Set-TransportConfig -ExternalDsnMaxMessageAttachSize 15MB -InternalDsnMaxMessageAttachSize 15MB

In Exchange 2013
New-SystemMessage is a command used to set the DSN (Delivery status Notification)

for reference
https://technet.microsoft.com/en-us/library/aa998878%28v=exchg.150%29.aspx



some Additional Knowledge and default Series for configuring limit is

  • Organizational Level # Is the Highest level in an organization
  • Send Connector
  • Receive Connector
  • AD Site Links
  • Routing Group Connectors
  • Mailbox Level      # Is the lowest level and take precedence over all the settings
Shell Commands where Message Limit can be checked
Get-ForeignConnector | fl Name,MaxMessageSize
Get-SendConnector | fl Name,MaxMessageSize
Get-ReceiveConnector | fl Name,MaxMessageSize
Get-ADSiteLink | fl Name,MaxMessageSize
Get-RoutingGroupConnector | fl Name,MaxMessageSize
Get-TransportConfig | fl MaxSendSize,MaxReceiveSize
Get-DistributionGroup | fl name,MaxSendSize,MaxReceiveSize
Get-DynamicDistributionGroup | fl name,MaxSendSize,MaxReceiveSize
Get-Mailbox | fl name,MaxSendSize,MaxReceiveSize
Get-MailContact | fl name,MaxSendSize,MaxReceiveSize
Get-MailPublicFolder | fl name,MaxSendSize,MaxReceiveSize
Get-MailUser | fl name,MaxSendSize,MaxReceiveSize


Get-Mailbox -FIlter {MaxSendSize -ne $null -OR MaxReceiveSize -ne $null} | ft Name,MaxSendSize,MaxReceiveSize



Thursday, June 11, 2015

After rebooting Exchange 2010 server is stuck on "Applying Group Policy settings"

After rebooting server, Users are unable to send and receive Email

We are able to
All of the Exchange related services are in stopped state and after rebooting Exchange server, stuck on "Applying Group Policy settings"

We replicated DC from "AD sites and services", added Exchange server "SVR13" into Exchange server

Group from "Exchange Security Group"and suggest to reboot he box. still same issue.

Customer is able to boot Exchange server into Networking with Safe mode


http://www.exchangewarrior.com/exchange-2007/exchange-server-stuck-on-applying-group-policy-settings/

Troubleshooting Steps : DAG suddently failover

Exchange 2010 Service pack 3 with Update Rollup 2.

Understand that one of the DAG member stopped responding for the clients hence the users were unable to access their mailbox.

In order to overcome this situation, customer has moved all the resources to another node and rebooted the problem node


Diagnosis Given : Network issue, Network connectivity lost between FSW and Exchange

Friday, March 27, 2015

Exchange 2013 Installation on Windows 2012 Std R2

Installing only CAS role

In powershell (Run as Administrator) 

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

Reboot will be required

2. Install Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit

badge 3. Exchange setup




Installing MBX role or Mixed mode

In powershell (Run as Administrator) 

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

reboot will be required

Need to install after Windows feature 


and finally run Exchange setup

Thursday, February 26, 2015

Exchange 2013 SP1 There are 3-4 users getting dual archive mailbox

Issue :

1. Users are in Outlook 2013/Outlook 2010 and OWA, few users are getting dual Archive mailbox

2. For the same user, Inbox is visible in Archive Mailbox, both from Outlook and OWA



Resolution :


1. Test-E-mail Autoconfiguration" from Outlook shows that the Outlook is connecting to another users Mailbox and Full mailbox permission is added for another user's Mailbox in the user mailbox


Removing full Mailbox permission for another user mailbox from the original user's Mailbox resolves the issue


2. When Archive Mailbox is enabled for user, Exchange will copy the frame like inbox, sent and delete Item etc but will not publish until data is moved to Archive mailbox via Retention Policy



Exchange 2013 New-MailboxRestoreRequest :: The term 'New-MaiboxRestoreRequest' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Issue : From Exchange management Shell, Running command is providing this error


New-MailboxRestoreRequest –SourceDatabase <Source-Database> -SourceStoreMailbox <Disconnected-Mailbox> -TargetMailbox <Destination-Mailbox> -TargetRootFolder <Folder-in-Destination-Mailbox> -AllowLegacyDNMismatch


New-MaiboxRestoreRequest : The term 'New-MaiboxRestoreRequest' is not recognized as the name of a cmdlet, function,
script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is
correct and try again.
At line:1 char:1
+ New-MaiboxRestoreRequest -SourceDatabase "recovery" -SourceStoreMailbox "dd ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~
   + CategoryInfo          : ObjectNotFound: (New-MaiboxRestoreRequest:String) [], CommandNotFoundException
   + FullyQualifiedErrorId : CommandNotFoundException 



Resolution: Open EMS in Administrator mode and run the command again



 -AllowLegacyDNMismatch : this switch will allow to restore Database into different location from the original


To receive GUID for the user

Get-MailboxStatistics –Database recoveryDatabase | ft DisplayName,MailboxGUID,DisconnectReason –AutoSize

Get-MailboxRestoreRequest //This command can helpus to check with restore status

Create Recovery Database
New-MailboxDatabase -Recovery -Name RDB1 -Server MBX2
New-MailboxDatabase -Recovery -Name RDB2 -Server MBX1 -EdbFilePath "C:\Recovery\RDB2\RDB2.EDB" -LogFolderPath "C:\Recovery\RDB2"

Get-MailboxDatabase <RecoveryDatabaseName> | Format-List
New-MailboxRestoreRequest -SourceDatabase DB1 -SourceStoreMailbox 1d20855f-fd54-4681-98e6-e249f7326ddd -TargetMailbox Morris

Get-MailboxRestoreRequest -Status Completed | Remove-MailboxRestoreRequest

Tuesday, February 24, 2015

LDP from Exchange Command Prompt


Get-Mailbox mb1 | % { dsquery * $($_.DistinguishedName) - attr * }

Eg:
get-mailbox "zena.james" | % {dsquery * $($_.distinguishedName) -attr *} 



Where MB1 is the alias of the Mailbox user

LDP > Connection "FQDN of DC" >> Bind > Tree "Ok" > Search the Object >> Goto the Connection > Click new >> and then click again on the Object > Output is on the right side