← Back to projects
PROJECT

Real-estate group in Hangzhou | JumpServer rollout for 80+ vSAN VMs and seven systems

JumpServer was introduced as a controlled operations entry point for more than 80 vSAN virtual machines supporting seven business systems. The delivery focused on assets, roles, accounts, authorization and phased cutover rather than treating bulk asset import as project completion.

HangzhouReal estateJumpServer / 80+ vSAN VMs / seven systems
01

Project context

The group had more than 80 vSAN virtual machines supporting seven business systems, with administrative access spread across many assets and accounts. The JumpServer project started with asset ownership, operator roles and least-required access, then moved administrative paths in batches so the new gateway did not simply reproduce shared accounts and excessive privileges.

02

Objectives

  • Use JumpServer as the controlled administration entry point for 80+ vSAN virtual machines and seven business systems.
  • Map operators, roles and assets into maintainable authorization relationships.
  • Move administrative access in stages while preserving continuity and a fallback path.
03

Scope baseline

01

Group 80+ VMs by business system, environment and ownership.

02

Design role- and asset-group authorization before migrating operator access.

03

Pilot connections and credentials on lower-risk assets before expansion.

04

Onboard in batches and verify login, authorization and audit records after each batch.

04

Delivery and controls

  1. 01

    Group 80+ VMs by business system, environment and ownership.

  2. 02

    Design role- and asset-group authorization before migrating operator access.

  3. 03

    Pilot connections and credentials on lower-risk assets before expansion.

  4. 04

    Onboard in batches and verify login, authorization and audit records after each batch.

  5. 05

    Consolidate the asset inventory, account ownership, authorization matrix, audit checks and the process for adding or removing future access.

05

Risk and change control

R01

Shared or over-privileged accounts were reviewed before assets were imported into the new access model.

R02

Service or automation dependencies were separated from interactive administrator access so platform onboarding did not break applications.

R03

Access cutover was staged by asset group, with a fallback path retained until representative connections and audit records were proven.

06

Acceptance and handover

  • More than 80 vSAN virtual machines were grouped and onboarded as planned.
  • Operations staff could reach assets for the seven business systems only within their assigned authorization scope.
  • Representative Windows/Linux and management endpoints passed connection and audit validation.
  • Asset, account and authorization matrices plus the access add/remove process were handed over.

Key deliverables

Asset and account inventoryAuthorization matrixConnection/audit validationAccess lifecycle procedure

Planning a similar project?

Share the current environment, business impact and target outcome. We will confirm scope, dependencies and delivery boundaries first.

Discuss a similar project →