Microsoft Copilot is all around...

  As the debut of Microsoft 365 Copilot approaches, there are a lot of Copilot features set to be introduced across the Microsoft 365 ecosystem. Here are a few noteworthy additions: Microsoft has unveiled a series of innovative features in the upcoming releases of Windows 11, some of them are already released, and some are currently available in preview builds. The Windows 11 Copilot, conveniently located in the taskbar, eliminates the need to open your Edge browser. It is seamlessly integrated with Bing Enterprise Chat (BEC) and ChatGPT, making it really easy to get started on your creative journey. Included in Windows 11 is the new co-creator feature in Paint. This feature, also in preview, is integrated with DALL-E and provides a swift and straightforward method for creating illustrations and images. If you possess a knack for crafting descriptions, you can generate quite impressive imagery. Another AI-powered feature is image creation directly from BEC. This feature, also integrate

Installation error when upgrading Exchange 2010 to SP1

I encountered a strange issue when I upgraded an Exchange 2010 installation just the other day. I could not find any technet articles or other blog posts with anything similar to my error. So I thought I'd share my error and solution.

The installation is a rather small one, so I have all the roles co-located on one server.

First of all, I was not able to upgrade using GUI at all. It told me I had to select components, even though all the components were already selected. It just gave me a nonsense error message. It was only after disabling the UMserver (as suggested by this document: I was able to run the wizard.

Unfortunately I was still not able to install the service pack from the GUI. I then tried to run the /m:upgrade /installwindowsfeature from command prompt. The setup still feiled. When studying the error setup logs (great logging of the setup by the way) I noticed it was complaining about not being able to read the language-packages. And this is where I was puzzeled: The setup was looking for the languagepack on the desktop of my administrator account, not in the setupdirectory I was running setup from.

My simple solution to the problem was this: Copy all the language folders to the desktop. I rebooted the Exchange server (A failed install will need to be rebooted before running setup again) and ran again. And this time it worked just fine.

Anyone with a good explanation on the placements of the language files? Please drop me a note in the comments section ;)