Jump to content




Sign in to follow this  
tsk4600

Activate Win7 MAK in TS



Recommended Posts

is it possible without MDT2010?

i have tried with:

step 1: cscript.exe slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

Step 2: cscript.exe slmgr.vbs /ato

 

Step 1 runs with succes but then the TS fails in step 2.

 

any ideas how to activate? :)

Share this post


Link to post
Share on other sites


hi there,

 

does this method work manually for you ?

 

when you run it in the task sequence, what error do you get in the smsts.log ?

 

have you seen the Volume Activation guide for MAK/KMS here ?

 

here's the relevant MAK material

 

MAK Activation

 

MAK activation is used for one-time activation through Microsoft’s hosted activation services, with no renewals required. For background information about MAK activation, see the Volume Activation Planning Guide.

Converting KMS Clients to MAK Activation

 

Windows 7 and Windows Server 2008 R2 install automatically as KMS clients. To convert a KMS client to MAK activation, install a MAK. A MAK can be installed during or any time after operating system installation.

 

A MAK key can be installed on a reference image of Windows 7 and Windows Server 2008 R2 to make all installations from that image use MAK activation instead of the default KMS activation. Doing so alleviates the need to specify a MAK in an unattended installation file.

 

Installing a MAK During Operating System Installation

 

Administrators can convert a KMS client to a MAK client during the initial installation of Windows 7 or Windows Server 2008 R2 by including a MAK in an unattended setup (Unattend.xml) file. The Unattend.xml file can be used with Setup.exe or Windows Deployment Services. For more information, see the Unattended Windows Setup Reference help file in the Windows AIK at http://go.microsoft.com/fwlink/?LinkId=136976. For a sample unattended installation file, see “Appendix B: Sample Unattended Installation File.”

 

Note: The MAK is stored in clear text in the Unattend.xml file. During an unattended installation, the file Unattend.xml or AutoUnattend.xml is copied to the %SystemRoot%\Panther folder of the target computer. However, at the end of the Setup process, the Setup program replaces it with “SENSITIVE*DATA*DELETED.”

 

Installing a MAK After Operating System Installation

 

A volume edition of Windows 7 and Windows Server 2008 R2 can be configured to use MAK activation by using the Control Panel System item or by running the Slmgr.vbs script:

 

*

 

To install a MAK by using the System application, click the Change your product key link, and then type the MAK in the Change your product key for activation dialog box.

*

 

To install a MAK by using Slmgr.vbs, run the following command at a command prompt:

 

slmgr.vbs /ipk <MultipleActivationKey>

 

where MultipleActivationKey is the MAK.

 

If users install a MAK by using the UI, the MAK client attempts to activate itself over the Internet one time. If the users install a MAK key by using the Slmgr.vbs script, the MAK client does not try to activate automatically.

 

Disabling Automatic Activation

 

To disable automatic activation on any MAK client, set the DWORD registry value Manual to 1. This value is in the registry subkey HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\Activation.

Top of Page

Activating MAK Clients

 

The MAK client attempts to activate over the Internet at the next scheduled interval. Administrators can force immediate activation over the Internet, by telephone, or by using the Volume Activation Management Tool (VAMT).

 

To confirm activation, check the system tray for a notification that says, “Windows is activated.” Alternatively, type slmgr.vbs /dli at a command prompt to view the activation status of a computer.

Activating MAK Clients over the Internet

 

A MAK client can be activated over the Internet in either of two ways:

 

*

 

Click the Click here to activate Windows now link in the Control Panel System item. Windows reports whether the activation was successful. If activation was unsuccessful, a wizard presents additional options.

*

 

Run slmgr.vbs /ato at a command prompt. Additional options are not presented when using slmgr.vbs.

 

Activating MAK Clients Through a Proxy Server

 

Activation over the Internet may be blocked if the proxy server requires user authentication. In Microsoft Internet Security and Acceleration (ISA) Server, this setting is called Basic Authentication. Because activation requests do not present the user's credentials to the proxy server, Microsoft recommends not using Basic Authentication with ISA Server or other proxy servers. However, if Basic Authentication or a comparable mechanism must be used on the proxy server, add the following URLs to the Proxy Authentication exclusion list:

 

