Microsoft 365 updates on new Copilot capabilities

on
Microsoft has announced a set of upcoming enhancements that continue to expand the value of Copilot across Microsoft 365. These updates introduce new ways for users to manage collaboration and meeting experiences with less context switching and more control. As always, timelines may shift as development progresses. I have provided the official reference IDs and documentation links for your convenience. Schedule meetings directly from Copilot Chat The first update introduces a new capability that allows users to schedule meetings directly from Copilot chat. This feature reached general availability worldwide with rollout completed by late January 2026. It enables users to find available times, book rooms, draft agendas, and send invitations entirely within the chat experience, reducing the need to move between applications and helping streamline everyday workflow. The feature is on by default, requires no administrator configuration, and respects all existing calendar and meeting polici...

Installing OCS 2007 R2 (Still fighting a bit)

on
Once again, .NET 3.5 is a prerequisite for installing OCS 2007, and once again the installation for this failed. A tip for you might be to enable these things ahead of the installation of OCS. I do not remember having the same problem on OCS 2007 with Windows server 2003. It might be a 2008 issue as much as a R2 problem. If anyone do install this on Windows 2003, please let me know if you run into the same issues.

Now, off to the installation at hand. First of is the Back End server on which I just installed SQL.
If you are going to install everything on one box, you don't have to read much to install OCS (a basic understanding of the components involved is really helpful though). But if you are about to what I am, install an Enterprise installation with back ends, frontends and possibly balance loaders and several pools. Reading the docs is just for you! Also, make sure the right client tools are inplace, and server times are synchronized (I am using SQL 2008 on the back end, and the installation comes with 2005 client tools).

Installing BE is really just about "preparing" the environment. For those you who have not seen the wizard; This is a task of it's own. A few simple steps to complete.

Installing the FE is another matter. Again; If you are installing all on one box, there isn't too many pitfalls. But when you deploy to several servers, you need to keep your head straight when it comes to poolnames, servernames, sipdomains and certificates.... If you have a basic understanding, it should not be too hard, but still... whatch out for those pitfalls when assigning roles, names and certificates. My biggest obstacle was figuring out how to add the certificate to IIS. AS it turned out, the management tools were not installed (and are not by default).