New Year, New Momentum: Here are three Copilot updates to get you started into 2026

on
It's a new year, so I thought I'd start the year by mentioning three features already released, or soon going to be released. One of the features improves the workflow of sharing files with comments, the other improves the application specific Copilot, and the last feature makes it easer to find the nest available timeslot for a 1:1 meeting. As with all of my other posts, timelines can shift, and the timelines in this post is as written in the Message Center at the time of posting. AI-Summary experience when sharing files. With this new feature, copilot intent to help users share files with clearer context in just a few steps. Users will get the capability to generate a concise summary of a file and include it when sharing from the File Explorer share dialog or the OneDrive activity center. This will make it easier to share the context of a file and giving the receiver a faster understanding of what a document or file contains before they open it. General Availability announced...

Installation error when upgrading Exchange 2010 to SP1

on
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: http://technet.microsoft.com/en-us/library/ff630921.aspx) 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 setup.com /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 setup.com 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 ;)