New Year, New Momentum: Here are three Copilot updates to get you started into 2026

on
It's a new year, so I thought I'd start the year by mentioning three features already released, or soon going to be released. One of the features improves the workflow of sharing files with comments, the other improves the application specific Copilot, and the last feature makes it easer to find the nest available timeslot for a 1:1 meeting. As with all of my other posts, timelines can shift, and the timelines in this post is as written in the Message Center at the time of posting. AI-Summary experience when sharing files. With this new feature, copilot intent to help users share files with clearer context in just a few steps. Users will get the capability to generate a concise summary of a file and include it when sharing from the File Explorer share dialog or the OneDrive activity center. This will make it easier to share the context of a file and giving the receiver a faster understanding of what a document or file contains before they open it. General Availability announced...

A bit dissapointed? (Not really!)

on
#UC #Exchange #Hyper-v #FTMG

Well, here I am. Going to build me a new lab. There are several reasons for this, and I might come back to those (reasons) later.

As a UC guy, I need to test and understand "everything" when I am working for a customer. And to be a bit more prepared at some of the "other" stuff, I thought I should build a mini site with a few essential components. At the same time, I'm curious to what new functions and obstacles new releases might bring.

The complete LAB will be installed in Hyper-V on a Win2008 R2 server. To save some time and space, I have installed Win2008 R2 on a master drive which has been write protected. All servers I install use differentiating disks. This setup (don't forget to sysprep the master disk, and don't activate windows on it if you're going for a similar setup) allows for a really fast setup of new machines. It leaves only a few minor steps to complete when activating a new server. I am not sure how well this setup works in a production environment, so I'would reccomend a different strategy there (maybe: Create a master drive and run sysprep, then copy and rename each new instance)

So far, I have Installed:
2 FTMG servers (and creating a "DMZ" in between). Yes, FTMG is a RC only, but it looks promising and I need to know whats coming.
1 Server to act as AD/DNS/DHCP/CA and File/Print (Not best practice, but this is LAB is about functionallity, not BP)
1 Server running Exchange 2010.
** to be continued**

Now to my so called disappointment:
When installing Exchange 2007 on Win2008 and 2008 R", there have been "obstacles" standing in the way for a quick and easy installation of Exchange. I was looking forward to meet these new obstacles I expected when I sat down to install Exchange 2010. ** Disappointed** I followed the "howto" information on the web, and found it to be running smoothly and without a hitch...... Hats off to whoever made the installation as easy as it should be :)

You should though, be aware of the prerequisites and requirements of the server before running "install exchange". These are found on the web, not on the CD. Which of course might cause you a headache if the exchange server does not have http/s internet connectivity at the time of installation. Why don't the include a "prepare my computer" script in the setup program?

Next task? Install OCS 2007 R2 in the environment. I'll let you know how this turns out.