Sep 04 2021 07:07 AM
In both ADK post 2004 version VAMT 3.1 fails to connect to the SQL instance.
- cannot connect to existing instance of SQL (2014)
- cannot connect to new database in above instance
Workaround:
uninstall ADK Windows 11 or Server 2022 and install ADK 2004. Works immediately.
Who from Microsoft Team can help to triage and fix this?
Sep 13 2021 03:00 AM - edited Sep 13 2021 03:15 AM
Sep 13 2021 03:00 AM - edited Sep 13 2021 03:15 AM
@Karl_Wester-Ebbinghaus
THANKS !!!
I have spent xx hours on this problem and this posting probably save me xx hours more.
However, when installed it refuses to accept 2022 key and upgrade ends (of course) with the same error. At least I can serve our current installations, but not 2022. Any info to share with this issue?
Sep 14 2021 09:40 AM
@Raymond Andreassen you're welcome but it seems you are reporting an entirely different issue with activation. I said that the Database connection of VAMT 3.x does not work anymore.
Sep 15 2021 05:28 AM
@Michael Reinders @Mary Hoffman @Raymond Andreassen
Hi there we are trying to setup Server 2022 for production and VAMT 3.1 is still a blocker
VAMT 3.1 from Windows 2004 ADK cannot import keys generic activation keys for Windows Server 2022
VAMT 3.1 from Server 2022 or Windows 11 ADK would be able but cannot open any database. Please let me know if this could be reproed (I can for 2 customers) and you can bring hotfix for the VAMT / ADK Win 11 / 2022 or I need to open a ticket.
Thank you very much in advance. I have not caught this in the preview as there was no need for centralized management of KMS activation via ADBA.
Sep 20 2021 10:22 AM
SolutionSep 21 2021 01:28 AM - edited Sep 21 2021 01:29 AM
While this is no official solution, thank you very much for reporting a temporary workaround.
I hope the ADK team will bring an update that will care for that, so we don't have to rely on this manual workaround comparingly to the Office 2010 KMS setup, that have not been fixed to support Windows 10 and Server 2016 and later in the cscript, and needs manual intervention. Now this Office is out of support. ADK is not, so I have still some hope.
Sep 26 2021 05:31 PM
Our Windows Server 2022 Standard KMS keys from the VLSC, while are accepted and recognized by VAMT after doing the fix in this thread, still will not commit to Active Directory.
Oct 07 2021 04:39 AM
hi @auRiSmith what you mean by do not commit to AD?
Oct 07 2021 04:46 AM
Oct 11 2021 05:31 AM
Oct 25 2021 04:07 AM
Oct 25 2021 04:15 AM
The design decision is intentional to not update any on premises inbox tools in Windows Server.
Example: Server Manager will not have filtering options for 2019 or 2022, even though it is a PowerShell oneliner, very unfortunately.
Print Management console is still missing in context menu in Server Manager,
File Explorer will still miss the VSS config on ReFS volumes on context menu in Explorer. All dev energy flowing into Windows Admin Center.
I hoped that some low hanging fruit regression could have been fixed, and could be still fixed with a CU without breaking anything else.
@Mary Hoffman on the topic do you have any news for an ETA on this VAMT fix? The workaround seems to work, but as I do not understand the DB structure cannot tell if this could be done in a new ADK version or something else needs to be changed.
if you have the time I would of course appreciate some BI Reports for the other mentioned feature requests and fixed brought up in Insider Dev and repeated here offtopic to Alban.
Oct 26 2021 10:45 AM
Nov 02 2021 05:52 PM
Nov 04 2021 07:40 AM
Nov 04 2021 12:07 PM
Dec 28 2021 03:23 PM
Original install has a "-" in the DB Name. 2022 ADK VAMT won't allow the "-" in the DB Name
Jan 04 2022 09:34 AM
Jan 05 2022 01:45 AM
Hi @Mary Hoffman thanks for the follow-up. Can we expect the fixes will be released to the GAC of Windows Server 2022 after testing in Insider?
Jan 05 2022 07:05 AM
Sep 20 2021 10:22 AM
Solution