If you are responsible for procuring or planning AV equipment rather than managing the network, the most practical challenge when deploying NDI cameras is often not the equipment itself — it is figuring out how to communicate with your organization's IT department. NDI cameras run on standard Ethernet and theoretically just need a network connection to work, but deploying them in a managed corporate or campus environment means encountering IT's own network policies. Rather than discovering after purchase that "IT says we can't set it up this way," it is far more efficient to walk into the conversation with specific questions. Below are five questions worth prioritizing.
NDI discovery relies on mDNS or a Discovery Server to let devices find each other. Sharing a subnet with the general office network can cause mutual interference and may expose camera streams to unintended departments. Ask IT directly: "Can a dedicated subnet or VLAN be set up for these NDI cameras?" This is the single most foundational step and can prevent the majority of subsequent problems.
Some NDI transmission mechanisms use Multicast packets. Without proper switch handling, these can trigger broadcast storms that slow the entire network. This is a technical setting that typically requires IT to configure in the switch management interface — worth explicitly confirming and requesting before deployment.
By default, NDI sources broadcast as a "Public" group, theoretically discoverable and receivable by anyone on the same network. If the cameras capture sensitive content (boardrooms, exam classrooms), this must be addressed proactively. The official free NDI Access Manager tool allows sources to be assigned to custom groups — only receivers in the corresponding group can see those sources. For larger environments with devices spread across subnets, an NDI Discovery Server can centralize source discovery and reduce mDNS broadcast traffic. Ask IT: "Do we need to restrict who can see these camera feeds?" — then decide whether to enable group-based access control.
If cameras or decoders support PoE/PoE+ (802.3at), a PoE+ switch can supply power over the network cable, eliminating a dedicated power run and resulting in much cleaner cabling — especially for ceiling-mount or hard-to-power locations. The prerequisite is that the switch supports the correct PoE standard and has a power budget sufficient for all devices. Confirm switch specifications with IT or facilities in advance to avoid arriving on-site and finding insufficient port count or power budget.
Campus and corporate networks frequently have strict firewall rules or policies that restrict device-to-device communication (isolating different departments, different classrooms). NDI requires that devices be able to discover each other and exchange streams. If the default network policy is "block first, ask later," NDI cameras may not even be able to transmit a basic picture. Inform IT of how the system works and ask them to confirm whether additional rule exceptions need to be created.
Most of these five questions do not require you to configure anything yourself — the point is to inform IT of the network requirements before deployment. Most corporate and campus IT teams are unfamiliar with professional AV protocols like NDI. Explaining clearly upfront — "this is what it is, this is what it needs from the network" — typically saves enormous amounts of on-site troubleshooting time, and makes IT far more willing to cooperate because they know exactly what they are being asked to support.
Installing NDI cameras is not complicated. What usually determines whether a deployment goes smoothly is whether the network-side communication was done thoroughly. Prepare these five questions and schedule a short meeting with IT before procurement — this prevents the majority of network problems that would otherwise only surface on-site. For more detail on NDI network architecture and switch configuration, see "The Ultimate Guide to NDI Production Workflows."