http://go.microsoft.com/*

https://sls.microsoft.com/*

https://sls.microsoft.com:443

http://crl.microsoft.com/pki/crl/products/MicrosoftRootAuthority.crl

http://crl.microsoft.com/pki/crl/products/MicrosoftProductSecureCommunications.crl

http://www.microsoft.com/pki/crl/products/MicrosoftProductSecureCommunications.crl

http://crl.microsoft.com/pki/crl/products/MicrosoftProductSecureServer.crl

http://www.microsoft.com/pki/crl/products/MicrosoftProductSecureServer.crl

 

Activating MAK Clients Using the Telephone

 

To activate computers that are connected to the organization’s network but do not have Internet connectivity by using Slmgr.vbs. In the Command Prompt window, type:

 

slmgr.vbs TargetComputerName <Username> <Password> /dti

 

To display the information required to complete telephone activation. To obtain the telephone number for an Activation Call Center in your local region, run slui.exe 4. Use the Interactive Voice Response system to obtain the confirmation ID (CID); then, run:

 

slmgr.vbs TargetComputerName <UserName> <Password> /atp <CID>

 

To install the CID. If activation is performed frequently or multiple computers are activated, it may be more useful to automate the process using the Slmgr.vbs script.

Activating MAK Clients Using VAMT

 

VAMT allows automation of MAK deployment and activation over the network by distributing MAKs from a centralized console, as Figure 2 shows. VAMT queries Microsoft activation servers to get the number of remaining activations for a given MAK, then lists the activation status of all MAK-activated systems in the environment. This count is a snapshot in time, not a real-time count. VAMT version 1.2 is included in the Windows AIK, which is available from the Microsoft Download Center at http://go.microsoft.com/fwlink/?LinkId=136976.

 

The VAMT user interface

 

Figure 2 The VAMT user interface

 

Dd772269.img02_VAD(en-us,TechNet.10).jpg

 

Disable Automatic Activation

 

Automatic activation can be disabled on any KMS client by setting the existing DWORD value Manual to 1. This value is in the registry subkey HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\Activation.

Integrating MAKs with Deployment Workbench

 

Microsoft Deployment Toolkit (MDT) also provides a solution for deploying MAKs. In Deployment Workbench, administrators configure the MAK in task sequences, which add the MAK to the Unattend.xml file used during installation. Administrators can prepare the reference image for KMS activation, then, during deployment, MDT activates the installation by using a MAK as long as it does not detect a KMS infrastructure. MDT applies the MAK after installing the image. For more information about MDT, see Deployment TechCenter at http://technet.microsoft.com/en-us/deployment/default.aspx.

Top of Page

Reactivating Computers

 

Periodically, Windows 7 and Windows Server 2008 R2 check the hardware configuration of the computer on which the operating system is installed. If the operating system detects that the hardware is substantially different, reactivation is required. The actual weighting factors and threshold values vary, because these values must keep pace with the constantly evolving computer hardware market. In general, computers that use MAK activation use the same reactivation rules as retail activation. KMS clients focus more on hard disk changes to determine the need for reactivation.

 

Client activations are valid for 180 days. This period is called the activation validity interval. To remain activated, KMS clients must renew their activation by connecting to the KMS host at least once every 180 days. By default, KMS client computers attempt to renew their activation every seven days. After a client’s activation is renewed, the activation validity interval begins again.

Top of Page

Appendix A: Optional Configurations

 

Volume Activation supports optional configurations that may work in some environments but are not recommended for most. The procedures in this appendix require a Software Protection Service restart before they take effect.

Enabling Standard User Activation

 

To enable standard user activation on a KMS client, add a new DWORD registry value named UserOperations and set its value to 1. Create this value in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform registry subkey.

 

When complete, administrative rights are no longer required for some operations, such as installing a product key (slmgr.vbs /ipk), installing a license (slmgr.vbs /ilc), or rearming (slmgr.vbs /rearm). This means that a standard user can switch a KMS client to MAK activation, manually activate a computer, and—if necessary—replace an existing MAK with a new MAK. Doing so is not recommended, however, because it lowers security on the computer.

 

Note If a standard user installs a MAK or KMS key, the ProductID registry values are not updated. This behavior primarily affects product support, and Microsoft Customer Support Services (CSS) is aware of this situation.

