Appearance
Endpoints
Endpoints are devices managed by Ordyn.
Endpoints are devices that run the Ordyn agent or are enrolled into Ordyn through another service client.
Endpoint States
| State | What it means |
|---|---|
| Staged | A prepared record awaiting enrollment. |
| Pending approval | Enrollment succeeded and an operator must approve management. |
| Approved | The endpoint can participate in management within its licensed capacity. |
| Suspended | Management is temporarily blocked while identity and history are preserved. |
| Revoked | The current identity is permanently invalidated. |
Use Endpoint Operator to manage lifecycle state. Resume management restores a suspended endpoint. A revoked endpoint must enroll again.
Endpoint certificate renewal
Connected approved Agents request renewal automatically when their certificate is within 240 days of expiry. Use Renew certificate for planned certificate replacement or a move to another compatible authority and Edge host.
For damaged credentials, follow Agent repair.
Revoke vs delete
Revoke an endpoint to remove trust while retaining its record and history. Delete it when the record should be removed. Use suspension for a temporary management block.
Busy endpoints
Select Busy or the endpoint's connection status, such as Connected or Disconnected, to inspect current and waiting work. Needs attention means the execution outcome is uncertain. Work that does not delay other tasks is available under Other work, including when the endpoint is not busy.
Use Cancel execution beside the affected work. For a running execution that supports cancellation, Ordyn requests a stop from the agent. A cancellation acknowledgement means the request was accepted; confirmation that execution stopped clears the wait.
For unresolved work, the confirmation offers to clear the server wait, including while the endpoint is offline. This recovery does not require the endpoint to reconnect. It leaves the execution outcome unknown and closes the associated job for this endpoint or configuration profile run when shown in the confirmation. Completed job history is preserved. Other work can proceed when the endpoint is available; any execution still running on the device may overlap.
Endpoint Operator can cancel standalone work, including alert checks. Job and configuration profile recovery use their existing access requirements.
Force abort target is a separate recovery action for cancelling jobs. It clears the job's server-side state and does not guarantee that execution has stopped on the device.
Switch endpoints
Switch endpoints are SNMP-managed network switches.
They are created manually with kind switch, a hostname or management IP, an assigned SNMP service client, an assigned SNMP credential profile, and any optional global SNMP collection profiles. The hostname is the SNMP management address.
Switches do not enroll, do not have endpoint certificates, and do not establish edge connections. Their connected state comes from the assigned SNMP service client, and their active state comes from recent successful switch system status collection.
See SNMP for service-client setup, credential profiles, switch port inventory, interface traffic monitoring, endpoint-to-port mapping, and SNMP trap triggers.
Printer endpoints
Printer endpoints are SNMP-managed printers.
They are created manually with kind printer, a hostname or management IP, an assigned SNMP service client, an assigned SNMP credential profile, and any optional global SNMP collection profiles. The hostname is the SNMP management address.
Printers do not enroll, do not have endpoint certificates, and do not establish edge connections. Their connected state comes from the assigned SNMP service client, and their active state comes from recent successful printer system status collection.
See Printer Endpoints for setup, collected facts, automatic refresh behavior, job support, and limitations.
Telematik endpoints
Manage Konnektors and card terminals through the Telematik service. Use the Konnektor overview and Card Terminals tab to inspect inventory and linked terminal endpoints. For a job that verifies a card's PIN, follow SMC-B verification.
Net node routing and network interfaces
Endpoints can have a net node, which is responsible for direct network interaction with the endpoint, such as PXE boot, Wake-on-LAN, or ICMP requests.
The effective net node is resolved in this order:
- direct endpoint assignment
- inherited folder assignment
- inherited tenant assignment
Use Service routing from an endpoint's action menu and select the Net Node tab to set or clear a direct endpoint assignment. Folder and tenant assignments are managed from the same slideover on the corresponding folder or tenant views.
The endpoint overview shows the effective net node with its assignment source.
Host network interfaces are the shared source for Wake-on-LAN, PXE matching, IPAM observations, switch-port matching, and net-node reachability probes.
Agent endpoint interfaces may be MAC-only, IP-only, or contain both values. MAC-only interfaces are useful for Wake-on-LAN and PXE matching. Net-node probes require an IP address.
When interface data changes, Ordyn refreshes IPAM observations, switch-port matching, PXE configuration, and the assigned net node configuration as needed.
Supported AMT endpoints also have an Intel AMT interface in this section. It stores the IPv4 address used for out-of-band AMT connections and appears in IPAM. Use AMT Administrator to correct its management IPv4 address when needed.
Browsing files
Open an endpoint's Filesystem tab to browse files and folders. The Windows drive list can be out of date; enter a known full path if the drive you need is not listed.
Editing endpoints
Use Edit endpoint for the device's operational identity and infrastructure roles. A display name helps operators recognize the device without changing its hostname.
Infrastructure roles
Mark hosts that run Ordyn itself so maintenance can allow for the resulting interruption. Select Ordyn server host for the server, Ordyn edge host with its hosted Edge service, or Ordyn hypervisor host with the infrastructure endpoints it hosts.
Collectors
Use Collectors for custom inventory values.
Configuration Profiles
Use Configuration Profiles to audit or enforce device settings.
Windows Firewall Rules
Manage local rule policies through the Firewall view.
Docker
Use Docker Inventory to investigate and operate Linux containers.
Microsoft Hyper-V VMs
Use Hyper-V management for host inventory, VM actions, and consoles.
Intel AMT
Use Intel AMT for supported hardware management while Windows is offline.
Powering on endpoints
Use Power on for one or more endpoints. Resolve any reported requirements before retrying an unavailable device.
Automatic uses Hyper-V for identified virtual machines and prefers Intel AMT for physical endpoints, with Wake on LAN as a fallback. Choosing a specific method uses only that method.
Power on requires configured Intel AMT, a connected manageable Hyper-V host, or an assigned connected net node and the endpoint's MAC address for Wake on LAN. Use the role required by the selected management method; see Access Control.
The audit log and endpoint history record power-on requests and the methods attempted. A successful request does not guarantee that the endpoint is online.
To power on endpoints as part of a job, use the Power on endpoint step or Power on endpoints before running.