Windows Server 2022 - KMS Activation yet?
I noticed Friday on my company's VLSC site that there are now MAK and KMS keys for WS2022. I have confirmed that I can now activate 2022 with a MAK key, volume license. However, I'm unable to activate it via our KMS server. I found the KMS key on our VLSC site: Windows Srv 2022 DataCtr/Std KMS XXXXX-XXXXX-XXXXX-XXXXX-KQDWV KMS (Masked for privacy) I used these commands on our KMS server (running WS2016): slmgr.vbs /ipk KMS key slmgr.vbs /ato Both commands were successful. When I type slmgr.vbs /dlv all, I see this entry: Name: Windows(R), ServerDatacenter edition Description: Windows(R) Operating System, VOLUME_KMS_WS22 channel Activation ID: --- Application ID: --- Extended PID: 03612-04573-000-204477-03-1033-14393.0000-1972021 Product Key Channel: Volume:CSVLK Installation ID: --- Use License URL: https://activation-v2.sls.microsoft.com/SLActivateProduct/SLActivateProduct.asmx?configextension=Retail Validation URL: https://validation-v2.sls.microsoft.com/SLWGA/slwga.asmx Partial Product Key: KQDWV License Status: Licensed Remaining Windows rearm count: 1000 Remaining SKU rearm count: 1001 Trusted time: 7/19/2021 7:39:34 AM Key Management Service is enabled on this machine Current count: 50 Listening on Port: 1688 DNS publishing enabled KMS priority: Normal (Items masked for privacy) This all appears normal. Does anyone know why WS2022 won't activate yet? This is what I get on my WS2022 systems: Something prevented us from communicating with our activation servers. Wait a few minutes and then try again. Error code: 0x87E10BC6 I can even enter this command on the 2022 system to manually tell it to use our KMS server (Yes, I joined the 2022 system to our AD domain) slmgr.vbs -skms ourkmsserver.domain.name That works, but when I try: slmgr.vbs /ato It gives essentially the same error. Does anyone know if these keys are simply too new? Might there be a patch or MCU required on older Windows Server O/Ss to be able to activate newer versions? I know there was a patch back in the day that 2012 R2 KMS servers needed to install before they could successfully activate 2016 servers. Thank you for any info you may have! - Michael
Cannot Change Adapter settings
Windows Server 2019 TP build 17713 and earlier build 17650. I cannot change the network adapter settings when the server is a domain controller and logged in as a Domain Administrator. The following error will show up: Windows cannot access the specified device, path, or file. You may not have the appropriate permission to access the item. I am able to change the network adapter settings on standalone server Windows 2019 TP logged in as local Administrator. Any tips to be able to change the network settings?
Windows Server 2019 version info
Preliminary tests have revealed that the version of 'kernel32.dll' found on our current preview build Windows Server 2019 system is of the form '10.0.x.x'. Hence, it would appear that the major/minor version numbers have not changed, at least not as of yet, from those for Windows Server 2016. Checking the version of 'kernel32.dll' is the method suggested within the Microsoft docs that we use in order to determine the OS version. Will the version numbers be updated when goes production? If so, can you tell us what those version numbers will be ? Thanks, RobWindows Server 2022 adds support for Microsoft 365 Apps
Updating our support policy through October 2026 Based on feedback from customers, we are happy to share that we are updating our support policy for Microsoft 365 Apps on Windows Server 2022. Support for on-premises and Azure deployments will be available through October 2026. This covers the period in which Windows Server 2022 is in mainstream support. Support for running Microsoft 365 Apps on Windows Server 2022 is currently in preview. If you want to begin testing on Windows Server 2022, we recommend that you use the most current, supported version of Microsoft 365 Apps available in Current Channel. We will provide information about which versions of Microsoft 365 Apps are supported on Windows Server 2022 at a later date. We will be updating our support pages and documentation in the coming days.How to Install WSL 2 on Windows Server
A couple of months ago Microsoft announced the Windows Subsystem for Linux 2 (WSL 2), which is a successor of the Windows Subsytem for Linux shipped a couple of years ago. WSL 2 is currently available for Windows Insiders running Windows 10 Insider Preview Build 18917 or higher and with the Docker Tech Preview, you can now even run Docker Linux Container directly on WSL 2. With the latest Windows Server Insider Preview build 18945, you are also able to run WSL 2 on Windows Server. In this blog post, I am going to show you how you can install the Windows Subsystem for Linux 2 (WSL 2) on Windows Server. The Windows Subsystem for Linux was already available in earlier versions of Windows Server; however, WSL 2 brings a lot of new advantages. Read more here: https://www.thomasmaurer.ch/2019/08/how-to-install-wsl-2-on-windows-server/
Graphics Driver For AMD Ryzen APU doesn't work properly in Windows Server 2019 Preview Build 17666
1. Background In Feb 12 2018, AMD rolled out Desktop-based Ryzen APU chips, which come with integrated Vega graphics in cpu. Such Ryzen APU chips are ideal for home server. But the problem is, Graphics Driver (sometimes says "GPU Driver") for Ryzen APU only works on Windows 10 1709 and above. So Windows Server 2016 (based on Windows 10 1607 LTSB) could not use these Ryzen APU chips (for example: https://community.amd.com/message/2863802 ). In AMD support forum, someone replied a topic about "Graphics Driver issues on Windows 10 LTSB branch": "You will need to contact Microsoft to keep you up to date on progress for a fix (I assume you're an enterprise customer). Many of the recent problems involving AMD graphics were caused by poorly implemented Microsoft updates in Win10." (Source: https://community.amd.com/thread/227154 ) Now comes with Windows Server 2019 Preview Build 17666, which based on Windows 10 1803. But Graphics Driver For AMD Ryzen APU also doesn't work properly. So I start this conversation, hope can help others. 2. Problem detail: Graphics Driver 2.1 Can not install Graphics Driver by normal AMD installation. During installation, it showed Error 182 and quit. AMD installation program reported "errornum: 182, errorStr: UNKNOWN AMD Hardware" 2.2 Can not install Graphics Driver by specific driver folder in Device Manager. AMD Graphics Driver limits the OS ProductType in Driver INF file. "NTamd64.10.0.1...14310" means it can only be installed on VER_NT_WORKSTATION(0x0000001). 2.3 BSOD on atikmpag.sys After modify Driver INF file to "NTamd64.10.0...14310", it can be installed by specific driver folder in Device Manager (with disable signature check during boot). So Graphics Driver can work on Windows Server 2019 Preview Build 17666 with Ryzen APU. But It's possible to be so happy you could die. There came with a BSOD while I was using remote desktop. The real proble is a myth. Only dump file said it is BugCheck 0x116 VIDEO_TDR_ERROR, which caused by atikmpag.sys. This means Graphics Driver For AMD Ryzen APU doesn't work properly at sometime. 2.4 OpenCL could not work on AMD Ryzen APU Another Graphics Driver doesn't work properly problem is that, OpenCL could not work on AMD Ryzen APU. AMD Ryzen APU support OpenCL, and it works properly on Windows 10 Insider Preview 17666. But in Windows Server 2019 Preview Build 17666, all test programs reported that OpenCL not found in AMD Ryzen APU. 3. Other Problem: Chipset Driver In fact, neither Graphics Driver For AMD Ryzen APU nor Chipset Driver could work or install properly in Windows Server 2019 Preview Build 17666. I tested ON Motherboard which comes with Chipset A320, the results are: 3.1. Can not install drivers 3.1.1. [Critical Error] Graphics Processing Unit (GPU) Driver For Ryzen APU. (Detail are above) 3.2. Auto-install wrong drivers 3.2.1 [Medium Error] AMD PSP Device During installation, it auto-install drivers from "C:\AMD\AMD-Chipset-Drivers\Packages\Drivers\AMDPSP_svr\WT64A", which only support Naples chipset, not A320 Chipset. The right drivers should come from "C:\AMD\AMD-Chipset-Drivers\Packages\Drivers\AMDPSP\WT64A" 3.3. Has to manual install drivers 3.3.1 [Low Error] AMD USB3.1 eXtensible Host Controller During installation, it can not detect such driver. User has to manual install it in Device Manager. 3.3.2 [Low Error] AMD SATA Controller During installation, it can not detect such driver. User has to manual install it in Device Manager. 4. Affected CPU All AMD Ryzen APU are affected in Windows Server 2019 Insider Preview, including: - AMD Ryzen 3 2200G with Radeon™ Vega 8 Graphics - AMD Ryzen 3 2200GE with Radeon™ Vega 8 Graphics - AMD Ryzen 3 PRO 2200G with Radeon™ Vega 8 Graphics - AMD Ryzen 3 PRO 2200GE with Radeon™ Vega 8 Graphics - AMD Ryzen 5 2400G with Radeon™ Vega 11 Graphics - AMD Ryzen 5 2400GE with Radeon™ Vega 11 Graphics - AMD Ryzen 5 PRO 2400G with Radeon™ Vega 11 Graphics - AMD Ryzen 5 PRO 2400GE with Radeon™ Vega 11 Graphics …… 5. Suggestion 5.1 For customer If you want to use AMD Ryzen APU for home server, you have to wait for Windows Server 2019. 5.2 For Microsoft As AMD Support forum suggest customers to contact Microsoft, I think microsoft has to test more AMD Ryzen APU Driver on Windows 10, including Windows Server 2019 Insider Preview. If needed, Microsoft should make some suggestions to AMD, not only about Graphics Driver, but also Chipset Driver. I will continue testing Windows Server 2019 Insider Preview on AMD Ryzen APU. At last, My test platform are: - Motherboard comes with Chipset A320 - AMD Ryzen 5 PRO 2400GE with Radeon™ Vega 11 Graphics
