Smart PSS
Support & Setup in
Manhattan

How the method changes, building by building

Lobby desks. We start with how the desk is used, not with the software. Which cameras does staff need in front of them all the time, which do they call up only when something happens, and who is allowed to export? The client then gets a fixed opening layout on the main monitor, a second view group for the garage, service door and package room, and a recorder login for the desk that can watch and search but not delete or reconfigure. The PC’s Windows account is a standard user, not an administrator, so a curious overnight hand can’t install anything over it. If the building wants the client to come back by itself after a power cut, we decide that with the resident manager, because convenience and lock-down pull in opposite directions.

Security offices on large complexes. The first conversation is about size. SmartPSS Lite’s datasheet lists 64 devices and 64 video channels; Reddit users who hit the limit describe an error the moment the 65th channel connects. A complex with several recorders and hundreds of cameras either divides the work — one Lite workstation per group of buildings, each under the ceiling — or moves to Dahua’s DSS server platform, which is built for central control rooms. We set out both options with what each needs in hardware and licensing before anyone buys anything.

Pre-war co-ops. The usual fault is age. An old desktop in the super’s office, an old SmartPSS release, a recorder password the installer chose and never handed over. We confirm with the managing agent who owns the system, recover or reset access on the recorder with documented proof of ownership, move the super’s PC to SmartPSS Lite, and leave the admin password with the agent rather than taped to the monitor.

Tenant office floors. Here the IT provider is the gatekeeper and should be. We send the brief before the visit: program name and source, install path, service account, the ports the client needs to the recorder’s address and nothing else. On the day we install it with them watching, test from a standard user account, and confirm the firewall rule is narrow — this one PC to this one recorder, not the whole office to the whole camera segment.

Showrooms, lofts and conversions. Where a landlord’s lobby cameras and a tenant’s floor cameras are both Dahua, it is easy to end up with one PC that shows both and a muddle about who controls what. We keep them as separate devices in separate groups, use a login on the landlord’s recorder that the landlord issued, and write down in the hand-over which recorder belongs to whom. In new conversions, we get the developer, the managing agent and the installer to agree on the recorder passwords before the installer’s contract ends.

Buildings that use a smart-card or face-reader entry alongside the cameras should read the Tenant Data Privacy rules below before turning on face features; our Manhattan access control installation team handles the door side.

The Desk PC and the People Who Control It

The building’s IT contractor locked down the lobby PC — what does SmartPSS Lite need permission to do?

Less than most people fear. It needs to be installed once by someone with administrator rights, to write to its own data folder (that is where local recordings, snapshots and settings go — Dahua’s monitor manual names the default record path under Data/User/Record), and to open network connections from the PC to the recorder’s address on the recorder’s client port, which is TCP 37777 by default on Dahua equipment. If devices are added by serial number instead, it also needs to reach Dahua’s P2P service on the internet. It doesn’t need inbound connections to the PC, and it doesn’t need the desk user to be a Windows administrator.

We write that down as a short brief for the IT contractor, with the installer file’s source and the install folder, and do the install with them. Endpoint tools that flag unfamiliar video software tend to quarantine it on the next scan unless IT has approved it by name; agreeing that up front is what stops the client disappearing two days after we leave.

Should the desk’s SmartPSS Lite sign itself back in after a power cut, or wait for a person?

It depends on what the desk is for. SmartPSS Lite has a “Remember Password” option at its login screen, and Windows can be set to start the program at sign-in, so a desk can come back on its own after a cut. That suits a lobby where the screen must be up before the next person arrives and nobody on the overnight shift has the client password. It doesn’t suit an office reception where anyone walking past could sit down and browse recordings.

Our usual compromise for staffed lobbies: the PC signs into a limited Windows account automatically, the client opens with a remembered login that belongs to a watch-only recorder account, and the screen lock is off during staffed hours. For offices, the client stays behind the person’s own Windows login. Either way the recorder’s admin password is never the one remembered.

Our lobby workstation still runs the SmartPSS release installed around 2020 — what changes if we leave it alone?

The cameras keep recording, because recording happens on the recorder, not the PC. What stops is the desk’s view. Dahua’s wiki says SmartPSS has been discontinued and is no longer supported, and members of the IP Cam Talk forum reported in 2024 that Dahua’s cloud would stop P2P connections from SmartPSS 2.0 builds from 2019 and 2020; one thread title from the period reads “old SmartPSS (v2.003) cannot connect to Dahua NVR starting today, but SmartPSS lite can.” An old client added by IP address on the local network may limp on, but it gets no fixes and sits on a PC that IT will eventually reimage.

We would rather move it on a quiet afternoon than on the morning it fails. Before uninstalling we photograph the device list, layouts and tours, then rebuild them in SmartPSS Lite so the desk sees the same screens it is used to.

How do we stop an overnight guard from changing recorder settings through the desk client?

