Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, November 30, 2017 10:13 PM
Greetings,
We are currently in the process of rewriting an application that assists with multiple disconnected systems using token based activation.
In Windows 7 Enterprise, the command that we ran from an elevated command prompt to invoke the Microsoft Windows Activation wizard was "slui 1". The wizard would prompt to use a certificate off our our token (Smart Card) and Windows would activate without issue.
In Windows 10 Enterprise (Build 1511) we are able to manually invoke the Windows Activation Wizard and activate Windows with our token via the Start -> Settings -> Update & Security -> Activation and click activate. The "slui 1" and "slui 2" appear to do nothing on Windows 10. The "slui 3" command allows a new MAK key to be inputted and "slui 4" is activation via telephone.
Ultimately, our goal is to have a command in Windows 10 that functions as "slui 1" did in Windows 7. If anyone knows how to do this with token based activation any assistance would be greatly appreciated. Alternatively, if there is a command that can programmatically be ran that invokes the Windows Activation wizard via Start -> Settings -> Update & Security -> Activation and click activate that would work as well.
All replies (7)
Friday, December 1, 2017 9:04 PM âś…Answered | 1 vote
That is correct and that is how we loaded the Token based Activation Issuance Licenses. The /fta switch requires the certificate on the smartcard to be the same on every activation attempt which will not work because we have multiple users doing multiple system activations. Does anyone know a means to programmatically open the "System Info" page? I know the shortcut is Start button + Pause.
control /name Microsoft.System
Don [doesn't work for MSFT, and they're probably glad about that ;]
Friday, December 1, 2017 3:17 AM | 1 vote
You are right.
The "slui 1" and "slui 2" no longer work on Windows 10.
On windows 10, we use SLUI 3 brings up the CHANGE PRODUCT KEY window and SLUI 4 brings up the CALL MICROSOFT & MANUALLY ACTIVATE window.
However, Windows 10 uses the same command line utility slmgr as Windows 7 for activation with a MAK (Multiple Activation Key).
slmgr -ipk <ProductKey>
slmgr -ato
Activate using Key Management Service
/en-us/windows/deployment/volume-activation/activate-using-key-management-service-vamt
Slmgr.vbs Options for Volume Activation
https://technet.microsoft.com/en-us/library/dn502540(v=ws.11).aspx
Regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Friday, December 1, 2017 3:38 PM
Unfortunately, this is in a disconnected environment where KMS nor MAK activation is possible. That's why we went down the path of token based activation.
Friday, December 1, 2017 6:13 PM | 1 vote
Hello
You should be able to use slmgr.vbs to manage Token Activation
Open an elevated CMD prompt and run slmgr /? to get the list of commands available.
Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
Friday, December 1, 2017 8:01 PM
That is correct and that is how we loaded the Token based Activation Issuance Licenses. The /fta switch requires the certificate on the smartcard to be the same on every activation attempt which will not work because we have multiple users doing multiple system activations. Does anyone know a means to programmatically open the "System Info" page? I know the shortcut is Start button + Pause.
Friday, December 1, 2017 9:36 PM
Just to be clear, there is no direct replacement for the slui 1 command From Windows 7 to Windows 10? That would be the best path forwards.
Monday, September 24, 2018 2:41 PM
navigate to c:\windows\system32
type: cscript slmgr.vbs /ltc
copy thumbprint for the signing cert
type cscript slmgr.vbs /fta <thumbprint info here, minus the brackets> <PIN is optional>
example: cscript slmgr.vbs /fta thumbprint pin