For example, Elasticsearch 6.8.x will be maintained until the GA release of Elasticsearch 8.0.0. At the release of Elasticsearch 8.0.0, we will continue to maintain the last 7.x series, and begin maintaining the 8.0.x minor series, then 8.1.x series, then 8.2.x series of minor releases. Hello Guys and welcome back to another videoHow to download Smiling X Corp 2 Mod ApkI hope you liked our today's video if then make sure to like and subscrib. Tensorflow 1.x not available for python 3.8 #39768. Cboettig opened this issue on May 21, 2020 9 comments. Stat:awaiting response subtype: ubuntu/linux TF 1.15 type:build/install. Cboettig added the type:build/install label on May 21, 2020. DirectX Description. DirectX is a Windows-based collection of APIs designed by Microsoft to run and display applications which feature high-performance multimedia such as full-col.
- Xversion 1 3 6 X 8 0 Doors
- Xversion 1 3 6 X 8
- Xversion 1 3 6 X 8 Pressure Treated Gothic Fence
- Xversion 1 3 6 X 8 Fiberglass Front Door
Download
Abstract
This document describes how to download and install IBM® Data Studio Version 4.1.x.
Download Description
IBM Data Studio is a no-charge offering that consists of the Data Studio client.
The Data Studio client provides an integrated development environment for instance and database administration, routine and Java application development, and query tuning that can be installed with other IBM software products so that they can share a common environment.
Xversion 1 3 6 X 8 0 Doors
Important: The Data Studio web console is no longer supported, however you can easily perform the same tasks with our replacement offering, the IBM Data Server Manager(DSM). You can download DSM from the IBM Support Portal, and get detailed installation and configuration information at the DSM Knowledge Center.
For more details about this release, see the following resources:
For information about the high level features in IBM Data Studio and the databases that are supported, see IBM Data Studio features: by data server and component on the support site.
Prerequisites
You must meet the following prerequisites to install IBM Data Studio:
- For the client, approximately 2GB of disk space is required for the product package installation.
- For the Data Studio client, you need Installation Manager Version 1.8.7 or later.Installation Manager Version 1.8.7 is included with the Data Studio client. You can also obtain the latest version of Installation Manager from the following support site: http://www.ibm.com/support/docview.wss?uid=swg27025142.
For a complete list of the hardware and software requirements, see System requirements for IBM Data Studio.
Before you begin
Important:- In the Data Studio V4.1.3, eclipse is upgraded to Eclipse Neon(4.6.3).
- Upgrade scenario DS 4.1.2 to 4.1.3 is not supported.
- If you previously installed 32-bit products on your computer with a 32-bit version of Installation Manager, you must download the 32-bit version of the IBM Data Studio package because it includes a compatible 32-bit version of Installation Manager. You can then use the 32-bit package to install either a 32-bit or 64-bit version of the IBM Data Studio product.Note: If Data Studio fails to start after you installed Version 4.1.3 on Windows 32-bit, see the troubleshooting instructions at the following link: http://www-01.ibm.com/support/docview.wss?uid=swg22013128.
- For Microsoft Windows 8, you must have administrator privileges and disable the user account control (UAC).
Use the following information to download IBM Data Studio Version 4.1.x and then perform a typical installation.
You download IBM Data Studio Version 4.1.x from the web. IBM Passport Advantage customers who have a DB2 license can also download IBM Data Studio Version 4.1.x from IBM Passport Advantage.
IBM Data Studio Version 4.1.x uses IBM Installation Manager to install the client. For complete installation instructions, see the following topics in the Data Studio Information Center:
- Installing the Data Studio client
- Installing the Data Studio client
Tip: Download the Quick Start Guide for IBM Data Studio Version 4.1.1 to view a diagram of a typical installation and to help you install each component of IBM Data Studio.
Step 1. Click one of the following tabs to either download from the Web or from Passport Advantage:
Tab navigation
- Download from the web - selected tab,
- Download from IBM Passport Advantage
Step 2. Click the following tab for the Data Studio component that you want to download and install:
Tip: See the following support page for information about the available fixes that you can download and install: Fix packs for IBM Data Studio.
To download and install the Data Studio client Version 4.1.x:
- Download the full Data Studio product image:You can also choose to download the full Data Studio image, which include a copy of IBM Installation Manager. Downloading the full product image is useful when installing Data Studio on a computer without an internet connection or when you want to install Data Studio on multiple computers. For more information about installing Data Studio on multiple computers, see Enterprise deployment of the IBM Data Studio client.
- Download the client from the download table below.Tips:
- You can use either the 32-bit or 64-bit versions of Installation Manager to install the either a 32-bit or 64-bit version of Data Studio.
- If you previously installed 32-bit products on your computer with a 32-bit version of Installation Manager, you must download the 32-bit version of the IBM Data Studio package because it includes a compatible 32-bit version of Installation Manager. You can then use the 32-bit package to install either a 32-bit or 64-bit version of the IBM Data Studio product.
- Extract product package to a directory on your computer, for example: C:tempdatastudio.
Important: To avoid possible installation errors, the directory path where you extract the compressed product files must not exceed 90 characters in length. - From the directory where you extracted the product, run the executable file:
- On Windows, run:
launchpad.exe
. - On Linux, run:
launchpad.sh
.
- You must run this file as an administrator if you plan to perform an administrative installation.
- If you are a not an administrator, and you are on a 64-bit version of Windows, you must run the
launchpad_win_nonadmin64.exe
file instead of thelaunchpad.exe
file.
- On Windows, run:
- Follow the installation wizard steps in IBM Installation Manager to install the product.
- Download the client from the download table below.
URL | SIZE | RELEASE DATE |
---|---|---|
Full Data Studio product images | 1.5 GB | 28 Aug 2014 |
Step 2: If you are a IBM Passport Advantage customer with a DB2 license, click one of the following tabs for the operating system onto which you want to download and install IBM Data Studio:
Tab navigation
- AIX - selected tab,
- HP-UX
- Linux
- Solaris
- Windows
Supported platforms
For the versions of Microsoft Windows that are supported, see the System requirements for IBM Data Studio.
Downloadable parts
Refer to the tables below for details about what each part contains.
Required parts
To install IBM Data Studio Version 4.1.x on the Windows platform, you must download the following parts:
Part number | File name | Description |
---|---|---|
CN6FBML | CN6FBML.zip | IBM Data Studio Client V4.1.2 for Windows |
CN1B2ML | CN1B2ML.zip | IBM Data Studio Client V4.1.1 for Windows |
CN1AUML | CN1AUML.zip | |
CN0RWML | CN0RWML.zip |
Supported platforms
For the versions of Linux that are supported, see the System requirements for IBM Data Studio.
Downloadable parts
Refer to the tables below for details about what each part contains.
Required parts
To install IBM Data Studio Version 4.1.x on the Linux platform, you must download the following parts:
Part number | File name | Description |
---|---|---|
CN6FCML | CN6FCML.tar.gz | IBM Data Studio Client V4.1.2 for Linux |
CN1B3ML | CN1B3ML.zip | IBM Data Studio Client V4.1.1 for Linux |
CN1AVML | CN1AVML.zip | |
CN1AXML | CN1AXML.zip | |
CN1AWML | CN1AWML.zip | |
CN0RWML | CN0RWML.zip |
Supported platforms
For the versions of AIX that are supported, see the System requirements for IBM Data Studio.
Downloadable parts
Refer to the tables below for details about what each part contains.
Required parts
To install IBM Data Studio web console Version 4.1.1 on the AIX platform, you must download the following parts:
Part number | File name | Description |
---|---|---|
CN1AYML | CN1AYML.zip | IBM Data Studio web console 4.1.1 for AIX |
CN0RWML | CN0RWML.zip | IBM Data Studio V4.1.1 Quick Start Guide for the client and web console |
Supported platforms
For the versions of HP-UX that are supported, see the System requirements for IBM Data Studio.
Downloadable parts
Refer to the tables below for details about what each part contains.
Required parts
To install IBM Data Studio web console Version 4.1.1 on the HP-UX platform, you must download the following parts:
Part number | File name | Description |
---|---|---|
CN1AZML | CN1AZML.zip | IBM Data Studio web console 4.1.1 for HPUX |
CN0RWML | CN0RWML.zip | IBM Data Studio V4.1.1 Quick Start Guide for the client and web console |
Supported platforms
For the versions of Solaris that are supported, see the System requirements for IBM Data Studio.
Downloadable parts
Refer to the tables below for details about what each part contains.
Required parts
To install IBM Data Studio web console Version 4.1.1 on the Solaris platform, you must download the following parts:
Part number | File name | Description |
---|---|---|
CN1B0ML | CN1B0ML.zip | IBM Data Studio web console 4.1.1 for Solaris SPARC |
CN1B1ML | CN1B1ML.zip | IBM Data Studio web console 4.1.1 for Solaris x86-64 |
CN0RWML | CN0RWML.zip | IBM Data Studio V4.1.1 Quick Start Guide for the client and web console |
Downloading the product from Passport Advantage
IMPORTANT: Before you start, verify that you have an IBM ID, and that the Passport Advantage® primary contact at your company granted your IBM ID permission to access and download IBM Data Studio. If you do not have an IBM ID, you can create one at the Passport Advantage site.
- Locate the IBM Data Studio Version 4.1.x eAssembly for the platform or platforms that you need to use. The eAssembly part numbers are provided in the tabbed sections of this document.
- Download the parts that you need from Passport Advantage at: http://www.ibm.com/software/passportadvantage.
If you are not familiar with Passport Advantage, view a short tutorial on Downloading Products from Passport Advantage from the IBM Electronic Support Channel on YouTube. You can also download the video directly from IBM Electronic Support. - Unpack each of the parts onto your system.
- Follow the instructions in the Quick Start Guide for IBM Data Studio to install the product.
Tip: See the following support page for information about the available fixes that you can download and install: Fix packs for IBM Data Studio.
Post-Installation Instructions
After you install the product, see the following topics for post-installation information:
If you plan to tune single SQL statements that run on DB2 for z/OS by using the Statistics Advisor and related tools, see Configuring DB2 for z/OS Subsystems for the No-Charge Tuning Features.
[{'Product':{'code':'SS62YD','label':'IBM Data Studio'},'Business Unit':{'code':'BU053','label':'Cloud & Data Platform'},'Component':'Installation/Migration','Platform':[{'code':'PF002','label':'AIX'},{'code':'PF010','label':'HP-UX'},{'code':'PF016','label':'Linux'},{'code':'PF027','label':'Solaris'},{'code':'PF033','label':'Windows'},{'code':'PF035','label':'z/OS'}],'Version':'4.1.1.0;4.1.2.0;4.1.3.0','Edition':','Line of Business':{'code':'LOB10','label':'Data and AI'}}]
Document Information
Modified date:
15 June 2018
-->15 June 2018
The Azure Active Directory (Azure AD) team regularly updates Azure AD Connect with new features and functionality. Not all additions are applicable to all audiences.
Minecraft windows 10 edition free with multiplayer. This article is designed to help you keep track of the versions that have been released, and to understand what the changes are in the latest version.
Looking for the latest versions?
You can upgrade your AADConnect server from all supported versions with the latest versions:
- If you are using Windows Server 2016 or newer you should use Azure AD Connect V2.0. You can download the latest version of Azure AD Connect 2.0 using this link. The release notes for the latest V2.0 release are here
- If you are still using an older version of Windows Server you should use Azure AD Connect V1.6. You can download the latest version of Azure AD Connect V1 using this link. The release notes for the latest V1.6 release are here
- We are only applying critical changes to the V1 versions going forward, and you may not find some of the features and fixes for V2 in the V1 releases - so you should upgrade to the V2 version as soon as possible.
This table is a list of related topics:
Topic | Details |
---|---|
Steps to upgrade from Azure AD Connect | Different methods to upgrade from a previous version to the latest Azure AD Connect release. |
Required permissions | For permissions required to apply an update, see accounts and permissions. |
Important
On 31 August 2022, all 1.x versions of Azure Active Directory (Azure AD) Connect will be retired because they include SQL Server 2012 components that will no longer be supported. Either upgrade to the most recent version of Azure AD Connect (2.x version) by that date, or evaluate and switch to Azure AD cloud sync.
You need to make sure you are running a recent version of Azure AD Connect to receive an optimal support experience.
If you run a retired version of Azure AD Connect it may unexpectedly stop working and you may not have the latest security fixes, performance improvements, troubleshooting and diagnostic tools and service enhancements. Moreover, if you require support we may not be able to provide you with the level of service your organization needs.
Go to this article to learn more about Azure Active Directory Connect V2.0, what has changed in V2.0 and how this change impacts you.
Please refer to this article to learn more about how to upgrade Azure AD Connect to the latest version.
For version history information on retired versions, see Azure AD Connect version release history archive
Note
Releasing a new version of Azure AD Connect is a process that requires several quality control step to ensure the operation functionality of the service, and while we go through this process the version number of a new release as well as the release status will be updated to reflect the most recent state.Not all releases of Azure AD Connect will be made available for auto upgrade. The release status will indicate whether a release is made available for auto upgrade or for download only. If auto upgrade was enabled on your Azure AD Connect server then that server will automatically upgrade to the latest version of Azure AD Connect that is released for auto upgrade. Note that not all Azure AD Connect configurations are eligible for auto upgrade.
To clarify the use of Auto Upgrade, it is meant to push all important updates and critical fixes to you. This is not necessarily the latest version because not all versions will require/include a fix to a critical security issue (just one example of many). Critical issues would usually be addressed with a new version provided via Auto Upgrade. If there are no such issues, there are no updates pushed out using Auto Upgrade, and in general if you are using the latest auto upgrade version you should be good.However, if you'd like all the latest features and updates, the best way to see if there are any is to check this page and install them as you see fit.
Please follow this link to read more about auto upgrade
1.6.16.0
Note
This is an update release of Azure AD Connect. This version is intended to be used by customers who are running an older version of Windows Server and cannot upgrade their server to Windows Server 2016 or newer at this time. You cannot use this version to update an Azure AD Connect V2.0 server.This release is not supported on Windows Server 2016 or newer. This release includes SQL Server 2012 components and will be retired on August 31st 2022. You will need to upgrade your Server OS and AADConnect version before that date.We will begin auto upgrading eligible tenants when this version is available for download, autoupgrade will take a few weeks to complete.
Release status
10/13/2021: Released for download and auto upgrade.
Bug fixes
- We fixed a bug where the Autoupgrade process attempted to upgrade AADConnect servers that are running older Windows OS version 2008 or 2008 R2 and failed. These versions of Windows Server are no longer supported. In this release we only attempt autoupgrade on machines that run Windows Server 2012 or newer.
- We fixed an issue where, under certain conditions, miisserver would be crashing due to access violation exception.
2.0.28.0
Note
This is a maintenance update release of Azure AD Connect. This release requires Windows Server 2016 or newer.
Release status
9/30/2021: Released for download only, not available for auto upgrade.
Xversion 1 3 6 X 8
Bug fixes
- On the Group Writeback Permissions page in the Wizard we removed a download button for a PowerShell script and changed the text on the wizard page to include a learn more link, which links to an online article where the PowerShell script can be found.
- We fixed a bug where the wizard was incorrectly blocking the installation when the .NET version on the server was greater than 4.6, due to missing registry keys. Those registry keys are not required and should only block installation if they are intentionally set to false.
- We fixed a bug where an error would be thrown if phantom objects are found during during the initialization of a sync step. This would block the sync step or remove transient objects. The phantom objects are now ignored.Note: A phantom object is a placeholder for an object which is not there or has not been seen yet, for example if a source object has a reference for a target object which is not there then we create the target object as a phantom.
Functional changes
- A change was made that allows a user to deselect objects and attributes from the inclusion list, even if they are in use. Instead of blocking this, we now provide a warning.
1.6.14.2
Note
This is an update release of Azure AD Connect. This version is intended to be used by customers who are running an older version of Windows Server and cannot upgrade their server to Windows Server 2016 or newer at this time. You cannot use this version to update an Azure AD Connect V2.0 server.We will begin auto upgrading eligible tenants when this version is available for download, autoupgrade will take a few weeks to complete.
Release status
Xversion 1 3 6 X 8 Pressure Treated Gothic Fence
9/21/2021: Released for download and auto upgrade.
Functional changes
- We added the latest versions of MIM Connectors (1.1.1610.0). More information can be found at the release history page of the MiM connectors
- We have added a configuration option to disable the Soft Matching feature in Azure AD Connect. We advise customers to disable soft matching unless they need it to take over cloud only accounts. This article shows how to disable Soft Matching.
Bug fixes
- We fixed a bug where the DesktopSSO settings were not persisted after upgrade from a previous version.
- We fixed a bug that caused the Set-ADSync*Permission cmdlets to fail.
2.0.25.1
Note
This is a hotfix update release of Azure AD Connect. This release requires Windows Server 2016 or newer and fixes a security issue that is present in version 2.0 of Azure AD Connect, as well as some other bug fixes.
Release status
9/14/2021: Released for download only, not available for auto upgrade.
Bug fixes
- We fixed a security issue where an unquoted path was used to point to the Azure AD Connect service. This path is now a quoted path.
- Fixing an import config issue with writeback enabled when using the existing AD connector account.
- We fixed an issue in Set-ADSyncExchangeHybridPermissions and other related cmdlets, which were broken from 1.6 due to an invalid inheritance type.
- The cmdlet we published in a previous release to set the TLS version had an issue where it overwrites the keys, destroying any values that were in them. We fixed this by only creating a new key if one does not already exist. A warning is also added to let users know the TLS registry changes are not exclusive to Azure AD Connect and may impact other applications on the same server as well.
- We added a check to enforce auto upgrade for V2.0 to require Windows Server 2016 or newer.
- We added 'Replicating Directory Changes' permission in the Set-ADSyncBasicReadPermissions cmdlet.
- We made a change to prevent UseExistingDatabase and import configuration from being used together since these could contain conflicting configuration settings.
- We made a change to allow a user with the Application Admin role to change the App Proxy service configuration.
- We removed the '(Preview)' label from the labels of Import/Export settings - this functionality has been in General Availability for some time now.
- We change some labels that still refered to 'Company Administrator' - we now use the role name 'Global Administrator'.
- We created new AAD Kerberos PowerShell cmdlets '*-AADKerberosServer' to add a Claims Transform rule to the AAD Service Principal.
Functional changes
- We added the latest versions of MIM Connectors (1.1.1610.0). More information can be found at the release history page of the MiM connectors
- We have added a configuration option to disable the Soft Matching feature in Azure AD Connect. We advise customers to disable soft matching unless they need it to take over cloud only accounts. This article shows how to disable Soft Matching.
2.0.10.0
Release status
8/19/2021: Released for download only, not available for auto upgrade.
Note
This is a hotfix update release of Azure AD Connect. This release requires Windows Server 2016 or newer. This hotfix addresses an issue that is present in version 2.0 as well as in Azure AD Connect version 1.6. If you are running Azure AD Connect on an older Windows Server you should install the 1.6.13.0 build instead.
Release status
8/19/2021: Released for download only, not available for auto upgrade.
Known issues
- Under certain circumstances the installer for this version will display an error mentioning that TLS 1.2 is not enabled and will stop the installation. This is due to an error in the code that verifies the registry setting for TLS 1.2. We will correct this in a future release. Customers who see this issue should follow the instructions for enabling TLS 1.2 that can be found in the article 'TLS 1.2 enforcement for Azure AD Connect'.
Bug fixes
- We fixed a bug where, when a domain is renamed, Password Hash Sync would fail with an error indicating 'a specified cast is not valid' in the Event log. This is a regression from earlier builds.
1.6.13.0
Note
This is a hotfix update release of Azure AD Connect. This release is intended for customers who are running Azure AD Connect on a server with Windows Server 2012 or 2012 R2.
8/19/2021: Released for download only, not available for auto upgrade.
Bug fixes
- We fixed a bug where, when a domain is renamed, Password Hash Sync would fail with an error indicating 'a specified cast is not valid' in the Event log. This is a regression from earlier builds.
Functional changes
There are no functional changes in this release
2.0.9.0
Release status
8/17/2021: Released for download only, not available for auto upgrade.
Bug fixes
Note
Xversion 1 3 6 X 8 Fiberglass Front Door
This is a hotfix update release of Azure AD Connect. This release requires Windows Server 2016 or newer. This release addresses an issue that is present in version 2.0.8.0, this issue is not present in Azure AD Connect version 1.6
- We fixed a bug where, when syncing a large number of Password Hash Sync transactions, the Event log entry length would exceed the maximum allowed length for a Password Hash Sync event entry. We now split the lengthy log entry into multiple entries.
2.0.8.0
Note
This is a security update release of Azure AD Connect. This release requires Windows Server 2016 or newer. If you are using an older version of Windows Server, please use version 1.6.11.3.This release addresses a vulnerability as documented in this CVE. For more information about this vulnerability please refer to the CVE.You can download the latest version of Azure AD Connect 2.0 using this link.
Release status
8/10/2021: Released for download only, not available for auto upgrade.
Functional changes
There are no functional changes in this release
1.6.11.3
Note
This is security update release of Azure AD Connect. This version is intended to be used by customers are running an older version of Windows Server and cannot upgrade their server to Windows Server 2016 or newer as this time. You cannot use this version to update an Azure AD Connect V2.0 server.This release addresses a vulnerability as documented in this CVE. For more information about this vulnerability please refer to the CVE.You can download the latest version of Azure AD Connect 1.6 using this link
Release status
8/10/2021: Released for download only, not available for auto upgrade.
Functional changes
There are no functional changes in this release
2.0.3.0
Note
This is a major release of Azure AD Connect. Please refer to the Azure Active Directory V2.0 article for more details.
Release status
7/20/2021: Released for download only, not available for auto upgrade
Functional changes
- We have upgraded the LocalDB components of SQL Server to SQL 2019.
- This release requires Windows Server 2016 or newer, due to the requirements of SQL Server 2019. Note that an in-place upgrade of Windows Server on an Azure AD Connect server is not supported, so you may need to use a swing migration.
- In this release we enforce the use of TLS 1.2. If you have enabled your Windows Server for TLS 1.2, AADConnect will use this protocol. If TLS 1.2 is not enabled on the server you will see an error message when attempting to install AADConnect and the installation will not continue until you have enabled TLS 1.2. Note that you can use the new 'Set-ADSyncToolsTls12' cmdlets to enable TLS 1.2 on your server.
- With this release, you can use a user with the user role 'Hybrid Identity Administrator' to authenticate when you install Azure AD Connect. You no longer need the Global Administrator role for this.
- We have upgraded the Visual C++ runtime library to version 14 as a prerequisite for SQL Server 2019
- This release uses the MSAL library for authentication, and we have removed the older ADAL library, which will be retired in 2022.
- We no longer apply permissions on the AdminSDHolders, following Windows security guidance. We changed the parameter 'SkipAdminSdHolders' to 'IncludeAdminSdHolders' in the ADSyncConfig.psm1 module.
- Passwords will now be reevaluated when an expired password is 'unexpired', regardless of whether the password itself is changed. If for a user the password is set to 'Must change password at next logon', and this flag is cleared (thus 'unexpiring' the password) then the 'unexpired' status and the password hash are synced to Azure AD, and when the user attempts to sign in in Azure AD they can use the unexpired password.To sync an expired password from Active Directory to Azure Active Directory please use the Synchronizing temporary passwords feature in Azure AD Connect. Note that you will need to enable password writeback to use this feature, so the password the use updates is written back to Active Directory too.
- We have added two new cmdlets to the ADSyncTools module to enable or retrieve TLS 1.2 settings from the Windows Server.
- Get-ADSyncToolsTls12
- Set-ADSyncToolsTls12
You can use these cmdlets to retrieve the TLS 1.2 enablement status, or set it as needed. Note that TLS 1.2 must be enabled on the server for the installation or AADConnect to succeed.
- We have revamped ADSyncTools with several new and improved cmdlets. The ADSyncTools article has more details about these cmdlets.The following cmdlets have been added or updated- Clear-ADSyncToolsMsDsConsistencyGuid
- ConvertFrom-ADSyncToolsAadDistinguishedName
- ConvertFrom-ADSyncToolsImmutableID
- ConvertTo-ADSyncToolsAadDistinguishedName
- ConvertTo-ADSyncToolsCloudAnchor
- ConvertTo-ADSyncToolsImmutableID
- Export-ADSyncToolsAadDisconnectors
- Export-ADSyncToolsObjects
- Export-ADSyncToolsRunHistory
- Get-ADSyncToolsAadObject
- Get-ADSyncToolsMsDsConsistencyGuid
- Import-ADSyncToolsObjects
- Import-ADSyncToolsRunHistory
- Remove-ADSyncToolsAadObject
- Search-ADSyncToolsADobject
- Set-ADSyncToolsMsDsConsistencyGuid
- Trace-ADSyncToolsADImport
- Trace-ADSyncToolsLdapQuery - We now use the V2 endpoint for import and export and we fixed issue in the Get-ADSyncAADConnectorExportApiVersion cmdlet. You can read more about the V2 endpoint in the Azure AD Connect sync V2 endpoint article.
- We have added the following new user properties to sync from on-prem AD to Azure AD
- employeeType
- employeeHireDate - This release requires PowerShell version 5.0 or newer to be installed on the Windows Server. Note that this version is part of Windows Server 2016 and newer.
- We increased the Group sync membership limits to 250k with the new V2 endpoint.
- We have updated the Generic LDAP connector and the Generic SQL Connector to the latest versions. Read more about these connectors here:- Generic LDAP Connector reference documentation- Generic SQL Connector reference documentation
- In the M365 Admin Center, we now report the AADConnect client version whenever there is export activity to Azure AD. This ensures that the M365 Admin Center always has the most up to date AADConnect client version, and that it can detect when you're using an outdated version
Bug fixes
- We fixed an accessibility bug where the screen reader is announcing an incorrect role of the 'Learn More' link.
- We fixed a bug where sync rules with large precedence values (i.e. 387163089) cause an upgrade to fail. We updated the sproc 'mms_UpdateSyncRulePrecedence' to cast the precedence number as an integer prior to incrementing the value.
- We fixed a bug where group writeback permissions are not set on the sync account if a group writeback configuration is imported. We now set the group writeback permissions if group writeback is enabled on the imported configuration.
- We updated the Azure AD Connect Health agent version to 3.1.110.0 to fix an installation failure.
- We are seeing an issue with non-default attributes from exported configurations where directory extension attributes are configured. When importing these configurations to a new server/installation, the attribute inclusion list is overridden by the directory extension configuration step, so after import only default and directory extension attributes are selected in the sync service manager (non-default attributes are not included in the installation, so the user must manually reenable them from the sync service manager if they want their imported sync rules to work). We now refresh the AAD Connector before configuring directory extension to keep existing attributes from the attribute inclusion list.
- We fixed an accessibility issues where the page header's font weight is set as 'Light'. Font weight is now set to 'Bold' for the page title, which applies to the header of all pages.
- The function Get-AdObject in ADSyncSingleObjectSync.ps1 has been renamed to Get-AdDirectoryObject to prevent ambiguity with the AD cmdlet.
- The SQL function 'mms_CheckSynchronizationRuleHasUniquePrecedence' allow duplicates precedence on outbound sync rules on different connectors. We removed the condition that allows duplicate rule precedence.
- We fixed a bug where the Single Object Sync cmdlet fails if the attribute flow data is null i.e. on exporting delete operation
- We fixed a bug where the installation fails because the ADSync bootstrap service cannot be started. We now add Sync Service Account to the Local Builtin User Group before starting the bootstrap service.
- We fixed an accessibility issue where the active tab on AAD Connect wizard is not showing correct color on High Contrast theme. The selected color code was being overwritten due to missing condition in normal color code configuration.
- We addressed an issue where users were allowed to deselect objects and attributes used in sync rules using the UI and PowerShell. We now show friendly error message if you try to deselect any attribute or object that is used in any sync rules.
- We made some updates to the 'migrate settings code' to check and fix backward compatibility issue when the script is ran on an older version of Azure AD Connect.
- Fixed a bug where, when PHS tries to look up an incomplete object, it does not use the same algorithm to resolve the DC as it used originally to fetch the passwords. In particular, it is ignoring affinitized DC information. The Incomplete object lookup should use the same logic to locate the DC in both instances.
- We fixed a bug where AADConnect cannot read Application Proxy items using Microsoft Graph due to a permissions issue with calling Microsoft Graph directly based on AAD Connect client id. To fix this, we removed the dependency on Microsoft Graph and instead use AAD PowerShell to work with the App Proxy Application objects.
- We removed the writeback member limit from 'Out to AD - Group SOAInAAD Exchange' sync rule
- We fixed a bug where, when changing connector account permissions, if an object comes in scope that has not changed since the last delta import, a delta import will not import it. We now display warning alerting user of the issue.
- We fixed an accessibility issue where the screen reader is not reading radio button position. We added added positional text to the radio button accessibility text field.
- We updated the Pass-Thru Authentication Agent bundle. The older bundle did not have correct reply URL for HIP's first party application in US Gov.
- We fixed a bug where there is a 'stopped-extension-dll-exception' on AAD connector export after clean installing AADConnect version 1.6.X.X, which defaults to using DirSyncWebServices API V2, using an existing database. Previously the setting export version to v2 was only being done for upgrade, we changed so that it is set on clean install as well.
- The 'ADSyncPrep.psm1' module is no longer used and is removed from the installation.
Known issues
- The AADConnect wizard shows the 'Import Synchronization Settings' option as 'Preview', while this feature is generally Available.
- Some Active Directory connectors may be installed in a different order when using the output of the migrate settings script to install the product.
- The User Sign In options page in the Azure AD Connect wizard mentions 'Company Administrator'. This term is no longer used and needs to be replace by 'Global Administrator'.
- The 'Export settings' option is broken when the Sign In option has been configured to use PingFederate.
- While Azure AD Connect can now be deployed using the Hybrid Identity Administrator role, configuring Self Service Password Reset will still require user with the Global Administrator role.
- When importing the AADConnect configuration while deploying to connect with a different tenant than the original AADConnect configuration, directory extension attributes are not configured correctly.
1.6.4.0
Note
The Azure AD Connect sync V2 endpoint API is now available in these Azure environments:
- Azure Commercial
- Azure China cloud
- Azure US Government cloud
- This release will not be made available in the Azure German cloud
Release status
3/31/2021: Released for download only, not available for auto upgrade
Bug fixes
- This release fixes a bug in version 1.6.2.4 where, after upgrade to that release, the Azure AD Connect Health feature was not registered correctly and did not work. Customers who have deployed build 1.6.2.4 are requested to update their Azure AD Connect server with this build, which will correctly register the Health feature.
1.6.2.4
Important
Update per March 30, 2021: we have discovered an issue in this build. After installation of this build, the Health services are not registered. We recommend not installing this build. We will release a hotfix shortly.If you already installed this build, you can manually register the Health services by using the cmdlet as shown in this article
Note
- This release will be made available for download only.
- The upgrade to this release will require a full synchronization due to sync rule changes.
- This release defaults the AADConnect server to the new V2 end point. Note that this end point is not supported in the German national cloud and if you need to deploy this version in this environment you need to follow these instructions to switch back to the V1 end point. Failure to do so will result in errors in synchronization.
Release status
3/19/2021: Released for download, not available for auto upgrade
Functional changes
- Updated default sync rules to limit membership in written back groups to 50k members.
- Added new default sync rules for limiting membership count in group writeback (Out to AD - Group Writeback Member Limit) and group sync to Azure Active Directory (Out to AAD - Group Writeup Member Limit) groups.
- Added member attribute to the 'Out to AD - Group SOAInAAD - Exchange' rule to limit members in written back groups to 50k
- Updated Sync Rules to support Group Writeback v2-If the 'In from AAD - Group SOAInAAD' rule is cloned and AADConnect is upgraded.
- The updated rule will be disabled by default and so the targetWritebackType will be null.
- AADConnect will writeback all Cloud Groups (including Azure Active Directory Security Groups enabled for writeback) as Distribution Groups.-If the 'Out to AD - Group SOAInAAD' rule is cloned and AADConnect is upgraded.
- The updated rule will be disabled by default. However, a new sync rule 'Out to AD - Group SOAInAAD - Exchange' which is added will be enabled.
- Depending on the Cloned Custom Sync Rule's precedence, AADConnect will flow the Mail and Exchange attributes.
- If the Cloned Custom Sync Rule does not flow some Mail and Exchange attributes, then new Exchange Sync Rule will add those attributes.
- Note that Group Writeback V2 is in private preview at this moment and not publicly available.
- Added support for Selective Password hash Synchronization
- Added the new Single Object Sync cmdlet. Use this cmdlet to troubleshoot your Azure AD Connect sync configuration.
- Azure AD Connect now supports the Hybrid Identity Administrator role for configuring the service.
- Updated AADConnectHealth agent to 3.1.83.0
- New version of the ADSyncTools PowerShell module, which has several new or improved cmdlets.
- Clear-ADSyncToolsMsDsConsistencyGuid
- ConvertFrom-ADSyncToolsAadDistinguishedName
- ConvertFrom-ADSyncToolsImmutableID
- ConvertTo-ADSyncToolsAadDistinguishedName
- ConvertTo-ADSyncToolsCloudAnchor
- ConvertTo-ADSyncToolsImmutableID
- Export-ADSyncToolsAadDisconnectors
- Export-ADSyncToolsObjects
- Export-ADSyncToolsRunHistory
- Get-ADSyncToolsAadObject
- Get-ADSyncToolsMsDsConsistencyGuid
- Import-ADSyncToolsObjects
- Import-ADSyncToolsRunHistory
- Remove-ADSyncToolsAadObject
- Search-ADSyncToolsADobject
- Set-ADSyncToolsMsDsConsistencyGuid
- Trace-ADSyncToolsADImport
- Trace-ADSyncToolsLdapQuery
- Updated error logging for token acquisition failures.
- Updated 'Learn more' links on the configuration page to give more detail on the linked information.
- Removed Explicit column from CS Search page in the Old Sync UI
- Additional UI has been added to the Group Writeback flow to prompt the user for credentials or to configure their own permissions using the ADSyncConfig module if credentials have not already been provided in an earlier step.
- Auto-create MSA for ADSync Service Account on a DC.
- Added ability to set and get Azure Active Directory DirSync feature Group Writeback V2 in the existing cmdlets:
- Set-ADSyncAADCompanyFeature
- Get-ADSyncAADCompanyFeature
- Added 2 cmdlets to read AWS API version
- Get-ADSyncAADConnectorImportApiVersion - to get import AWS API version
- Get-ADSyncAADConnectorExportApiVersion - to get export AWS API version
- Changes made to synchronization rules are now tracked to assist troubleshooting changes in the service. The cmdlet 'Get-ADSyncRuleAudit' will retrieve tracked changes.
- Updated the Add-ADSyncADDSConnectorAccount cmdlet in the ADSyncConfig PowerShell module to allow a user in ADSyncAdmin group to change the AD DS Connector account.
Bug fixes
- Updated disabled foreground color to satisfy luminosity requirements on a white background. Added additional conditions for navigation tree to set foreground text color to white when a disabled page is selected to satisfy luminosity requirements.
- Increase granularity for Set-ADSyncPasswordHashSyncPermissions cmdlet - Updated PHS permissions script (Set-ADSyncPasswordHashSyncPermissions) to include an optional 'ADobjectDN' parameter.
- Accessibility bug fix. The screen reader would now describe the UX element that holds the list of forests as 'Forests list' instead of 'Forest List list'
- Updated screen reader output for some items in the Azure AD Connect wizard. Updated button hover color to satisfy contrast requirements. Updated Synchronization Service Manager title color to satisfy contrast requirements.
- Fixed an issue with installing AADConnect from exported configuration having custom extension attributes - Added a condition to skip checking for extension attributes in the target schema while applying the sync rule.
- Appropriate permissions are added on install if the Group Writeback feature is enabled.
- Fix duplicate default sync rule precedence on import
- Fixed an issue that caused a staging error during V2 API delta import for a conflicting object that was repaired via the health portal.
- Fixed an issue in the sync engine that caused CS objects to have an inconsistent link state
- Added import counters to Get-ADSyncConnectorStatistics output.
- Fixed unreachable domain de-selection(selected previously) issue in some corner cases during pass2 wizard.
- Modified policy import and export to fail if custom rule has duplicate precedence
- Fixed a bug in the domain selection logic.
- Fixes an issue with build 1.5.18.0 if you use mS-DS-ConsistencyGuid as the source anchor and have clone the In from AD - Group Join rule.
- Fresh AADConnect installs will use the Export Deletion Threshold stored in the cloud if there is one available and there is not a different one passed in.
- Fixed issue where AADConnect does not read AD displayName changes of hybrid-joined devices
1.5.45.0
Release status
07/29/2020: Released for download
Functional changes
This is a bug fix release. There are no functional changes in this release.
Fixed issues
- Fixed an issue where admin can't enable 'Seamless Single Sign On' if AZUREADSSOACC computer account is already present in the 'Active Directory'.
- Fixed an issue that caused a staging error during V2 API delta import for a conflicting object that was repaired via the health portal.
- Fixed an issue in the import/export configuration where disabled custom rule was imported as enabled.
Next steps
Learn more about Integrating your on-premises identities with Azure Active Directory.