locked
Activate Windows on disconnected client RRS feed

  • Question

  • How could I activate the Windows on mobile client (laptop) based on the following criteria? What are the available choices?

    • Disconnected from office network but VPN can be initiated
    • KMS is setup in the office network

     

    Tuesday, March 23, 2010 3:06 PM

Answers

  • Hello Microsoft Gal

    The client gets 180 activation period once it activates with the KMS host machine.  After 7 days it will attempt to renew it's activation and reset the date back to 180 days.  The client is still licensed when attempting to renew, but it will wait 7 days prior to attempting to renew.

    The 7 days is just for the renewal interval

    If the client is unlincensed it will attempt to contact the KMS host every 2 hours or when network status of the machine changes after the initial 2 hours.

    See this doc

    http://technet.microsoft.com/en-us/library/ee355153.aspx#EXAA

    KMS Activation Timing section.

    The slmgr /ato can be used in the unlicensed state as well as for renewals

     

     


    Thanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights
    • Marked as answer by Microsoft Gal Monday, March 29, 2010 1:52 AM
    Thursday, March 25, 2010 11:22 PM

All replies

  • Hello Microsoft Gal,

    KMS clients should be able to activate with the KMS host over VPN if the Firewall port 1688 is open.


    Thanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights
    Wednesday, March 24, 2010 1:25 AM
  • Hi,

    So once VPN is connected and firewall port is opened, the KMS clients could activate via KMS host automatically?

    Can I issue the command to activate the Windows by using this command >> slmgr -ato? Internet connection is required for this method of activation?

    Wednesday, March 24, 2010 7:25 AM
  • Hello Microsoft Gal,

    Yes the client will attempt to activate automatically if it is in a unlicensed state.

    The client waits 7 days before attempting to renew it's license so it will not attempt to renew unless the 7 days have passed.

    Yes you can issue the command slmgr /ato.  Internet connection is not required for this command to be run.

     


    Thanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights
    Wednesday, March 24, 2010 5:20 PM
  • Thanks for the reply again.

    You mean if the client is in unlicensed state and the client has to wait for 7 days before it can apply the licensed key from KMS & activate the Windows? In this case, the command slmgr /ato can be used to force activate the windows with the VPN connection? Once the windows is activated, thereafter also doesn't require to communicate with KMS host? Will the windows expire after a few months? Is there any thing we need to do after that? for eg, to connect to KMS host from time to time to avoid expiration?

    The slmgr /ato can also be used to activate the windows without VPN connection (without KMS)? I believe in this case, Internet connection is required for this type of activation,right?

     

     

    Thursday, March 25, 2010 2:24 AM
  • Hello Microsoft Gal

    The client gets 180 activation period once it activates with the KMS host machine.  After 7 days it will attempt to renew it's activation and reset the date back to 180 days.  The client is still licensed when attempting to renew, but it will wait 7 days prior to attempting to renew.

    The 7 days is just for the renewal interval

    If the client is unlincensed it will attempt to contact the KMS host every 2 hours or when network status of the machine changes after the initial 2 hours.

    See this doc

    http://technet.microsoft.com/en-us/library/ee355153.aspx#EXAA

    KMS Activation Timing section.

    The slmgr /ato can be used in the unlicensed state as well as for renewals

     

     


    Thanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights
    • Marked as answer by Microsoft Gal Monday, March 29, 2010 1:52 AM
    Thursday, March 25, 2010 11:22 PM
  • Alright. Thank you very much.

     

    Monday, March 29, 2010 1:50 AM