Configuration requise ; identifiant Sample Clauses

Configuration requise ; identifiant. Apple Soyez attentif au fait que le Logiciel Apple est pris en charge uniquement par le matériel de marque Apple possédant la configuration requise spécifiée comme indiqué par Apple. En outre, l’utilisation et l’accès à certaines fonctionnalités du Logiciel Apple et certains services (tel que défini dans la section 5) peut nécessiter l’obtention d’une combinaison unique d’un nom d’utilisateur et d’un mot de passe, connue sous le nom d’identifiant Apple.
AutoNDA by SimpleDocs
Configuration requise ; identifiant. Apple Soyez attentif au fait que le logiciel Apple est pris en charge uniquement par le matériel de marque Apple possédant la configuration requise spécifiée comme indiqué par Apple. En outre, l’utilisation et l’accès à certaines fonctionnalités du logiciel Apple et certains services (tel que défini dans la section 5) peut nécessiter l’obtention d’une combinaison unique d’un nom d’utilisateur et d’un mot de passe, connue sous le nom d’identifiant Apple.

Related to Configuration requise ; identifiant

  • Encryption Requirements DST will not locally store Fund Data on any laptops or mobile devices (e.g., Blackberries, PDAs) managed by DST.

  • Installation requirements We (if we install the System) or our contractor (if we procure a contractor to install the System) must:

  • Information Requirement The successful bidder's shall be required to advise the Office of Management and Budget, Government Support Services of the gross amount of purchases made as a result of the contract.

  • Contracting Information Requirements Contractor represents and warrants that it will comply with the requirements of Section 552.372(a) of the Texas Government Code. Except as provided by Section 552.374(c) of the Texas Government Code, the requirements of Subchapter J (Additional Provisions Related to Contracting Information), Chapter 552 of the Government Code, may apply to the Contract and the Contractor agrees that the Contract can be terminated if the Contractor knowingly or intentionally fails to comply with a requirement of that subchapter.

  • Information Requirements The Company covenants that, if at any time before the end of the Effectiveness Period the Company is not subject to the reporting requirements of the Exchange Act, it will cooperate with any Holder and take such further reasonable action as any Holder may reasonably request in writing (including, without limitation, making such reasonable representations as any such Holder may reasonably request), all to the extent required from time to time to enable such Holder to sell Registrable Securities without registration under the Securities Act within the limitation of the exemptions provided by Rule 144 and Rule 144A under the Securities Act and customarily taken in connection with sales pursuant to such exemptions. Upon the written request of any Holder, the Company shall deliver to such Holder a written statement as to whether it has complied with such filing requirements, unless such a statement has been included in the Company’s most recent report filed pursuant to Section 13 or Section 15(d) of Exchange Act. Notwithstanding the foregoing, nothing in this Section 7 shall be deemed to require the Company to register any of its securities (other than the Common Stock) under any section of the Exchange Act.

  • Documentation Required The certificates and endorsements shall be received and approved by the District before Work commences. As an alternative, the Contractor may submit certified copies of any policy that includes the required endorsement language set forth herein.

  • Data Location 1.1. The CONTRACTOR shall not store or transfer non-public COUNTY data outside of the United States. This includes backup data and Disaster Recovery locations. The CONTRACTOR will permit its personnel and contractors to access COUNTY data remotely only as required to provide technical support. (Remote access to data from outside the continental United States is prohibited unless approved in advance and in writing by the County.) 1.2. The CONTRACTOR must notify the COUNTY in advance and in writing of any location changes to CONTRACTOR’s data center(s) that will process or store County data.

  • Information Required The report must include, at a minimum, the name, category, description, expected outcomes, anticipated CCBF contribution, anticipated start date, and anticipated end date of each active Eligible Project.

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

  • Documentation Requirements ODM shall pay the MCP after it receives sufficient documentation, as determined by ODM, detailing the MCP’s Ohio Medicaid-specific liability for the Annual Fee. The MCP shall provide documentation that includes the following: 1. Total premiums reported on IRS Form 8963;

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