Red Hat Directory Server Use Cases Subscription Services are provided for Red Hat Directory Server only when used for its supported Use Case in accordance with the terms of this Exhibit and Table 3.1 below.
Supplier Diversity Seller shall comply with Xxxxx’s Supplier Diversity Program in accordance with Appendix V.
Reverse ADSL Loops If a CLEC’s ADSL Transmission Unit (including those integrated into DSLAMs) is attached to Sprint’s Network and if an ADSL Copper Loop should start at an outside location, and is looped through a host or remote, and then to the subscriber, the copper plant from the outside location to the Sprint host or remote central office must be a facility dedicated to ADSL transmission only and not part of Sprint’s regular feeder or distribution plant.
SAFECOM Recipients receiving federal financial assistance awards made under programs that provide emergency communication equipment and its related activities must comply with the SAFECOM Guidance for Emergency Communication Grants, including provisions on technical standards that ensure and enhance interoperable communications.
Verizon OSS Information 8.5.1 Subject to the provisions of this Section 8, in accordance with, but only to the extent required by, Applicable Law, Verizon grants to CBB a non-exclusive license to use Verizon OSS Information.
Red Hat Enterprise Linux Server Add-Ons Red Hat Enterprise Linux Server Subscriptions may be purchased with one or more add-on options (“Add-On(s)”). Add-Ons require a separate paid and active Software Subscriptions for each Unit that deploys, installs, uses or executes such Add-On. Each Unit of Add- Ons must match the Support Level (Standard and/or Premium), Unit of Measure and capacity as the underlying Red Hat Enterprise Linux Unit. Add-Ons are not supported on Red Hat Enterprise Linux Subscriptions with a Self-support service level except Smart Management Add-Ons. The Add-Ons include: High Availability, Load Balancer, Resilient Storage, Scalable File System, Smart Management, Extended Update Support, Extended Life Cycle Support and High Performance Network.
Return of University Records Contractor agrees that within thirty (30) days after the expiration or termination of this Agreement, for any reason, all University Records created or received from or on behalf of University will be (1) returned to University, with no copies retained by Contractor; or (2) if return is not feasible, destroyed. Twenty (20) days before destruction of any University Records, Contractor will provide University with written notice of Contractor’s intent to destroy University Records. Within five (5) days after destruction, Contractor will confirm to University in writing the destruction of University Records.
Teaching Staff Assigned to More Than One Building Each Educator who is assigned to more than one building will be evaluated by the appropriate administrator where the individual is assigned most of the time. The principal of each building in which the Educator serves must review and sign the evaluation, and may add written comments. In cases where there is no predominate assignment, the superintendent will determine who the primary evaluator will be.
Independent Monitors 8.1 The BUYER has appointed Independent Monitors (hereinafter referred to as Monitors) for this Pact in consultation with the Central Vigilance to as Monitors) for this Pact in consultation with the Central Vigilance Commission (Names and Addresses of the Monitors to be given).
DNS name server availability Refers to the ability of a public-‐DNS registered “IP address” of a particular name server listed as authoritative for a domain name, to answer DNS queries from an Internet user. All the public DNS-‐registered “IP address” of all name servers of the domain name being monitored shall be tested individually. If 51% or more of the DNS testing probes get undefined/unanswered results from “DNS tests” to a name server “IP address” during a given time, the name server “IP address” will be considered unavailable.