By making sure the client logs into the recorder with an account that can’t. SmartPSS connects to each recorder with a username and password stored in its device list; whatever that recorder account is allowed to do, the desk can do. If the installer typed in the admin login, the desk has admin rights over the recorder, including deleting recordings and changing the schedule.

We create a separate operator account on the recorder with live view and playback only, put that into the desk’s device entry, and keep the admin login with the resident manager or managing agent. Dahua’s own security appendix to the SmartPSS Lite manual recommends exactly this: add users according to need and give each a minimum set of permissions, with account lock enabled.

Reaching the Recorder Across a Managed Network

The recorder sits on the camera VLAN and the desk PC on the office VLAN — which traffic has to cross between them?

One narrow path. Dahua documents its recorders’ default ports as TCP 37777 for client connections, UDP 37778, HTTP 80, HTTPS 443 and RTSP 554. For SmartPSS Lite added by IP address, the essential rule is from the desk PC’s address to the recorder’s address on TCP 37777. HTTP or HTTPS is useful if staff should also open the recorder’s web page, and RTSP only if another program will pull streams. Nothing else on the office segment needs to reach the camera segment.

That keeps the IT provider’s “deny by default between segments” approach intact, which is the point of having a camera VLAN. We give the IT contact the exact source, destination and port so the rule is written once and documented, rather than someone opening the whole camera network to the floor to make the problem go away.

When the PC and the recorder are in the same building, should the client reach the recorder by serial number or by local address?

By local address, almost always. Adding a device by serial number uses Dahua’s P2P service, which relays the connection through the internet even when the PC is twenty feet from the recorder. It is convenient for a laptop that travels, but it makes a lobby desk depend on the building’s internet line and on Dahua’s cloud being up. In March 2026 a Reddit user reported that Dahua called a P2P problem “a global issue” with no estimate for a fix, while the phone app still worked for him.

A device added by its reserved local address keeps working when the internet is down, which is exactly when the desk may need it. We reserve the recorder’s address on the building’s DHCP server or set it fixed, add it by IP, and leave P2P for the remote laptops that genuinely need it.

Our tenant firewall blocks unknown outbound traffic — can the desk client work with no cloud path at all?

Yes, for everything that happens inside the office. SmartPSS Lite talking to a recorder by IP on the same network needs no internet connection: live view, playback, export and local alarms all run between the PC and the recorder. What won’t work without a path out is P2P access by serial number, and any feature that depends on Dahua’s cloud.

For offices with a strict egress policy that is often the cleanest setup: the recorder has no route to the internet, the desk sees it locally, and anyone who must check from outside does it over the company’s VPN to the office network rather than through a vendor cloud. We set that up with the IT provider, not around them.

Big Buildings and the Limits of One Workstation

How should a security office with a few hundred cameras divide them between desk workstations and operators?

Start from the limit and from the people. Dahua’s datasheet caps a single SmartPSS Lite install at 64 devices and 64 video channels, and a Reddit user who hit it described the error appearing “as soon as more than 64 channels have connected to the software.” In a Manhattan complex with a garage, a courtyard, several lobbies and stairwells, three 32-channel recorders already pass it — and no single operator can watch that many tiles usefully anyway.

So we divide by duty, not by recorder. One workstation carries the entrances and package rooms the front post must see live; a second carries garages, loading docks and service corridors for the patrol supervisor; playback and export sit with the manager’s login. Each stays under the ceiling. Where the building wants one operator to call up any camera from one console, the answer is Dahua’s DSS server platform, built for central control rooms, with server hardware and licensing priced separately after a walk-through.

What does a security office need to run a four-screen camera wall from one workstation?

A PC with enough decoding power and enough video outputs, and a client set up with view groups. Dahua’s datasheet tests SmartPSS Lite on an Intel Core i5-6500 with 8 GB of memory, and quotes 64 channels of D1 — standard-definition — decoding on that machine. Modern cameras send far heavier streams than D1, so a wall of 4-megapixel or 4K cameras needs either a stronger PC or the sub-streams the recorder provides for multi-view.

Dahua’s wiki shows how to move a SmartPSS tab onto a second monitor. We build one view group per screen, set the walls to use sub-streams, check the CPU load with every screen running, and only then hand the room over. Where the load is too high, the answer is a better graphics card or fewer live tiles, not hoping.

How long does the client keep its own snapshots, alarm records and logs on the PC?

Dahua’s datasheet gives SmartPSS Lite a default storage time of 62 days for images and video saved by the platform and for its database, adjustable up to 365 days. That covers snapshots, clips recorded manually from the desk and the event records the client keeps. It does not change how long the recorder keeps its own footage, which depends on the recorder’s drive and recording settings.

For buildings with a footage-retention policy, the number that matters is the recorder’s. We set the client’s retention to match the policy so the PC doesn’t quietly hold copies longer than the building says it keeps them, and size the recorder drive for the days the policy names.

Footage Requests, Logs and Privacy

A detective asked for the lobby recording from one night — who at the building should handle it, and what goes in the hand-over?

