Exchange 2013 CU18 has been released to the Microsoft download centre! Exchange 2013 has a different servicing strategy than Exchange 2007/2010 and utilises Cumulative Updates (CUs) rather than the Rollup Updates (RU/UR) which were used previously. CUs are a complete installation of Exchange 2013 and can be used to install a fresh server or to update a previously installed one. Exchange 2013 … Read the rest “Exchange 2013 CU18 Released”
When building out a lab, you might need to attach the same ISO to multiple VMs. In this case I was installing multiple Exchange 2016 severs, and wanted to easily add the same ISO file to each of the VMs.
This was on my Windows 10 laptop which makes quick work of the task since we can use PowerShell.
The VMs to target all have the same naming convention. The VMs for the Exchange 2016 lab start with… Read the rest “Quick Tip–Adding Same ISO DVD Image To All Hyper-V Lab VMs”
While operating in an Exchange hybrid model, users expect to see a consistent GAL no matter if they or other people to be contacted are on-premises or in Exchange Online. In order for the Exchange on-premises servers to be able to build up a complete GAL there needs to be at least some mailbox information added to the AD user object. If Exchange Online mailboxes are added by simply assigning an … Read the rest “Automating Enable-Remote Mailbox”
Patch Tuesday this month featured updates to address security issues in Exchange 2010, 2013 and 2016. Two weeks ago today, July 11th heralded the arrival of Rollup Update Rollup 18 (RU18) for Exchange Server 2010 Service Pack 3 along with updates for Exchange 2013 and 2016.
Exchange 2010 SP3 RU18 is the latest rollup of customer fixes currently available for Exchange Server 2010. All updates, bo… Read the rest “July 2017 Exchange Security Updates–Have You Updated?”
An issue came to light when onsite recently with a customer. The design specifications from the Exchange team were not being correctly implemented. In this environment there is a separate Windows team who are responsible for managing the underlying server OS and hardware. They are to follow the prescribed process and steps laid down by the application owner but this was not consistently happeni… Read the rest “Script To Check Exchange NTFS Cluster Size”
Imagine the situation. You just finished deploying AD FS 2016 and Web Application Proxy (WAP) servers in a highly available environment with the AD FS namespace load balanced internally and externally. There are multiple AD FS servers and WAP servers. This is an interesting deployment project and all is going well. After verifying that core AD FS and WAP functionality works as expected you th… Read the rest “WAP 2016 Published Application Not Working – HTTP Error 503”
Exchange 2016 CU6 has been released to the Microsoft download centre! Exchange 2016 has a different servicing strategy than Exchange 2007/2010 and utilises Cumulative Updates (CUs) rather than the Rollup Updates (RU/UR) which were used previously. CUs are a complete installation of Exchange 2016 and can be used to install a fresh server or to update a previously installed one. Exchange 2013 ha… Read the rest “Exchange 2016 CU6 Released”
Exchange 2013 CU17 has been released to the Microsoft download centre! Exchange 2013 has a different servicing strategy than Exchange 2007/2010 and utilises Cumulative Updates (CUs) rather than the Rollup Updates (RU/UR) which were used previously. CUs are a complete installation of Exchange 2013 and can be used to install a fresh server or to update a previously installed one. Exchange 2013 … Read the rest “Exchange 2013 CU17 Released”
One of the deployment validation and testing tools which was also present in earlier AD FS releases is the /IdpInitiatedSignon.htm page. This page is available by default in the AD FS 2012 R2 and earlier versions. Though it should be noted this page is disabled by default in AD FS 2016.
From the system you wish to test from, navigate to the AD FS namespace's idpinitiatedsignonpage. This will be i… Read the rest “How to Enable IdpInitiatedSignon Page In AD FS 2016”
When configuring AD FS for Office 365, one of the final steps is to link Azure AD with the on-premises AD FS deployment. This should occur only after AD FS and WAP servers have been fully deployed, verified and tested.
When linking the AD FS infrastructure with Office 365, we must use the Azure AD PowerShell module. We need to point the module at the primary AD FS server using the Set-MsolADFSCon… Read the rest “PSRemoting for Office 365 AD FS Configuration”