Computer Inventory & Device Management

Explore devices & inventory in detail.

Devices & inventory

Customers, sites & devices

Organise the estate by customer and site, with scoped access, device types, connection state and signed-in users.

Close explanation of Customers, sites & devices

What it does

Organise computers around the people and places they belong to. Customer and site structure provides the context for support, policies, reporting and access, whether the environment is one household, one business or several managed clients.

How you can use it

• A structured estate. Group devices by customer and site, and keep device type, connection state and available signed-in-user information close to the list.
• Customer-specific care. Apply the appropriate alert routing, update choices, automation rules and portal settings to the environment being supported.
• From fleet to detail. Filter the estate, open an individual computer and move into its hardware, software, security, performance and support views.

In practice

An IT support company can distinguish a client’s head office from its branch, review the branch computers and plan work within that client’s agreed settings.

Controls & availability

Customer scope limits what an account can see and act on. A technician’s access to one client does not automatically give them access to another.

Ask us about Customers, sites & devices

Devices & inventory

Hardware inventory

Explore processor, memory, firmware, hardware details, storage, battery and available health readings.

Close explanation of Hardware inventory

What it does

Understand the computer behind the reported problem. Hardware inventory brings together the available processor, memory, firmware and storage details, with battery and hardware-health readings where the device supports them.

How you can use it

• A useful specification. Review model, serial and component information to identify the machine and assess its suitability for the software it needs to run.
• Storage and battery context. Inspect available drive and battery readings when diagnosing limited space, ageing hardware or a laptop that no longer holds its charge.
• Inventory connected to support. Use the hardware picture alongside performance history, warranty information and changes instead of working from the customer’s recollection alone.

In practice

Before recommending a memory upgrade for a slow office PC, the technician can confirm its existing specification and compare it with the observed workload.

Controls & availability

Inventory reflects what the agent can collect and when it last reported. A missing hardware-health reading is shown as unavailable, not proof that the component is healthy.

Ask us about Hardware inventory

Devices & inventory

Software inventory

See installed applications, versions and support or vulnerability findings. Investigate what is installed across an environment.

Close explanation of Software inventory

What it does

See the applications and versions reported by a device, then investigate the wider environment when a particular programme matters. This helps explain support issues, plan compatible updates and identify software needing closer review.

How you can use it

• Installed application details. Review collected names and versions alongside operating-system information to understand the software environment on a specific computer.
• Estate-wide investigation. Find computers reporting an application and compare versions, helping the team judge whether a problem is isolated or affects a wider group.
• Links to other evidence. Bring inventory into update planning and configured vulnerability or support-status checks, while keeping uncertain matches available for review.

In practice

When an application vendor reports a problem in one release, the support team can identify the computers reporting that version and review the appropriate update route.

Controls & availability

An installed application is not necessarily eligible for automatic updating. Package support, installation context and customer exclusions still decide what Vycko can change.

Ask us about Software inventory

Devices & inventory

Performance history

Read processor and memory history over different time ranges, with gaps and stale readings represented honestly.

Close explanation of Performance history

What it does

A computer can feel slow even when it looks normal at the moment someone checks it. Performance history helps the team look back at processor and memory behaviour and compare periods around the reported symptom.

How you can use it

• Different time ranges. Review the available history over a useful period, from a recent problem to a longer-running pattern.
• Patterns rather than one reading. Look for repeated peaks or sustained pressure, then connect those observations to processes, events and the applications in use.
• Honest gaps. See where samples are missing or old, so a computer that was offline does not appear to have had an uneventful period.

In practice

A business says a workstation becomes slow each afternoon. The technician compares the available history with scheduled tasks and running applications before choosing the next diagnostic check.

Controls & availability

History is sampled evidence rather than a recording of every moment. High CPU or memory use does not automatically trigger a reboot or process termination.

Ask us about Performance history

Devices & inventory

Network details

Keep adapters, addresses and connectivity information alongside the device. Check remote access and Wake-on-LAN availability.

Close explanation of Network details

What it does

Keep the computer’s network information with the rest of its record. Adapter and address details help a technician understand how the device is connected and distinguish a local device problem from a connectivity issue.

How you can use it

