Should I use the NVR PoE ports or a separate PoE switch?

For smaller contained systems, NVR PoE ports can be fine. For larger or more distributed sites, a separate PoE switch is often the cleaner and more scalable design.

Should I activate IP cameras before mounting them?

Where practical, yes. Proving the camera on a short known-good path first can save a lot of ladder time later.

When should remote viewing be set up on an IP CCTV system?

After local live view, recording and playback are already proven on the NVR.

Why does an IP camera show live view but still create support issues later?

Because live view alone does not prove recording, storage health, event linkage, night performance or remote handover.

When should I use the buying guides instead of this page?

Use the buying guides when the customer still needs help choosing the right brand, NVR size, camera family or system structure.

Support

IP Camera and NVR Installation Guide

A clean IP CCTV install is a networked system job, not just a camera mounting job. The technician needs to think through PoE, switching, IP addressing, activation, recorder storage, analytics, remote access and the final handover order.

CCTV Installation Support

Summary

Use this guide when installing IP cameras and an NVR on a home, office, retail, warehouse or mixed-use site. It is written to reduce commissioning mistakes and support callbacks.

Applies to

IP cameras and NVRs
PoE NVR systems
NVR plus external PoE switch systems
Home, commercial and warehouse CCTV installs

Difficulty and time

Difficulty: Moderate to advanced

Estimated time: Half day to multiple days depending on channel count, switching and network design

What you will need

NVR with HDD installed or ready to initialise
IP cameras, Cat5e/Cat6 cabling and PoE path
Local monitor and mouse for the NVR
Router or LAN access for remote-viewing setup
Network labels, patch leads and a staged commissioning plan

What this guide covers

Choose the network architecture
Run and label Cat cable properly
Prove each camera first
Add cameras to the NVR
Set up storage and recording
Tune analytics and alerts
Finish with handover and export checks

This guide is for technicians installing IP cameras with an NVR, whether the cameras land directly on an NVR with built-in PoE or through a separate PoE switch. It assumes the equipment is already on site and the job now needs to be installed and commissioned properly.

IP systems are usually the better long-term choice when the site wants flexible cabling, higher camera counts, stronger recorder options, separate switching, easier expansion and cleaner integration with modern app workflows. The trade-off is that the installer must manage both the physical path and the network path.

The most common revisit jobs on IP systems come from skipping the staged setup order. Cameras get mounted before they are proven, switch budgets are guessed, passwords are not documented, the NVR recording schedule is left at defaults, or remote viewing is handed over before local recording has ever been tested.

If the customer still has not chosen the right platform, send them first to the Hikvision, HiLook or Dahua buying guides. This page is about installation and commissioning after the equipment has been chosen.

Before you start

Before mounting cameras, decide whether this is an all-in-one PoE NVR job or a separate-switch network job. That choice affects addressing, expansion and troubleshooting.

Count the final camera total, not just the cameras being installed today.
Check whether the NVR PoE ports alone are enough or whether an external PoE switch is the cleaner design.
Confirm the switch power budget against the actual camera load, especially if using PTZs, deterrence lighting or heaters.
Plan which cameras need the strongest angles: front door, driveway, cash point, dock, gate or server-room entry.
Decide who the owner account will be for app setup before the technician starts binding devices.

Important

Do not bind the app before the local system is proven

The technician should first prove power, live view, recording, time, storage and playback locally. App binding comes after the local CCTV system already works.

If remote viewing is configured too early, support often gets distracted by phone symptoms while the real fault is still on the LAN, the PoE path or the NVR schedule.

What usually causes this

PoE path or switch-budget problems.
Camera activation or password mismatch.
Poor channel naming and poor documentation.
Remote-viewing setup attempted before local recording was proven.

Diagram: small IP system using NVR PoE ports

This is common on smaller contained sites where the NVR is close to the camera cable returns.

[IP Camera 1] ---- Cat6 ----
[IP Camera 2] ---- Cat6 -----
[IP Camera 3] ---- Cat6 ------> [PoE NVR + HDD] ---- HDMI ----> [Local Monitor]
[IP Camera 4] ---- Cat6 -----/

[PoE NVR] ---- LAN ----> [Router / Internet] ----> [Owner App / Shared Users]

Good for:
- smaller homes
- small shops
- contained offices

Diagram: IP system with external PoE switch

This is usually the cleaner design when camera counts grow, cable runs spread across a site, or future expansion matters.

