There are cases that already allocated Instance Tree has to be changed. Some Software Releases are able to change the Instance Tree, but for cases when they do not or when root Software Instance has to be changed Operator has to take proper actions.
The typical use cases for those actions are:
Locate the Instance Tree directly or navigate to it from Operator Assigned Support Request.
Check carefully the whole Instance Tree, and find the Software Instance to work on. Remember, that in some cases, for example in case of resilient main instance (but not resilient root instance) access to data will be lost, whereas data will stay until cleanup phase.
If possible, ask the user to create new Instance Tree and migrate data by himself.
Before moving the instance check that there is no SLA which would confilict with the desired state, like for example that runner1 of resilient webrunner is set on given computer, or that SLA for the Instance Tree puts root Software Instance on given computer. In such case coordinate changes with the user, so that new instance will be requested eslewhere.
Navigate to the Software Instance in question.
Check again that it's the exact instance to be moved.
In the classic UI select action Rename and Request Stop. Read carefully the information and if you're sure click Rename and Request Stop button. You'll see that Software Instance title and software release are changed and that it became Stop Requested.
After some time the new instance will be automatically re-requested and the Instance Tree will restabilise.
There is no need to do more actions on this instance, as if it is in stopped state, it is not going to be processed, but still the data will be there.
In case if cleanup is needed, like that the already moved instance is on a decommissioned computer, you can find back the instance and execute action Rename and Request Destroy. Do the action with care, and before executing read carefully and understand the consequences.