Rehosting definition

Rehosting. The process of changing the computer on which a Node-locked or Floating license is installed is called Rehosting (this process does not apply to Dongle licenses, as the dongle can be used on any Windows-based computer). Perpetual Node-locked or Floating licenses are distributed in 12- month increments to allow users to change the computer on which the software product is installed during the renewal period (months 11 and 12 of the 12-month perpetual license increment). For perpetual licenses, no fees are charged to renew a license on the same computer. Additionally for perpetual licenses, no fees are charged to change the computer on which the software product is installed during the renewal period (months 11 and 12 of the 12-month perpetual license increment), but if the request is made during months 1-10 after the initial license installation or following the end of the previous renewal period, a rehosting fee may apply. Rehosting is also available for subscription licenses, and no fees will be charged to change the computer on which the software product is installed at the end of the subscription period, although a rehosting fee may be charged if the request is made during the subscription period.
View Source

Examples of Rehosting in a sentence

  • A Personal License is not transferable from one computer to another without Re-hosting.

  • Unisys Rehosting Project Team DCS Security Officer, DSHS ISO, CTS- WaTech Security 12 Inventory List Eight weeks after SOW execution.

  • Unisys Rehosting Project Team, Sponsors and Steering Committee DSHS Project Manager 2 Deliverables Matrix Two weeks after SOW execution Contains the name of the deliverable, who reviews, days given for each step in the review cycle, acceptance criteria and who accepts.

  • Unisys Rehosting Project Team SSPS Technical Manager, DCS IT Chief, DCS Security Officer, Del Nbr Deliverable Due Acceptance Criteria Reviewer Approver IT Manager of Operational Services 13 Physical Design Nine weeks after SOW execution.

  • Unisys Rehosting Project Team DCS IT Chief, DCS Security Officer, SSPS Technical Manager, ET Operations, CTS-WaTech 16 System Test Cases Ten weeks after SOW execution Test Cases shall cover all use cases.

  • Unisys Rehosting Project Team DCS IT Chief, DCS Security Officer, SSPS Technical Manager, ET Operations Del Nbr Deliverable Due Acceptance Criteria Reviewer Approver 31 Full Services Acceptance Two weeks prior to go live.

  • Unisys Rehosting Project Team CTS-WaTech Security, DSHS ISO 14 Network Connectivity Nine weeks after SOW execution.

  • Unisys Rehosting Project Team DCS IT Chief, DCS Security Officer, SSPS Technical Manager, ET Operations Milestone 5: Services Go-Live 30 Customer Service for Pre- Go-Live Begins Two months prior to Go-Live Processes defined in the deliverables are in place, people have been identified, communication has been delivered and all documentation has been received.

  • Unisys Rehosting Project Team DCS IT Chief, DCS Security Officer, SSPS Technical Manager, ET Operations Milestone 2: Setup and Configuration 11 Logical Design Five weeks after SOW execution.

  • Unisys Rehosting Project Team DCS IT Chief, DCS Security Officer, SSPS Technical Manager, ET Operations 28 Readiness Checklist Acceptance Readiness checklist has been reviewed by vendor and DSHS, all items have been successfully completed Unisys Rehosting Project Team DCS IT Chief, DCS Security Officer, SSPS Technical Manager, ET Operations 29 Disaster Recovery Plan Includes all processes required for DR.