Deactivation only needs half the process. Namely, there's only the request (which you put on the server).
Offline deactivation process
garyoFor offline activation, you do this: TA_ActivateRequestToFile(): saves req to file TA_ActivateFromFile(): activates using response fileBut for offline _de_activation, I only see TA_DeactivationRequestToFile(). I can't find TA_DeactivateFromFile() which would be the second half of the protocol.
If this is in sample code somewhere, perhaps I missed it.