﻿PLAIN TEXT EDITION
Same instructions as the Word manual. Page references refer to the Word/PDF edition.
In Notepad, enable Word Wrap for easier reading.

RHS ATE PC Installation Guide

NoTraffic  |  Technician procedure  |  Version 0.2  |  September 29 2026

Use this guide to prepare an RHS ATE station with the Software2 package. Start with the administrator setup, then complete the production-user and VPN checks. The script ending successfully does not replace the final station test.

1 Prepare the station

- Use 64-bit Windows 11 with the required International and LocalAccounts PowerShell commands. English (United States) display-language resources must already be installed.

- Have working internet access, existing administrator credentials, and the station-specific VPN profile from DevOps. NI online installers and Python packages still require internet access.

- Confirm the standard production account, normally ProductionLine. Sign into it once to create its Windows profile, then sign out. Setup will ask you to confirm this account.

- Have the approved NoTraffic NI account and Development serial available from IT. Keep credentials in the approved credential store.

2 Extract the package

Download the current Software2.zip from the approved distribution location. If the ZIP Properties dialog offers Unblock, select it. Extract into C:\admin so the launcher is at:

C:\admin\Software2\RHS_ATE_Setup.cmd

Use a fresh folder. Do not mix old setup scripts or manually renamed .txt copies into this package. The launcher and PowerShell script must remain beside the installers.

3 Start administrator setup

Right-click RHS_ATE_Setup.cmd and select Run as administrator. Enter existing administrator credentials if requested. ATEAdmin is created by setup if missing; it is not required to exist beforehand.

At the production-account prompt, press Enter for ProductionLine or enter the correct account, such as DOMAIN\username. Confirm the displayed profile is the intended operator profile. If it does not exist, sign into that account once and rerun.

Continue with the prompts on page 2. Logs and resume records are stored in C:\ProgramData\RHS-ATE-Setup.

Administrator setup and activation

4 Complete the installer sequence

The script unblocks all files in the extracted package and its subfolders. It applies US language defaults, ensures ATEAdmin belongs to the local Administrators group, and runs the bundled installers one at a time.

Installation order: NI-VISA, NI-DAQmx, NI TestStand, OpenVPN, Python 3.12 with custom settings, Python requirements and dependency check, then the operator interface (mysetup.exe).

Complete each wizard with default options unless page 5 specifies otherwise. For NI, wait until NI Package Manager has finished and reported success before typing YES in the script window.

Choose Restart later in installer dialogs when available. If the script reports restart required, restart Windows and run the same launcher as administrator. Use the same administrator account. Completed installer steps are retained.

If an installer fails or returns an unverified status, setup stops. Resolve the error before rerunning; do not treat an error code as success. See page 4 for recovery.

5 Activate NI TestStand

Confidential - authorized technicians only. This section contains account credentials. Do not distribute these manuals publicly.

1. Open Windows Start, type "NI License Manager", and open the application.

2. Click Activate Software.

3. Enter the following account credentials:

Username: corpit@notraffic.com

Password: ^9Uwz#HjtO@xu3$u

4. In the activation-method dropdown, select Serial Number.

5. Select the Developer option.

6. Enter serial number D11L1071292.

7. Click Activate and verify that activation succeeds.

Close TestStand and the operator interface, then type YES in the script window. Setup now backs up the existing system Cfg directory and copies the bundled configuration contents into it. Matching files are overwritten and verified.

6 Apply the production user configuration

The script copies UserInterface.xml into the confirmed production profile after mysetup.exe has completed. An existing XML file is backed up first. For ProductionLine, the destination is:

C:\Users\ProductionLine\AppData\Local\National Instruments\TestStand 2023 (64-bit)\UserInterface.xml

The path above wraps for readability; it is one continuous path. On repeat runs, already applied configuration is preserved. Only type REAPPLY if you intend to reset system configuration from the package.

Finish under the production account

