3. Technical support and product expertise
3.1 Investigating SOTI MobiControl problems
My recorded troubleshooting approach starts with gathering the relevant details and identifying possible points of failure. I review internal documentation and related cases in SharePoint, SOTI Wiki, SOTI Help, and Salesforce, then use technical evidence to narrow the investigation. When the issue involves unexpected behaviour or a possible defect, I work with L3 staff, SMEs, and triage leads and create Jira records for Development.
That technical evidence includes Android ADB and dump-state information, server Event Viewer output, application logs, and database information collected through SQL Server Management Studio. My resume also records prepared SQL maintenance operations, queries, table checks, and database truncation activities in the relevant support context.
For cloud environments, I monitored virtual-machine resources, firewall configuration, and application-specific upgrades. My SOTI MobiControl support responsibilities included environment setup, cloud/server upgrades and maintenance, and cloning customer environments for investigation.
3.2 SOTI MobiControl device management across platforms
Within SOTI MobiControl support, my Windows device-management experience includes Windows CE and Windows Desktop Classic and Modern enrollment and configuration. Apple work includes iOS and macOS, Apple Business Manager, automated enrollment, volume-purchase application deployment, and configuration settings. Android work includes enterprise, BYOD, Corporate Personal, and Classic mobility implementations. SOTI MobiControl's online help confirms the product's Android, Apple, and Windows device-management scope; the specific work I performed is recorded in my resume.
The supporting ecosystem includes Honeywell Enterprise Provisioner, Zebra StageNow, Samsung Knox, and Apple Business Manager. I also set up and troubleshot SOTI Cloud Link Agents for on-premise directory-service integration. This platform-specific experience provides context for the later writing examples on enrollment and device configuration, without implying that I independently designed each underlying platform capability.
3.3 SOTI Connect, SOTI XSight, and SOTI Identity
Outside SOTI MobiControl, my support work also covered three other SOTI products. For SOTI Connect, I installed and configured environments using MQTT and REST protocol adapters and HiveMQ brokers and configured Zebra and SATO mobile printers. For SOTI XSight, I diagnosed remote-control and operational-data issues. For SOTI Identity, I configured roles and permissions and integrated identity providers and directory services with Azure Active Directory, now Microsoft Entra ID. These statements describe my resume-recorded work; the product capabilities are consistent with SOTI Connect's protocol-adapter help, certified printer list, SOTI XSight remote-control help, and SOTI Identity user-management help.
This breadth extends beyond terminology about a single product. I worked with devices, protocols, access control, directory integration, and diagnostics; the Skills page connects those areas to specific roles and tasks.
The Skills page pairs each product and supporting tool with the role in which I used it. The writing chapter then shows how that product understanding informed later help research and revisions.
3.4 Customer continuity and colleague support
Aligned-engineer work required familiarity with the customer's environment and ongoing concerns. My resume records both cloud and on-premise support, named enterprise accounts, escalation assistance, and feedback to junior agents. Those details sit alongside the knowledge-base work because supporting an individual case and improving reusable knowledge were connected parts of the role.