Yes this will happen in Jun ’18 release of Exchange cumulative update and after that If your system does not meet requirements which included .NET Framework 4.7.1 it would not allow to you install either exchange 2013 or Exchange 2016.
So make sure in the next few months you do testing in your lab environment and make sure it goes through you change management process (if any) and get the system ready. This is major update. At this point it not clear how or what will happen if you have existing Exchange 2013/2016 without .NET Framework 4.7.1 and new Servers installed after June ’18 with .NET 4.7.1.
I will update this post as soon as I hear back from Exchange product team, till then stay tuned.
Exchange Team Blog
Released: December 2017 Quarterly Exchange Updates
KB articles that describe the fixes in each release are available as follows:
Reminder for Hybrid
In hybrid deployments where Exchange is deployed on-premises and in the cloud, or who are using Exchange Online Archiving (EOA) with their on-premises Exchange deployment are required to deploy the most current (e.g., 2013 CU19, 2016 CU8) or the prior (e.g., 2013 CU18, 2016 CU7) Cumulative Update release.
Microsoft has identified a condition where Free/Busy lookups from On-Premises to O365 in a hybrid configuration may fail.
After you install Microsoft Exchange Server 2016 Cumulative Update 8 (CU8), free/busy queries from Microsoft Office 365 users to on-premises mailboxes in hybrid environments fail if the cloud mailboxes are not archive-enabled.
This problem occurs because of a known issue that affects OAuth connectivity in Exchange Sever 2016 CU8.
To work around this issue, create personal archive mailboxes for each cloud mailbox.
This problem is scheduled to be fixed in Microsoft Exchange Server 2016 Cumulative Update 9 (CU9). For a supported fix for CU8, contact Microsoft Support.
Join me again Friday Oct 20th
Are you preparing for Azure Architect Certification, if so then check this out. I’m delivering one of the module on Business Continuity and Disaster Recovery and Azure Monitoring. Event is sold out more than 200 participants. You can register for the next event checkout out with your Microsoft contact.
#6 Design a management, monitoring, and business continuity strategy
- Design a monitoring strategy
- Identify the Microsoft products and services for monitoring Azure solutions
- leverage the capabilities of Azure Operations Management Suite and Azure Application Insights for monitoring Azure solutions
- leverage built-in Azure capabilities
- identify third-party monitoring tools, including open source
- describe Azure architecture constructs, such as availability sets and update domains, and how they impact a patching strategy
- analyze logs by using the Azure Operations Management Suite
- Describe Azure business continuity/disaster recovery (BC/DR) capabilities
- Leverage the architectural capabilities of BC/DR
- describe Hyper-V Replica and Azure Site Recovery (ASR)
- describe use cases for Hyper-V Replica and ASR
- Design a disaster recovery strategy
- Design and deploy Azure Backup and other Microsoft backup solutions for Azure
- leverage use cases when StorSimple and System Center Data Protection Manager would be appropriate
- design and deploy Azure Site Recovery
- Design Azure Automation and PowerShell workflows
- Create a PowerShell script specific to Azure, automate tasks by using the Azure Operations Management Suite
- Describe the use cases for Azure Automation configuration
- Evaluate when to use:
- Azure Automation
- Desired State Configuration (DSC)
Find more details here
70-534 Architecting Azure Solutions Event Summary
Hi, I’m speaking again after the summer break. This time I’m speaking to NYC Enterprise Collaboration User Group. There is no fee to attend this event but you will need to register the event on meetup. Click the url below.
Businesses of all sizes are taking advantage of the convergence of cloud and mobile technology to enhance collaboration and productivity, accommodate different work styles, and reduce costs. Many companies now let employees work from anywhere, provide cloud-based productivity tools so those workers can communicate and collaborate more effectively, and encourage them to use their own devices for work.
In this presentation/discussion we will take a close look at the Team and how it can best fit for your day to day work.
Imagine a scenario that
You create Microsoft Team, which does the magic of offering full collaboration in no time (I super love it). Microsoft Team is based on Office 365 Group so it does get an email address like this
The beauty of this Group is that you can start sending the emails directly to this group and you can leverage Outlook App to start conversation with the members who are part of the Group. Yes I said GROUP and I didn’t say Team though I created Microsoft Team.
Yes this is what I’m trying to explain, Microsoft Team does not show the conversation which is done using the Group which was created by Team. To start the conversation you need to create a new Chanel, and then either use App or Desktop client or send email directly to that Channel to appear in the Conversation in that particular Team,,,, i know is sounds complicated 🙂 – Is there fix .. not now may I’m sure very soon.
Read my previous blog post why this can (Microsoft Teams) be a No Go in a large enterprise
Microsoft Teams – Hello Microsoft Take It To Next Level
I will keep this post short and to the point because if you want know more about Microsoft Team you can search about it. I’m writing my experience about Microsoft Team which very minor issues but how it can go to the next level which is related to a BIGGER ISSUE and A PROBLEM.
So what about minor ones?
If you notice this is a taskbar in MacBook and you can there is email notification for outlook but all the way on the right corner there is Microsoft Team’s and it does not show me any notification whenever there is updated related to a chat or calendar invite or anything. It does not show any notification.
The OTHER minor issues it that, now you can see all your Office Group in the Outlook App on your mobile device (I’m using iOS) but all the management/administration feature such as Add/Remove the member I still can’t do that from the Outlook App and still dependent on Groups App, wish it were managed by the same Outlook App.
The MAJOR Issue
It may not be a major issue for so many of you but I can say this will not work in any large enterprise organization because it will be stuck to security and it may not be compliant. Here is the thing. If are using Microsoft Team in your tenant and you Tenant for example has primary domain name as techiesonly.com , the channels in the team are mail enable and if you look at their smtp alias they are not the same as your tenant. I’m sure you know what I’m saying here. You channel conversation is routed via email using a different email route and email alias somewhere in the cloud and then coming back to your conversation history. Though your Microsoft Team is built on Office Group (a exchange mailbox) but your conversation are somewhere in the cloud and There is no information available on the that is a question. I’m sure Microsoft will address that and fix it soon.