Introducing Azure DevOps Server 2022 Update 1 RC1

Gloridel Morales

September 19th, 202313 0

Today we’re very excited to announce the first release candidate (RC1) of Azure DevOps Server 2022.1!

With this release, we’ve added many new features that you’ve been asking for. Here are a few of the highlights:

There are many more features with this release, and you can read all about those features in our release notes. You can download Azure DevOps Server 2022.1 RC1 today. A direct upgrade to Azure DevOps Server is supported from any version of TFS, including Team Foundation Server 2015 and newer. Let us know any feedback or questions via the Developer Community.

Resources

Gloridel Morales Senior Program Manager, Azure DevOps

Read next

New Boards Hub Rollout Update
In July, we provided an overview on the steps for New Boards hub to go GA. In this blog post, we wanted to provide a short update on where things are at and what you can ...
Dan Hellem
September 25, 2023
0 comment

13 comments

Leave a comment

  • Mike Fourie 0

    Thanks Gloridel

    Some minor feedback

    • “Pull request widget for multiple repos” is duplicated in the release notes.
    • “Copy Dashboard” – we have this already in 2022.
    • “Interactive boards reports” – its not clear what the change is here when I compare to the SAAS product. The server has all these already.

    Disappointed to not see the Boards experience refresh but still a decent set of updated. Thanks again.

    • Gloridel MoralesMicrosoft employee 0

      Hi Mike, thank you for sharing your feedback. We have updated the release notes to address the items that you pointed out.

  • Adrian Parker 1

    Looks like 2022.1 RC1 suffers the same issue as 2022.0.1 where you cannot install and configure it on Windows Server Core (2019 or 2022).

    On Server 2022 Core the installer fails to start with:
    Class not registered

    On Server 2019 Core the server configuration wizard fails with:
    Unable to find an entry point named
    ‘NetFreeAadJoinInformation’ in DLL ‘netapi32.dll’

    More detail can be found here:
    https://developercommunity.visualstudio.com/t/Configuration-wizard-fails-after-upgrade/10385103

    • Gloridel MoralesMicrosoft employee 0

      Hi Adrian, thank you for installing RC1 and sharing your feedback. This issue will be addressed in the Azure DevOps Server 2022.1 RC2 release.

  • Jonathan Gillette 0

    I had patched our test ADO box with 2022.0.1 Patch 3 previously, and just finished the 2022.1 update, this warning appeared when it completed. I’m guessing you’ll update this task by the time the non-RC version is out.

    [2023-09-22 12:13:36Z][Warning] Updating an existing task Azure file copy (eb72cb01-a7e5-427b-a8a1-1b31ccac8a43) with an older version 2.226.2. The service already had version 2.227.3. This means the task author must bump their version number.

    • Gloridel MoralesMicrosoft employee 0

      Hi Jonathan, we are currently investigating this. We will get back to you once we have details about what is causing this warning.

      • Jonathan Gillette 0

        Looks like it was most of the tasks updated in the latest patch, when looking through the install logs

        [Warning@08:22:21.821] [2023-09-22 12:13:45Z][Warning] Updating an existing task Azure file copy (eb72cb01-a7e5-427b-a8a1-1b31ccac8a43) with an older version 3.226.2. The service already had version 3.227.3. This means the task author must bump their version number.
        [Warning@08:22:21.821] [2023-09-22 12:13:55Z][Warning] Updating an existing task Azure file copy (eb72cb01-a7e5-427b-a8a1-1b31ccac8a43) with an older version 4.226.2. The service already had version 4.227.0. This means the task author must bump their version number.
        [Warning@08:22:21.821] [2023-09-22 12:14:08Z][Warning] Updating an existing task Azure file copy (eb72cb01-a7e5-427b-a8a1-1b31ccac8a43) with an older version 5.226.2. The service already had version 5.227.0. This means the task author must bump their version number.
        [Warning@08:22:21.821] [2023-09-22 12:16:53Z][Warning] Updating an existing task PowerShell (e213ff0f-5d5c-4791-802d-52ea3e7be1f1) with an older version 2.226.1. The service already had version 2.226.2. This means the task author must bump their version number.
        [Warning@08:22:21.822] [2023-09-22 12:18:26Z][Warning] Updating an existing task SSH (91443475-df55-4874-944b-39253b558790) with an older version 0.226.1. The service already had version 0.226.2. This means the task author must bump their version number.
        [Warning@08:22:21.822] [2023-09-22 12:19:17Z][Warning] Updating an existing task Windows machine file copy (731004d4-1d66-4f70-8c05-638018b22210) with an older version 1.226.2. The service already had version 1.227.0. This means the task author must bump their version number.
        [Warning@08:22:21.822] [2023-09-22 12:19:17Z][Warning] Updating an existing task Windows machine file copy (731004d4-1d66-4f70-8c05-638018b22210) with an older version 2.226.2. The service already had version 2.227.0. This means the task author must bump their version number.
        [Info @08:22:22.100] Node returned: Warning
        [Warning@08:22:22.100] [2023-09-22 12:13:36Z][Warning] Updating an existing task Azure file copy (eb72cb01-a7e5-427b-a8a1-1b31ccac8a43) with an older version 2.226.2. The service already had version 2.227.3. This means the task author must bump their version number.

        • Gloridel MoralesMicrosoft employee 0

          Hi Jonathan, we’ve implemented a fix and will release it with Azure DevOps Server 2022.1 RC2. Thank you for installing RC1 and reporting this issue.

  • Jonathan Gillette 0

    Do not sync tags when fetching a Git repository
    Looked through a couple of the builds and I do not see this option available in the screen, it shows the same options as 2022.0.1 does.

  • Dennis Lindqvist 0

    I’ve been trying to do an unattended setup that includes Search configuration, but the documentation at https://learn.microsoft.com/en-us/azure/devops/server/install/unattended doesn’t give a comprehensive overview of parameters or inputs available.

    How do I find out what inputs I can use that isn’t part of the ini-files created using tfsconfig /create ?

Feedback usabilla icon