ASSET TRACKING

Global Asset Telemetry.

Active Directory natively lacks a fast, reliable way to show which specific workstation a user is currently logged into. This background engine silently sweeps the network to compile a master JSON database of active user-to-computer relationships.

SEE HOW IT WORKS
Telemetry Engine ● SCANNING

[UHDC] [1/3] Loading Database...

> [OK] Loaded 4,102 historical entries.

[UHDC] [2/3] Fetching Computer List from AD...

> [OK] Found 1,250 target workstations.

[UHDC] [14%] NEW: jsmith found on LAPTOP-US-4829

[UHDC] [28%] NEW: mscott found on DESKTOP-HQ-9912

[UHDC SUCCESS] Map Complete!

> Total DB Entries: 4,104 | New Connections: 2

Resilient Background Orchestration

Designed to run on a weekly schedule, this engine builds the intelligence framework that powers the rest of the UHDC. It is engineered for absolute data integrity, ensuring network drops or server reboots never corrupt your asset maps.

Strict LDAP Filtering

Optimizes scan times by utilizing strict LDAP filters. It explicitly targets active, enabled endpoints running Windows 10 or Windows 11, deliberately excluding servers and deprecated operating systems from the polling loop.

Additive Composite Keys

Utilizes a User-Computer composite key structure. This explicitly prevents a user who logs into a shared conference room PC from overwriting their primary laptop record in the database.

Atomic Auto-Saving

Executes an atomic save operation every 50 loops. It serializes the array to a .tmp file first, confirms the JSON payload is valid, and only then overwrites the live production file to prevent corruption.

INTERACTIVE TRAINING ENGINE
⭐ 300 XP

How Junior Techs Learn This Tool:

While the UHDC UI parses the background telemetry database automatically, a junior technician should know how to manually search the raw data if the graphical interface is unavailable. The training engine teaches them how to use the classic find command to instantly search the central JSON database from any command prompt to locate a user's active hardware.

type "\\server\UHDC$\Core\UserHistory.json" | find /i "jsmith"

The In-Person Equivalent

Walking the floor, going desk to desk, wiggling the mouse on every active computer, and writing down the username displayed on the Windows lock screen.

Technical Q&A

Q: What network ports are required for this engine to map the network?
This script is network-intensive. It requires Port 389/636 (LDAP/S) to query Active Directory for the computer list. It uses Port 5985 (WSMan/HTTP) to query WMI on the target endpoints for the logged-on user. Finally, it uses Port 445 (SMB) to read, backup, and save the central JSON database on the network share.
Q: What happens if the server hosting the script reboots halfway through scanning 2,000 computers?
The database will not corrupt. The script utilizes an atomic auto-save block. It writes the data in memory to a temporary file (.tmp), validates it, and then instantly swaps it with the live file. The most data we would ever lose from an unexpected termination is the last 49 endpoints scanned. Furthermore, an automatic .bak file is generated at the very start of the execution.
Q: Does this script overwrite existing records if a PC is offline?
No, the script runs in "Additive Mode." When it loads the existing database at the start, it pulls all historical records into memory. If a PC is offline and fails the ping check, the script simply skips it, but the historical record remains safely in the master array and is saved back to the disk.
Q: Why do we use a composite key (`User-Computer`) instead of just using the Username?
If we used just the Username, the database would only remember the last computer a user logged into. If a user has a desktop and a laptop, or occasionally logs into a shared kiosk, the composite key allows the database to store and track all of their active devices simultaneously for accurate AD lookups.