Two new updates to Microsoft 365 Copilot for Word: Smarter Creation and Researcher agent

on
What’s New in Microsoft 365 Copilot for Word Microsoft continues to evolve its Copilot capabilities in Word, bringing powerful new features that enhance productivity and streamline workflows. Two newly announced updates are rolling out this fall: First out of the gate is the integration of the Researcher Agent, allowing great content generation within Word itself. The second update is bringing more of the search and creation capabilities we have in Chat directly into Word. These updates represent a meaningful step toward closing the functionality gap between Copilot in Word and Copilot Chat. For me, this is a most welcomed improvement, making it easier for end users to get the results they want even faster, with less friction and more flexibility. Deep Research with the New Researcher Agent in Word Not too long ago, Microsoft introduced the Researcher agent in Copilot Chat, but moving and editing that content required copy/paste and jumping between applications. With this coming update...

Call Manager 4.2 database issue after a publisher failure

on
This is a post for future reference. A customer of mine experienced some strange symptoms on their CUCM’s this week. And it took me some time to figure out what and why.
Issue at hand: When logging on to ccmadmin on the publisher, several ip-phones where not registered. But the phones were operational, and showed no sign of error. When logging on to the subscriber, I found all of the “not registered” phones registered. But all phones registered on the publisher was here “not registered”.
Troubleshooting: I tried booting the CUCMs but it did not help. I tried to restart services and manually fail over phones to one of the CUCMs. But the result was always the same. Whichever CUCM which did not have the phones registered, listed the phones as "not registered”.
Resolution: I’ve seen this before, and suspected a broken SQL link. Running DBHelper confirmed my suspicions, and fixed part of my problems. After recreating the publish/subscribe link in SQL, I expected the call managers to perform normally. But not so. I then booted the subscriber, but nothing changed. Only after booting the publisher first, then followed by the subscriber fixed the problem entirely.