Coming soon: Copilot Studio Agent Report Template

on
Copilot Studio Agent Report Template Microsoft is rolling out a new feature in Viva Insights: the Copilot Studio agent report template. This Microsoft Power BI template will be available in public preview starting mid-April 2025, and provides an aggregated view of Microsoft Copilot Studio agent adoption and impact across the organization over time, with the flexibility to explore details for specific agents. This feature will bring valuable insights into the usage of agents, making it easier for organizations to make informed adjustments and optimize their performance. The Copilot Studio agent report covers usage and impact metrics for agents built using Copilot Studio that are published outside of Microsoft 365 Copilot or Microsoft 365 Copilot Chat, and excludes agents that enhance Microsoft 365 Copilot and autonomous agents. Eligibility Criteria To access this feature, tenants must meet one of the following criteria: Viva Insights licenses: Either a minimum of 50+ assigned Viva Insi...

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 ;)