Windows 7 / Getting Started

Volume Activation Scenarios

Each Volume Activation method is best suited to a particular network configuration. To select the best activation method or methods for the organization, assess the network environment to identify how different groups of computers connect to the network. Connectivity to the corporate network, Internet access, and the number of computers that regularly connect to the corporate network are some of the important characteristics to identify. Most mediumsized to large organizations use a combination of activation methods because of the varied ways their client computers connect to their networks.

KMS is the recommended activation method for computers that are well connected to the organization's core network or that have periodic connectivity, such as computers that are offsite. MAK activation is the recommended activation method for computers that are offsite with limited connectivity or that cannot connect to the core network because of security restrictions. These include computers in lab and development environments that are isolated from the core network.

Table below lists common network configurations and the best practice recommendations for each type. Each solution factors in the number of computers and network connectivity of the activation clients.

Volume Activation Recommendations by Scenario
Network InfrastructureRecommendationsConsiderations
Core network
Well-connected LAN
Most common scenario
If total computers > KMS activation threshold:
  • Small (< 100 machines):
    KMS host = 1
  • Medium (> 100 machines):
    KMS host ≥ 1
  • Enterprise: KMS host > 1
If total computers ≤ KMS activation threshold:
  • MAK (by telephone or Internet)
  • MAK Proxy
Minimize the number of KMS hosts
Each KMS host must consistently maintain a count of total machines
> KMS activation threshold
KMS hosts are autonomous
KMS host is activated by telephone or Internet
Isolated network
Branch office, highsecurity network segments, perimeter networks
Well-connected zoned LAN
If ports on firewalls can be opened between KMS clients and hosts:
  • Use KMS hosts in core network
If policy prevents firewall modification:
  • Use local KMS hosts in an isolated network
  • MAK (by telephone or Internet)
  • MAK Proxy
Firewall configuration
  • RPC over TCP (TCP port 1688)
  • Initiated by the client
Change management on firewall rule sets
Test or development lab
Isolated network
If total computers > KMS activation threshold:
  • KMS host = 1 (per isolated network)
If total computers ≤ KMS activation threshold:
  • No activation (reset grace period)
  • MAK (by telephone)
  • MAK Proxy performed manually
Variable configuration
Limited number of computers
KMS host and MAK activation through telephone; MAK Proxy performed manually
Individual disconnected computer
No connectivity to the Internet or core network
Roaming computers that periodically connect to the core network or connect through a virtual private network (VPN)
Roaming computers with Internet access but no connection to the core network
For clients that connect periodically to the core network:
  • Use the KMS hosts in the core network
For clients that never connect to the core network or have no Internet access:
  • MAK (by telephone)
For networks that cannot connect to the core network:
  • If total computers > KMS activation threshold:
    • Small: KMS host = 1
    • Medium: KMS host ≥ 1
    • Enterprise: KMS host > 1
  • If total computers ≤ KMS activation threshold, MAK Independent or MAK Proxy performed manually
For clients that never connect to the core network but have Internet access:
  • MAK (by Internet)
Restricted environments or networks that cannot connect to other networks
KMS host can be activated and then moved to disconnected network
KMS host and MAK activation by telephone; MAK Proxy performed manually

The following sections describe examples of Volume Activation solutions in heterogeneous corporate environments that require more than one activation method. Each scenario has a recommended activation solution, but some environments may have infrastructure or policy requirements that are best suited to a different solution.

[Previous] [Contents] [Next]