Adaptiva Support Statement for Configuration Manager
Adaptiva is committed to remaining current with regard to Microsoft Configuration Manager releases. Our official support statement is that we will support any new current branch build of ConfigMgr within 4 weeks of it being generally available (Slow-Ring).
Builds are tested against both the technical preview release of ConfigMgr and the production build after its public release and we endeavor to perform thorough current Adaptiva build validation as well as regression testing against all new features and changes to existing features where possible.
If you believe a compatibility issue exists between a version of Adaptiva that you are running and a feature in ConfigMgr, please log a support ticket and we will investigate as soon as possible.
The table below shows the current minimum supported Adaptiva version for each release of ConfigMgr (latest version of ConfigMgr supported is shown at the top).
| Configuration Manager Version (descending) |
Min. Adaptiva Version | Notes |
|---|---|---|
| ConfigMgr 2403 | 5.5.677.1* |
Testing complete No issues to report |
| ConfigMgr 2309 | 5.5.677.1* |
Testing complete No issues to report *NOTE: Additional registry keys available to improve support for UUP deployments. Follow the article for updates: Using Unified Update Platform (UUP) with Adaptiva OneSite – Adaptiva Support Portal |
| ConfigMgr 2303 | 5.5.677.1* |
Testing complete No issues to report *NOTE: UUP support starting March 28, 2023 requires Adaptiva version 8.1.936.1000 as the minimum version with Byte Level Patching enabled. UUP is supported on ConfigMgr builds 2203 and later. With additional configuration in Client Settings, it can be supported on build 2111. |
| ConfigMgr 2211 | 5.5.677.1* |
Testing complete. No issues have been found. *NOTE: See 2303 |
| ConfigMgr 2207 | 5.5.677.1* |
Testing completed. No issues found. *NOTE: See 2303 |
| ConfigMgr 2203 | 5.5.677.1* |
Testing completed. No issues found. *NOTE: See 2303 |
| ConfigMgr 2111 | 5.5.677.1* |
Testing completed. No issues found *NOTE: See 2303 |
| ConfigMgr 2107 | 5.5.677.1 |
Testing completed: No issues found NOTE: The new Implicit Uninstall feature may experience delays up to 25 minutes before the content request is submitted for download. This is true even with Policy Bandwidth Management enabled. This is by design in ConfigMgr |
| ConfigMgr 2103 | 5.5.677.1 | |
| ConfigMgr 2010 | 5.5.677.1 | |
| ConfigMgr 2006 | 5.5.677.1 | |
| ConfigMgr 2002 | 5.5.677.1 | |
| ConfigMgr 1910 Hotfix Rollup KB4537079 | 5.5.677.1 |
|
| SCCM 1906 | 5.5.677.1 | |
| SCCM 1902 | 5.5.677.1 | |
| SCCM 1810 | 5.5.677.1 |
|
| SCCM 1806 | 5.5.677.1 |
|
| SCCM 1802 Hotfix KB4339794 | 5.5.674.0 + Client 5.5.674.1 |
|
| SCCM 1710, 1710 UR1 & 1710 UR2 | 5.5.674.0 |
|
| SCCM 1706, 1706 U1, 1706 U2 & 1706 UR1 | 5.5.659.0 | |
| SCCM 1702 & 1702 UR1 | 5.5.659.0 | |
| SCCM 1610, 1610 U1, 1610 Interop Update & 1610 UR | 5.5.659.0 | |
| SCCM 1606 & 1606 UR1 | 5.5.659.0 | |
| SCCM 1602 & 1602 UR1 | 5.5.659.0 | |
| SCCM 1511 | 5.5.659.0 |
|
| SCCM 2012 (R2 SP1 CU4 and Below) | 4.5.630 | |
| SCCM 2007 (All Builds) | 5.5.673.0 |
|
| Please note: The versions shown above are the minimum supported version for the respective ConfigMgr version. All later versions of the Adaptiva server and client are also supported. |
Advisories
Applicable to all versions of Adaptiva when upgrading the ConfigMgr version:
- It is always advisable to upgrade the Adaptiva installation to the latest version when performing an ConfigMgr upgrade. The latest version can be found here
- The Adaptiva Server should always be upgraded before the clients. It's recommended that the Adaptiva Client and Adaptiva Workbench on the Adaptiva Server should be upgraded at the same time as the Adaptiva Server component itself. Other Adaptiva Clients in the environment can be upgraded at any time thereafter.
- In most cases Adaptiva and ConfigMgr can be upgraded independently of one another and in either order, see notes for each release for any changes to this.
- When upgrading the ADK to version 1607/14393 or later, take a backup of the existing bcdedit and point the P2P PXE Perspective - bcdedit.exe text box to the new location after upgrade. This is in reference to the known issue here
- If upgrading the OneSiteDownloader.exe to version 5.5.668 or above, it is advisable to ensure that clients are upgraded to version 5.5.668 or higher prior to updating the boot image. Alternatively, ensure that the task sequence variable OneSiteServerNameOrIP is added to any active task sequences with a value set to the hostname or IP address of the respective Adaptiva server.
Comments
0 comments
Article is closed for comments.