The notion of “best practice” has long been an elastic commodity when applied to Exchange architecture and design. Consultants and consulting companies have professed to have their own magic method to ensure the successful deployment of Exchange since the first version appeared nearly twenty years ago. There’s nothing harmful in following a successful recipe. Problems only appear when people refuse to change the recipe to reflect new developments.
Last week, I wrote about a report issued by security company Cybereason that reported how an attacker had gathered 11,000 sets of user credentials after planting a compromised OWAAUTH.DLL file on an Exchange server. A spirited debate duly resulted and Cybereason commented back on the original post.
After what seems to have been a much calmer Technology Adoption Program (beta tests), Exchange 2016 passed all the required quality benchmarks to reach Release-to-Manufacturing (RTM) status on September 29. Of course, RTM is an archaic term dating back to the time when software was ceremoniously handed over by development to the folks who created copies of the distribution kit on floppy disks, then CDs, and latterly DVDs for delivery to customers.
I’m on the way back home after the 2015 IT/DEV Connections conference, which took place this week in the Aria Hotel in Las Vegas. Thankfully, everything seemed to run smoothly and the Enterprise Collaboration track functioned without too many problems. We had to do one quick room switch and Surface Pro 3 and other PCs posed some “interesting” AV challenges to get output to the projectors. HDMI seemed to be a particular problem and the AV team was not impressed that many speakers ran Windows 10 build 10532. Apparently VGA remains the lingua franca for AV guys.