ENDPOINT ENGINEERING

Five disciplines.
One operating view.

Explore practical service areas, common failure patterns, deliverables, and outcomes for every platform Tech With Arun supports.

CHOOSE A DISCIPLINE

Go deeper than
a services list.

Each area below has its own detailed page, with the work covered, warning signs to look for, and what a useful engagement should leave behind.

CM01

SCCM / MECM

Practical engineering for Microsoft Configuration Manager environments—from daily health and software delivery to patching, OSD, migrations, and recovery.

More reliable deploymentsFaster root-cause analysisClearer compliance evidenceLower operational risk
Explore SCCM / MECM
IN02

Microsoft Intune

Design, assess, and improve Intune for enrollment, Autopilot, applications, compliance, configuration, endpoint security, and proactive remediation.

Predictable enrollmentSafer policy rolloutCleaner app deliveryActionable compliance
Explore Microsoft Intune
TN03

Tanium

Operational guidance for questions, sensors, packages, actions, targeting, reporting, hygiene, and high-scale troubleshooting in Tanium.

Safer fleet actionsFaster investigationsReusable contentStronger audit evidence
Explore Tanium
PS04

PowerShell Automation

Production-minded PowerShell for endpoint administration, Microsoft Graph, reporting, packaging, remediation, orchestration, and support tooling.

Less repetitive workSafer executionClearer evidenceMaintainable automation
Explore PowerShell Automation
PY05

Python Scripting

Practical Python utilities for APIs, data transformation, reporting, validation, packaging, and cross-platform operational workflows.

Connected workflowsReliable reportingLess manual handlingSupportable utilities
Explore Python Scripting

THE OPERATING PRINCIPLE

Useful work leaves
the team stronger.

A good technical outcome includes evidence, decisions, guardrails, documentation, and ownership—not only a configuration change.

01

Understand

Map the environment, constraints, failure pattern, and desired outcome.

02

Prove

Collect evidence and test assumptions before changing production.

03

Improve

Implement in controlled stages with validation and rollback.

04

Transfer

Leave the runbook, knowledge, and ownership with your team.

NOT SURE WHERE THE PROBLEM SITS?

Start with the outcome.
We will map the technology.

Discuss your environment