Replacing expired internal transport certificate in Microsoft Exchange Hub Transport Server with new certificate

As a busy system administrator, you could overlook as below event logs.

You need to renew the expired internal transport certificate when you see this event logs.

It's easy.

First you need to check the certificate details with Powershell command as below

Get-ExchangeCertificate | fl

Then you know what certificate is expired and what are its service and thumbprint.

Once you knew all details about it, take note/copy thumbprint of it and try to replace with new certificate by using Powershell command as below.

Get-ExchangeCertificate –Thumbprint "Invalid Certificate Thumbprint Here" | New-ExchangeCertificate

Powershell will prompt you to perform overwrite the existing certificate. Just type "Y" or "Yes" or hit "Enter".

Now you already replaced out of date internal transport certificate.

Next step is to remove the invalid/ out of date certificate.

Use below Powershell command to remove it.

Remove-ExchangeCertificate -ThumbPrint "old-thumbprint-here"

Yes. You've done in replacing new certificate with old certificate and removed the invalid certificates from your server.

May you all be happy.
(Be knowledgeable, pass it on then)

Comments

Fortigate guide for Begineer - 6

I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a

Why do we need network virtualization?

We need to think about Server Virtualization first if we want to talk about Network Virtualization. In the era of cloud computing, servers are virtualized and used in Data Centers. We are facing a lot of problem when we virtualized our Servers, 1) Routing and Switching Problem Routing become the issue when we create Virtual Switch and VLANs according to production requirement. Network Team might need some time to change on their end to meet with Server Virtualization Team changes on their end. ၂) Firewall Services Physical Firewall are difficult to manage due to the large number of rules needed to satisfy business requirements. New applications, new projects, and new networks all come with potential security requirements, which impact centralized firewall management. ၃) Load Balancing Let's say your company deploys a new physical load balancer for each tenant, resulting in increased capital expenditures. Once a tenant reaches their maximum capacity, it ca

Solving "WSUS administration console was unable to connect to the WSUS Server via the remote API" error

Today, I've got below when I try to connect my WSUS Server via WSUS Console. Below logs are display in Event Logs too. The WSUS administration console was unable to connect to the WSUS Server via the remote API. Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. The WSUS administration console was unable to connect to the WSUS Server via the remote API. Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 172.16.99.98:80 Source System Stack Trace: at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, S

ICT for Myanmar in English

Search This Blog