Windows 10: Windows Server Long Path Name Support 2016 vs 2019

[COLOR=rgba85, 85, 85, 1]I have an issue with extracting a tar file with relatively long paths ~120+ chars into a folder structure that is also relatively long 130 chars, as some of the file names are long enough they exceed the 260 character limit for path names. We have enabled the Enable Win32 long paths policy, as well as ensured that the LongPathsEnabled registry value is set to 1, and the servers were rebooted after the change. I'm using 7-Zip v19.00 to do the extracts and have used both TAR and ZIP files to ensure that the format doesn't play a part.[/COLOR]


[COLOR=rgba85, 85, 85, 1]On a Windows Server 2016 instance, the extract works correctly with no errors. However, on a Windows Server 2019 instance, using the same TAR and ZIP files and the same target path to extract 130 chars, several files fail to extract, apparently because the paths are longer than 260 characters. We validated this by shortening the extract target path slightly, which allowed all files to extract without error.[/COLOR]


[COLOR=rgba85, 85, 85, 1]We are able to make this work with the 7-Zip GUI and with WinZip, but the command line fails consistently on Server 2019. [/COLOR]


The one server configuration difference we noticed was that the Server 2016 box has .NET 4.7 and the Server 2019 box has .NET 4.7.2.


[COLOR=rgba85, 85, 85, 1]What differences in long path handling have we missed in Server 2019 vs 2016?[/COLOR]

[COLOR=rgba85, 85, 85, 1]
Thanks in advance![/COLOR]

:)

 

Activate RDS CAL 2019 on Windows Server 2016

Dear Microsoft Support,



We recently purchased Windows Server RDS CAL 2019.

When we tried to install Windows Server RDS CAL 2019 into Windows Server 2016, it shows the license is not recognized and couldn’t install.



My questions are :

1. Can’t Windows RDS CAL 2019 be installed in Windows Server 2016? If can, how?
2. Is there any way to downgrade RDS CAL from 2019 to 2016 version?

Thanks,

 

Office 2019

Only supported on Win10. Sorry, 8.1 users, only 4 years old, gotta go.

Microsoft Office 2019 will only work on Windows 10

https://blogs.technet.microsoft.com...-to-office-and-windows-servicing-and-support/

Spoiler Office 2019
Last year at Ignite, we announced Office 2019 – the next perpetual version of Office that includes apps (including Word, Excel, PowerPoint, and Outlook, and Skype for Business) and servers (including Exchange, SharePoint, and Skype for Business). Today we’re pleased to share the following updates:

• Office 2019 will ship in H2 of 2018. Previews of the new apps and servers will start shipping in the second quarter of 2018.
• Office 2019 apps will be supported on:
  • Any supported Windows 10 SAC release
  • Windows 10 Enterprise LTSC 2018
  • The next LTSC release of Windows Server
• The Office 2019 client apps will be released with Click-to-Run installation technology only. We will not provide MSI as a deployment methodology for Office 2019 clients. We will continue to provide MSI for Office Server products.

 

Exchange Support For Windows Server 2016


Exchange Support For Windows Server 2016

Source: https://blogs.technet.microsoft.com/...s-server-2016/