What is the best way to 'Publish' my application for thin Clients to connect

Hi David, 
I would say that best practice in this case is to set up a Terminal Server machine, since a Standard Server OS only supports two active sessions, and connect to it using RDP from the thin clients. This will require a Microsoft Terminal Server license though.

In regards of your statement that you don't want to direct them to your application on your Development PC, I assume you still want changes made to your development application to be distributed to your clients at some point?

You can update your application manually by publishing the application to the remote node. This requires some manual work, but the Terminal Server node is then not relying on the development node. 

https://docs.aveva.com/bundle/intouch-hmi/page/315538.html

But since you mention that you have a Stand alone InTouch application I would personally use NAD (Network Application Development) to ensure that modifications done to your development machine are distributed to your clients.

https://docs.aveva.com/bundle/intouch-hmi/page/315564.html

I'm now assuming that you are not distributing your applications from a galaxy using Application server, if this is the case, then NAD is not required and you can use the development and deploy mechanism within Application Server (Managed App).

Ensure that your Thin clients are connecting using different user accounts and InTouch will ensure that they get a "private working" directory for the application since running multiple sessions from the same application directory is not supported.

You can enable Terminal Server and run for 120 days without a license if you want to evaluate the solution before ensuring license.

Developing applications for multiple instances also requires you to make some decisions on how to manage Historical Logging (if used), Distributed and Historical Alarming (if used), IO Communications, but either way InTouch will support you in this with available features that enables Terminal Server and/ or multiple clients solutions.

https://docs.aveva.com/bundle/intouch-hmi/page/671434.html

I hope this get you started.

Hi David, 
I would say that best practice in this case is to set up a Terminal Server machine, since a Standard Server OS only supports two active sessions, and connect to it using RDP from the thin clients. This will require a Microsoft Terminal Server license though.

In regards of your statement that you don't want to direct them to your application on your Development PC, I assume you still want changes made to your development application to be distributed to your clients at some point?

You can update your application manually by publishing the application to the remote node. This requires some manual work, but the Terminal Server node is then not relying on the development node. 

https://docs.aveva.com/bundle/intouch-hmi/page/315538.html

But since you mention that you have a Stand alone InTouch application I would personally use NAD (Network Application Development) to ensure that modifications done to your development machine are distributed to your clients.

https://docs.aveva.com/bundle/intouch-hmi/page/315564.html

I'm now assuming that you are not distributing your applications from a galaxy using Application server, if this is the case, then NAD is not required and you can use the development and deploy mechanism within Application Server (Managed App).

Ensure that your Thin clients are connecting using different user accounts and InTouch will ensure that they get a "private working" directory for the application since running multiple sessions from the same application directory is not supported.

You can enable Terminal Server and run for 120 days without a license if you want to evaluate the solution before ensuring license.

Developing applications for multiple instances also requires you to make some decisions on how to manage Historical Logging (if used), Distributed and Historical Alarming (if used), IO Communications, but either way InTouch will support you in this with available features that enables Terminal Server and/ or multiple clients solutions.

https://docs.aveva.com/bundle/intouch-hmi/page/671434.html

I hope this get you started.