Asset Management is the hardware register: who has what, what is on the shelf, and what is broken. Open it from Tools, under Management.
Three ways to look at it
Switch with the tabs at the top:
- By users, what each person holds
- By assets, the full register
- Site, shared site equipment
Search across all of them with Search assets, tags, serial numbers…
Give somebody hardware
A user with no machine shows No computer has been assigned to this user yet. Depending on the ticket you will be offered Check out kit, Check out replacement, or a plain Assign Computer.
Check out kit is the day-one bundle for a new hire. The panel spells out what it contains: a laptop, a monitor, a keyboard, a mouse, and a headset.
A kit needs a laptop that has actually been built. With none available you get No laptop is set up yet. and Build one in Computer Deployment, then check out the kit. That is the correct order for onboarding tickets: build the machine, check out the kit, then ship it.
Check out replacement is the equivalent for swapping out a broken machine.
Take hardware back
Return device starts a return, and it appears on offboarding tickets, where the point is reclaiming kit from someone leaving. It needs a return label, and the app blocks you without one: Include a return label first — without one the device can’t ship back to IT.
The return label on a replacement computer is a separate rule enforced in Ship Manager, not here.
Check in takes an asset back off its holder and returns it to stock.
Register a PC you have built
Registering a finished machine puts it on the hardware register so it can be checked out to someone. You do not have to register a machine just to ship it: Ship Manager will post a unit straight off the shelf. Registration is what Check out kit and Check out replacement require.
- Open Asset Management.
- Choose the pending build under Choose which deployed PC to register.
- Set Device type (Desktop or Laptop) and a Status.
- Select Register asset.
The name comes from the build, not from you. If nothing is waiting you get No builds waiting for registration, with the explanation that machines land here once you finish a deployment including the baseline apps at the end. A build abandoned before that last stage never reaches the shelf.
Registration errors are specific:
| Message | Meaning |
|---|---|
| {name} is already in use by another asset. Only one device can carry that name. | Two machines cannot share a name. |
| The name must follow the SD convention, for example SD1042. | The build’s name is not in the company format. |
| No build is waiting to be registered. | Finish a deployment first. |
| This PC is already registered. | It is already on the register. |
| Pick who this PC is checked out to. | A checked-out status needs a holder. |
Statuses
Deployed, Ready to deploy, Needs to be imaged, Broken, Decommissioned and Lost.
Change one with Change status. There is an order rule on Deployed: Assign this asset to a user first, then mark it deployed. A deployed asset with nobody holding it is a gap in the register, so the tool refuses it.
Sync from AD
Sync from AD pulls the latest people across from Directory. The result tells you how many users came over and how many of them are still waiting for a computer, which is a quick way to find onboarding work you have not done yet.