Abstract: A master license entry that links a software application to a user identification can be made. Application licenses to use the software application can be roamed to multiple computing machines. Feature licenses for added features of the software application can be roamed to those computing machines as well. Multiple overlapping license rights for the software application may be linked to the master license entry. A count of how many license rights for the software application are linked to the master license entry can be maintained. Requests for licenses may be refused if the count of license rights has reached zero.

Abstract: A master license entry that links a software application to a user identification can be made. Application licenses to use the software application can be roamed to multiple computing machines. Feature licenses for added features of the software application can be roamed to those computing machines as well. Multiple overlapping license rights for the software application may be linked to the master license entry. A count of how many license rights for the software application are linked to the master license entry can be maintained. Requests for licenses may be refused if the count of license rights has reached zero.

Abstract: Techniques involving detection of misuse of digital licenses pertaining to application use. An identification of unsigned applications or other use-protected applications enabled for use at a user device is obtained. The identification of such applications is directed to a licensing authority to seek digital license renewal for using the applications. A renewed digital license is received if the provided identification of use-protected applications corresponds to what is authorized by the licensing authority for use at the user device. In other embodiments, verification information may be provided to protect the identification of unsigned applications from tampering, such as information indicative of whether the identification of unsigned applications originated at the user device in which the use-protected applications are used, and indicative of whether the identification of the unsigned applications is a copy of a previous identification of the unsigned applications.

Abstract: One or more techniques and/or systems are disclosed for generating a developer license that allows a developer application to run on developer machine. A user identification (userID) used to register a user can be used by the user to register as a developer. The userID can be authenticated for the registered developer. Further, a machine used by the developer for the developer application can be registered, and a resulting hardware identification (hardwareID) can be authenticated for the registered developer machine. Additionally, a developer certificate can be generated for the registered developer. The developer certificate can be authenticated and used to sign the developer application. The developer license can be generated for the developer, allowing the developer machine to execute the developer application, based at least upon the authenticated userID, the authenticated hardwareID, and the authenticated developer certificate.

Abstract: Techniques involving detection of misuse of digital licenses pertaining to application use. An identification of unsigned applications or other use-protected applications enabled for use at a user device is obtained. The identification of such applications is directed to a licensing authority to seek digital license renewal for using the applications. A renewed digital license is received if the provided identification of use-protected applications corresponds to what is authorized by the licensing authority for use at the user device. In other embodiments, verification information may be provided to protect the identification of unsigned applications from tampering, such as information indicative of whether the identification of unsigned applications originated at the user device in which the use-protected applications are used, and indicative of whether the identification of the unsigned applications is a copy of a previous identification of the unsigned applications.

Abstract: Techniques involving detection of misuse of digital licenses pertaining to application use. An identification of unsigned applications or other use-protected applications enabled for use at a user device is obtained. The identification of such applications is directed to a licensing authority to seek digital license renewal for using the applications. A renewed digital license is received if the provided identification of use-protected applications corresponds to what is authorized by the licensing authority for use at the user device. In other embodiments, verification information may be provided to protect the identification of unsigned applications from tampering, such as information indicative of whether the identification of unsigned applications originated at the user device in which the use-protected applications are used, and indicative of whether the identification of the unsigned applications is a copy of a previous identification of the unsigned applications.

Abstract: One or more techniques and/or systems are disclosed for generating a developer license that allows a developer application to run on developer machine. A user identification (userID) used to register a user can be used by the user to register as a developer. The userID can be authenticated for the registered developer. Further, a machine used by the developer for the developer application can be registered, and a resulting hardware identification (hardwareID) can be authenticated for the registered developer machine. Additionally, a developer certificate can be generated for the registered developer. The developer certificate can be authenticated and used to sign the developer application. The developer license can be generated for the developer, allowing the developer machine to execute the developer application, based at least upon the authenticated userID, the authenticated hardwareID, and the authenticated developer certificate.

