AirWatch Remote Assist for faster field troubleshooting

Field faults rarely arrive as neat incidents. A technician in a mining operation outside Perth may need urgent help with a rugged tablet, while a service engineer in Melbourne struggles with an application that works on the office network but fails on mobile data. Screenshots and error messages often describe the symptom without revealing the device, network, identity or application state behind it.

AirWatch Remote Assist gives authorised IT teams a controlled way to support managed devices in the field. Subject to platform configuration, device permissions and licensing, support personnel can inspect diagnostic information, share a screen and, where permitted, interact with the device remotely. This shortens the distance between a worker and a technical expert without granting permanent administrative access.

For Australian organisations, the capability fits naturally within an enterprise mobility management strategy. It connects live troubleshooting with the wider AirWatch device management platform, helping support teams manage applications, configurations, security policies and business endpoints while reducing unnecessary travel to sites in Sydney, Brisbane, Adelaide, Canberra and regional areas.

What remote assistance changes in the field

Traditional device management focuses on configuration and policy. Administrators can apply restrictions, deploy applications, monitor compliance and retire devices through the AirWatch console, but those functions do not always explain an active problem. A technician may know that a tablet is out of compliance without knowing which application is blocking a work process.

Remote device support adds a time-bound assistance layer. An authorised employee or managed service provider can investigate issues involving unstable applications, VPN connections, Wi-Fi authentication, screen lockouts, system prompts or unusual device behaviour. Live observation can reveal whether a failure is caused by a damaged peripheral, an outdated operating system, a conflicting application setting or a service that cannot reach its backend.

The same approach can support less technical staff. A support analyst may guide a user through an approval prompt, demonstrate a corrected procedure or request relevant diagnostic details while the user remains in control. This is particularly valuable for bring-your-own-device programmes, where employees use personally owned smartphones and tablets for work and the organisation does not control every hardware component.

Remote assistance should not become an open-ended surveillance system. Clear consent, role-based permissions, session controls and audit records are essential. The objective is to restore productive work quickly while preserving the user’s privacy and the organisation’s security requirements.

A practical remote troubleshooting workflow

A reliable process begins before anyone views a screen. The service desk should verify the device identifier, the reported symptom and the requester’s identity. Where possible, the AirWatch record should be checked for ownership, enrolment status, operating system version, installed applications, compliance state and recent administrative changes. This avoids attaching a support session to the wrong asset or duplicating work already completed by another technician.

The technician then confirms that remote assistance is authorised and explains what will be shared. The requester may need to approve a prompt on the device, while some controls remain unavailable because of operating system restrictions, work-profile policies or the device’s management state. A good runbook states whether screen viewing, annotation, remote interaction or only guided support is appropriate for each support category.

During the session, the technician can use the available device and application information to test a hypothesis in real time. Reinstalling a managed application, checking a certificate, switching between Wi-Fi and mobile data or reviewing a failed policy deployment may resolve the issue immediately. If the fault cannot be corrected online, the session becomes part of the escalation package for a mobile technician or an on-site visit.

Afterward, the support team should document the cause, actions taken, temporary workarounds and permanent fix. Logs and diagnostic records support trend analysis, while a clear closeout prevents the same problem from generating repeated calls. Remote support and device management work best when each session feeds improvements back into configuration, applications and support procedures.

Preparing devices, people and policies

Device preparation determines how much assistance can be delivered. Business devices should be enrolled, assigned to the correct organisation group and connected to the intended identity and application services. Management profiles, VPN access, enterprise certificates and support applications should be tested before deployment. Personal devices participating in a BYOD programme also need clear limits on the information that an employer may access.

Connectivity must be considered from the beginning. Remote troubleshooting is useful in a regional warehouse or on a roadside job, but a weak mobile signal can make screen sharing slow or unreliable. Support procedures should define when to use a low-data diagnostic method, when to ask the user to move to a better signal and when to defer assistance until the device can obtain a stable connection. The Australian geography makes this particularly relevant where field teams operate outside major metropolitan centres.

