How to Know What Product Use Rights Apply Sample Clauses

How to Know What Product Use Rights Apply. Generally, the use rights in effect at the time Institution signs the Enrollment will apply. Any changes Microsoft makes to the use rights for existing versions after Institution signs the Enrollment will not apply to Institution. For versions that were not yet released at the time of signing, the use rights in effect when that version is first released will apply. Generally, even if Institution chooses to run an earlier version of a Product than the one Institution is licensing, the use rights for the latest version Institution is licensed to use will still apply.
AutoNDA by SimpleDocs
How to Know What Product Use Rights Apply. This section describes where to find the use rights that apply to Products, when Microsoft can change those use rights, and when Microsoft can withdraw a Product from the program and how that would affect Customer.
How to Know What Product Use Rights Apply. Generally, Microsoft agrees to lock-in the Product Use Rights at the start of the agreement, for current versions, and on the date of first release, for new versions, so that any subsequent changes Microsoft makes to the Product Use Rights will not affect any Registered Affiliates. A special rule applies in the case of downgrades, as described below.
How to Know What Product Use Rights Apply 

Related to How to Know What Product Use Rights Apply

  • License Types (a) A Team License shall mean a subscription license that provides a limited number of licenses to a set amount of developers for a named Customer. Customer must procure enough active licenses for each individual who has Programmatic Access. A Team License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. A Team License cannot be used as a floating license. (b) A Project License shall mean a subscription license which covers one named Customer application. The license fees are based on the total number of developers working on a named project, regardless of whether such developers are directly using the Licensed Product. For the purposes of pricing and license administration, a “Project Group” is deemed to be a distinct Customer software team within a Customer’s business unit that works towards a distinct business purpose for the benefit of a single application. Customer is required to identify the name of each such Project Group to Syncfusion; such name must be unambiguous in nature. It is acknowledged and agreed by Customer that each identified Project Group shall exist for a valid business purpose and not just as a means for consolidating software licenses to minimize license fees that are otherwise due. If, in the sole opinion of Syncfusion, multiple Customer teams would each individually meet the above definition of a Project Group, such multiple teams shall not be combined for the purpose of consolidating licenses under a single Project Group. Customer is responsible for providing information about each such Project Group to Syncfusion. By entering into this Agreement, Customer represents that after the effective date, it will not withhold information that Syncfusion requires to properly license each such Project Group, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (c) A Division License shall mean a subscription license which will cover one named Division and allow for development work on more than one project within such Division. A Division shall mean a business unit within Customer’s organization that works towards a distinct business purpose. Customer is required to identify the name of such Division to Syncfusion; such name must be unambiguous in nature. License fee determinations will be at the sole discretion of Syncfusion and be based on such factors including, but not limited to, Customer’s Division size, developer count, and the scope of the Division’s business purpose. By entering into this Agreement, Customer acknowledges that it is responsible for providing information about the named Customer Division to Syncfusion sufficient for Syncfusion to price the Division License, and Customer represents that it will not withhold information that Syncfusion requires to properly license each such named Customer division, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (d) A Global License shall mean a subscription license for all development for a named Customer, where the license fees are based on the overall size of a named Customer. A Global License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. (e) A Retail License shall mean a single named user, non-transferable license to use the Licensed Product. Retail Licenses will only made available to Customers in Syncfusion’s sole discretion and only when the number of such End-Users is finite and readily ascertainable. Accordingly, Syncfusion will make a determination as to whether or not the provision of Retail Licenses is appropriate under the circumstances applicable to any given Customer, and Syncfusion reserves the right, in its sole discretion, to refuse to make available Retail Licenses to a Customer and instead require a given Customer to procure a Project License, Division License, or Global License as circumstances dictate. A Retail License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer.

  • Know-How The term “

  • License Type Your license to a Product will be under a Named User or CPU license type, as specified on an order. Each Named User license to a Product entitles a Named User to access and use that Product in one production environment and up to two non-production environments. Each CPU license to a Product entitles you to assign the Product to a single CPU in one production environment and up to two non-production environments, for use in support of an unspecified number of Named Users.

  • Sublicense to Use the Scudder Trademarks As exclusive licensee of the rights to use anx xxxxxcense the use of the "Scudder," "Scudder Investments" and "Scudder, Stevens & Clark, Inx." xxxdemaxxx (xxgether, the "Scuddex Xxxxx"), xxx xerexx xxant the Trust a nonexclusive right xxx xxxlicense to use (i) the "Scudder" name and mark as part of the Trust's name (the "Fund Namx"), xxd (ii) the Scudder Marks in connection with the Trust's investment products xxx xxxvices, in each case only for so long as this Agreement, any other investment management agreement between you or any organization which shall have succeeded to your business as investment manager ("your Successor") and the Trust, or any extension, renewal or amendment hereof or thereof remains in effect, and only for so long as you are a licensee of the Scudder Marks, provided however, that you agree to use your best xxxxxxx to maintain your license to use and sublicense the Scudder Marks. The Trust agrees that it shall have no right to suxxxxxxxe or assign rights to use the Scudder Marks, shall acquire no interest in the Scudder Marks othxx xxxx the rights granted herein, that all of txx Xxxxt's uses of the Scudder Marks shall inure to the benefit of Scudder Trust Company xx xxxer and licensor of the Scudder Marks (xxx "Xrademark Owner"), and that the Trust shall nxx xxxxlenge the validity of the Scudder Marks or the Trademark Owner's ownership thereof. The Truxx xxxxher agrees that all services and products it offers in connection with the Scudder Marks shall meet commercially reasonable standards of duaxxxx, xs may be determined by you or the Trademark Owner from time to time, provided that you acknowledge that the services and products the Trust rendered during the one-year period preceding the date of this Agreement are acceptable. At your reasonable request, the Trust shall cooperate with you and the Trademark Owner and shall execute and deliver any and all documents necessary to maintain and protect (including but not limited to in connection with any trademark infringement action) the Scudder Marks and/or enter the Trust as a registered user thereof. Xx xxch time as this Agreement or any other investment management agreement shall no longer be in effect between you (or your Successor) and the Trust, or you no longer are a licensee of the Scudder Marks, the Trust shall (to the extent that, and as soon ax, xx xawfully can) cease to use the Fund Name or any other name indicating that it is advised by, managed by or otherwise connected with you (or your Successor) or the Trademark Owner. In no event shall the Trust use the Scudder Marks or any other name or mark confusingly similar therexx (xxxluding, but not limited to, any name or mark that includes the name "Scudder") if this Agreement or any other investment advisory agrexxxxx xetween you (or your Successor) and the Fund is terminated.

  • License for Txdot Logo Use DocuSign Envelope ID: 08011FCF-93C2-4F54-8A05-20A33047A1D8

  • Vendor Logo (Supplemental Vendor Information Only) No response Optional. If Vendor desires that their logo be displayed on their public TIPS profile for TIPS and TIPS Member viewing, Vendor may upload that logo at this location. These supplemental documents shall not be considered part of the TIPS Contract. Rather, they are Vendor Supplemental Information for marketing and informational purposes only. Some participating public entities are required to seek Disadvantaged/Minority/Women Business & Federal HUBZone ("D/M/WBE/Federal HUBZone") vendors. Does Vendor certify that their entity is a D/M/WBE/Federal HUBZone vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. NO Some participating public entities are required to seek Historically Underutilized Business (HUB) vendors as defined by the Texas Comptroller of Public Accounts Statewide HUB Program. Does Vendor certify that their entity is a HUB vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. No Can the Vendor provide its proposed goods and services to all 50 US States? Yes

  • USE OF NASA NAME AND NASA EMBLEMS A. NASA Name and Initials Partner shall not use "National Aeronautics and Space Administration" or "NASA" in a way that creates the impression that a product or service has the authorization, support, sponsorship, or endorsement of NASA, which does not, in fact, exist. Except for releases under the "Release of General Information to the Public and Media" Article, Partner must submit any proposed public use of the NASA name or initials (including press releases and all promotional and advertising use) to the NASA Associate Administrator for the Office of Communications or designee ("NASA Communications") for review and approval. Approval by NASA Office of Communications shall be based on applicable law and policy governing the use of the NASA name and initials. B. NASA Emblems Use of NASA emblems (i.e., NASA Seal, NASA Insignia, NASA logotype, NASA Program Identifiers, and the NASA Flag) is governed by 14 C.F.R. Part 1221. Partner must submit any proposed use of the emblems to NASA Communications for review and approval.

  • Name; Trade Names and Styles The name of Borrower set forth in the heading to this Agreement is its correct name. Listed on the Schedule are all prior names of Borrower and all of Borrower's present and prior trade names. Borrower shall give Silicon 30 days' prior written notice before changing its name or doing business under any other name. Borrower has complied, and will in the future comply, with all laws relating to the conduct of business under a fictitious business name.

  • Background Screening VENDOR shall comply with all requirements of Sections 1012.32 and 1012.465, Florida Statutes, and all of its personnel who (1) are to be permitted access to school grounds when students are present, (2) will have direct contact with students, or (3) have access or control of school funds, will successfully complete the background screening required by the referenced statutes and meet the standards established by the statutes. This background screening will be conducted by SBBC in advance of VENDOR or its personnel providing any services under the conditions described in the previous sentence. VENDOR shall bear the cost of acquiring the background screening required by Section 1012.32, Florida Statutes, and any fee imposed by the Florida Department of Law Enforcement to maintain the fingerprints provided with respect to VENDOR and its personnel. The parties agree that the failure of VENDOR to perform any of the duties described in this section shall constitute a material breach of this Agreement entitling SBBC to terminate immediately with no further responsibilities or duties to perform under this Agreement. VENDOR agrees to indemnify and hold harmless SBBC, its officers and employees from any liability in the form of physical or mental injury, death or property damage resulting from VENDOR’s failure to comply with the requirements of this section or with Sections 1012.32 and 1012.465, Florida Statutes.

  • License Rights The Recipient must provide a license to its “subject data” to the Federal Government, which license is: (a) Royalty-free, (b) Non-exclusive, and (c) Irrevocable, (2) Uses. The Federal Government’s license must permit the Federal Government to take the following actions provided those actions are taken for Federal Government purposes: (a) Reproduce the subject data, (b) Publish the subject data, (c) Otherwise use the subject data, and (d) Permit other entities or individuals to use the subject data, and

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!