Learn about license deployment models.
Unserved Licenses |
Served Licenses |
---|---|
Licenses can be used only on the machine for which the license was generated. |
Licenses can be distributed from a network license server to products running on any network machine. |
No license administration is required. However, when new licenses are required for product updates, you must update and deploy each license for each machine where the product update will run. |
The license server requires administration. When new licenses are required for product updates, SPDC or SMP lets you update all licenses for a specific license server in a single step. |
No license reporting or asset management capabilities are available. |
Allows license monitoring and reporting of license use, capacity planning, and asset management using SAMreport. |
Installed locally and always available. |
Requires a functioning license server and network. If the license server or network fails, you must fix the problem or install an alternate license server before the product grace period expires. |
If a machine where the product is running fails, you must regenerate all of its licenses and deploy those licenses to the replacement machines. |
If a machine where the product is running fails, you can move the product to a new machine, and it will acquire licenses from the running license server. If the license server host machine fails, use the Manage License Hosts functionality at SPDC or SMP to move its licenses to a new network license server host. |
License files are distributed across each machine running a product, and therefore they are difficult to manage and control. |
License files are centrally located and managed. |
Unserved Standalone Seat (SS) licenses do not allow product use via Remote Desktop Connection or other terminal services clients. |
Products can be used via Remote Desktop Connection or other Terminal Services clients, irrespective of the type of license in use. |