Specifying the parameter isolates the effects of the option to the edition associated with that Activation ID. The parameter expands /ato support to identify a Windows edition installed on the computer. Note: Starting with Windows 8 (and Windows Server 2012), the /stao option is deprecated. Systems that have been set to suspend automatic KMS activation attempts (/stao) still attempt KMS activation when /ato is run.
#SLMGR REARM WINDOWS 10 LICENSE KEY#
This operation must be run from an elevated command prompt, or the Standard User Operations registry value must be set to allow unprivileged users extra access to the Software Protection Service.įor retail editions and volume systems with a KMS host key or a Multiple Activation Key (MAK) installed, /ato prompts Windows to attempt online activation.įor systems with a Generic Volume License Key (GVLK) installed, this prompts an attempt at KMS activation. To prevent instability in the license service, the system should be restarted or the Software Protection Service should be restarted. If a key is already installed, it is silently replaced. If the key is valid and applicable, the key is installed. The product key provided by the parameter is confirmed valid and applicable to the installed operating system.
#SLMGR REARM WINDOWS 10 INSTALL#
Password for the account with required privileges on the remote computerĪttempts to install a 5×5 product key. Name of a remote computer (default is local computer)Īccount with the required privilege on the remote computer The following describes the syntax of the Slmgr.vbs script, and Table 2 describes each command-line option: slmgr.vbs ] įor support of other software using Volume Activation, see the documents specifically written for those applications. For more information about WMI properties and methods for Volume Activation, see the section, “WMI Properties and Methods,” later in this reference guide. To manage remote clients, use the Volume Activation Management Tool (VAMT) version 1.2 or later, or create custom WMI scripts that are aware of the differences between platforms. The remote machine does not support this version of SLMgr.vbs
For example, running cscript slmgr.vbs /dlv produces the following output: Microsoft (R) Windows Script Host Version 5.8Ĭopyright (C) Microsoft Corporation. Attempting to manage an older system from Windows 7 or Windows Server 2008 R2 will generate a specific version mismatch error. Using Slmgr.vbs to manage a Windows 7 or Windows Server 2008 R2 system from the Windows Vista® operating system is not supported. Applies To: Windows 10, Windows 8.1, Windows Server 2012 R2īecause of WMI changes in Windows 7 and Windows Server 2008 R2, the Slmgr.vbs script is not intended to work across platforms.