We often get asked how to easily via PowerShell determine which Active Directory Domain Controllers and Global Catalog servers an Exchange 2007, 2010, 2013, 2016, or 2019 are using for directory access during an Exchange migration using the Priasoft Migration Suite for Exchange. As you may know, Exchange DSAccess will choose its list of server(s) based on suitability tests and then caches this access info. To get the current list of DC’s and GC’s run the following PowerShell command:
▼ Please scroll down to see the Powershell Command ▼
FEATURED PRIASOFT
OFFICE 365 MIGRATION TOOLS
Public Folder Data Migration
Seamless Office 365 Public Folder Migration Tool
Eliminate the need for unreliable third-party tools. Our solution guarantees seamless mail-enabled public folder migration, content transfer, and precise Public Folder permission migration.
Public Folder Permissions Reporting
Public Folder Reporting & Analysis for Office 365
Gain control and deep insights into your Exchange / Office 365 Public Folders with comprehensive reporting, analysis, and remediation
Outlook Profile Migration
Outlook Profile Updater for Smooth Migrations
Ensure smooth transitions during migrations with our Outlook Profile Update Manager. Don’t let AutoDiscover issues ruin your experience—update profiles correctly from the start.
PST and Mailbox Export With Powershell
Efficient PST & Office 365 Exchange Administration
Manage PSTs effortlessly with our DevOps-friendly solution. From ingestion to data export for legal discovery, and efficient Office 365 mailbox management, all powered by PowerShell.
Powershell Command to locate the current Domain Controller and Global Catalog servers being used by Exchange
Command (replace ServerName with a valid Exchange server name below):
Get-ExchangeServer -Identity “ServerName” -status | fl
Note: You must run this command directly on each Exchange server or create separate powershell sessions to each Exchange server in order to get accurate information.
If you run this command from a remote powershell session (e.g. Import-PSSession) the returned results will all say the same DCs and GCs and will be a reflection of the Exchange server to which the powershell session is connected.
If you run this command while directly on an Exchange server but specify a server different than the server itself, you will get similarly inaccurate results.
Presto! You know have access to which DC’s and GC’s are being used by Exchange 2007, 2010, 2013, 2016, or 2019.
Ready to Talk Through Your Migration?
Priasoft has been handling Exchange and Microsoft 365 migrations since 1999. Whether you're scoping a new project or recovering from a stalled one, our engineers have seen it before. No sales pitch — just a working conversation with people who have done this work at scale.
The Exchange Experts – Who Are We?
Priasoft, a Microsoft Partner, offers enterprise-class solutions for Exchange migration, management, and eDiscovery. Supporting Exchange 2010, 2013, 2016, 2019, and Office 365/Exchange Online, our platform enables secure migration, management, and organization of email data, with advanced tools for compliance, public folder analysis, and AI-driven insights.