Local operational arrangements also matter. Australian deployments commonly involve enterprise integrators, resellers and internal IT teams that understand sector requirements in mining, logistics, utilities, construction and government. Packages and pricing should be reviewed in Australian dollars, with GST and any local implementation services confirmed during procurement. If evaluation hardware is imported, the organisation should use appropriate customs documentation, declare duties correctly and consider temporary-admission arrangements with a customs broker rather than sending devices through the trial without assessing border requirements.

People and procedures should be ready alongside the technology. Support staff need role-specific training, while managers need a simple method for approving access. A small test programme covering the most common field issues can expose missing permissions, inaccurate device records and unclear escalation paths before broader deployment.

Security and Australian compliance considerations

Remote assistance can expose sensitive information because a screen may contain customer records, health information, financial data or business credentials. Access should therefore follow least-privilege principles, with strong authentication for support accounts and approval workflows for sensitive actions. Sessions should be limited to approved purposes, and organisations should determine how long recordings, chat transcripts and diagnostic logs are retained.

For organisations subject to the Privacy Act 1988, the Australian Privacy Principles provide a useful framework for handling personal information. Support access should be necessary, proportionate and properly governed, with access and incident processes documented. Some organisations also operate under state health, financial services or education requirements that add further controls. A remote support policy should identify the relevant legal basis, restrict the categories of data that may be viewed and define when consent is required.

Security assessments should cover the complete support chain rather than focusing only on the mobile device. MFA, conditional access, endpoint compliance, encryption, auditability and timely removal of access for departing staff all contribute to a defensible control environment. The ASD Essential Eight can help structure this assessment, particularly around identity management, application control and incident response, although it does not prescribe a particular remote support product.

Procurement teams should verify exactly which capabilities are included in the selected package and how remote assistance aligns with existing identity, service-desk and endpoint controls. This prevents an organisation from assuming that every AirWatch licence or device operating system supports the same level of interaction.

Matching support methods to field issues

No support method solves every situation. The AirWatch management console is strongest for fleet-wide administration, while live remote assistance is designed for active troubleshooting. Generic remote desktop tools can support personal computers, but they may not integrate cleanly with managed mobile devices, enrolment context or enterprise approval processes. An on-site visit remains necessary when a fault involves physical damage, inaccessible equipment or work that cannot be performed remotely.

Support method Best suited to Operational context Main limitation
AirWatch Remote Assist Guided or interactive troubleshooting of enrolled devices Uses managed-device context and policy-aligned support permissions Capability depends on licensing, enrolment and operating-system controls
AirWatch management console Configuration, compliance, applications and device lifecycle Supports broad administration across enrolled endpoints Does not replace a live diagnostic session
Generic remote desktop Direct access to compatible computers and apps Useful for flexible ad hoc support Mobile integration, consent controls and audit context may be limited
On-site technician Physical faults, peripherals and complex local issues Provides hands-on assessment in the field Requires travel, scheduling and higher response cost

The practical model combines these approaches. The console identifies the device and its compliance state, remote assistance investigates the live fault, and an on-site visit handles physical or environmental problems. Support routing should make that progression clear, including the trigger for dispatching a technician to a mine site, warehouse or customer premises.

Run a controlled remote assistance pilot

A focused trial can show whether remote troubleshooting reduces response times for the issues that matter most. Choose representative devices and use cases, define which support teams may assist users, and measure first-contact resolution, time saved, escalations and user satisfaction. A fully functional 30-day free trial provides an opportunity to test these workflows against realistic scenarios rather than relying only on demonstrations.

AirWatch pricing and package comparisons should be assessed alongside the operational requirements of the organisation. Buyers can also review customer stories involving comparable device fleets, security controls or field-service environments, then discuss integration and support needs with the sales team.

For Australian organisations ready to improve device support, contact AirWatch or its associated VMware sales team to arrange a 30-day free trial, compare suitable packages and build a secure remote troubleshooting programme around the devices already working in the field.