7 Restart and check user settings

Restart Windows and sign in as the standard production user. Check Windows display language, preferred language, keyboard, regional format and country: English (United States), US keyboard, and United States.

The administrator script updates its own user settings, the welcome screen and defaults for new profiles. Existing production profiles must be checked separately. Adjust them through Windows Settings if necessary.

8 Install Visual Studio Code

Run VSCodeUserSetup-x64-1.92.2.exe from Software2 normally under the standard production account. Do not choose Run as administrator. Enable Add to PATH and Register as an editor for supported file types when offered.

9 Set the station globals

Open the following sequence in the TestStand Sequence Editor:

C:\Users\Public\Documents\TestExe\exampleTemplate 2022.seq

Copy the value of FileGlobals.Info to StationGlobals.Info, save the station globals, and verify that station-specific values are correct with the ATE owner. Do this after the bundled Cfg copy. Confirm the operator interface opens with the expected settings.

10 Configure the unique VPN profile

Obtain the .ovpn profile assigned to this PC from DevOps. Never reuse another station's profile. The generic Software2 package does not contain a VPN profile.

Configure OpenVPN GUI using the connection file assigned to the computer you are currently setting up:

1. Open C:\admin\Software2\VPNFiles\Used VPN File Connections.txt.

2. Find your computer name and note the associated .ovpn file.

3. In the taskbar, right-click the OpenVPN GUI icon.

4. Select Import, then select Import file.

5. Browse to C:\admin\Software2\VPNFiles.

6. Select the .ovpn file noted in step 2 and add it to OpenVPN GUI.

For the required connection at user login, use the OpenVPN GUI approach: import the assigned profile while signed in as the production user, connect manually, and verify access to the required database or application.

Have IT configure the GUI to launch at that user's login with the approved profile selected for connection. The documented GUI argument is --connect followed by the profile name. Authentication requirements must permit the intended automatic connection.

Do not also configure the same profile for service-based automatic connection. A profile placed in config-auto represents a different service workflow; confirm that approach with IT before using it. The script does not configure either VPN startup mechanism.

Restart, sign into the production account and confirm the VPN connects without a manual Connect action. Verify database access; a running tray icon alone is not a successful test. Record IT follow-up if automatic connection is not working.

Verification and recovery

11 Complete the acceptance checks

- Under the production account, confirm US English, US keyboard and US regional settings after restart.

- Launch Python, VS Code, TestStand and the operator interface without errors.

- Confirm the correct NI license is active and StationGlobals.Info contains the correct station values.

- Verify automatic VPN connection after login and access to the required RDS database or application.

- Run a representative ATE test and verify expected results, including result uploads where required.

From a new PowerShell window, check the intended Python installation:

C:\Python312\python.exe --version
C:\Python312\python.exe -m pip check

Record the PC name, production account, date, technician, package version, test result and any outstanding items in the ticket. Do not mark the station ready while required checks remain incomplete.

If setup stops

Message or symptom: Script execution blocked | Action: Run RHS_ATE_Setup.cmd as administrator. It starts PowerShell with a session-only execution-policy bypass.

Message or symptom: Installer error including -125071 | Action: Read the installer message and setup log. Resolve the cause before rerunning. This code is not accepted as success.

Message or symptom: Restart required | Action: Restart Windows and rerun the same launcher as the same administrator.

Message or symptom: Production profile missing | Action: Sign into the intended production account once, sign out, and rerun.

Message or symptom: pip is not recognized | Action: Use the explicit python.exe -m pip command below. For dependency or network errors, inspect the actual pip output.

C:\Python312\python.exe -m pip install -r "C:\admin\Software2\requirements.txt"

Logs, completed.json and configuration backups are in C:\ProgramData\RHS-ATE-Setup. Resume records track work completed by this script; they do not detect subsequent software removal. Ask IT before clearing records or restoring a configuration backup.

Installer reference