Abstract: One or more techniques and/or systems are disclosed for generating a test application license for a developer application, such as to test a licensing portion of the developer application on a developer machine. An application identifier (appID) can be created that is particular to the developer application. Developer binding data associated with an authenticated developer of the developer application can be created that is particular to the developer. The appID and developer binding data are combined to create bound application developer data. The test application license is generated for the developer application based at least upon an authenticated developer certificate and the bound application developer data. The generated test application license provides for the licensing portion of the developer application to be tested on the developer machine.

Abstract: Techniques involving detection of misuse of digital licenses pertaining to application use. An identification of unsigned applications or other use-protected applications enabled for use at a user device is obtained. The identification of such applications is directed to a licensing authority to seek digital license renewal for using the applications. A renewed digital license is received if the provided identification of use-protected applications corresponds to what is authorized by the licensing authority for use at the user device. In other embodiments, verification information may be provided to protect the identification of unsigned applications from tampering, such as information indicative of whether the identification of unsigned applications originated at the user device in which the use-protected applications are used, and indicative of whether the identification of the unsigned applications is a copy of a previous identification of the unsigned applications.

Abstract: Software restriction policy rules can be automatically generated by parsing through a specified metadata source and generating the rules in accordance with indicated preferences. Metadata sources can include storage locations, such as folders, in which case rules for each executable file in the folder can be generated. Metadata sources can also include trusted publisher stores, installation logs, difference files, and other like data sources. Indicated preferences can select from among rules based on the publisher, for files that are signed, or rules based on hashes or path information for unsigned files. In generating rules to prevent the execution of specified files, if an optimized set of rules is desired, a check can be made to determine if an exception to an existing rule can be generated instead of a new rule. The automated parsing of the indicated metadata source can provide for both completeness and correctness.

Abstract: The claimed subject matter provides a method for licensing software in a computing environment. An exemplary method includes initiating application software program on a computer system having a plurality of authorized users, one of the authorized users having a single-user license to use the software program. An identity of a current user of the computer system is checked. Operation of the software program is prohibited if the current user is one of the plurality of authorized users other than the user who is granted the single-user license.

Abstract: The claimed subject matter provides a method for revoking licensed software in a computing environment. An exemplary method includes receiving a machine ID from a computer system. An application program and a license credential for the application program are sent to the computer system. Subsequently, upon theft or other loss of the computer system, a request to revoke the license credential is received. The request identifies the machine ID. When the computer system subsequently initiates a connection, the connection is detected based on the machine ID. An indication that the license credential for the application program is revoked is sent to the computer system. When the application program is later initiated, its operation is disabled because of the revocation of the license credential.

Abstract: A master license entry that links a software application to a user identification can be made. Application licenses to use the software application can be roamed to multiple computing machines. Feature licenses for added features of the software application can be roamed to those computing machines as well. Multiple overlapping license rights for the software application may be linked to the master license entry. A count of how many license rights for the software application are linked to the master license entry can be maintained. Requests for licenses may be refused if the count of license rights has reached zero.

Abstract: The claimed subject matter provides a method for managing license upgrades in a computing environment. An exemplary method includes sending a request to upgrade a license status of application software program. The method further includes receiving licensing information indicating a change to the license status of the software program, the change to the license status of the software program being sufficient to allow the user to use the software program under the changed status automatically, and without further action by a user.

Abstract: Software restriction policy rules can be automatically generated by parsing through a specified metadata source and generating the rules in accordance with indicated preferences. Metadata sources can include storage locations, such as folders, in which case rules for each executable file in the folder can be generated. Metadata sources can also include trusted publisher stores, installation logs, difference files, and other like data sources. Indicated preferences can select from among rules based on the publisher, for files that are signed, or rules based on hashes or path information for unsigned files. In generating rules to prevent the execution of specified files, if an optimized set of rules is desired, a check can be made to determine if an exception to an existing rule can be generated instead of a new rule. The automated parsing of the indicated metadata source can provide for both completeness and correctness.