Brug på server Sample Clauses

Brug på server. Du må installere softwaren på en xxxxx flere filservere i dit interne netværk, men kun til brug for den software, der initieres fra en computer inden for det samme interne netværk, som tilladt ifølge afsnit 2.2. Det samlede xxxxx xxxxxxx (ikke antallet af samtidige brugere), der er i stand til at bruge softwaren på en sådan/sådanne computer-filserver(e), må ikke overstige det tilladte antal. For eksempel giver ovenstående dig hverken installationstilladelse xxxxx adgang (direkte xxxxx via kommandoer, data xxxxx instruktioner) til softwaren (a) xxx xxxxx til en computer, der ikke indgår i dit interne netværk, (b) til at aktivere webhostede arbejdsgrupper xxxxx offentligt tilgængelige tjenester, (c) for personer xxxxx kollektive enheder til at bruge, downloade, kopiere xxxxx på anden vis drage fordel af softwarens funktionalitet, medmindre de har licens fra Adobe, (d) som komponent i et system, en arbejdsgang xxxxx en tjeneste, der er tilgængelig for flere end det tilladte xxxxx xxxxxxx, xxxxx (e) til opgaver, der ikke initieres af en individuel bruger (f.eks. automatisk serverbearbejdning).
AutoNDA by SimpleDocs

Related to Brug på server

  • 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.

  • Server Use This agreement does not permit you to install or Use the Software on a computer file server. For information on Use of Software on a computer file server please refer to xxxx://xxx.xxxxx.xxx/go/acrobat_distribute for information about Adobe Reader; or xxxx://xxx.xxxxx.xxx/go/licensing for information about the Adobe Runtimes.

  • Servers Marco backs up the following servers only: Windows Servers, SQL servers, Exchange server, and Virtual Machines images running VMWare or Hyper V.

  • Server Software Subject to the terms and conditions of this XXXX, Vocera grants you the non-exclusive right to (i) install and run (“Use”) the Server Software on computer systems (each, a “Server Computer”) located at End User’s Facilities in the geographic territory designated above (“Territory”); (ii) to Use the Client Software in conjunction with Authorized Client Devices and such Server Computers; and (iii) for pilot licenses for certain Software provided on a trial basis, use such Software for the limited term specified by Vocera in writing. You may Use the standard Server Software on one primary Server Computer (or a primary cluster of computers suitably configured for productive use of the Server Software). You may install backup copies of the Server Software on backup Server Computers to provide redundancy in the event of failure of the primary Server Computer(s) but, unless you have acquired additional licenses or a failover license from Vocera, you may not run such backup or additional copies concurrently with the primary copies. Vocera grants you the right to use the applicable License Key issued by Vocera only to enable Use of the Server Software in conjunction with the licensed Server Computers. Server Software may be licensed for a Subscription Term as specified in the Quote.

  • 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.

  • 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.

  • Web Hosting If Customer submits a Service Order(s) for web hosting services, the following terms shall also apply:

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.

  • Directory Listing and Directory Distribution 41 5. Voice Information Service Traffic 43 6. Intercept and Referral Announcements 44 7. Originating Line Number Screening (OLNS) 44 8. Operations Support Systems (OSS) Services 44 9. Poles, Ducts, Conduits and Xxxxxx-xx-Xxx 00 00. Telephone Numbers 51 11. Routing for Operator Services and Directory Assistance Traffic 51 12. Unauthorized Carrier Change Charges 52 13. Good Faith Performance 52 INTERCONNECTION ATTACHMENT. 53 1. General 53 2. Points of Interconnection and Trunk Types 53 3. Alternative Interconnection Arrangements 57 4. Initiating Interconnection 58 5. Transmission and Routing of Telephone Exchange Service Traffic 59

  • Digital Health The HSP agrees to:

Time is Money Join Law Insider Premium to draft better contracts faster.