• Connection context. Review available network adapters, IP addresses and other collected connection details when a computer cannot reach the resources it normally uses.
• Useful identification. Use supported address and adapter information to find the right machine across the estate rather than relying only on its display name.
• Remote-support planning. Review relevant connectivity and Wake-on-LAN information before arranging a supported connection or a wake attempt.

In practice

A laptop works at home but cannot reach an office service. Its reported adapter and addressing information gives the technician a starting point for a focused network investigation.

Controls & availability

This is device-level network visibility. It does not imply comprehensive monitoring or configuration of every router, switch, printer or other network appliance.

Ask us about Network details

Devices & inventory

Users & groups

Review accounts and group membership. Use authorised actions for account access and password resets where supported.

Close explanation of Users & groups

What it does

Understand the accounts and group membership on a supported computer and use authorised tools when access needs attention. Keeping this information on the device page helps connect an account issue to the machine being investigated.

How you can use it

• Account visibility. Review available local users and groups to understand who has access and which memberships may explain a permission problem.
• Targeted management. Use supported, permitted local-account and group actions rather than making a broader change than the support task requires.
• Password assistance. Follow the supported password-reset workflow where applicable, with the correct permissions and the additional requirements of the target environment.

In practice

A member of staff cannot use a local resource. The technician reviews the computer’s account and group evidence before deciding whether an authorised membership change is appropriate.

Controls & availability

Local account tools and domain account tasks have different requirements. A domain password reset needs the appropriate supported domain-controller route; device access alone is insufficient.

Ask us about Users & groups

Devices & inventory

Printers, startup & tasks

Investigate printers and the available share readings, startup entries and scheduled tasks in dedicated device views.

Close explanation of Printers, startup & tasks

What it does

Look beyond the headline symptom into the components that often explain everyday support problems. Dedicated device views bring printer information, startup entries and scheduled tasks into the same investigation as services and performance.

How you can use it

• Printing context. Inspect available printer and relevant share readings when a queue, connection or print-service problem interrupts work.
• Startup visibility. Review what is configured to start with the computer or user session when investigating a slow sign-in or unexpected application behaviour.
• Scheduled work. Inspect collected tasks and use supported authorised actions where available, linking recurring behaviour to the timing of a task.

In practice

A computer becomes busy shortly after sign-in. The technician compares startup entries and scheduled tasks with performance evidence to decide what needs further investigation.

Controls & availability

Availability varies by device and collected evidence. Disabling a startup entry or task is a change and must follow the relevant permissions and customer rules.

Ask us about Printers, startup & tasks

Devices & inventory

Device actions

Restart, shut down, lock, sign out or message a device within the applicable rules. Refresh inventory and manage agent health.

Close explanation of Device actions

What it does

Handle common device tasks from the support workflow without losing the record of what happened. Vycko offers supported actions for the computer, signed-in session and agent, with the appropriate checks before a disruptive change.

How you can use it

• Computer and session actions. Use permitted restart, shutdown, lock, sign-out and message actions where supported, choosing the relevant device and context.
• Support-specific tasks. Refresh inventory, request a fresh check, capture an allowed screenshot or use a supported safe-mode workflow when the investigation calls for it.
• Agent management. Review agent health and use the supported restart or management route when the collection or connection itself needs attention.

In practice

After an approved update, a technician arranges a restart at an appropriate time and checks the computer’s subsequent connection and update state.

Controls & availability

Actions are capability- and policy-dependent. Restarting or signing someone out can interrupt work, so the customer’s approval and notification requirements still apply.

Ask us about Device actions

Devices & inventory

Changes & device notes

Follow hardware, software and settings changes, with attribution where available. Keep useful notes and history with the device.

Close explanation of Changes & device notes

What it does

When something starts behaving differently, knowing what changed can shorten the investigation. Vycko keeps available hardware, software and settings changes with the device, alongside notes that preserve the human context.

How you can use it

• A change timeline. Review detected differences in collected device information and compare their timing with the reported problem.
• Available attribution. Where a change relates to a platform action, use the linked job or activity information to understand how it happened.
• Useful notes. Keep support observations, known quirks and follow-up information with the machine, making the next handover easier.

In practice

An application begins failing after its reported version changes. The technician can relate the change to the support incident and review any associated update activity.

Controls & availability

