Wednesday, April 11, 2018

Exchange Server 2013 Enters Extended Support Lifecycle Phase



Exchange Server 2013 enters the Extended Support phase of product lifecycle on April 10th, 2018. During Extended Support, products receive only updates defined as Critical.

With the transition of Exchange Server 2013 to Extended Support, the quarterly release schedule of cumulative updates will end. The last planned cumulative update for Exchange Server 2013, Cumulative Update 21, will be released in June 2018.


Additional Information:
https://blogs.technet.microsoft.com/exchange/2018/04/10/exchange-server-2013-enters-extended-support-lifecycle-phase/



Exchange 2010 - End of Support Is Coming

 
On January 14, 2020, Exchange Server 2010 will reach end of support.
 
 
Additional Information:
 
 

Wednesday, February 28, 2018

Outlook Error: There is a problem with the proxy server's security certificate. Outlook is unable to connect to the proxy server (Error Code 80000000)

I had an interesting issue while working on one project. When customers working with Outlook, sometimes some Outlook clients received the following certificate error message:
 
There is a problem with the proxy server's security certificate.
Outlook is unable to connect to the proxy server (Error Code 80000000).
 
 
I want to share my solution on this issue.

Monday, January 29, 2018

Exchange 2010: Change Password with Outlook Web Access

Applies to: Exchange Server 2010
 
Enable change password feature in Outlook Web App:
 
Log on to the Client Access server.
Open Registry Editor
regedit
 
Find registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange OWA
 
Create the following DWORD value if it doesn't already exist: ChangeExpiredPasswordEnabled. The value type will be REG_DWORD
Set the value of ChangeExpiredPasswordEnabled to 1
Restart IIS
iisreset /noforce
 


Note:
You must make this change on each Client Access server that supports Outlook Web App 
 

Friday, January 5, 2018

PowerShellTip: Get Computer Name

To easily retrieve computer name in Windows PowerShell, use the environmental variable ComputerName.

[PS]$env:ComputerName

This can be useful in scripts.