How To Activate Windows 10 / Server 2016 Through Command Line

If you are having problems activating Windows 10, Server 2016, Windows 8, or Server 2012 one of these three solutions below should get you through:

This is handy if the GUI won’t start and you want to skip some steps to get it to work.

  1. click START (gets you to the tiles)4-no-change-product-key-link-missing-dns-error-0x8007232b-dns-error-activate
  2. type RUN
  3. type slui 3 and press ENTER
    1. yes, SLUI: which stands for SOFTWARE LICENSING USER INTERFACE
      1. SLUI 1 brings up the activation status window
      2. SLUI 2 brings up the activation window
      3. SLUI 3 brings up the CHANGE PRODUCT KEY window
      4. SLUI 4 brings up the CALL MICROSOFT & MANUALLY ACTIVATE window
  4. Type in your product key
  5. Have a nice day.

  1. Launch a CMD as an Administratorcommand-line-to-activate-windows-slmgr-slui
  2. Type: slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
  3. Press Enter

If your key is valid and you are connected to the internet, it should activate within a second or two.

In Canada and the US, call the support line directly at 1 800-936-4900, otherwise, use this table of Microsoft Activation Phone Numbers to do the deed.

You also might find some of our previous posts on activation problems to be helpful:  urtech.ca/?s=activation

Non è stato possibile recapitare il messaggio in una cartella pubblica perché il recapito a questo indirizzo è limitato ai mittenti autenticati

The message could not be delivered to a public folder because the delivery to this address is limited to authenticated senders

In Exchange 2013 e Exchange 2016 occorre abilitare i permessi per gli utenti anonimi nelle Public Folder

controllare gli attuale permessi con:

Get-PublicFolder “\” -Recurse | Get-PublicFolderClientPermission | Out-File -FilePath “c:\Temp\PFPerms.txt”

Assegnare i permessi all’utente anonimo:

Get-PublicFolder “\” –Recurse | Add-PublicFolderClientPermission -User Anonymous -AccessRights “CreateItems”

fonte:http://windowsitpro.com/blog/security-design-change-office-365-public-folders-causes-inbound-email-ndr

vedi anche: https://technet.microsoft.com/en-us/library/aa997560(v=exchg.150).aspx#CreateItems