A detected difference does not always identify its cause or author. Attribution is shown where available, and private operator notes are not exposed as customer-portal conversations.

Ask us about Changes & device notes

Devices & inventory

Warranty tracking

See warranty details, upcoming expiry and report coverage. Manufacturer lookups depend on configured provider access.

Close explanation of Warranty tracking

What it does

Bring warranty information into proactive care and replacement discussions. Vycko can show available coverage details, highlight approaching expiry and include warranty context in the dashboard, customer views and reports.

How you can use it

• Coverage at a glance. Review the stored warranty information alongside the device’s identity and hardware details.
• Upcoming decisions. Use expiry views to identify machines that may need a coverage discussion or replacement review before a fault becomes urgent.
• Supported lookups and manual records. Use configured manufacturer-provider access where available, and record information manually when an automatic lookup is unsuitable.

In practice

A business reviews laptops approaching the end of coverage and combines their warranty, condition and support history to plan the next purchasing discussion.

Controls & availability

Manufacturer lookups depend on configured access and the provider’s response. A firmware date is not proof of manufacture or a substitute for confirmed warranty coverage.

Ask us about Warranty tracking

Devices & inventory

Virtual machines

Read available Hyper-V and VMware host and virtual machine information, including state and capacity. Availability depends on the environment.

Close explanation of Virtual machines

What it does

Keep supported virtualisation information visible alongside the physical host. Read-only Hyper-V and VMware views help the team understand which virtual machines are present and how their state and available capacity relate to the wider environment.

How you can use it

• Host context. Review collected virtualisation-host information so an incident can be investigated with an understanding of the underlying platform.
• Virtual-machine visibility. Inspect available guest names, state and resource information, connecting host observations to the machines running on it.
• Capacity discussions. Use the supported inventory as evidence when reviewing resource pressure or planning further investigation.

In practice

Several virtual servers become slow at similar times. Host and virtual-machine information helps the support team decide whether to investigate shared capacity before treating each guest separately.

Controls & availability

These views are read-only and depend on supported collectors and configured access. They do not imply that Vycko creates, moves, snapshots or deletes virtual machines.

Ask us about Virtual machines

Devices & inventory

Certificates

Review collected certificate details and expiry findings, with dashboard and reporting views for attention where needed.

Close explanation of Certificates

What it does

Expired certificates can interrupt services that otherwise appear healthy. Vycko collects supported certificate information and brings relevant expiry findings into device, dashboard and reporting views so the team can plan a response.

How you can use it

• Certificate context. Review available validity dates and certificate details, with supported service assignments such as web hosting or remote desktop where they can be identified.
• Relevant expiry attention. Focus on watched certificates that appear in use or otherwise meet the monitoring rules, rather than treating every unused expired certificate as an active service fault.
• Configurable thresholds. Use the applicable customer settings to decide when approaching expiry needs attention and which device types are monitored.

In practice

A support team sees an in-use server certificate approaching expiry and can arrange renewal work before the associated service starts rejecting connections.

Controls & availability

Certificate collection is read-only. Vycko’s expiry visibility does not automatically renew, issue or install a certificate, and unsupported assignments may remain unknown.

Ask us about Certificates

Devices & inventory

Device location

Keep a written room and floor, map the site, and review supported device positions with their source, accuracy and time.

Close explanation of Device location

What it does

Know where an asset belongs and understand the quality of any reported position. Vycko combines a written device location, site addresses and supported location readings, with maps that distinguish a building from an approximate or precise device position.

How you can use it

• A location in words. Record a room, floor or description such as “accounts office, desk four”. This remains useful even when the computer cannot report its position.
• Site maps and pins. Add a postal address or place a site pin by hand, giving the team a practical reference for the environment.
• Reported positions. Review supported approximate internet-address location and Windows location readings, with the source, time and available accuracy attached to the result.

In practice

A technician finds the correct office workstation from its written room and desk description, while a laptop’s last supported location is shown with its age and accuracy.

Controls & availability

Reported location depends on customer settings, Windows permissions and available positioning. Approximate town-level results are not an exact address; location visibility is restricted by role.

Ask us about Device location

Features depend on the device, operating system, installed agent and configured permissions. Readiness checks provide evidence and guidance, not certification. The website tour uses illustrative data and does not connect to live devices.