Support for Prior Versions Sample Clauses

Support for Prior Versions. Licensee must timely install all Fixes and New Versions to receive Support Services. In some cases, it may not be practical for certain customers to install a New Version immediately upon release. Therefore, PowerSchool may, in its discretion, continue to provide Telephone and E-mail Support for the prior version of Licensed Product for a period of time after release of a New Version. Licensee acknowledges that Fixes and other code maintenance will not be available for prior versions of Licensed Product (including SRC) after the release of a New Version.
AutoNDA by SimpleDocs
Support for Prior Versions. During the Term, Contractor shall continue to provide Maintenance and Support for versions of the Licensed Software within one Release or Version prior to the most recent release (for example, support will continue for version 2.0 up through and including version 4.0).
Support for Prior Versions. As set forth in Section 4 of these Policies, Licensee must timely install all Fixes and New Versions to receive Support Services. In some cases, it may not be practical for certain customers to install a New Version immediately upon release. Therefore, Pearson may, in its discretion, continue to provide Telephone and E-mail Support for the prior version of Licensed Product for a period of time after release of a New Version. Licensee acknowledges that Fixes and other code maintenance will not be available for prior versions of Licensed Product (including SRC) after the release of a New Version.
Support for Prior Versions. As set forth in Section 4 of these Policies, Licensee must timely install all Fixes to receive Support Services. In some cases, it may not be practical for certain customers to install a Fix or New Version immediately upon release. Therefore, Crow Canyon may, in its discretion, continue to provide Support for the prior version of Licensed Product for a period of time after release of a New Version. Licensee acknowledges that Fixes and other code maintenance may not be available for prior versions of Licensed Product after the release of a New Version.
Support for Prior Versions. ISOCOR will support a previous version (major and minor) release for six (6) months following release of a new version of a Product.

Related to Support for Prior Versions

  • Software Modifications Company may request that BNYM, at Company’s expense, develop modifications to the software constituting a part of the Licensed System that BNYM generally makes available to customers for modification (“Software”) that are required to adapt the Software for Company’s unique business requirements. Such requests, containing the material features and functionalities of all such modifications in reasonable detail, will be submitted by Company in writing to BNYM in accordance with the applicable, commercially reasonable procedures maintained by BNYM at the time of the request. Company shall be solely responsible for preparing, reviewing and verifying the accuracy and completeness of the business specifications and requirements relied upon by BNYM to estimate, design and develop such modifications to the Software. BNYM shall have no obligation to develop modifications to the Licensed System requested by Company, but may in its discretion agree to develop requested modifications which it, in its sole discretion, reasonably determines it can accomplish with existing resources or with readily obtainable resources without disruption of normal business operations provided Company agrees at such time in writing to pay all costs and expenses, including out-of-pocket expenses, associated with the customized modification. BNYM shall be obligated to develop modifications under this Section 2.16 only upon the execution of and in accordance with a writing containing, to BNYM’s reasonable satisfaction, all necessary business and technical terms, specifications and requirements for the modification as determined by BNYM in its sole judgment (“Customization Order”) and Company’s agreement to pay all costs and expenses, including out-of-pocket expenses, associated with the customized modification (“Customization Fee Agreement”). All modifications developed and incorporated into the Licensed System pursuant to a Customization Order are referred to herein as “Company Modifications”. BNYM may make Company Modifications available to all users of the Licensed System, including BNYM, at any time after implementation of the particular Company Modification and any entitlement of Company to reimbursement on account of such action must be contained in the Customization Fee Agreement.

  • Software License Subject to the terms of this Agreement, Viasat grants to you a personal, non-exclusive, non-assignable and non-transferable license to use and display the software provided by or on behalf of Viasat (including any updates) only for the purpose of accessing the Service ("Software") on any computer(s) on which you are the primary user or which you are authorized to use. Our Privacy Policies provide important information about the Software applications we utilize. Please read the terms very carefully, as they contain important disclosures about the use and security of data transmitted to and from your computer. Unauthorized copying of the Software, including, without limitation, software that has been modified, merged or included with the Software, or the written materials associated therewith, is expressly forbidden. You may not sublicense, assign, or transfer this license or the Software except as permitted in writing by Viasat. Any attempt to sublicense, assign or transfer any of the rights, duties or obligations under this license is void and may result in termination by Viasat of this Agreement and the license. You agree that you shall not copy or duplicate or permit anyone else to copy or duplicate any part of the Software, or create or attempt to create, or permit others to create or attempt to create, by reverse engineering or otherwise, the source programs or any part thereof from the object programs or from other information made available under this Agreement.

  • License for Use of Software and Other Intellectual Property Unless expressly prohibited by the licensor thereof or any provision of applicable law, if any, the Borrower hereby grants to the Administrative Agent on behalf of the Secured Parties a limited license to use, without charge, the Borrower’s and the Servicer’s computer programs, software, printouts and other computer materials, technical knowledge or processes, data bases, materials, trademarks, registered trademarks, trademark applications, service marks, registered service marks, service xxxx applications, patents, patent applications, trade names, rights of use of any name, labels, fictitious names, inventions, designs, trade secrets, goodwill, registrations, copyrights, copyright applications, permits, licenses, franchises, customer lists, credit files, correspondence, and advertising materials or any property of a similar nature, as it pertains to the Borrower Collateral, or any rights to any of the foregoing, only as reasonably required in connection with the collection of the Transferred Receivables and the advertising for sale, and selling any of the Borrower Collateral, or exercising of any other remedies hereto, and the Borrower agrees that its rights under all licenses and franchise agreements shall inure to the Administrative Agent’s benefit (on behalf of the Secured Parties) for purposes of the license granted herein. Except upon the occurrence and during the continuation of a Termination Event, the Administrative Agent and the Lenders agree not to use any such license without giving the Borrower prior written notice.

  • Information Systems Acquisition Development and Maintenance Security of System Files. To protect City Information Processing Systems and system files containing information, Service Provider will ensure that access to source code is restricted to authorized users whose specific job function necessitates such access.

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Updates “Updates” are changes that do not require a change to the established Centralized Contract terms and conditions. Updates may include: Centralized Contract changes and updates made in accordance with the previously approved pricing formula (e.g. discount from list price); adding new products or services within the established, previously approved pricing structure; lowering pricing of products or services already on Contract, deleting products or services available through the Centralized Contract, adding product or service that do not fall under the previously established price structure or discounts under the Contract, re-bundled products, and other updates not listed above that are deemed to be in the best interest of the State and do not result in a change to the established Centralized Contract terms and conditions. Updates must be submitted to OGS for review, and must be accompanied by a justification of reasonableness of price if the change results in a change in pricing methodology. OGS will notify Contractor in writing if approved.

  • Software Licenses Seller has all necessary licenses to use all material third-party software used in connection with the Purchased Assets, and to Sellers’ knowledge, Sellers’ use of third-party software does not infringe the rights of any Person or Entity.

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

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