XRecovery can be used on a Windows computer that remains offline. Activation uses two computers and the supplied offline activation tool: computer A has internet access, while computer B is the offline machine where XRecovery will run.
Prepare both computers
Install the supplied activation tool as documented on both computers. Confirm that computer B has the correct system date and time. Prepare removable media that you can use to exchange the request and response files between A and B.
Keep the activation code private. Scan the transfer media according to your organization’s security process before moving it between network zones.
Export the request from offline computer B
Run the offline activation tool on computer B with administrator rights when required. Choose the option to obtain the offline credential and save the machine request file. The existing tool uses a request file named `fingerprint.req`.
Copy that request file to the transfer media. Computer B does not need an internet connection for this step.
Generate the response on online computer A
Move the request file to computer A. Open the supplied tool, import the fingerprint request, enter the activation code, and generate the offline activation response. The existing workflow produces a license response named `license.token`.
Copy the response file to the transfer media. Do not edit or rename its contents.
Apply the response on computer B
Return the response file to computer B. Open the activation tool, import `license.token`, and use the verify-and-apply action. After a successful application, XRecovery on B can remain offline.
Troubleshooting
If the response is rejected, first check the date and time on computer B and confirm that the response was generated from that computer’s current request. If the tool cannot write a temporary file, close it and rerun it with administrator rights. Preserve the original request, response, activation code, and error text while contacting support.
Offline activation does not remove the need to exchange metadata between A and B. It allows B itself to remain disconnected while A performs the internet-dependent part of the workflow.