Confirm what hardware you actually received
Open Hardware for your server and compare the processor, memory, local storage, BIOS/UEFI version and model-specific capabilities against what you ordered and what your workload needs. Keep a note of the hostname together with these hardware facts - you'll want it on hand if you ever need to open a support request.
Reporting a suspected hardware fault
Use Hardware replacement to describe exactly what you're observing and which component you suspect. Keep the server reachable through a working management route if you can, gather the relevant timestamps from Activity before you report the issue, and avoid opening the chassis or changing firmware yourself while a diagnostic is in progress - that can make the fault harder to pin down.
Keeping multiple servers organised with Tags
Open Tags to add your own key/value labels - environment, role, maintenance owner, whatever makes sense for your setup. Tags are purely organisational: they make it much easier to tell similar servers apart in the selector and in your operation history, but they never change the server's actual configuration or who can access it.
Before changing firmware or a hardware capability
Check that your operating system supports the change, take a verified backup, and schedule it for a proper maintenance window rather than doing it live. Some firmware settings and processor capabilities affect how the server boots or whether it stays reachable, so double-check you have the right server selected and a recovery path ready before applying anything high-impact.
