How can we help? 👋

Hardware Tags

Hardware Tags Explaination

XEOX System Tags

Automatically, following tags will be assigned to each hardware:

  • Hardware Class

e.g. Notebook, Desktop, Server

  • Operation System

e.g. Windows10, Windows2016

  • Site

For each of your sites a tag will be created automatically.

  • Windows 10 Subversion

e.g. W10_1709, W10_1909, ...

  • Windows Features
    • Active Directory Domain Service for Domain Controllers
    • DHCP Server
    • DNS Server (on Domain Controllers)
    • Print Server
    • ...
  • Architecture
    • x64 for 64 Bit AMD/Intel

Agent Behavior

  • Websockets

If you assign the tag WEBSOCKET to a Windows Client (Desktop or Notebook), the Agent on the machine will use a Websocket connection for a faster response. Server Operating systems are using Websockets automatically. Websockets are also enabled by default for small customers with fewer than 10 devices.

In case of Websockets the agent is responding to jobs immediately (few seconds). Otherwise, you have to wait up to 15 minutes for a hardware to begin with a job.

NoWebsocket disables websockets.

For changes at the websocket behavior a service restart on the Windows machine is required. This can be done in Windows Service Manager or with a job / action "Agent restart"

  • DebugAgent

With the tag DebugAgent requests between server and agent are logged and stored on the device.

  • 24x7

This is a very simple solution for a base monitoring.

XEOX is checking the heartbeats of devices with the 24x7 tag. If an Agent isn't sending heartbeats for longer than a few minutes, an e-mail would be sent.

In case of network problems (e.g. firewall down, Internet Provider problem, ...) or a Hardware reboot after update no e-mail would be sent to prevent spamming you with useless e-mails.

To receive Alerts please subscribe to OTHER / Notification Mail for 24/7 Tag.

Custom Tags:

Feel free to order / group your hardware with custom tags. Tags can also be used for jobs, for example, to group a list of devices with a tag and create a job for that group.

Did this answer your question?