Due to the vulnerability that allows privilege escalation I wrote about in this post, Microsoft has released a cumulative update for all supported versions of Exchange Server (Exchange 2010, 2013, 2016 and 2019).
… Read more
Symptom: Large mail.que file size
Last week my Icinga started alerting about low free space in my Exchange server disk.
After using a software to scan for file sizes I realized there was a too big mail.que file.
This is the file in which exchange manages its queues before finally delivering emails. It is usually located in <Exchange_Installation_Path>/TransportRoles/data/Queue
… Read more
Some days ago I tried to cleanup old certificates from my Exchange servers, but I received the following error:
[PS] C:\> Remove-ExchangeCertificate -Thumbprint D09EDD6D5F18C175254AB97046AAAAAAAAAAAAA
Are you sure you want to perform this action?
Remove certificate with thumbprint DD09EDD6D5F18C175254AB97046AAAAAAAAAAAAA from the computer's certificate store?
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is
… Read more
In June 2018 Microsoft released Cumulative Update 21 (build 15.00.1395.004) which is the last planned quarterly update for Exchange 2013 (https://blogs.technet.microsoft.com/rmilne/2018/06/19/exchange-2013-cu21-released/)
I was not sure about updating my Exchange 2013 directly from CU12 to CU21. It is supposed to be supported by Microsoft. Maybe I could install an intermediate CU before but, anyway, I decided to move on.… Read more
When performing mailbox migrations using the New-MoveRequest, the movement is performed online while the user is using the mailbox without suffering outage until the end.
Only when completing the movement there are some seconds during which the user mailbox is not online.
Thats the reason to use the parameter “SuspendWhenReadyToComplete“. It moves almost all the mailbox except the … Read more
Last week I was testing the IMAP/SMTP connection of my Exchange 2013. Unexpectedly Outlook returned the following error:
The message does not appear completely but seems to be “550 5.7.1 Client does not have permissions to send as this sender”. Obviously the user does have the permissions (the user was the owner of the mailbox itself).
Thanks … Read more
Exchange 2013 can produce IMAP issues when trying to authenticate. This is a known bug in CU9 and CU10 but in my CU12 scenario also happens.
The IMAPSettings EnableGSSAPIAndNTLMAuth atribute must be set to False in order to solve the problem.
Yesterday, when one of my users asked me how to configure the email client using IMAP I realized … Read more
When I was migrating my Exchange platform from 2010, I ensured that the backups using Veritas NetBackup were also working in Exchange 2013, both against the active or passive node of the DAG, and also the granular backups
At a certain moment, the backups started to fail (thanks I am monitoring the transaction log disks free space using … Read more
Stop using Outlook to export and/or import PST for your mailboxes. By using the Powershell commands (New-MailboxExportRequest and New-MailboxImportRequest) I have saved much time. And they come with some useful options.
Here some simple and interesting examples:
Simple mailbox export
[PS] C:\> New-MailboxImportRequest -Mailbox "user1" -FilePath "\\MYSERVER\PST\user1.pst"
The path must be an UNC path, a shared folder. After executing the … Read more
When export a PST using the New-MailboxExportRequest command, a UNC path is a mandatory parameter to set the target folder where the PST file will be saved.
Probably, that folder will not have the correct to permissions to allow Exchange to write into it, so the command would return this error:
[PS] C:\> New-MailboxExportRequest "user1" -FilePath "\\MYSERVER\PST\user1.pst"
Unable to open
… Read more