Forum Discussion
ADK for Windows 11 and ADK for Windows Server 2022: VAMT does not work anymore
- Hi
After half internet read, I was able to correct this error with the instruction on
https://www.reddit.com/r/sysadmin/comments/oypsd8/vamt_database_not_a_valid_vamt_database/
You have to run the command in the VAMT database.
alter table base.GenuineStatusText alter column GenuineStatusText nvarchar(255) NULL
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.
mreinders 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.
- Hi
After half internet read, I was able to correct this error with the instruction on
https://www.reddit.com/r/sysadmin/comments/oypsd8/vamt_database_not_a_valid_vamt_database/
You have to run the command in the VAMT database.
alter table base.GenuineStatusText alter column GenuineStatusText nvarchar(255) NULLWhile 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.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.
