The main reason why this watermark is showing up is due to the LabVIEW VIs that TestStand is using were opened and saved last time with an evaluation version of LabVIEW.
In order to solve this issue, you can follow one of the following approaches:
- Mass compile VIs using an activated version LabVIEW and then redeploy
- Configure LabVIEW adapter to execute using the LabVIEW Run-Time Engine on the deployment machine
- You must open the VIs with a licensed version of LabVIEW and just save them again. This will prevent the watermark to keep showing up in the TestStand sequence.