Disabling Activation Notifications

 

Although not recommended, software licensing notifications can be turned off by adding a new DWORD value named NotificationDisabled with a value of 1 to the registry. Create it in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\Activation registry subkey. This value disables all software licensing notifications, including balloons, wizards, and task dialog boxes.

 

NOTE: This setting is ignored if the grace period has expired. For more information on Grace Period Expiration behaviors see: What If Systems Are Not Activated? (http://technet.microsoft.com/en-us/library/dd878528.aspx)

Registry Key Changes for Activation Features

 

Windows 7 and Windows Server 2008 R2 include a new Software Protection Platform (SPP) key in the registry. For product activation in managed environments, configure the Activate Windows now dialog box to display an optional Learn About Activation Online link, as shown in Figure 3.

 

Learn about activation online

 

Figure 3 Learn about activation online

 

Clicking this custom link loads an administrator-defined URL in the user’s default browser. This URL can point to a custom Web page or other file stored on the local computer or on a network share. A Volume Licensing customer can use this link to provide customer-specific information about activation. Displaying the link requires setting the REG_SZ value AlternateURL to the URL of the Web page to display when the user clicks it. The value AlternateURL is in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\ACTIVATION registry subkey.

 

 

 

Appendix B: Sample Unattended Installation File

 

<?xml version="1.0" encoding="utf-8"?>

<unattend xmlns="urn:schemas-microsoft-com:unattend">

   <settings pass="windowsPE">

       <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

           <UserData>

               <AcceptEula>true</AcceptEula>

           </UserData>

</component>

   </settings>

   <settings pass="specialize">

       <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS"
xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

           <ProductKey>MAK Product Key</ProductKey>

       </component>

   </settings>

<cpi:offlineImage cpi:source="" xmlns:cpi="urn:schemas-microsoft-com:cpi" />

</unattend>

Share this post


Link to post
Share on other sites

Hi I need someones help with KMS,, first off we have 2 DNS servers, not sure if this will effect KMS or not. Secondly how do you deploy KMS Automatically to a new image created with WDS. We can deploy KMS manually as long as we enable the WMI in the Firewall.

I am fairly new to KMS and not too sure if we have done things correctly.

Share this post


Link to post
Share on other sites

did you see this post ?

Share this post


Link to post
Share on other sites

Yes I have checked, it's not so much difficulty in following the instructions, it's just that I am getting an error message when I run the slmgr.vbs -ipk command... error is 0xC004F015...

Share this post


Link to post
Share on other sites

Yes I have checked, it's not so much difficulty in following the instructions, it's just that I am getting an error message when I run the slmgr.vbs -ipk command... error is 0xC004F015...

 

This is now resolved, I needed to contact Microsoft about it, but for future reference if anyone wants to know, if you want to issue out W7 KMS license you need to make sure that the server 2008 host has a genuine Server 2008 SP2 KMS license to start with, other wise you won't be able to use it for W7.

We were scratching our heads about this, but I am glad it is now sorted.

Share this post


Link to post
Share on other sites

do you mean that you activated the server 2007 kms host with a different non-kms key ? or what ?

Share this post


Link to post
Share on other sites

do you mean that you activated the server 2007 kms host with a different non-kms key ? or what ?

 

Let me explain, apparently according to MS when you receive a license you get two versions for Server 2008. One is a normal license, which will only activate KMS license's for Vista and Server 2008. Another license is for Server 2008 SP2, which will activate W7 as well as Server 2008 SP2. Sorry if I didn't make myself clear, but I only found out after speaking to the MS license department, as you know I was having problems setting up KMS. To confirm what type of license you have you need to open an elevated Cmdr session and type "slmgr.vbs /dli" if it says anything with Volume_ MAK in the Description field then it's the wrong type of license. I hope this makes sense, as it was something that caused me problems.

Share this post


Link to post
Share on other sites

I have 3 questions relating to KMS activation;

1st-can you have 64bit and 32bit KMS license on a single KMS host?

2nd-do you need to set up a separate KMS host for office 2010? if so how do you do this?

3rd-can you change a PC from MAK to KMS license? I have tried and it says that it is not a genuine license.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  


×