Wonderware Intouch Installation Guide Site

If InTouch WindowViewer must start after other applications (databases, OPC servers, etc.) at system boot:

Select this if you need to build and modify HMI screens (WindowMaker).

Ensure the password meets Windows complexity requirements and that you have full administrative rights to create local accounts.

Review the installation summary screen to confirm your selected features. Click . wonderware intouch installation guide

For more detailed technical specifications, you can refer to the official AVEVA InTouch HMI User Guide .

Wonderware InTouch (now part of the suite) follows a structured installation process that requires setting up system prerequisites, such as .NET Framework and SQL Server, before the core HMI components. 1. Pre-Installation Check

: The initial installation may be slower because prerequisite components are being installed. On subsequent installations (or reinstallations), the system will not re-prompt for prerequisites already present. If InTouch WindowViewer must start after other applications

Select "Development Workstation" if you plan to create applications, or "Runtime" for operator nodes only.

Minimum 8 GB (16 GB or higher highly recommended for development environments).

: Use the WWClient utility (run by typing WWClient in Start → Run) to directly test SuiteLink communications with configured DAServers. before the core HMI components.

Ensure your machine meets the minimum and recommended specifications to prevent performance issues during runtime.

Before running the installer, ensure your system meets the hardware and software specifications to avoid installation failures or performance bottlenecks. Hardware Requirements (Minimum vs. Recommended)

: Locate Setup.exe on your installation media and select Run as Administrator . Select Installation Type :

If you run into issues during setup, let me know. I can help you troubleshoot if you tell me:

The installer requires a dedicated Windows user account to manage background services and cross-node communication.