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.

Missing Meet URL for users of Lync Hoster Pack v2

on
The company I work for deployed Lync Hoster Pack v2 in the fall of 2013. At first, all things seemed fine, but after a while we received incident tickets regarding users who did not get the meet url published when creating a new meeting.

It has been a long road tring to find the root cause of this issue, especially since we at first saw no difference between the users we created where it worked, and users where it did not work. All users were deployed through the Citrix Cortex service for provisioning.

All users were provisioned correctly with Domainmap, TenentID and ObjectID. And if we moved users from one place to another it started working again.

It all turned out to be a rights issue in Active Directory. The root OU had it's correct settings, but when we deployed several resellers through the Cortex service, these reseller OU's did not inherit the rights from the parent OU. Applying the correct rights to all the sub OU's in the tree fixed the issue for all customers.

Here's a quick script to set the correct rights for hosting on all OU's in a tree:

Import-Module activedirectory
Import-Module lync
$counting = 0
$moreISH = Get-ADOrganizationalUnit -LDAPFilter '(name=*)' -SearchBase `
'ou=reseller,ou=hosting,dc=domain,dc=net'| select DistinguishedName
foreach ($ou in $moreISH){
Grant-CsOuPermission -OU $ou.DistinguishedName -Verbose -ObjectType user
$counting ++
}
Write-Host "Set rights on $counting OU's" -ForegroundColor Green

The commands above must be run a computer where the Active Directory and the Lync module is available.

These are the changes made by the command http://technet.microsoft.com/en-us/library/hh849655(v=ocs.14).aspx