What's new in viewLinc 5.2

viewLinc 5.2 strengthens security, expands device support, and keeps your monitoring system aligned with current platform requirements—so you can maintain reliable alarming, reporting, and supportability over the long term. Older viewLinc versions can require server operating systems that are no longer supported, which increases cybersecurity and compliance risk and limits escalation options. Updating to viewLinc 5.2 helps keep your monitoring system on supported, maintainable infrastructure.

If your alarm emails rely on Microsoft 365 basic authentication, changes in Exchange Online authentication can disrupt SMTP-based alarm email delivery unless your environment is updated and configured for modern authentication. Microsoft has been removing basic authentication across Exchange Online and has published a staged deprecation path for SMTP AUTH basic authentication. 

Recommendation: Review your tenant’s SMTP AUTH / authentication settings and update your viewLinc environment to reduce the risk of missed alarm notifications.

• Manage users and groups directly in Windows Active Directory (AD).
• Selected AD users and groups can be created automatically in viewLinc.
• Changes to user status or group membership synchronize to viewLinc.
• Secure authentication against Active Directory.
• Consolidate user management and reduce duplication of effort.

viewLinc 5.2 includes additional alarms to help you detect risk earlier and improve visibility during communication interruptions:
• Alarms that highlight the potential for out-of-spec conditions even when data is incomplete.
• Alarms for delayed-but-incoming data (for example, during backfill after a communication interruption).
• Alarms for unrecoverable measurements (for example, if a probe is removed from a data logger).

• TLS support aligned with current security expectations (including TLS 1.3 in server requirements for the web interface and secure email protocol). 
• Encrypted data handling and improved protection against tampering (where applicable to configuration and deployment).

viewLinc 5.2 supports newer device families and capabilities including: VaiNet wirless RFL100 data logger, VDL200 multi-parameter PoE data logger, and the ANP115 Analog Input Probe support (via VDL200). 
Using ANP115 with VDL200 expands the types of measurements you can bring into viewLinc, including:

• Door switches
• Differential pressure
• Flow
• Fluid level
• Electrical properties
• Gas concentration

viewLinc 5.2 supports global teams with a consistent user experience across regions and sites. Now available in 11 languages, including Korean (added in viewLinc 5.2), helping standardize training, reduce translation workarounds, and improve day-to-day usability for local operators—while maintaining a common system for enterprise reporting and compliance documentation.

Vaisala supports viewLinc customers through updates in a way that fits validated, change-controlled environments. Because viewLinc is designed as a closed system for regulated use (with access control, audit trails, and data integrity features aligned to 21 CFR Part 11 expectations), updates aren’t “automatic” in the consumer-software sense. Instead, we help customers choose the right timing and the right reason to update—whether the driver is a critical fix, a security enhancement, a new feature that matters to their workflow, or enabling new hardware for expansion.

Practically, our support centers on a well-documented, low-risk update pathway: we provide guidance to back up the system before changes, publish detailed release/errata documentation describing code fixes, features, and hardware enablement, and give recommendations for maintaining validation status. Where appropriate, we also help customers right-size validation effort—for example, by pointing to specific IQ/OQ sections to re-execute after a service update (based on the change scope and the customer’s internal risk assessment and quality procedures). And when customers have questions—“Should we update now, or wait?”—they can call us to review what’s in the release and what’s coming next, so updates can be planned around real needs rather than done by habit.