Remember to check the Knowledge Base for a solution before you enter a new ticket.

Assign Existing Hardware

Creation date: 5/26/2026 12:02 PM    Updated: 7/27/2026 8:48 AM
Argus IT Help Desk · Hardware
Assigning an Existing Argus-Inventoried Device
For hardware Argus already owns — usually same-day to 2 business days.
Hardware will NOT be deployed until the form is complete AND manager approval is confirmed
Incomplete requests go on hold. Submit early — deployment is typically same-day to 2 business days for assets already configured for the recipient's role.
🧭  Is this the right form?
✅ Yes, use this form if
A device that already exists in Argus inventory needs to be issued to a specific staff member — whether you know the asset tag, or you're asking IT to pick a suitable device from stock.
❌ No — use a different article if
New employee → New User Onboarding Request (KB-30001). Brand-new hardware to order → Requesting New Hardware (KB-200001). Broken hardware → a troubleshooting ticket. Squirrel POS hardware (iPads, terminals, printers) → KB-200001 — Squirrel deployment has extra vendor-side coordination.
📋  The form — copy into your ticket and fill in
ASSET ASSIGNMENT REQUEST
=========================

REQUESTER (who is submitting this ticket)
Your name:
Your email:
Your job title:
Your department / property:

RECIPIENT (who will receive the device)
Recipient name:
Recipient email:
Recipient job title:
Recipient property / venue:

DEVICE BEING ASSIGNED
[ ] Specific device - Asset tag:
[ ] Any suitable device from stock (IT will select)

DEVICE TYPE - REQUIRED
[ ] Laptop      [ ] Desktop
[ ] Monitor (quantity / size if known):
[ ] Docking station
[ ] Keyboard / mouse / headset
[ ] Cell phone (already-provisioned company device - HR awareness required)
[ ] Other - describe:

REASON FOR ASSIGNMENT - REQUIRED
[ ] Replacement for failing / outdated device - old asset tag:
[ ] Replacement for lost / stolen device (incident report: [ ] Yes [ ] No)
[ ] Additional device for existing role
[ ] New role assignment requiring different hardware
[ ] Re-deployed device (previously reclaimed, now re-issued)
[ ] Transfer from another staff member (previous user's name):

CONFIGURATION / ACCESS NEEDED
[ ] Standard configuration (Microsoft 365, Outlook, browser)
[ ] Specific systems or software (OPERA Cloud - which property,
    Squirrel back office, Adobe license, VPN, Optimum Control...):
[ ] Copy access from existing user (whose access to mirror?):

DELIVERY / PICKUP - REQUIRED
[ ] Pickup at IT office
[ ] Deliver to property - property and full address:
Attention to (full name):
Access notes (gate codes, reception hours, etc.):

TIMELINE
When is this needed by:
Is this urgent (operations-affecting): [ ] Yes [ ] No

APPROVAL - REQUIRED
Approved by (manager name and email):
Approval date:
Has the manager been notified this ticket is going in?
[ ] Yes - expecting it   [ ] Not yet - IT may contact them

ADDITIONAL NOTES
🧠  Why the key fields matter
Asset tag
Know which specific device (e.g. "issue laptop #02001")? Include it — IT pulls it from inventory and starts configuring immediately. Don't know? Tick "any suitable device."
Reason for assignment
Affects preparation: replacements may need data migration; transfers need the old profile cleared; new roles may need different software.
Copy access from existing user
The single fastest way to get permissions right — one operation mirrors a colleague's folders, lists, and app permissions.
Delivery details
Remote properties (Four Points YLW, Hampton / Home2 FSJ): incomplete addresses are the #1 delay.
🕑  Lead times
  • Specific device, standard config: same day to 1 business day
  • Specific device needing software/access setup: 1–2 business days
  • Any-device-from-stock with new configuration: 2–3 business days
  • Not actually in stock? We convert it into a hardware order (KB-200001) with its own lead time — typically 5+ business days.
✅  What happens next
1
Ticket reviewed; missing info or approval gets a reply.
2
Device availability confirmed in inventory.
3
Configured for the recipient — M365 sign-in, requested software, access mirrored from the reference user, standard security policies.
4
Tested, then shipped or made available for pickup.
5
Recipient gets a confirmation — and a reminder to record the asset tag.
💡 After delivery: verify it works within the first business day · note the asset tag · return the old device if this was a replacement.
🔗  Related
New User Onboarding (KB-30001) · Requesting New Hardware (KB-200001) · User Off-Boarding (KB-30002)
ArgusIT KB# 200003 · Tags: hardware · asset · assignment · deploy