![]() ![]()
Then, the administrator confirms that the Windows Firewall exceptions are set to allow KMS client traffic and configures client computers, as Table 6 describes.Ī customer URL is set to direct users with activation issues to the Contoso help desk ![]() Traffic will be divided: 75% to the KMS_*1 hosts and 25% to the KMS_*2 hosts. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform DnsDomainPublishList=Ĭonfigure SRV priority and weight so that clients will contact KMS_W* hosts if available before trying KMS_E* hosts. This group is given Read, Write, and Delete rights to the record _vlmcs._.ĭHCP servers are configured to add and to the DNS suffix search list for all clients.įirewalls between east and west domains are configured to allow RPC traffic to the KMS hosts on port 1688.Ĭonfigure SRV priority and weight so that clients will contact KMS_E* hosts if available before trying KMS_W* hosts. KMS_W* hosts are added to the security group KMS_W. This group is given Read, Write, and Delete rights to the record _vlmcs._. KMS_E* hosts are added to the security group KMS_E. The IT administrator accomplishes this by making the following configuration changes (see Table 5): 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. If neither is available, the clients will attempt KMS_W1 and, finally, KMS_W2. 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. Two KMS hosts are configured in, and two are configured in. 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). Clients’ IP addressing is provided dynamically by DHCP, including specifying the local DNS host, local gateway address, and so on. Users regularly travel geographically, and their network connection changes from one domain to the other. Its client systems are standardized on Windows Vista, but the Windows Vista systems are being replaced by Windows 7 clients. This link has limited bandwidth, so resources (including DNS) are replicated on both sides of the WAN link to reduce traffic when possible.Ĭontoso uses image-based deployment. Network traffic can pass privately between the two networks through a firewalled wide area network (WAN) link. ![]() KMS implementation in a complex, global networkĬontoso has expanded into two domains, and. See the section, “Activation Policy Values,” for more information about KMS count requirements. The clients pick one or the other host and are activated (as soon as the KMS count rises above the threshold). KMS clients on the Contoso network query DNS and receive the SRV records for both KMS hosts. The Key Management Service firewall exception needs to be enabled. The host KMS_2 is now activated against Microsoft via the Internet: Slmgr.vbs /ato.įinally, the administrator confirms that the KMS host exclusion is enabled in Windows Firewall. ![]() The IT administrator accesses the DNS server, locates the RR for _vlmcs._, and changes its permissions to give KMS_Hosts Read, Write, and Delete permission to the record. KMS_1 automatically publishes its SRV resource records (RRs) to DNS. The host KMS_1 is activated against Microsoft via the Internet: Slmgr.vbs /ato. The administrator adds the servers KMS_1 and KMS_2 to the KMS_Hosts membership. The IT administrator then creates a Security Group in Active Directory® Domain Services (AD DS) named KMS_Hosts. 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: Slmgr.vbs /ipk #Kristenix right click image converter serial key update#This configuration supports DNS dynamic update protocol and DNS record scavenging to remove stale records.Ĭontoso purchases a license agreement that provides a KMS key, which will activate all of its systems. The DNS server runs Microsoft DNS in its default configuration. The implementation expanded to support a global network.ĭefault KMS implementation for a single-site networkĬontoso has 100 Windows 7 Enterprise clients and a mixed set of Windows Vista, Windows Server 2008, and Windows Server 2008 R2 systems. KMS can support simple, single-site networks and global networks. The following sections describe key scenarios for KMS and MAK activation. KMS and MAK Activation Scenarios for Volume ActivationĪpplies To: Windows 10, Windows 8.1, Windows Server 2012 R2 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |