Opened the wrong way — this page has no styling and no images.
Image and stylesheet paths are resolved from the site root (/assets/…), so opening the file directly resolves them to C:\assets\… and nothing loads.
To see it properly: unzip 2_双击进后台改字_仅Windows.zip and double-click 启动后台.bat — the browser then shows the full site with styling, images and the ZH/EN switch.
(This zip is a plain static preview: opened directly it shows one page at a time, without styles, images or the language switch.)
Once uploaded it works normally: live traffic arrives over http, not by double-clicking a file.
This notice only appears when the file is opened locally; online visitors never see it.
ProductsWireless access & coverageSwitching & data centerOptical access & transportOptics & cabling
ServicesManaged NOCImplementation & deliverySpare parts & maintenanceAdvisory & architecture
SolutionsManaged network operations & NOCCampus & wireless coverageCloud-network branchesSecurity & compliance
Case studiesScale · managed operationsSpeed · bulk migrationContinuity · legacy retrofitTechnical notes
About usCompany profileCertificationsOffices & contactTechnical notes
Resources & contactTechnical notesFAQDelivery processPricingPrivacy & termsContact usOffice address
Case studies / IT operations / Hong Kong, China
Multi-vendor takeover7×24 on-site and remoteITIL processCN / EN / Cantonese

A global communications group in Hong Kong, and the multi-vendor stack we took over

The client is a leading global communications consultancy. Its Hong Kong office is the Asia-Pacific operations hub, linked to more than twenty offices worldwide. The equipment on site is not weak — Fortinet firewalls, Cisco switches, Aruba wireless. The real question was never what to buy, but who would keep the architecture running.

0+
Offices worldwide (Hong Kong is the APAC hub)
0brands
Vendor stacks on site
0hours
On-site and remote cover
0languages
Mandarin / Cantonese / English

Client and scenario

Ruder Finn Asia is a leading global communications consultancy. The Hong Kong office runs Asia-Pacific operations and works daily with more than twenty offices worldwide. IT in a firm like this has one characteristic: few people, but an enormous dependence on the network and collaboration tools. An email, a cross-timezone video call, a live client pitch — if any one of them stalls, it is a business incident.

The office infrastructure was already in place, on mainstream brands. The client did not want a rebuild; they wanted someone accountable for the long run on top of the existing stack — nothing replaced, responsibility settled.

Client
Ruder Finn Asia, Hong Kong office · Asia-Pacific operations hub
Delivered by
Vnets Information Technology Limited (VNETS), Penghai's Hong Kong subsidiary
Service model
7×24 on-site and remote support · ITIL service process
Languages
Mandarin · Cantonese · English
Existing equipment
Fortinet firewalls · Cisco switches · Aruba wireless (Instant On)
Compliance focus
Personal data and access audit requirements in a cross-border office

Three questions before taking over

The difficulty here is not technical. It is ownership, once one stack, three vendors and two timezones are added together.

01

One network, three vendors, three consoles

Fortinet owns the perimeter, Cisco the switching, Aruba the wireless: three consoles, three log streams, three firmware cadences. When something breaks, the first step is rarely diagnosis — it is working out which layer owns it.

02

Daytime faults happen at night too

The Hong Kong office links more than twenty sites worldwide: faults raised locally by day must close the same day, while Europe's and America's daytime is Hong Kong's small hours. Cover cannot be one forwarded phone.

03

Cross-border work has to be traceable

Staff accounts, guest access and device changes must all answer who changed what, and when. A stronger password does not solve that; process and records do.

"The equipment was fine. What was missing was the person who gets woken at three in the morning and knows which box to touch." — delivery lead

How we took over

Take over first, improve second: protect what the client has already bought, and draw the line of responsibility clearly.

STEP 01

No replacement, just takeover

The existing Fortinet / Cisco / Aruba estate stayed. The first step was a clean handover of the asset list, configuration backups, accounts and permissions — the ledger everything else is built on.

STEP 02

Certification to match the kit

Three vendors on site means three certification tracks. Our engineers hold the relevant Fortinet, Cisco and HPE (Aruba) certifications, so they work on the equipment directly instead of escalating layer by layer.

STEP 03

ITIL in practice

Incidents, changes, assets and reporting run on ITIL practice: what takes the emergency path, which changes need prior approval, how often reports appear — agreed up front and auditable afterwards.

STEP 04

Cover and language

The Hong Kong team provides 7×24 on-site and remote support in Mandarin, Cantonese and English. Requests at a multinational come from different regions, and a language gap turns straight into response delay.

STEP 05

Cross-border compliance

Access and records follow Hong Kong and international data protection requirements: who may enter a device, what trace a change leaves, how long logs are kept — all fixed in process.

Scope of service

The day-to-day running of one office from perimeter to endpoint — not just fixing the box that raised the ticket.

Perimeter · firewall policy maintenance, firmware and signature updates, VPN and remote access
Switching and internal network · VLAN and port management, link redundancy, loop and broadcast storm handling
Wireless · Aruba Instant On coverage and roaming, guest network isolation, channel optimization
Office IT · endpoint access, printing and meeting room equipment, new-starter setup
Accounts and permissions · domain accounts, share permissions, leaver revocation
Backup and recovery · scheduled backups of key configurations, version rollback after a failure
Change and tickets · change requests, implementation records, ticket closure and follow-up
Reporting · monthly incident and change report, asset change list, open improvements

Where it stands

The contract was signed in May 2026 and service began then; delivery continues. The client's internal service metrics are contractual and are not disclosed here — this page only describes how delivery runs.

1counterparty
Three vendors and one office, under a single team
0replacements
No equipment replacement was asked for at takeover
7×24
On-site and remote support across timezones

For a client like this the measure is plain: people in the office stop talking about the network. Meetings connect, files open, the client pitch does not drop — IT fades into the background, which is where it belongs.

Compiled from the company's WeChat announcement of 11 May 2026 and project site records; the client name has been publicly disclosed, and the contract governs the specific terms and metrics.

Another multi-vendor stack on your hands?
Start with an inventory.

Contact us →