[IP Camera A] ---- Cat6 ----
[IP Camera B] ---- Cat6 -----
[IP Camera C] ---- Cat6 ------> [PoE Switch] ---- uplink ----> [NVR + HDD]
[IP Camera D] ---- Cat6 -----/
[IP Camera E] ---- Cat6 ----/

[NVR] ---- LAN ----> [Router / Internet]

Check:
- switch PoE budget
- uplink path
- LAN addressing
- future expansion

Diagram: staged commissioning order for an IP CCTV site

This is the install order that usually reduces support calls later.

1. Prove camera power and network
2. Activate and document credentials
3. Add to NVR and confirm live view
4. Set time, HDD and recording
5. Test playback locally
6. Tune events and analytics
7. Bind app to owner account
8. Test export and user handover

Step 1: Decide the network architecture first

Start with the design choice: cameras directly on NVR PoE ports, or cameras on one or more external PoE switches. That decision affects addressing, testing and expansion.

Use direct NVR PoE ports for smaller contained systems where the recorder location is central and expansion is limited.
Use external PoE switches where camera counts are larger, cable runs are spread across the site, or future expansion matters.
If the cameras will sit on the customer LAN, document the IP strategy early.
Check whether the site wants VLAN separation or a simple flat LAN before commissioning begins.

Step 2: Run, label and test the Cat cable properly

Treat every cable run like part of the network, not just a camera tail. A neat patching and labelling job saves large amounts of fault-finding time later.

Use clean terminations and do not leave untidy joins above ceilings.
Label both ends of every run with the final camera position name.
Keep moisture out of external junctions and use proper glands or protected housings where needed.
Where a run is suspiciously long or routed through harsh areas, test it with a known-good patch path before blaming the camera.

Step 3: Bring up and prove each camera before final mounting if practical

On IP systems, a quick bench or near-recorder proof test can save a lot of ladder time. Confirm the camera powers up, negotiates and shows live video before you trust the full site run.

Use a short patch lead and a known-good PoE source for first proof if the camera is not yet mounted.
Activate the camera if the platform requires it, and document the password strategy.
Confirm the camera appears on the NVR or discovery tool before it disappears into the ceiling space or eave.
Only after that should the final field cable be relied on.

Step 4: Mount cameras for the actual scene objective

Camera placement still decides the result. A technically correct network install can still be a poor CCTV install if the lens, height or angle is wrong.

Front-door cameras should catch an approaching face near the door, not a distant head at the bottom of frame.
Driveway and garage views should balance overview with enough detail on the vehicle approach.
Warehouse dock cameras should avoid glaring direct headlight lines where possible.
If a deterrence or full-colour camera is used, check spill light, flashing-light logic and how nearby reflective surfaces behave at night.

Step 5: Add cameras to the NVR in a controlled order

Once the cameras are powered and physically installed, add them into the NVR cleanly. Prove each one instead of bulk-adding everything and hoping the passwords or addressing align.

Name the channels properly as you add them.
Confirm each camera shows stable live video before moving to the next one.
If a camera will not add, stop and check activation state, password, subnet and protocol instead of repeatedly retrying blindly.
On mixed-brand jobs, be realistic about ONVIF limits and smart-feature loss.

Step 6: Configure storage, recording and time correctly

This is the point where the system becomes useful evidence equipment rather than a collection of live views.

Set the correct time, date and time zone first.
Initialise the hard drive and confirm healthy status.
Choose continuous, event or mixed recording per channel based on the site risk and storage plan.
Check overwrite behaviour so the customer understands retention expectations.
Run local playback immediately once a short test period has recorded.

Step 7: Tune the scene, analytics and alerts after recording is proven

Analytics, human or vehicle filtering, deterrence lights and app notifications should be the later stage of commissioning, not the first.

Start with one critical camera and one event type before copying settings across the site.
Check detection zones and schedules in daylight and, where important, again at night.
Do not leave the site relying only on phone notifications; prove the event locally on the NVR as well.
If the site wants remote alerts, enable them only after the local event path is already working.

Step 8: Finish with app handover, export testing and technician checklist sign-off

The final stage is owner handover. The technician should leave behind a working system, the correct owner account and a clear record of how the system was commissioned.

Bind the recorder or system to the owner account, not a shared installer login.
Share access properly if multiple users need it.
Test live view, playback and one export before leaving site.
Document camera names, switch locations, passwords held by the owner, and any channels that still need night fine-tuning.

Worked example

Example: small office with a PoE NVR

Situation: A six-camera office job covered reception, front entry, rear staff door, office corridor, server-room entry and car park approach. The customer already had a PoE NVR and matching fixed IP cameras.

Solution used: The installer proved each camera on a short patch lead first, then used the NVR PoE ports because the recorder location sat centrally. Channels were named by area, the HDD was initialised, and local playback was tested before the app was handed over.

Why this was chosen: This site did not need separate switching or complex VLAN work. The simple contained NVR path was cleaner and easier for future support.

Installation notes: The server-room and reception views were checked carefully for privacy and useful angle rather than just wide overview.

Worked example

Example: warehouse with distributed PoE switching

Situation: A warehouse had cameras across the front office, loading dock, internal aisle, yard gate and rear roller doors. A single NVR location existed, but the cable runs were spread too widely for a neat all-in-one PoE NVR layout.

Solution used: The installer used an external PoE switch structure, added cameras into the NVR in a staged order, then proved local playback and night views before enabling app access.

Why this was chosen: A distributed switch design gave better cable routing, cleaner expansion and easier future servicing than trying to drag everything back to the NVR PoE ports.

Installation notes: The important technician decision was architecture first, not just where the cameras would physically mount.

Common mistakes

Using the NVR PoE ports for a site that really needed distributed PoE switching.
Forgetting to allow for future camera expansion.
Mounting all cameras before proving the first one on the network.
Setting up the app before confirming local playback and recording.
Leaving channel names as Camera 01, Camera 02 and so on with no real site meaning.

Troubleshooting table

Symptom	What to check	What to do next
Camera powers up but will not add to NVR	Activation, password, subnet or ONVIF issue	Check the camera locally, confirm its IP and re-add with the correct credentials.
Several cameras drop out at once	PoE switch issue, power budget or uplink problem	Check switch load, uplink status and whether the problem follows one switch.
Good live view but no footage later	Recording schedule, HDD or event linkage issue	Check local playback, storage status and schedule before blaming the app.
Night image poor on one camera	Placement, reflection, insufficient light or poor scene setup	Review the physical view first, then retest settings after dark.

When to contact support

Contact SecurityWholesalers support when you can provide the NVR model, camera models, network layout, switch path and the exact point in the commissioning order where the fault appears.

If the underlying issue is that the chosen platform does not suit the job, stop and move back to the brand buying guides instead of forcing a poor design.

Related support guides

CCTV Networking Support - Return to the networking support hub.
NVR Not Detecting Camera: Step-by-Step Troubleshooting Guide - Useful when one or more IP cameras refuse to add.
PoE Camera Not Working: Troubleshooting Checklist - Useful when the physical or PoE path looks wrong.
Static IP vs DHCP for CCTV Systems - Useful for final network design and serviceability.
Tech Support Guides - Browse the full technical support library.

Related buying guides

CCTV Buying Guide - Broader camera-system selection guide.
NVR Buying Guide - Recorder sizing and feature-planning guide.
Hikvision Buying Guide - Useful if the customer is considering or already standardising on Hikvision.
HiLook Buying Guide - Useful for simpler home and small-business CCTV paths.
Dahua Buying Guide - Useful if the site is comparing Dahua as the system path.

Relevant product categories

CCTV Products - General CCTV category if replacement hardware is needed.
Hikvision CCTV Products - Hikvision cameras and NVRs.
HiLook CCTV Products - HiLook value-led CCTV products.
Dahua CCTV Products - Dahua cameras and recorders.

Still stuck?

Need help choosing or setting up a system? Contact SecurityWholesalers support with your order number, product model and a clear description of the issue.

Frequently asked questions

Should I use the NVR PoE ports or a separate PoE switch?
For smaller contained systems, NVR PoE ports can be fine. For larger or more distributed sites, a separate PoE switch is often the cleaner and more scalable design.
Should I activate IP cameras before mounting them?
Where practical, yes. Proving the camera on a short known-good path first can save a lot of ladder time later.
When should remote viewing be set up on an IP CCTV system?
After local live view, recording and playback are already proven on the NVR.
Why does an IP camera show live view but still create support issues later?
Because live view alone does not prove recording, storage health, event linkage, night performance or remote handover.
When should I use the buying guides instead of this page?
Use the buying guides when the customer still needs help choosing the right brand, NVR size, camera family or system structure.