Agilent CrossLab Start Up Services Agilent Cary UV Workstation Plus 1.6 Software Site Preparation Checklist

Agilent Cary UV Workstation Plus 1.6 — Site Preparation and Software Requirements: Executive Summary

Importance of the topic

The software site-preparation checklist for Agilent Cary UV Workstation Plus 1.6 sets the foundation for reliable instrument operation, regulatory compliance, and efficient commissioning. Proper preparation reduces installation delays, prevents data loss, and ensures that system services (instrument discovery, data storage, and report export) function in daily laboratory workflows. This document is essential for laboratory managers, IT administrators, and service engineers who must coordinate hardware, network, and security prerequisites prior to installation.

Objectives and overview of the checklist

• Define customer responsibilities and pre-install actions to avoid rescheduling of installation services.
• Specify supported software and operating-system configurations and required add-ons.
• Detail recommended workstation hardware and network interface requirements for instrument control.
• Provide firewall and antivirus guidance, including the ports required for internal services and instrument communication.
• Identify upgrade pathways and constraints for previous software versions.

Customer responsibilities

• Provide an appropriately configured PC and physical bench/network connectivity for the instrument and software.
• Ensure current Windows updates and necessary .NET components are installed before installation.
• Gather sales order details, software authorization codes and backups of existing data when upgrading.
• Have a system/network administrator available to connect to the intranet or domain, and designate a local administrator account for installation tasks.
• Disable or remove unvalidated third-party antivirus/firewall products before installation, or be prepared to open required ports manually.
• Be present during installation (especially if installation and introduction services were purchased) to capture operational and safety information.

Methodology and configuration requirements

• Operating systems: 64-bit Windows 10 (21H2) or Windows 11 (21H2) or later. Specific .NET components (.NET 3.5, .NET 4.8 Advanced Services, .NET Core 6.x) must be available; the System Preparation Tool installs required components when needed.
• Language/localization: English validated version; simplified Chinese and Japanese supported when appropriate system fonts are present.
• Browser and document viewers: modern Chrome or Edge desktop browsers with JavaScript enabled for online help; Adobe Acrobat Reader DC for documentation.
• Database: PostgreSQL is used for data storage; only the PostgreSQL instance bundled with the product is supported.
• Power management: disable sleep and other power-saving features to prevent data loss and ensure stable instrument control.

Computer, peripheral and network hardware

• Recommended workstation: desktop-class PC equivalent to an HP z2 G9; processor Intel i5 or equivalent, 3.0 GHz or greater, 6-core recommended.
• Memory and storage: minimum 16 GB RAM, 512 GB SSD recommended.
• Display and input: resolution 1600×900 minimum (1920×1080 recommended), mouse, and at least one USB 2.0 port.
• Network: the controlling PC requires a Gigabit-capable NIC for instrument communication. A second NIC or an external switch is recommended when the PC also needs intranet access.
• Instrument discovery: the Cary 3500 uses Zeroconf (mDNS) for automatic discovery and DHCP by default; direct LAN-to-PC connection is the common configuration.

Networking, firewall and security considerations

• The installer configures exceptions in the Windows Firewall under the domain profile; third-party firewalls must be pre-configured or disabled prior to installation.
• Key services require specific TCP/UDP ports for REST APIs, licensing services, data collection, and instrument mDNS discovery. Examples include standard web ports and several application-specific ranges—these must be opened between system components and the controlling PC.
• For domain-based deployments, use an appropriate service account (non-expiring or annually renewed) if user credentials are required for backend services. If domain authentication is used, ensure the service account has rights to read necessary Active Directory attributes when applicable.
• For environments subject to data-security regulations, ensure network time synchronization is in place and users do not operate as local administrators, preventing unauthorized time changes that could affect electronic signatures and audit trails.

Upgrade and compatibility notes

• Direct upgrades supported only from versions 1.4 or 1.5 to 1.6. Older versions (1.2 or earlier) require staged upgrades (first to 1.4), and intermediate upgrades are not included in the standard upgrade service.
• Upgrading from certain older Plus versions may require manual adjustments: complete outstanding e-signature workflows prior to upgrade; reapply signature settings and reconfigure roles where privileges have been moved to shared services.
• Cary UV Workstation Plus is not compatible with certain Agilent products (examples listed in the original checklist); verify the planned software ecosystem before installation.

Used instrumentation and software components

• Cary 3500 UV-visible spectrophotometer (network-capable; Zeroconf and DHCP supported for discovery).
• Cary UV Workstation Plus 1.6 software suite (includes PostgreSQL bundled for data storage).
• Recommended PC hardware (example: HP z2 G9 or equivalent), Windows 10/11 64-bit environments, and modern browsers (Chrome/Edge).
• Windows Defender is the only validated anti-malware tool; other security products have not been validated and should be disabled/removed prior to installation.

Main outcomes and discussion points

• When the checklist is followed, installation and configuration are streamlined, decreasing the likelihood of delays and failed installations due to missing OS updates, insufficient privileges, or firewall restrictions.
• Using direct LAN connections simplifies instrument control; however, integrating the PC into a domain or intranet adds complexity around credentials, service accounts, and drive-access rights for report export.
• Data integrity and regulatory compliance depend on appropriate backup strategies, time synchronization, and correct handling of e-signature workflows during upgrades.

Benefits and practical applications

• Reduces installation time and service costs by eliminating preventable setup issues.
• Ensures instrument control reliability, consistent data capture, and safe export of analytical reports in regulated and non-regulated labs.
• Provides clear responsibilities for IT and laboratory staff, improving coordination between vendors and customer teams during commissioning.

Future trends and potential applications

• Tighter integration with laboratory networks and shared services will drive the need for standardization of service accounts and hardened firewall rules across instrument fleets.
• Cloud-assisted services, more automated deployment tools, and containerized database components may simplify future installations and upgrades while improving reproducibility.
• Growing regulatory focus on cybersecurity and auditability will increase emphasis on validated antivirus solutions, stricter time synchronization controls, and centralized log collection for forensic readiness.

Conclusion

Adhering to the Cary UV Workstation Plus 1.6 site-preparation checklist mitigates many common installation risks, supports compliant laboratory operations, and streamlines post-install workflows. Early coordination between laboratory staff, IT, and Agilent service teams ensures the necessary OS updates, privileges, network configuration, and backup strategies are in place so the instrument and software deliver reliable, long-term performance.

Reference

• Agilent Cary UV Workstation Plus 1.6 — Software Site Preparation Checklist, Revision A.00, Issued 01 Aug 2025 (internal Agilent installation and system requirements document).