Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

Windows Server 2016 Activation and Servicing: A Comprehensive Guide, Exams of Service Management

install windows server 2016 official book brief

Typology: Exams

2016/2017

Uploaded on 10/04/2017

ahmad-alhafar
ahmad-alhafar 🇸🇪

5

(2)

7 documents

1 / 4

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Activating and Servicing Windows
After you complete the installation of Windows Server 2016, the next step is activating the operating
system. Windows Server 2016 gives you a few different options when it comes to activation.
In the past, many administrators would use the Volume Activation Management Tool ( VMAT ) to activate
both Microsoft operating systems and Microsoft products like Office.
Administrators can still use VMAT to activate Microsoft products like Office
but with the release of Windows Server 2016, there are some new ways to help administrators activate
the operating systems.
Key Management Service
Windows Server 2016 Key Management Service (KMS)
KMS allows your computers to get activated right on your local network without the need of contacting
Microsoft.
you must setup a KMS client-server network.
KMS clients are able to contact KMS servers as long as your network uses either a static TCP/IP
configuration or you have a Domain Name System (DNS) server setup.
you must configure and retrieve Volume Activation information. This is done by using a Software License
Manager (referred to as SL Manager) script (Slmgr.vbs).
This script can be run on a local system or a remote system but it needs to be run from a user's account
that uses an elevated command prompt.
KMS host systems can be any Windows client operating system running Windows Vista or higher and
any Server above Windows Server 2003.
To create or modify the slmgr.vbs script, an administrator can use either the Wscript.exe or
Cscript.exe application. Slmgr.vbs uses the Wscript.exe scripting engine by default. After an
administrator makes any changes to the Slmgr.vbs script, the Software Licensing Service must be
restarted. This can be done by using the Services Microsoft Management Console (MMC) or by running
the net stop and net start commands at an elevated command prompt (net stop sppsvc and net
start sppsvc).
The Slmgr.vbs script has different command line switches that you can use. Table 1.2 shows you some
of the different switches that you can use with the Slmgr.vbs script.
Table 1.2: Slmgr.vbs switches
Parameter Description
/ato This switch is used for retail and volume systems editions with a KMS
host key or a Multiple Activation Key (MAK) installed. The /ato
command prompts Windows to try to do an online activation. For any
systems that are using a Generic Volume License Key (GVLK), this
will make the system attempt to do a KMS activation.
/cdns This switch allows an administrator to disable KMS host automatic
DNS publishing.
pf3
pf4

Partial preview of the text

Download Windows Server 2016 Activation and Servicing: A Comprehensive Guide and more Exams Service Management in PDF only on Docsity!

Activating and Servicing Windows

After you complete the installation of Windows Server 2016, the next step is activating the operating system. Windows Server 2016 gives you a few different options when it comes to activation. In the past, many administrators would use the Volume Activation Management Tool ( VMAT ) to activate both Microsoft operating systems and Microsoft products like Office. Administrators can still use VMAT to activate Microsoft products like Office but with the release of Windows Server 2016, there are some new ways to help administrators activate the operating systems.

Key Management Service

Windows Server 2016 Key Management Service (KMS) KMS allows your computers to get activated right on your local network without the need of contacting Microsoft. you must setup a KMS client-server network. KMS clients are able to contact KMS servers as long as your network uses either a static TCP/IP configuration or you have a Domain Name System (DNS) server setup. you must configure and retrieve Volume Activation information. This is done by using a Software License Manager (referred to as SL Manager) script (Slmgr.vbs). This script can be run on a local system or a remote system but it needs to be run from a user's account that uses an elevated command prompt. KMS host systems can be any Windows client operating system running Windows Vista or higher and any Server above Windows Server 2003. To create or modify the slmgr.vbs script, an administrator can use either the Wscript.exe or Cscript.exe application. Slmgr.vbs uses the Wscript.exe scripting engine by default. After an administrator makes any changes to the Slmgr.vbs script, the Software Licensing Service must be restarted. This can be done by using the Services Microsoft Management Console (MMC) or by running the net stop and net start commands at an elevated command prompt (net stop sppsvc and net start sppsvc). The Slmgr.vbs script has different command line switches that you can use. Table 1.2 shows you some of the different switches that you can use with the Slmgr.vbs script.

Table 1.2: Slmgr.vbs switches

Parameter Description /ato (^) This switch is used for retail and volume systems editions with a KMS host key or a Multiple Activation Key (MAK) installed. The /ato command prompts Windows to try to do an online activation. For any systems that are using a Generic Volume License Key (GVLK), this will make the system attempt to do a KMS activation. /cdns (^) This switch allows an administrator to disable KMS host automatic DNS publishing.

/cpri (^) Administrators can use this switch to lower the priority of KMS host processes. /dli (^) Administrators can use this switch on the KMS host to view the current KMS activation count. /dlv (^) When an administrator uses this switch, the license information for the installed operating system is displayed. /ipk (^) This command will try to install a 5x5 product key. /sai activationInterva l This switch allows an administrator to change how often a KMS client attempts to activate itself when it cannot find a KMS host. The default setting is 120 minutes, but you can change the interval by replacing ActivationInterval with the number of minutes you want to set. /sdns (^) This switch allows an administrator to enable KMS host automatic DNS publishing. /spri (^) This allows an administrator to set the CPU priority of the KMS host processes to Normal. /sprt PortNumber (^) Using this switch allows an administrator to change the default TCP communications port on a KMS host from 1688 to whichever port the admin wants to use. To change the default port number, replace the PortNumber switch with the TCP port number to use. /sri RenewalInterval This switch allows an administrator to change how often a KMS client attempts to renew its activation by contacting a KMS host. If you need to change the default of 10080 (7 days), just replace RenewalInterval with a number of minutes you want to use. To run Slmgr.vbs remotely, administrators must supply additional parameters. They must include the computer name of the target computer as well as a username and password of a user account that has

Now that we looked at some of the ways to activate your Windows Server 2016 systems, let's take a look at how you can service your Windows Server systems. Table 1.4 will show the different versions for Windows Server 2016 and which servicing model each version uses.

Table 1.4: Servicing Models for Windows Server 2016

Installation Option LTSB Servicing CBB Servicing Desktop Experience Yes No Server Core Yes No Nano Server No Yes Long Term Servicing Branch (LTSB) 5 years of mainstream support and 5 years of extended support for the different versions of the Windows operating systems. This model will continue to be used in Windows Server 2016 (Desktop Support and Server Core) Current Branch for Business ( CBB ) This version of servicing is a more aggressive version and it was specifically designed with the cloud in mind. As the cloud continues to quickly evolve, the CBB servicing model is meant for that lifecycle. The CBB servicing model will continue to provide new features and functions to Windows Server allowing the server to evolve and grow with the rapidly changing industry. Microsoft's goal is to release updates multiple times per year for Nano Server thus keeping it changing with the industry.