One named person — usually the resident manager or the guard supervisor, not whoever is at the desk — should own the request, confirm it with the managing agent, and ask the detective what format they want. By default, give the original. SmartPSS Lite can clip and download recordings as .dav, .avi, .mp4 or .asf, according to Dahua’s monitor manual. The .dav file is Dahua’s native format and needs Dahua’s player, but it carries the recording as the recorder made it; .mp4 and .avi open anywhere but are converted copies. Many investigators accept either, and some want both: the native file with the player, and an .mp4 for quick viewing.

What we set up is the routine: search by time and camera, export a few minutes either side, save to a dated folder, copy to the medium the requester provides, and write the request in the log. We also check the PC and recorder clocks agree with each other, because a timestamp that is twenty minutes off is the first thing anyone questions.

Do face-detection alarms in SmartPSS Lite put our store under the city’s biometric signage rule?

Possibly, and it is worth getting right before switching anything on. Dahua lists face detection among SmartPSS Lite’s alarm types. NYC Administrative Code §22-1202 applies to retail stores, food and drink establishments and places of entertainment that collect, retain, convert, store or share customers’ biometric identifier information, defined to include a scan of face geometry, and requires a clear sign near all customer entrances.

Whether a given feature counts — detecting that a face is present versus recognising whose it is — is a question for the owner’s lawyer, not for an installer. Our practice is to leave face recognition off on retail floors unless the owner has made that decision in writing and posted the sign the city requires.

If the co-op adds face-reader entry managed from SmartPSS Lite, what does the Tenant Data Privacy Act ask of the board?

HPD’s guidance on Local Law 63 of 2021 says owners of multiple dwellings that use smart access systems — key fobs, RFID cards, phone apps, biometric identifiers or other digital technology — to grant entry to the building, its common areas or apartments must give tenants a data retention and privacy policy, and may not use the system to track people’s location outside the building. SmartPSS Lite can manage Dahua face-reader terminals and door controllers, so turning those on puts a building under that law.

The board should have its policy written and its counsel’s approval before enrollment starts. We set the terminals and SmartPSS Lite to keep no more than the policy allows and leave a note of where the data lives — on the controller, the PC, or both.

What should the desk write down each time someone views or exports footage?

Date and time of the request, who asked and on whose authority, which cameras and time range were viewed or exported, the file name and format, who received it and on what medium, and who at the desk did it. That is a one-line entry in a bound book or a shared sheet, and it is what lets a managing agent answer a shareholder or a lawyer months later.

Residents ask about this more than boards expect: one Reddit poster asked how to “force a landlord to show me the camera feed in the lobby,” and another wrote that “good management never gives security camera video to anyone except police.” A written log, alongside the building’s footage policy, is what keeps those conversations short.

Offices, Showrooms and Restaurants

Our office floor and the landlord’s lobby both run Dahua recorders — can one PC show both without blurring who controls what?

It can show both, as long as each recorder appears as its own device with its own login, issued by its own owner. The landlord gives the tenant a watch-only account on the lobby recorder, for the cameras it agrees to share; the tenant’s own recorder stays under the tenant’s admin. In SmartPSS Lite we put them in separate groups named for the owner, so nobody confuses a building camera with a suite camera when a request comes in.

What we won’t do is copy a landlord’s admin password into a tenant’s PC because it was the quickest way. When the lease ends, the landlord removes one account and the arrangement is over cleanly.

Will the attendance module work as a restaurant’s time clock?

For a single Dahua attendance terminal at the staff door, often yes. Dahua’s datasheet gives SmartPSS Lite’s attendance side capacity for 1,000 people, 32 shifts and 19 report types, and it handles schedules, leave and exception reports. It isn’t payroll software, so the hours still have to reach your payroll provider by export.

Two cautions for New York kitchens: a face-reading time clock collects employees’ biometric data, which deserves a written policy and legal advice before staff are enrolled; and the terminal should never sit where it can see a changing area. A card or PIN clock avoids the first issue entirely.

Arranging the Visit

What should be ready before the technician sits down at the desk PC?

Access to the PC with a Windows account that can install software, or an IT person who has one. Access to the room where the recorder is, and to the switch or firewall if the network has to change. The recorder’s admin password if anyone has it, and the name of the person who will own it at the end. A list of who uses the desk client and what each should be able to do.

Many Manhattan agents won’t let a vendor past the lobby without an insurance certificate naming them. Forward their wording when you book; the certificate goes to the agent a day or more before we arrive.

Does the building’s IT person have to be there for the visit?

Only if the network or the PC’s security settings have to change, and in Manhattan offices they usually do. A phone call at a set time is often enough: we tell them the one firewall rule and the one program approval we need, they make the change, we test. In residential buildings with no IT contractor, the managing agent’s office or the super with the router password fills that role.

What slows a visit is discovering on the day that nobody can approve the change. That is why we ask who controls the network when you book.