Versions Compared

Old Version 6

changes.mady.by.user Unknown User (iang)

Saved on

compared with

New Version Current

changes.mady.by.user publisher

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Method

UnquarantineDevice

ModuleSecurity
LibrarySecurity
Action


Excerpt
Allows devices to communicate with devices other than the Tachyon Switch and Background channel servers.
This is intended to be used after QuarantineDevice.

Changes made to routing tables, the hosts file, or IPv6 bindings during quarantine will be lost, as the agent will attempt to revert modifications it made back to a pre-quarantine state.

Warning

Ensure you understand the impact of using the Quarantine feature.

The quarantine methods are not suitable for use from TIMS (Tachyon Instruction Management Studio), mainly because of what they do (cut off the device from most connections) but also because no Tachyon Switch is involved with TIMS.


Parameters

(none)Reboot (bool, optional, default false): Reboot the device after Unquarantine. New in v8.0

Return values

Status (string): The quarantine status. If the response is a success, this will be NotQuarantined.

Note
If the device was already not in a quarantined state, the action is successful but nothing is returned ("success no content").


Example


Code Block
Security.UnquarantineDevice();

Security.UnquarantineDevice(Reboot: true);


Platforms
  • Windows
Notes
  • This is not available on Windows XP.
  • Quarantine requires working persistent storage.
    • If persistent storage is removed or corrupted during quarantine, the agent will be unable to revert to an unmodified state.
  • Upgrading the agent whilst under quarantine is not supported or reccommendedrecommended.
  • Rebooting device after Unquarantine operation can solve localhost connection issues