Managed IT and InfrastructureTechnical articlePublished 3 September 2026Technical content maintained by Maisi Zhiwei

What should managed IT services include, and how should a manufacturing or SME define scope and pricing?

Managed IT should not be priced only by PC count. Inventory networks, servers, Active Directory, VMware, backup, permissions and remote access first, then define remote/on-site frequency, change windows, SLAs, documentation and project boundaries.

Inventory first, change secondInfrastructure changes affect business continuity. Keep configuration backups, maintenance windows, validation checks and rollback criteria before production changes.

1. Define the operating boundary before discussing price

A common mistake is to price support only by the number of PCs. In an infrastructure-heavy business, complexity comes from dependencies: servers, switches, firewalls, Active Directory, VMware, backup, file permissions, ERP/MES and remote access. Start with an inventory and separate routine operations, incident response, project changes and third-party coordination.

2. What infrastructure-focused managed IT can cover

Networks and firewalls: switching, VLANs, routing, firewall rules, VPNs, dual WAN and branch connectivity.
Servers and identity: Windows Server, Active Directory, DNS/DHCP, Group Policy, file services and permissions.
Virtualization and backup: VMware vSphere/ESXi, Horizon, PVE, Veeam, NAS/VM/SQL protection and restore verification.
Projects and records: network upgrades, server/domain migrations, hardware replacement, configuration backup, topology, acceptance and handover documentation.

3. Information to prepare before requesting a quote

List critical servers and roles, hypervisors, network devices, firewall/ISP links, branches, AD/DNS, NAS, backup, databases and key applications. Clarify whether support is mainly remote or on-site, the expected inspection/reporting cadence, and which changes require maintenance windows and rollback plans.

4. Keep routine operations separate from project changes

Routine support can cover health checks, incidents, permissions, backup jobs, connectivity and small policy changes. Core-switch cutovers, server migrations, AD upgrades, storage redesigns and broad VLAN changes should be managed as projects with a runbook, checkpoints and rollback criteria.

5. Long-term support should improve documentation

A useful provider does more than restore service. Topology, configuration, change history, recovery evidence and ownership should become clearer over time so the environment is supportable by the business, not only by one engineer.

Remote or on-site?Logs, configuration, policy review and small-scope validation can often start remotely. Physical hardware, cabling, core-network cutovers, production changes and recovery drills are better scheduled in controlled on-site windows. On-site service is available by project in Zhejiang, Shanghai and Jiangsu; other regions can start remotely.

Frequently asked questions

Does managed IT always require an on-site engineer?

No. Many infrastructure issues can be assessed or resolved remotely. Hardware replacement, cabling, core-network cutovers and production changes are better handled with controlled on-site windows.

Can support be quoted as a fixed monthly fee?

Yes, after the environment and service boundary are clear: supported systems, response cadence, on-site visits, project exclusions and documentation requirements.

Need an assessment for your actual environment?

Share the current topology, device models, system versions, symptoms, impact, maintenance windows and available configuration/backup information. We can first assess risk, scope and rollback needs, then define remote, on-site or project work.