Deploying to one office is a project. Deploying to twelve is a logistics problem with an IT project inside it. The engineer cannot be everywhere, the sites have different closets and different ISPs, and the person plugging things in is usually the store manager, not a technician.
The way through is to move the skilled work to a staging bench, ship boxes that are labeled so a stranger can connect them, and give the person on site a short script and a phone number. Here is the process.
Survey every site before you buy anything
A remote survey with a form and a phone camera saves a lot of returns. Ask the site contact for photos of the demarcation point, the existing closet or cabinet, the power outlets, and the ceiling where access points might go. Ask for the ISP name, account number and circuit speed.
From those answers build a per-site sheet: what is there now, what is being replaced, cable runs needed, mounting constraints, and anything odd. The odd things are the ones that matter: the router in the kitchen, the site with no dedicated internet at all.
- Photos: demarc, closet, power, ceiling, any existing equipment with labels visible
- ISP: provider, account, speed, modem model, bridge mode yes or no, static IP yes or no
- Physical: rack or shelf, power outlets and UPS, cable paths, mounting surfaces
- People: on-site contact, hours, who has keys to the closet
- Constraints: landlord rules, shared tenancy, ceiling type, distance from closet to far corner
Stage everything on a bench
Every device is configured, updated and tested before it ships. Firewalls get their site config, WAN settings and VPN keys. Switches get VLANs and port profiles. Access points are adopted to the controller and assigned to the site. Then everything is powered on together on the bench and tested as a site, including the VPN back to the main office.
Use cloud-managed platforms where the client's budget allows. A device that pulls its configuration from a controller when it first sees the internet is far more forgiving of an on-site mistake than one that needs a console cable. For locally configured gear, keep a config backup per device before the box is sealed.
- Configure each device with its site-specific settings and update firmware
- Power the whole site kit on the bench and test: internet, VLANs, Wi-Fi, VPN, printing
- Record serial numbers and MAC addresses against the site in the inventory
- Back up each configuration to the documentation platform
- Label every device and every cable end before packing
Label and pack for a stranger
The person opening the box has never done this. Labels do the teaching. Each device gets a large label with its name and a number. Each cable gets a label at both ends that says where it goes: 'Cable 1: ISP modem to Firewall WAN', 'Cable 2: Firewall LAN1 to Switch port 1'.
Include a one-page picture guide in the box with a photo of the bench setup and numbered arrows. Include spares and a printed card with the support number and ticket reference. Ship with tracking to the site contact by name and confirm receipt before the install date.
- Device labels: name and number, large print, on the front
- Cable labels at both ends with source and destination
- A photo of the assembled kit with numbered arrows
- Spares: cables, power strip, patch panel keystones if used
- Support card: phone number, ticket reference, install window
Remote hands on the day
Schedule a call with the site contact for the install window. Walk them through the picture guide step by step while you watch the devices come online in the controller. Ask them to photograph the finished closet. If something does not come up, the most common causes are a cable in the wrong port, the ISP modem not in bridge mode, or a power strip that is switched off, so check those first.
For sites where the work is beyond a manager with a phone, such as pulling cable or mounting access points, hire a local low-voltage contractor for those tasks only, with your written scope and your labels. Do the network configuration yourself remotely once they have connected the hardware. If you would rather hand staging and shipping to someone who does it regularly, RackLedge runs multi-site rollouts nationwide.
- Confirm the box arrived and the contact has time set aside
- Start the call, share the picture guide, connect devices in numbered order
- Watch the controller for each device to check in; troubleshoot cable, bridge mode, power
- Test from a site laptop: internet, printing, the main application, Wi-Fi in the far corner
- Get closet photos, close the ticket, update the site documentation
Frequently asked questions
Should we ship all sites at once or in waves?
Waves. Do two or three sites first, fix the guide and the packing list from what you learned, then ship the rest in batches your support desk can handle on install days.
What if the site's ISP is not installed yet?
Ship anyway but do not schedule the install call until the circuit is confirmed live. Ask the site contact to test the ISP modem with a laptop and send a screenshot before the call.
How do we handle the old equipment?
Include a prepaid return label and a bag in the box. Ask the contact to pack the old gear once the new site is confirmed working, and track the return for wiping and disposal.
Takeaway
Survey each site remotely, configure and test the whole kit on a bench, label every device and cable for a stranger, and run install day as a phone call while you watch the controller. Ship in waves so the first sites improve the process for the rest. The engineer stays at the bench, and the sites still come up right.