OPERATING SYSTEM PATCHING Sample Clauses

OPERATING SYSTEM PATCHING. This feature includes the scheduled application of vendor recommended patches to the base Operating System on an “as-needed” basis. If patches are classified urgent by vendor due to a security risk; or if Customer requests that a patch be classified urgent then LightEdge will perform an emergency patch during next scheduled Emergency Maintenance window. LightEdge will not apply 3rd party patches to Operating System, patches to applications, patches to software or software library patches as part of this Service. If patching performed during previously agreed upon custom patching schedule and if Customer has agreed upon reboots after patching then LightEdge shall reboot Device without any further notification to Customer. If patching performed outside of a Scheduled Maintenance window requires a reboot of Customer Device then LightEdge will make a reasonable effort to contact Customer. If Customer cannot be reached after such reasonable effort then LightEdge reserves the right to reboot Customer Device without further notification. Any outage caused by application of operating system patches performed as part of this feature shall not be grounds for any SLA credit. Customer agrees to not hold LightEdge responsible for any unanticipated side effects or issues caused by this feature. Customer is responsible for checking status of Device and applications after such patches are applied. Upon discovery by Customer of any abnormality LightEdge will provide assistance in backing out any such patches. LightEdge will not be held responsible if patches cannot be backed out or if Customer Device cannot reasonably be returned to a pre-patch state. Customer has the option to “opt-out” or “opt-in” this particular feature at any time.
Sample 1Sample 2
AutoNDA by SimpleDocs
OPERATING SYSTEM PATCHING. When software vulnerabilities are revealed and addressed by a vendor patch, Opus obtains the patches from the vendor and categorizes the urgency of application as either "critical" or "non- critical" in nature. The determination of the critical/non-critical nature of patches is solely at the discretion of Opus, and Opus shall have no liability with respect to such determination. Opus will conduct testing for patches in its lab and on its internal production environment. Patches will be applied after they have been approved and qualified by Opus technicians. Non-critical patches are typically applied on a monthly basis whereas critical patches are applied on an `as needed' basis. Opus will apply any vendor supplied patch to supported software within one (1) business day of receiving a written request from Customer. Patches will be applied with the understanding that the patch has not been fully tested by Opus, and no guarantees are made by Opus as to the outcome of application of such patches. Opus will only apply vendor supplied and vendor supported patches. Customer will be notified via support ticket prior to the application of patches, unless agreed to otherwise.
Sample 1Sample 2
OPERATING SYSTEM PATCHING ilicomm will provide a patching service as part of its Fully Managed service unless otherwise stated on the Order Form or ilicomm has received a specific request from the Customer in writing or via the ilicomm ticketing system. Where the Customer has agreed for ilicomm to proactively apply patches these will be applied outside of Normal Business Hours unless the Customer requests for these to be schedule within Normal Business Hours. In the event that we become aware of critical updates, we will contact the Customer to arrange the earliest opportunity to apply these patches which is convenient to the Customer.
Sample 1Sample 2

Related to OPERATING SYSTEM PATCHING

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • System Upgrades The Connecting Transmission Owner shall procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement. To the extent that design work is necessary in addition to that already accomplished in the Class Year Interconnection Facilities Study for the Interconnection Customer, the Connecting Transmission Owner shall perform or cause to be performed such work. If all the Parties agree, the Interconnection Customer may construct System Upgrade Facilities and System Deliverability Upgrades. 5.2.1 As described in Section 32.3.5.3 of the SGIP in Attachment Z of the ISO OATT, the responsibility of the Interconnection Customer for the cost of the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement shall be determined in accordance with Attachment S of the ISO OATT, as required by Section 32.3.5.3.2

  • Review Systems The Asset Representations Reviewer will maintain and utilize an electronic case management system to manage the Tests and provide systematic control over each step in the Review process and ensure consistency and repeatability among the Tests.

  • Metering The Interconnection Customer shall be responsible for the Connecting Transmission Owner’s reasonable and necessary cost for the purchase, installation, operation, maintenance, testing, repair, and replacement of metering and data acquisition equipment specified in Attachments 2 and 3 of this Agreement. The Interconnection Customer’s metering (and data acquisition, as required) equipment shall conform to applicable industry rules and Operating Requirements.

  • Infrastructure Infrastructure serves as the foundation and building blocks of an integrated IT solution. It is the hardware which supports Application Services (C.3.2) and IT Management Services (C.3.3); the software and services which enable that hardware to function; and the hardware, software, and services which allow for secure communication and interoperability between all business and application service components. Infrastructure services facilitate the development and maintenance of critical IT infrastructures required to support Federal government business operations. This section includes the technical framework components that make up integrated IT solutions. One or any combination of these components may be used to deliver IT solutions intended to perform a wide array of functions which allow agencies to deliver services to their customers (or users), whether internal or external, in an efficient and effective manner. Infrastructure includes hardware, software, licensing, technical support, and warranty services from third party sources, as well as technological refreshment and enhancements for that hardware and software. This section is aligned with the FEA/DoDEA Technical Reference Model (TRM) which describes these components using a vocabulary that is common throughout the entire Federal government. A detailed review of the TRM is provided in Section J, Attachment 5. Infrastructure includes complete life cycle support for all hardware, software, and services represented above, including planning, analysis, research and development, design, development, integration and testing, implementation, operations and maintenance, information assurance, and final disposition of these components. The services also include administration and help desk functions necessary to support the IT infrastructure (e.g., desktop support, network administration). Infrastructure components of an integrated IT solution can be categorized as follows:

  • System Maintenance The Trust understands that USBFS will perform periodic maintenance to the System(s), which may cause temporary service interruptions. To the extent possible, USBFS shall notify the Trust of all planned outages and will perform any necessary maintenance during non-business hours.

  • Construction Services 4,500 thousand SDR for Japan Post in Group A 15,000 thousand SDR for all other entities in Group A 4,500 thousand SDR for entities in Group B Architectural, engineering and other technical services covered by this Agreement: 450 thousand SDR

  • Developer Attachment Facilities Developer shall design, procure, construct, install, own and/or control the Developer Attachment Facilities described in Appendix A hereto, at its sole expense.

  • Installation, Maintenance, Testing and Repair Unless otherwise agreed in writing by the Parties, to the extent required by Applicable Law, Interconnection provided by a Party shall be equal in quality to that provided by such Party to itself, any subsidiary, affiliates or third party. If either Party is unable to fulfill its obligations under this Section 14.2, it shall notify the other Party of its inability to do so and will negotiate alternative intervals in good faith. The Parties agree that to the extent required by Applicable Law, the standards to be used by a Party for isolating and clearing any disconnections and/or other outages or troubles shall be at parity with standards used by such Party with respect to itself, any subsidiary, affiliate or third party.

  • Evaluation Software If the Software is an evaluation version or is provided to You for evaluation purposes, then, unless otherwise approved in writing by an authorized representative of Licensor, Your license to use the Software is limited solely for internal evaluation purposes in non-production use and in accordance with the terms of the evaluation offering under which You received the Software, and expires 90 days from installation (or such other period as may be indicated within the Software). Upon expiration of the evaluation period, You must discontinue use of the Software, return to an original state any actions performed by the Software, and delete the Software entirely from Your system and You may not download the Software again unless approved in writing by an authorized representative of Licensor. The Software may contain an automatic disabling mechanism that prevents its use after a certain period of time. RESTRICTIONS

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