For those of you thinking about upgrading to the latest available version of the on-premises server (RC1), I wanted to post about my experiences with an upgrade from TFS 2018.
- Server OS requirements
- Group Selected Clauses
- Deployment Groups
- Update Max Attachment Size [Updated 03-OCT-2022]
Server OS Requirements
This is a big one, Windows Server 2019 and Windows Server 2022 are the only supported OSs. If most of your user base is on Windows 10/11 it is not such a big deal. However if you have users/devs running an older version of a client or server operating systems you may run into some TLS issues with some applications.
We had some devs on Windows Server 2012 R2 running PowerBuilder 2019 R3 using the MSSCI Provider (32-bit) which did not work after the upgrade. We added the following registry subkey values to resolve the issue:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp\]
DefaultSecureProtocols = (DWORD): 0xAA0
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp\]
DefaultSecureProtocols = (DWORD): 0xAA0
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions" = (DWORD
):00000001
"SchUseStrongCrypto" = (DWORD
):00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions" = (DWORD
):00000001
"SchUseStrongCrypto" = (DWORD
):00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions" = (DWORD
):00000001
"SchUseStrongCrypto" = (DWORD
):00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions" = (DWORD
):00000001
"SchUseStrongCrypto" = (DWORD
):00000001
Group Selected Clauses
If you’re trying to use the Group Select Clauses button, you might find it does nothing after selecting checkboxes of your clauses, hopefully this will be addressed in the next Release Candidate (RC)

Deployment Groups
If you click the “Show more” link you will get the error shown below
The requested version “7.0” of the resource is under preview. The preview flag must be supplied in the api-version for such requests. For example: “7.0-preview”

I am eagerly awaiting the next Release Candidate (RC) which should address those last two issues.
Update Max Attachment Size
In case you did not know, the max attachment size was increased in Azure DevOps Server to 60MB, which is huge compared to the 4MB default in TFS. If you’d like to change this setting, a few lines of PowerShell can make that happen.
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
$client = New-WebServiceProxy -Uri https://<serverUrl>/DefaultCollection/WorkItemTracking/v1.0/ConfigurationSettingsService.asmx -UseDefaultCredential
$client.SetMaxAttachmentSize(62914560)
Hopefully that helps someone out.
So many features have been added in this 2022 RC, if you haven’t migrated to Azure DevOps Services yet and are still running an on-premises version I urge you to check out the following:
- Delivery Plans
- New controls for environment variables in pipelines
- Generate unrestricted token for fork builds
- Templates support in YAML editor
- Group By Tags available in chart widgets
You can see the entire list of new features in the release notes.
No comments yet... Be the first to leave a reply!