Vendor access
This part is for Aigna staff
Vendors see their own installation and the device reference they need to build it: device types, setup guides and models. Everything else stays with Aigna.
Go to your installationModule
Projects is switched off
Projects, the schedule, planning, the work plan and the Lab. This demo has the Projects module switched off in Organisation settings.
Batch 2 of 8 · Project PRJ-10Simulated live
2 video bars
1 unit to review · 1 of 2 set upchecked just now
Setup is done by Aigna's engineers. Your installs are on the Deploy page.
Once for all 2
Through Fleet Lens, the Chicago office policySetup guide applied through Fleet Lens, the Chicago office policy. Read back from 1 of 2.
26 settings to set and 14 to check; 37 left at the manufacturer's default.See every settingThe setup guide
The same on every unit
- Location
- United States
- Time Zone
- America/Chicago
- Contact details
- Chicago office AV team, av-support@aigna.example
- Time Server
- Manual
- Primary Time Server Address
- ntp1.aigna.example
- Secondary Time Server Address
- ntp2.aigna.example
and 12 more, all in the setup guide
The units
Only what differs per unit. Each unit's build sheet has every setting worked out.Automatic updates: On. Fleet Lens turned them back on (advisory ADV-001).
Reapply the setup guide to this unit.
| Unit | Hostname | Pairs with | Provision | Install | Configure | |
|---|---|---|---|---|---|---|
| Build sheet | chi-1208-vc0110.40.12.214 | chi-1208-tc01 | ||||
| Build sheet | chi-1301-vc0110.40.13.50 | chi-1301-tc01 | ||||
Setup order
Optional: tick as you go, or let the checks do it1Pre-flight2/2
Confirm the model is supported and a Google Meet licence is free. The port gives DHCP and NTP and reaches zto.poly.com, lens.poly.com and swupdate.lens.poly.com on 443. Stage on a port without 802.1X. In Poly Lens, set the site policy to no automatic updates before the device arrives.
Do this before the steps after it.
2Connect HDMI, Ethernet, then power2/2
Note the IP address shown on screen. The default login is admin with the last six characters of the serial number.
Do this before the steps after it.
Why this order
The first boot goes straight to Poly's zero touch service. On a port without the right access it stalls or picks the wrong mode.
3Complete the setup prompts2/2
The device contacts Poly's zero touch service to choose its mode. Do not pick a provider yet.
Do this before the steps after it.
4Log in and set the admin password2/2
Security > Local Accounts
Use the site's password from the vault. Do this before pairing the TC10.
Do this before the steps after it.
Why this order
From 4.6.0 setup forces a new password, and every later step needs the admin login.
5Turn off automatic updates2/2
General Settings > Device Management
Clear Enable Automatic Updates, and check Only Check for Updates During Maintenance Hours is not quietly on. Do this before choosing Google Meet and before Poly Lens.
Do this before the steps after it.
Why this order
Device Management is behind the admin login.
6Country, time zone and time server2/2
General Settings > My Information > Location, then Date and Time
The default zone is US Central. Dublin and London share one zone value.
7Device name, room name and contact2/2
General Settings > System Settings
The hostname, the room number and name, and the site's AV team as contact.
8Choose Google Meet as the provider2/2
General Settings > Provider
Save, and the device restarts. Needs 4.0 or later (4.1 on the X52).
Do this before the steps after it.
Why this order
Automatic updates are on by default in Google Meet mode. Left on, the device can fetch VideoOS 5 as soon as it restarts, and version 5 has no Google Meet and cannot be rolled back.
9Enrol in the Google Admin console2/2
Devices > Google Meet hardware
Use the code on screen, name it the hostname and assign the room calendar.
Why this order
The enrolment code only appears after the restart into Google Meet.
10Pair one TC102/2
General Settings > Device Management > Available Devices
Same subnet and VLAN as the video bar. Pair it by its MAC address.
Why this order
Poly's guide has the admin password set before the TC10 pairs.
11Register to Poly Lens, then recheck updates2/2
Servers > Cloud
Open Device Management again after registering and check updates are still off.
Do this before the steps after it.
Why this order
Lens provisioning can turn automatic updates back on and make the device's own control read-only. With updates already off and the site policy set in pre-flight, nothing downloads in between.
12Hardening2/2
Security
Password rules, account lockout, idle timeout, Telnet and SSH off, SNMP v3 only if SNMP is ever used.
13Network extras last2/2
Network > LAN Network > LAN Options
LLDP, then proxy or VLAN tagging only at a site that needs them. 802.1X only where the site uses it, after its certificate is installed.
Why this order
A wrong VLAN or 802.1X setting cuts the device off. Do it once everything else is saved, and install the 802.1X certificate first.
14Verify2/2
Diagnostics > System Status
Check System Status, Servers > Cloud, the Google Admin console and Device Management. Then run the space's verification.
Every setting
40 in the setup guide, as patternsValues marked Per unit are patterns here. Each unit's build sheet has them worked out: chi-1208-vc01, chi-1301-vc01.
Dashboard1
- System detailsDashboardCheck it is Model, serial, software 4.6.x, Google Meet
Why
The first page after login. A glance confirms you are on the right device and the right software line.
System Settings2
- Device NamePer unitGeneral Settings > System SettingsSet to The hostnameWorked out on each build sheet
Why
Matches DNS, device management and monitoring, so one name finds the device everywhere. 40 characters at most.
- Room NamePer unitGeneral Settings > System SettingsSet to Room number and nameWorked out on each build sheet
Why
Shown to people at the far end. 32 characters at most.
My Information2
- LocationPer unitGeneral Settings > My Information > LocationSet to The site's countryWorked out on each build sheet
Why
Sets the power-line frequency, which stops the camera flickering under the space's lights.
- Contact detailsGeneral Settings > My InformationSet to The site's AV team and support address
Why
Anyone who opens the web interface knows who looks after the space.
Date and Time5
- Time ZonePer unitGeneral Settings > Date and TimeSet to The site's time zoneWorked out on each build sheet
Why
Meeting times on the touch controller must match the room calendar. The label Dublin shows under is not confirmed; it shares a value with London.
- Time ServerGeneral Settings > Date and TimeSet to Manual
Why
Use Aigna's time servers, not whatever the network offers.
- Primary Time Server AddressGeneral Settings > Date and TimeSet to ntp1.aigna.example
Why
A working time server is needed to reach Poly's zero touch onboarding.
- Secondary Time Server AddressGeneral Settings > Date and TimeSet to ntp2.aigna.example
Why
A second server, so one failure doesn't stop onboarding.
- Auto Adjust for Daylight Saving TimeGeneral Settings > Date and TimeSet to On
Why
No one has to touch the clock twice a year.
Provider1
- ProviderGeneral Settings > ProviderSet to Google Meet
Why
Aigna meets on Google Meet. Choose it only after updates are off.
Device Management4
- Enable Automatic UpdatesGeneral Settings > Device ManagementSet to Off
Why
Version 5 drops Google Meet and can't be rolled back. Firmware changes only after the Lab passes it. The on-device default is from the parameter reference, not tested on a unit.
- Only Check for Updates During Maintenance HoursGeneral Settings > Device ManagementCheck it is Off
Why
If this is on, the device still checks for updates at night. Check it is off. Its default is not documented.
- Maintenance Hours Begin and EndGeneral Settings > Device ManagementSet to 01:00 to 04:00, local time
Why
Any restart happens when no one is in the space.
- Download Update FromGeneral Settings > Device ManagementCheck it is Poly Online Support Center
Why
Updates come from Poly, but only when Aigna chooses to apply one.
Cloud1
- Cloud registrationServers > CloudSet to Registered to Aigna's Poly Lens account
Why
Poly Lens holds the site policy and shows the fleet. Recheck updates afterwards.
SNMP1
- Enable SNMPServers > SNMPCheck it is Off
Why
Monitoring uses Poly Lens and pings, so SNMP stays off.
LAN6
- IP addressNetwork > LAN Network > IP AddressesCheck it is DHCP (reserved)
Why
The address is reserved on the DHCP server, so the device stays on DHCP.
- Host NamePer unitNetwork > LAN Network > LAN OptionsSet to The hostnameWorked out on each build sheet
Why
The same name as the DNS record.
- Domain NameNetwork > LAN Network > LAN OptionsSet to aigna.example
Why
Completes the full name the certificate and monitoring use.
- Enable LLDPNetwork > LAN Network > LAN OptionsSet to On
Why
The switch learns what is plugged into each port, which keeps the port map true.
- 802.1p/QNetwork > LAN Network > LAN OptionsCheck it is Off
Why
The switch port puts the device on the AV VLAN, so the device doesn't tag its own traffic.
- Enable EAP/802.1XNetwork > LAN Network > LAN OptionsCheck it is Off
Why
Aigna's AV ports authenticate devices at the switch instead.
Local Accounts2
- Admin passwordPer unitSecurity > Local AccountsSet to From the password vault, per siteWorked out on each build sheet
Why
The default is printed on the device. From 4.6.0 setup forces a new one.
- Room passwordPer unitSecurity > Local AccountsSet to From the password vault, per siteWorked out on each build sheet
Why
Protects the space's settings on the TC10. Same reason as the admin password.
Password Requirements1
- Password rules and lockoutSecurity > Password RequirementsSet to 12 characters minimum, lockout after 5 tries
Why
Stops guessing the admin password from the AV VLAN.
Access5
- Web accessSecurity > AccessCheck it is On
Why
Turning it off breaks TC10 pairing.
- Idle session timeoutSecurity > AccessCheck it is 10 minutes
Why
An open admin session closes itself.
- Minimum TLS versionSecurity > AccessCheck it is 1.2
Why
Older TLS is refused.
- SSHSecurity > AccessCheck it is Off
Why
No remote shell on room devices.
- TelnetSecurity > AccessCheck it is Off
Why
Telnet sends the password in clear text. Check it is off.
Diagnostics1
- System StatusDiagnostics > System StatusCheck it is All green
Why
The last check before the space goes back into service.
Poly Lens3
- Onboarding methodPoly Lens (cloud) > OnboardingCheck it is DHCP, not a PIN or QR code
Why
Poly Lens policies don't apply to devices onboarded with a PIN or QR code.
- Policy levelPoly Lens (cloud) > PoliciesSet to Site
Why
Policies apply device first, then group, site and account; per-site policies carry each site's time zone and country.
- Software updates in the policyPoly Lens (cloud) > PoliciesSet to Off
Why
Lens provisioning can turn updates back on and lock the device's own controls.
Google Meet4
- Enroll a device with a codePer unitGoogle Admin console > DevicesSet to Device name: the hostnameWorked out on each build sheet
Why
Each device uses one Meet hardware licence; the same name as everywhere else.
- Room calendarPer unitGoogle Admin console > Device settings > CalendarSet to The space's calendar resourceWorked out on each build sheet
Why
The touch controller shows the space's meetings and joins them in one tap.
- Time zonePer unitGoogle Admin console > Device settingsSet to The site's time zoneWorked out on each build sheet
Why
Must match the device and the calendar.
- Scheduled rebootGoogle Admin console > Device settingsSet to Daily, inside the maintenance hours
Why
A fresh start each night, when no one is in the space.
Outbound access1
- Outbound accessFirewall (network team)Set to 443 to zto.poly.com, lens.poly.com and swupdate.lens.poly.com
Why
Onboarding, Poly Lens and software downloads all need these. Not confirmed whether blocking the update host also blocks the Meet package.