Scribd Logo
Upload

Welcome to Scribd!

  • Tiger

    Uploaded by

    Kota Rajesh
    1 views4 pages

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pptx, pdf, or txt
    1 views4 pages

    Tiger

    Uploaded by

    Kota Rajesh

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pptx, pdf, or txt
    of 4

    TIGERS

    By Samuel and Valentin

    Sensitivity: Internal
    Some facts about Tigers
    • Scientific name for a Tiger is ”Panthera Tigris”

    Sensitivity: Internal
    Sensitivity: Internal
    Successful ServiceNow Upgrades with - Prepare, Plan and Execute
    Day Day Day Day
    0 1 2 3

    Prepare and Plan! Upgrade Dev Instance Upgrade UAT Instance Upgrade Production Instance

    Deploy the changes that are ready for Clone completed from “prod” instance Clone completed from “prod” instance
    production and apply production to “dev” instance to “UAT” instance
    freeze Prod instance Upgrade completed.
    (Review your prod instance ServiceNow (consider ServiceNow backup schedule
    (latest changes deployed then will be cloned backup schedule to include latest
    (Planned and Scheduled on Day 0)
    for your prod instance to include latest
    to lower instances as well) deployments) deployments)
    Inform developers to backup their
    remaining development work in dev Lock users automatically using post Lock users automatically using post 1. Check skipped records count
    instance (if required) clone scripts. Remember to check mid clone scripts. Remember to check mid 2. Retrieve the captured skipped
    server status after clone server status after clone record updatesets from UAT after
    Decide on latest patch release and go successful upgrade.
    through upgrade release notes Schedule upgrade in dev instance Schedule upgrade in UAT instance 3. Review remaining skipped records,
    (ServiceNow recommends upgrade version (In hi portal) (In hi portal) if any
    during upgrade scheduling) (Count of skipped records mostly match)
    Review skipped records (due to
    Schedule production upgrade planned Retrieve the captured skipped record
    platform customizations) after
    on Day 3. updatesets from dev to UAT after Test your platform and portal.
    upgrade
    (In Hi Portal ServiceNow) (Remember to capture the skipped record upgrade. Review remaining skipped Remember to check midservers status
    updates in update set) records, if any after upgrade.
    (Count of skipped records mostly match due
    Send communication to change
    to same clone)
    managers/stakeholders on production Test your platform and open for
    upgrade schedule development activities
    Test your platform and portal. Open
    Upgrade completed successfully!
    Schedule clone from prod to dev Schedule clone from prod to UAT platform for users
    instance (For next day - Day 1) instance (For next day - Day 2)

    Sensitivity: Internal

    You might also like