activation
7 TopicsWindows Server 2022 Product Key
Good Morning everyone! I am new to using Server Insider builds, (i have used normal Win10 builds for many years) just wondering where i could find & use a product key to activate Windows Server 2022 (latest built). Any help would be great 😄 Thanks, JaySolved381KViews8likes26CommentsWindows Server 2022 Essential Activation
Hi, I'm writing for the company in which I work. The company, 1 year ago, bought a little server and the reseller gave us it with Windows Server 2022 Essential installed. The PK was put on the side of the server and gave us also a DVD. After a year, the server was giving some issues, so I've decided to buy a new HD to install it again. I've tried to put the DVD of Windows Server 2022 Essential into pc but I've just discovered it is in Deutch and I cannot speak in that language so for me is impossible to install it. Since I was not able to find any iso of this OS in microsoft website I've downloaded the 2022 standard evaluation. After installation I've tried to put into the activation tool the PK we have for this computer but system says this PK is not valid. Pls can anyone help me to understand how can I install again the 2022 essential with our PK? Thank you336Views0likes0CommentsKMS being overruled by Microsoft Activation server
tldr : For some reason the Microsoft activation link is taking precedence over my local KMS. Any ideas? The endpoints at my org have started to downgrade to Windows 10 Pro, sort of. On an effected endpoint, when I run slmgr /dlv, it says the endpoint is reaching out to https://activation-v2.sls.microsoft.com/SLActivateProduct/SLActivateProduct.asmx?configextension=Retail to activate. It also states that the license is Win10 Pro. However, if I run winver, it still comes up as Win 10 enterprise, which we are licensed for. We have had a KMS for a long time and it is and has been working fine. This just started happening recently. If I force the client to KMS by using slmgr /ipk "KMSKEY", then run /slmgr /ato, it correctly sets back to the kms. However, 4 to 8 hours later, it resets itself to point to https://activation-v2.sls.microsoft.com/SLActivateProduct/SLActivateProduct.asmx?configextension=Retail Its not group policy, I have run gpupdate /force and the endpoint is still looking at KMS. If I run nslookup -type-srv_vlmcs._tcp it comes back as the local KMS server, so I know my KMS is working ok. For some reason the Microsoft activation link is taking precedence over my local KMS. Any ideas?1.8KViews0likes1CommentWindows Server 2022 Essentials Activation Error
Hi, I bought a new Dell server with Windows Server 2022 Essentials licence. It came with the key for Windows Server 2022 Essentials. So, I found this article: https://learn.microsoft.com/en-us/windows-server-essentials/get-started/get-started, and here I can read the Note: With Windows Server 2022, the Essentials edition is available to purchase from OEMs only, however there is no specific installation media. Instead, an Essentials edition product key is used to activate the Standard edition of Windows Server 2022. So, I intalled using a Windows Server 2022 Standard ISO and it didn't ask for a key on installtion process and configured it, but when trying to activate, it gave this error: The product key you entered didn't work. Check the product key and try again, or enter a different one. (0xc004f050) I double and triple checked the key and I'm sure it's right. Need a help here, the server is already in production and can't be reinstalled. Thank you1.9KViews0likes2CommentsADBA Windows 10 Activation Not Persistent
I have setup ADBA for Windows 10 activation. We're having an issue where different and multiple workstations randomly get the watermark saying to activate Windows. When checking Start / Settings / Update & Security / Activation this also shows that Windows is not activated. HOWEVER when running SLMGR.VBS /DLV, the status shows as licensed. The various troubleshooting steps we have used include SLMGR /ato to reactivate which always works. SLMGR /ipk to manually apply the license (recommended by "MS Support") Replace the TOKENS.DAT (recommended by "MS Support") I put MS Support in quotes because it's their outsourced support. So far nothing has stuck. We have ADBA objects for Server 2019 and Office 2019. So far none of our 2019 servers or Office activations have this issue. Please help if possible. Thanks. FL1.2KViews0likes0Comments