Server management covers 24/7 monitoring with alert triage, operating system and firmware patching, security hardening and access control, backup verification, performance and capacity management, hypervisor and cloud instance management, and lifecycle planning. Scope per activity is set in a responsibility matrix agreed before the contract.

A help desk supports people: password resets, device issues, and application questions. Server management supports infrastructure: the servers, hypervisors, and cloud instances those applications run on. The two coordinate closely, but they are separate services with separate teams and response models.

The discipline is the same, but the tasks differ. Physical servers add hardware health, firmware, and out-of-band access. Virtual servers add host, cluster, and snapshot management. Cloud instances add right-sizing, reserved pricing, and platform-native backup. Most estates include all three.

Maintenance windows are set per server group during onboarding, based on business hours, production calendars, and change freezes. Patches are staged on a pilot group first, deployed in the agreed window with rollback ready, and critical patches follow a separate expedite path.

Yes, for servers where agents are restricted by vendor support or policy. Agentless monitoring through SNMP, WMI, SSH, or out-of-band controllers covers availability, hardware, and basic performance, with reduced depth on application and log data, which is noted in the matrix.

Backup jobs are reviewed daily for success, and restores are tested on a scheduled cadence against documented recovery objectives. Verification means a file, database, or full server is actually restored and checked, not just that the job log reported completion.

Hardware alerts are triaged immediately, the vendor case is opened under the client's warranty or support contract, and the workload is moved or recovered where virtualization or backup allows. Servers past warranty are flagged in the lifecycle register before this becomes an emergency.

Yes. Client administrators retain access under the same named-account and MFA standard applied to our team, and the responsibility matrix defines who makes which changes. Shared change records keep both teams aware of what was done and when.

Routine changes within the agreed scope, such as scheduled patching, run under a standing approval. Changes outside that scope are raised as tickets with impact, rollback, and timing, and executed only after the named client approver confirms, with the record retained.

Onboarding produces a server inventory, configuration records, dependency notes, runbooks for recurring tasks, and the responsibility matrix. Documentation is updated with every change and stored where the client can reach it, so it remains usable if the engagement ever ends.

Pricing is based on server count, environment mix, the engagement model, and coverage hours, with the responsibility matrix determining what each server includes. Calance confirms the estimate after discovery so the proposal reflects the actual estate.

Clients provide administrator access for onboarding, a named operations contact and change approver, maintenance window constraints, existing vendor and warranty contracts, and security and compliance requirements. Calance supplies monitoring, tooling, engineers, documentation, reporting, and the escalation path.

Targets are set by severity: critical incidents are acknowledged within 15 minutes around the clock, high within 30 minutes, medium within two business hours, and low within one business day. Workaround targets follow, and resolution depends on root cause.

Onboarding typically runs 60 to 90 days from contract to steady state, covering discovery, monitoring and access setup, patch catch-up, and the first service review. Estates with significant deferred maintenance take longer, and Calance sets expectations for that after discovery.

Documentation, runbooks, monitoring configuration, and credentials are handed back in a structured transition over an agreed notice period, and Calance supports the incoming team or internal staff through knowledge transfer so the estate stays operable throughout.