Use this page to check versions or perform a manual recovery. The normal process is the launcher on page 1; do not repeat successful installations unnecessarily.

Component: NI-VISA | Bundled installer: ni-visa_25.8_online.exe

Component: NI-DAQmx | Bundled installer: ni-daqmx_26.3_online.exe

Component: NI TestStand | Bundled installer: ni-teststand-2023_23.8_online.exe

Component: OpenVPN | Bundled installer: OpenVPN-2.7.4-I001-amd64.msi

Component: Python | Bundled installer: python-3.12.0-amd64.exe

Component: Operator interface | Bundled installer: mysetup.exe

Component: VS Code | Bundled installer: VSCodeUserSetup-x64-1.92.2.exe

Python custom installation

Choose Customize installation when installing manually. Apply these settings:

- Installation directory: C:\Python312. Enable Add python.exe to PATH.

- Select documentation, pip, Tcl/Tk and IDLE, Python test suite, and the py launcher.

- Install the py launcher for all users, using administrator privileges. This is separate from the Python all-users option.

- Enable file associations, application shortcuts and Add Python to environment variables.

- Leave Install Python for all users unchecked, matching the approved original screenshots.

- Leave precompile standard library, debugging symbols and debug binaries unchecked.

Python remains registered to the setup account. The script also adds C:\Python312 and C:\Python312\Scripts to the machine PATH without adding duplicate entries. Open a new terminal or sign in again to receive the updated PATH; test Python under the production account.

Additional prerequisites

requirements.txt lists Python packages, but some packages depend on separate software. Where those features are used, install the approved Tesseract OCR engine and Microsoft Visual C++ 2013 Redistributable x64. The current script does not install these prerequisites.

MobaXterm is not included in this package. Add it through the approved software process if required for the station.

File locations and package maintenance

Keep the three file purposes separate

System configuration: copy the contents of Software2\cfg into the destination below. Do not create an additional Cfg\cfg level. The script performs this copy after activation and retains a backup.

C:\ProgramData\National Instruments\TestStand 2023 (64-bit)\Cfg

Python dependencies: keep requirements.txt beside the setup script. It is input to pip; do not copy it into TestStand Cfg.

User interface configuration: UserInterface.xml belongs under the production user's AppData\Local\National Instruments\TestStand 2023 (64-bit) directory. The script resolves that profile by account identity and backs up an existing file.

Package maintenance

- Maintain one current RHS_ATE_Setup.cmd and RHS_ATE_Setup.ps1. Keep backups, old scripts and machine-specific VPN profiles outside the release ZIP.

- Bundle the approved installers, requirements.txt, UserInterface.xml, cfg\cfg, this manual and READ_ME_FIRST.txt.

- Rebuild Software2.zip with a single top-level Software2 folder. Update the distribution copy before asking technicians to download it.

- After changing configuration sources or package versions, test on a station before wider deployment. Confirm with the ATE owner which Drive revision belongs in the release.

Source references

Latest supplied draft: ATE_PC_Installation_Guide (5).docx. Its Drive links remain references for package maintenance; setup uses the bundled files and does not download from Drive.

Configuration references
https://drive.google.com/drive/folders/1ktfzxMQ7My9dGir6rs5mPIv_K0w9gcV4
https://drive.google.com/drive/folders/1DSjZ0O5Kto2jz0JX0OKVC5IUslPJMNcD
Requirements and user interface reference
https://drive.google.com/drive/folders/1hfLUxF-NkPFcOP4ssL-iuPQAKDk59bgn

Technical references: Python 3.12 Windows installer options at docs.python.org/3.12/using/windows.html; OpenVPN GUI connection arguments at community.openvpn.net/Pages/OpenVPN-GUI-New.

Revision record

Version 0.2 - September 29 2026. Consolidated the installation procedure, corrected file destinations, added activation and production-profile handling, and aligned the guide with local-package setup and recovery.
