Category: Troubleshooting

I was recently working with a customer enabling Copilot for their end users. After the Copilot license was assigned, it took several minutes to have Outlook for Windows, Word, PowerPoint, and Teams to have the Copilot option appear. However, the Outlook for Mobile app was taking longer. As a first step (as always it seems

Mark Nivens created this HealthChecker.ps1 file for Exchange servers for your on premises environment. This script checks various configuration items on the Exchange server to make sure they match the recommendations published in the "Exchange 2013 Sizing and Configuration Recommendations" guidance on TechNet. It also reports on Operating System and hardware information. You can run it remotely against a single

The question isn’t can you but should you. What’s a CU? Starting with Exchange Server 2013, the Exchange Product Group (PG) went to a quarterly updating process titled Cumulative Updates. These CU’s literally uninstall and reinstall Exchange when they are applied to a server. This is one reason a CU install process can take several hours. You’ll want to

There is a tool that helps you identify Lingering Objects in an Active Directory environment. It is the Lingering Object Liquidator, or LOL for short. A description from the download site: Lingering Object Liquidator automates the discovery and removal of lingering objects from an Active Directory Domain Services forest. The tool uses the DRSReplicaVerifyObjects method

I had posted a blog about what happens if you do have Lingering Links in your environment about a year ago. The blog here appeared on the Exchange Blog Site. Now that I have my own blog site up and running, I just wanted to make reference to the article as in the field, I still find customers

Microsoft has posted a shortcut alias link to assist customers when stuff breaks. It will direct people to a possible support solution. https://aka.ms/whenstuffbreaks

I have run into this issue several times in my travels and want people to be aware of this problem. In a DAG (Database Availability Group), if your databases are randomly mounting or flipping from one server to another, including across datacenters, you may be allowing your Network Interface Card (NIC) to go to sleep.