Skip to main content

interact

Description

Sets the target device for command line interactions to a specified ResourceID. This setting must be configured prior to any remote enumeration or script execution.

Usage

Example

In the below example, the dp device is queried. In the result the 16777221 is returned. The operator can now interact with that device and configure the command line.
Notice how the command prompt changes from () (C:\) >> to (16777221) (C:\) >> after setting the target device. This indicates that you are now targeting the device with ResourceID 16777221.

Finding ResourceIDs

You can find ResourceIDs using several methods:

Using get_device

Query a specific device by hostname to get its ResourceID:

Using get_lastlogon

Find devices where a specific user last logged on:

Using get_puser

Find devices where a user is configured as the primary user:

Using get_collection

List all devices in a collection:

exit

Description

Exit the admin console and return to the command line.

Usage

Example

The exit command terminates the admin shell session and returns you to your local command line. Any active target device interactions will be closed.

Command Flow

Here’s the typical workflow for using the admin module:
  1. Start the admin module with appropriate credentials
  2. Query for devices using database commands like get_device, get_lastlogon, or get_collection
  3. Set target device using interact [ResourceID]
  4. Execute commands on the target device using situational awareness or administrative commands
  5. Exit when finished using the exit command

Example Workflow

Some commands require an active target device interaction to function properly. Make sure to use the interact command with a valid ResourceID before attempting to run situational awareness commands or execute scripts.