Microsoft 365 Copilot: New Navigation, Voice, and Context Enhancements Arriving Soon

on
Here are three new updates to the user interface of Microsoft Copilot. These releases improve usability, expand interaction options, and streamline how users incorporate work content into prompts. All three of these features were actually announced "a long time ago", and the initial release started almost 6 months ago. But I guess the setup is complicated, as the rollout hasn't completed yet. This only proves the importance of paying attention to the official roadmap and the tenant message center in order to understand when features are being implemented for your organization. Timelines may continue to evolve as deployments progress, and this summary includes the official reference IDs and documentation links for verification. Refreshed Navigation Experience There is a redesigned navigation experience for the Microsoft 365 Copilot app heading your way, delivering a cleaner, more efficient layout. The update flattens the menu structure and groups related components to help...

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