Volume License Kms Vs Mak Key Atif Aslam Pehli Nazar Mein Unplugged Mp3 Free Download Sims 4 Maxis Match Default Eyes Ross Hill Scr System Operator Manual Format. There are 2 types of keys for Volume Licensing of Windows - KMS & MAK Keys. They both can be used to activate Windows in bulk, but serve different requirements of the Enterprise.
Updated: February 23, 2016
Applies To: Windows 10, Windows 8.1, Windows Server 2012 R2
The following sections describe key scenarios for KMS and MAK activation.
On this pageKMS scenarios
KMS can support simple, single-site networks and global networks. The following scenarios show:
Default KMS implementation for a single-site network
Contoso has 100 Windows 7 Enterprise clients and a mixed set of Windows Vista, Windows Server 2008, and Windows Server 2008 R2 systems. Contoso is a flat domain (Contoso.com). The DNS server runs Microsoft DNS in its default configuration. This configuration supports DNS dynamic update protocol and DNS record scavenging to remove stale records.
Contoso purchases a license agreement that provides a KMS key, which will activate all of its systems. The information technology (IT) administrator installs Contoso’s KMS host key (CSVLK) on two KMS hosts running Windows Server 2008 R2 by using the following command run locally at an elevated command prompt:
The IT administrator then creates a Security Group in Active Directory® Domain Services (AD DS) named KMS_Hosts. The administrator adds the servers KMS_1 and KMS_2 to the KMS_Hosts membership.
The host KMS_1 is activated against Microsoft via the Internet: Slmgr.vbs /ato. KMS_1 automatically publishes its SRV resource records (RRs) to DNS. The IT administrator accesses the DNS server, locates the RR for _vlmcs._tcp.contoso.com, and changes its permissions to give KMS_Hosts Read, Write, and Delete permission to the record. The host KMS_2 is now activated against Microsoft via the Internet: Slmgr.vbs /ato.
Finally, the administrator confirms that the KMS host exclusion is enabled in Windows Firewall. The Key Management Service firewall exception needs to be enabled.
KMS clients on the Contoso network query DNS and receive the SRV records for both KMS hosts. The clients pick one or the other host and are activated (as soon as the KMS count rises above the threshold). See the section, “Activation Policy Values,” for more information about KMS count requirements.
KMS implementation in a complex, global network
Contoso has expanded into two domains, east.contoso.com and west.contoso.com. Network traffic can pass privately between the two networks through a firewalled wide area network (WAN) link. This link has limited bandwidth, so resources (including DNS) are replicated on both sides of the WAN link to reduce traffic when possible.
Contoso uses image-based deployment. Its client systems are standardized on Windows Vista, but the Windows Vista systems are being replaced by Windows 7 clients.
Users regularly travel geographically, and their network connection changes from one domain to the other. Clients’ IP addressing is provided dynamically by DHCP, including specifying the local DNS host, local gateway address, and so on.
To provide activation support for the existing Windows Vista clients and the new Windows 7 clients, Contoso installs four KMS hosts (using its KMS B key). Two KMS hosts are configured in east.contoso.com, and two are configured in west.contoso.com.
The IT administrator configures the KMS hosts so that the DNS SRV records drive Windows 7 and Windows Server 2008 R2 clients in the east domain to KMS_E1, if available, or to KMS_E2. If neither is available, the clients will attempt KMS_W1 and, finally, KMS_W2. Likewise, DNS in the west domain is configured so that Windows 7 clients in the west domain will prefer contacting KMS_W1, then KMS_W2 and only when these fail will attempt activation with KMS_E1 and KMS_E2 on the far side of the WAN link.
The IT administrator accomplishes this by making the following configuration changes (see Table 5):
Table 5. KMS Host Configuration
Then, the administrator confirms that the Windows Firewall exceptions are set to allow KMS client traffic and configures client computers, as Table 6 describes.
Table 6. KMS Client Configuration
The client reference computer is KMS activated, then sysprep /generalize is run. The system is shut down and imaged using ImageX from the Windows 7 Windows Automated Installation Kit (Windows AIK). The Windows AIK is available to download at https://go.microsoft.com/fwlink/?LinkId=136976.
MAK scenarios
The following sections describe scenarios for MAK activation. This section involves network and workgroup environments that are typical within large enterprises.
In the Core Network environment, all computers are within a common network managed by AD DS. The Secure Zone represents higher-security Core Network computers that have addition firewall protection.
The Isolated Lab environment is a workgroup that is physically separate from the Core Network, and its computers do not have Internet access. The network security policy states that no information that could identify a specific computer or user may be transferred out of the Isolated Lab.
MAK independent activation
The VAMT allows automation of MAK deployment and activation over the network by distributing MAKs from a centralized console. 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 3.1 is included in the Windows ADK. For more information about VAMT, see Volume Activation Management Tool (VAMT) Technical Reference, and VAMT How-To Topics
In this scenario, the VAMT is deployed in the Core Network environment. The VAMT is installed on a central computer with network access to all client computers. Both the VAMT host and client computers have Internet access. The following instructions describe how to perform independent activation:
MAK proxy activation
In this scenario, the VAMT is used to activate workgroup computers within an Isolated Lab environment. For workgroups such as this, which are completely isolated from the larger network, you can perform MAK proxy activation by installing a second VAMT on a computer within the isolated workgroup and using removable media to transfer VAMT CILs between that computer and another VAMT host that has Internet access. For more information about configuring systems for VAMT remote management, see the VAMT help. The following steps describe how to use the VAMT tool for proxy activation:
Volume License Kms Vs Mak Key
VAMT support for KMS activation
In this scenario, the VAMT is used to install and activate KMS client keys on either Core Network or Isolated Lab computers. The procedure described below assumes that the VAMT has been installed and the computers have been added to the CIL. These tasks are described in steps 1–4 in either Scenario 1 (for the Core Network) or Scenario 2 (for the Isolated Lab workgroup).
Converting KMS 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 anytime 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
You 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 https://go.microsoft.com/fwlink/?LinkId=136976.
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 “SENSITIVEDATADELETED.”
Installing a MAK after operating system installation
You can configure a volume edition of Windows 7 or Windows Server 2008 R2 to use MAK activation by using the Control Panel System item or by running the Slmgr.vbs script:
Volume License Kms Vs Mak Key For Download
If users install a MAK by using the user interface (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. The user can use Slmgr.vbs /ato to manually activate the MAK over Internet.
See alsoKMS vs. MAKVolume License Kms Vs Mak Key For Windows 7
Windows’ recent operating systems, particularly Windows Vista, Windows Server 2008, 2008 R2, Windows 7, and Office 2010 use an activation technology called Volume Activation, which allows for activation automation that is transparent both to Volume Licensing customers and end users. Volume Activation can use either the Key Management Service (KMS) model or Multiple Activation Key (MAK) model to activate said systems. Customers can use both or either of the models. The main difference is in the type of key employed in the activation process. Add to that some practical considerations like organization type, network size, and OS versions, among others.
KMS was released right after Volume License Key technology, which required no activation at all. KMS does require activation, but it allows customers to do this within their own network, serving as a central location where all clients acquire an activation key. It is specifically designed for enterprise customers and is most compatible with Vista and Windows 2008. MAK, on the other hand, requires only a one-time activation with some support from Microsoft’s hosted activation services or a MAK Proxy Server.
Activation with MAK is made possible through a unique alphanumeric key capable of activating a specific number of computers. As far as installation is concerned, KMS proves more convenient, as it allows the computer to automatically detect it via DNS. A pre-requisite is a dynamic DNS with SRV record support; without it, manual and individual access to the clients’ registry may be required in order to locate the local KMS. With met pre-requisites, no further client configuration for activation is required upon installation, even with newly installed PCs, for as long as they are within the network.
Volume License Kms Vs Mak Key For Free
MAK activation needs keen supervision during the installation and activation process. Every PC added for activation is equal to individual configuration. However, MAK doesn’t need Internet access to complete activation. Similarly, KMS is also capable of completion without further changes to the firewall. The main requirement is for it to secure that the KMS host can connect to Microsoft’s volume licensing servers.
In terms of activation capacity and expiration, MAK is more advantageous than KMS. The former has a one-time, non-expiring activation and doesn’t require frequent updates with product keys, thus providing better security against activation failure. The only downside is in its limited number of activation, while the quantity of clients that can be catered to is dependent on the number of licenses purchased; this increases the need to repurchase licenses over time. Conversely, KMS has to maintain two levels of reactivation every 6 months. The first level comprises of every client within the network, the second – the KMS host. This entails an extra task of regularly monitoring the KMS server, DNS, as well as the clients and their connection status.
What’s good about it, though, is the fact that it can activate an infinite number of clients regardless of license. Another important factor to consider is the organization’s IT structure, i.e. the number of computers, the type of machines (laptop or desktop), the number of sub-branches/ departments. KMS works best with more than 50 computers, mostly desktops, and with a centralized set-up. This is due to the fact that it is highly dependent on a KMS host. Even though a customer has the option to use several hosts, it is still ideal to maintain a single server; otherwise, it increases the risk on the integrity of the client-DNS-server connection, and not to mention, more maintenance and probable troubleshooting work. Compared to KMS, MAK works more flexibly with fewer than 25 computers, both laptop and desktops, with decentralized IT structures. It does not pose much limitation, no matter how your IT infrastructure is organized – regardless of whether it has multiple branches, high security networks, and uses a good mix of desktops and field computers.
Volume License Kms Vs Mak Key For MacSummary:
Volume License Kms Vs Mak Key For Windows 10Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |