Active Directory Synchronization (DirSync) Deprecation
Action Required by: April 4, 2017
Details: We will be removing the Windows Azure Active Directory Synchronization feature from Office 365, beginning April 4, 2017. You are receiving this message because our reporting indicates your organization is using Windows Azure Active Directory Synchronization. When this change is implemented, administrators will no longer be able to synchronize their Active Directories. Instead of using Windows Azure Active Directory Synchronization, use Azure Active Directory Connect.
Message Center: MC45036 – We are removing Windows Azure Active Directory Synchronization from Office 365
Posted: April 13, 2016
Additional Information: Upgrade Windows Azure Active Directory Sync (“DirSync”) and Azure Active Directory Sync (“Azure AD Sync”)
Action Required by: October 31, 2017 at 5:59 PM UTC
Details: On October 31st, 2017, Exchange Online mailboxes in Office 365 will require connections from Outlook for Windows use MAPI over HTTP, our new method of connectivity and transport between Outlook for Windows and Exchange. In May of 2014, Microsoft introduced MAPI over HTTP as a replacement for RPC over HTTP. RPC over HTTP was a legacy connection protocol that is being deprecated from Exchange Online. Beginning October 31, 2017, Outlook for Windows clients using RPC over HTTP will be unable to access their Exchange Online mailbox. The necessary action depends on the version of Outlook in use in your organization. If you are using Outlook 2007 or earlier, you need to upgrade. Outlook 2007 does not contain support for the MAPI/HTTP protocol. We encourage you to update to the Office 365 ProPlus subscription, or access Outlook via the web browser (which is included in your current subscription plan). Outlook 2010-2016 customers will need to ensure their version of Outlook for Windows is set up to support MAPI/HTTP. At a minimum, you should ensure you have installed the December 2015 update. Lastly, ensure your Outlook clients are not using a registry key to block MAPI/HTTP.
Message Center: MC85988 – Potential service disruption for Outlook for Windows users
Posted: November 16, 2016
Additional Information: KB3201590: RPC over HTTP deprecated in Office 365 on October 31, 2017
On ADFS page you get error: 00000000-0000-0000-0d00-0080000000e1
Event viewer: Event 364 Microsoft.IdentityServer.Web.IdPInitiatedSignonPageDisabledException: MSIS7012: An error occurred while processing the request.
Get-AdfsProperties | select EnableIdPInitiatedSignonPage
Set-AdfsProperties -EnableIdPInitiatedSignonPage $true
If you’re a customer who uses Azure Active Directory Connect, you’ll want to know that Microsoft just released version 1.1.343.0, which adds support for Windows Server 2016 and SQL Server 2016 and fixes some bugs.
– Added support for installing Azure AD Connect on Windows Server 2016 standard or better.
– Added support for using SQL Server 2016 as the remote database for Azure AD Connect.
– Added support for managing AD FS 2016 using Azure AD Connect.
– Sometimes, installing Azure AD Connect fails because it is unable to create a local service account whose password meets the level of complexity specified by the organization’s password policy.
– Fixed an issue where join rules are not re-evaluated when an object in the connector space simultaneously becomes out-of-scope for one join rule and become in-scope for another. This can happen if you have two or more join rules whose join conditions are mutually exclusive.
– Fixed an issue where inbound synchronization rules (from Azure AD) which do not contain join rules are not processed if they have lower precedence values than those containing join rules.
On December 2010 i wrote an article: automatically move computers to the right OU.
In MDT 2012 update 1 this was an issue: MDT 2012 settings per task sequence
In MDT 2013 Update 2 this is still a issue:
How to fix:
I changed DeployWiz_SelectTS.vbs file and it work again
1. Edit DeployWiz_SelectTS.vbs
2. Add after Function ValidateTSList and Dim oTS
Set Oshell = createObject(“Wscript.shell”)
3. Add between End if and End Function
sCmd = “wscript.exe “”” & oUtility.ScriptDir & “\ZTIGather.wsf”””
oItem = oSHell.Run(sCmd, , true)
The Microsoft Deployment Toolkit (MDT), build 8443, is now available on the Microsoft Download Center. This update requires the Windows Assessment and Deployment Kit (ADK) for Windows 10, version 1607, available on the Microsoft Hardware Dev Center (adksetup.exe file version 10.1.14393.0).
You may notice that we are not tagging this release with a year or update version. To better align with the current branches of Windows 10 and Configuration Manager, and to simplify the branding and release process, we are now just referring to it as the “Microsoft Deployment Toolkit”, using the build number to distinguish each release. This is not necessarily a “current branch” of MDT; we are committed to updating MDT as needed with revisions to Windows, the Windows ADK, and Configuration Manager.
Here is a summary of the significant changes in this build of MDT:
- Supported configuration updates
- Windows ADK for Windows 10, version 1607
- Windows 10, version 1607
- Windows Server 2016
- Configuration Manager, version 1606
- Quality updates
- Deployment Wizard scaling on high DPI devices
- Johan’s “uber bug” for computer replace scenario
- Multiple fixes for the Windows 10 in-place upgrade scenario
- Several fixes to Configure ADDS step
- Removed imagex/ocsetup dependencies, rely solely on DISM
- Includes the latest Configuration Manager task sequence binaries (version 1606)
Zerto Virtual Replication Ends Hypervisor Vendor Lock-In
Zerto Virtual Replication (ZVR) is the first hypervisor-based replication solution to offer enterprise-class cross-hypervisor replication, disaster recovery, data protection and workload mobility. With ZVR, IT departments can automatically convert Hyper-V VMs to VMware, convert VMware VMs to Hyper- V, & convert Hyper-V to AWS for increased flexibility and cost savings.