Copilot in Outlook: Meeting Preparation Is About to Get Smarter

on
Currently, the “Prepare for meetings with Copilot” feature requires at least three participants. Starting mid-October, this is changing. Copilot will soon support all meetings, including 1:1s. The rollout will begin in mid-October and is expected to complete by November 2025 according to the message center. With this update, you’ll also see new real-time insights in the Outlook meeting event form, summarizing relevant context, tasks, documents, and other resources. Plus, you’ll be able to chat with Copilot to confirm action items or better understand meeting goals. The more context Copilot has, the better it works. Meeting series with related emails, shared documents, Teams chats, and previous Copilot transcriptions deliver the richest experience. If your organization limits Copilot to in-meeting use only and deletes content afterward, you’ll miss out on much of this value. Here is a relevant " how to " guide for users.

Installing OCS 2007 R2 on Windows 2008 R2

on
#OCS #WindowsServer #Powershell

Here is a tip for if you want to speed up the process of installing OCS on a Windows 2008 R2 server.

The installation wizard and guide is made for previous OS's, and is not capable of detecting or installing all of the features you need (.net framework beeing one of them). Also, I realized all the tech blogs I came across on google suggested to use the servermanagercmd.exe to add some of the prerequisites. servermanagercmd is depreciated, and I suggest you use Powershell in Windows 2008 R2.

So, before even thinking of starting the OCS setup, you should concider running the following commands in powershell (as administrator):

import-module servermanager
web-windows-auth,web-mgmt-compat,web-mgmt-console,web-http-logging,msmq-server,msmq-directory,rsat-addc,was-process-model,was-config-apis,NET-Framework-Core,Desktop-Experience -restart

So far, so good, but now I,m stuck with a new error: 0x80070534 "No mapping betweein account names and security IDs was done. This error is registered on the "setting NTFS rights" section in the error report. Anyone got an Idea?