Exchange 2013 – Page 4

Attempting to export a mailbox to PST from the Exchange Server 2013 ECP throws the error: “The call to ‘net.tcp://exchangeServer.domain.com (15.0.1178.0caps:1FFF)’ timed out. Error details: This request operation sent to ‘net.tcp://exchangeServer.domain.com/Microsoft.Exchange.MicrosoftReplicationService…”

March 8, 2017

Problem You attempt to export a user’s mailbox to PST via the Exchange 2013 ECP console but receive the following error: The call to ‘net.tcp://exchangeServer.domain.com (15.0.1178.0caps:1FFF)’ timed out. Error details: This request operation sent to ‘net.tcp://exchangeServer.domain.com/Microsoft.Exchange.MicrosoftReplicationService did not receive a reply within the configured timeout

Attempting to execute Create-PublicFolderMailboxesForMigration.ps1 to create target public folder mailboxes on Exchange 2016 fails

January 26, 2017

I’ve noticed that many of my clients and colleagues have been calling me about a specific step during the migration of Exchange 2010 Public Folders to Exchange 2016. Given the frequency of the calls I’ve gotten, I thought it would be a good idea to

Rerouting outbound SMTP mail through Exchange 2016 Send Connectors from Exchange 2010 fails with: 451 4.4.0 Primary target IP address responded with: “421 4.3.2 Service not available.”

January 14, 2017

Problem You’re currently migrating from Exchange Server 2010 to 2016 and have just reconfigured the Send Connectors to route outbound SMTP mail through Exchange 2016 but notice that sent emails are stuck in the Exchange 2010 queues with the following error: 451 4.4.0 Primary target

Microsoft Remote Connectivity Analyzer’s Exchange ActiveSync test fails at “Validating certificate trust for Windows Mobile devices.” when publishing Exchange 2016 services with Citrix NetScalers

January 4, 2017

Problem You’ve successfully published your Exchange 2016 services with Citrix NetScalers but noticed that when you run the Microsoft Remote Connectivity Analyzer’s Exchange ActiveSync test at https://testconnectivity.microsoft.com, it fails at the Validating certificate trust for Windows Mobile devices. test. The Microsoft Connectivity Analyzer is testing

Migrating Receive Connectors from Exchange 2010 to 2016 with native Exchange PowerShell cmdlets

December 21, 2016

I’ve been recently involved with a project where I had to assist a client with a Exchange 2010 to 2016 migration and one of the tasks I was assigned to do was to migrate the existing Exchange 2010 Servers receive connectors to the new Exchange

Security Alert with certificate error presented when users launch Outlook 2013 or 2016 in an Exchange Server 2016 environment

November 17, 2016

Problem You have recently migrated from an earlier version of Exchange 2010 or 2013 to Exchange Server 2016 and noticed that users are now receiving a Security Alert with a certificate error when they launch Outlook: Information you exchange with this site cannot be viewed

Auditing administrators granting “Full Access” permissions to mailboxes in Exchange 2016

July 26, 2016

One of the most common questions I’ve been asked by clients is whether there is a way to audit administrators granting Full Access permissions to mailboxes in Exchange and the answer to that is yes because every action made within the Exchange Admin Center or

Attempting to configure email server settings in Citrix Command Center throws the error: “Connection to mail server failed, provide accurate mail settings”

July 8, 2016

Problem You’re attempting to configure the email server settings in Citrix Command Center but notice that you receive the following error when you save the configuration: Error Connection to mail server failed, provide accurate mail settings Solution While there could be several reasons why this

Using Citrix NetScaler Rewrite Action and Policy to prevent the Location HTTP header from exposing internal IP addresses

May 5, 2016

I was recently asked by a client to fix an issue with their Exchange 2013 Outlook Web Access webpage where an HTTP request to the site would expose the internal IP address of the Client Access Server in the Location HTTP header as shown in

Changing Exchange Server 2013 UM dial plan for Unified Messaging enabled users

February 7, 2016

I was recently told by our telephony engineer that we needed to create a new UM dial plan with the URI Type set as SIP URI for our internal users that are using Exchange Unified Messaging for voicemail because of the migration from Exchange 2007

Blog

Attempting to execute Create-PublicFolderMailboxesForMigration.ps1 to create target public folder mailboxes on Exchange 2016 fails

Rerouting outbound SMTP mail through Exchange 2016 Send Connectors from Exchange 2010 fails with: 451 4.4.0 Primary target IP address responded with: “421 4.3.2 Service not available.”

Microsoft Remote Connectivity Analyzer’s Exchange ActiveSync test fails at “Validating certificate trust for Windows Mobile devices.” when publishing Exchange 2016 services with Citrix NetScalers

Migrating Receive Connectors from Exchange 2010 to 2016 with native Exchange PowerShell cmdlets

Security Alert with certificate error presented when users launch Outlook 2013 or 2016 in an Exchange Server 2016 environment

Auditing administrators granting “Full Access” permissions to mailboxes in Exchange 2016

Attempting to configure email server settings in Citrix Command Center throws the error: “Connection to mail server failed, provide accurate mail settings”

Using Citrix NetScaler Rewrite Action and Policy to prevent the Location HTTP header from exposing internal IP addresses

Changing Exchange Server 2013 UM dial plan for Unified Messaging enabled users

Hello! My name is Terence Luk and welcome to my blog.

Follow me:

Categories

Subscribe to the mailing list to receive posts updates!

Categories

Recent Posts

Web Application Update: Adding identity information of the user who has uploaded a file to a Storage Account

Configuring a Logic App to run an Azure AI Search Service Indexer to index new documents for RAG