Plant SCADA Access Anywhere Architecture - Server+Access Anywhere on other PC

We have performed some tests, but Citect Anywhere can in no way download it with such a license configuration form server in this configuration.

We also have tried to transfer license View Client to the VM machine PSANYWHERE and also receives software Protection Error

Hi Sebastian ,

It would be worth checking the command line argument (open Task Manager > Details > Right Click on Column > Select Columns > Command Line) and see what arguments are being used by the process. I have seen citect.ini file can have incorrect [Client]ComputerRole setting which can cause this issue. Look for the L argument below:

/L
This option allows you to specify which type of runtime license to consume. The syntax for this option is in the format /L:x, where x is one of license type options listed below:

0 = Full (default setting)
1 = View Only
2 = Control Client

Example: The /L:2 command will request a Control Client license

Also check that you are not using reservation feature in AEL. If you are, it must also have "Checkout" enabled, since the /x client process will add PID to end of the machine name when requesting the license.

Also check in Configurator that License Server is configured.

Hi Olivier,

I will check this commands.

I don't use reservation feature in AEL.

In Configurator Server i have configured Licence Server correctly , because I am able to connect in the local network to another PC with installed Plant Scada Runtime as one of client (Configurator Client connect to Licence Server) and i see in AEL (in use licence view).

My question how should i configure this to download the license through Access Anywhere to any computer in network (lan ,vpn) when i have licence server on on my PSSERVER (Win 11) and RDP PSANYWHERE (Win Server 2022) ?

In normal configuration I have always had a license server and RDP on the same machine.

 Hi Sebastian ,

There are two Windows user groups that are created on your Windows Server 2022 (PSANYWHERE server machine) on installation,

• SCADA.AnywhereControl
• SCADA.AnywhereView

When a new Anywhere (RDP) session is launched and signed in with a Windows user, PSANYWHERE server will evaluate which the user group this login user belongs to and then replicate the default citect.ini with the updated [Client]ComputerRole (1: Control; 2: ViewOnly) to

C:\Users\[login user]\AppData\Roaming\AVEVA Plant SCADA Access Anywhere\Launcher.

If AEL is configured on this PSANYWHERE, Plant SCADA will request an AEL license accordingly based on the ComputerRole setting when a new session is launched (Anywhere client). Each session is independent and an AEL license is issued with Process ID. 

If [Client]UseLocalLicense = 1 is set in the default citect.ini on PSANYWHERE, AEL will be bypassed and Anywhere clients will attempt to request floating licenses on the connected servers (PSSERVER).

Regards,

Jacky 

Hi Jacky,

Thanks to your hint now, it works and downloads a license from PSSERVER.

I had the user-rdp added to both groups (i delete now from AnywhereControl).

Hi Sebastian 

Thanks for the feedback and glad you have resolved the issue.

Hi Jacky Lang ,

We have Server Running Windows Server 2022, installed Plant SCADA Server 2023 R2 we will attempt to install Plant SCADA Access Anywhere 2023.
We have One Plant SCADA Full Server License (Including Server and Control Client License) - Softkey

If we install the Plant SCADA Access Anywhere server on the same machine as the Plant SCADA Server can we use that same Full license for the access anywhere session?

Mohannad Naser 

Hi Mohamed Keshk 

I assume you are using AEL for the Softkey?

The Server License (Full license) will be consumed by the Plant SCADA Server. If it is running as a Windows Service, it does allow one Client that is local to the machine to consume that license (you must run with /O argument or the citect.ini setting [Client]UseLocalLicense=1). So this could in theory be consumed and used by one Access Anywhere Session. But I think this might not work, with the additional Control Client license (hosted on the AEL Server), since any additional Access Anywhere sessions will also run with the "UseLocalLicense" setting and won't ever try to communicate with the AEL Server.

What we typically see in these types of architectures is the following:

1 Server License

250 Client Pack (Control Client and/or View Only types)

So when the Plant SCADA Server consumes the Server license, it also grabs the 250 Client pack. This will then be made available to local client sessions (like Access Anywhere sessions or other RDP clients) via the "UseLocalLicense" setting. They could also be made available to remote client machines via the "Floating License Mechanism" - basically the client when connecting to the Server will ask for a license over its connection.

There is a TechNote I'd recommend you take a look at: https://softwaresupportsp.aveva.com/en-US/knowledge/details/000034663?lang=en_US

Kind regards

Olivier

Hi Mohamed Keshk 

I assume you are using AEL for the Softkey?

The Server License (Full license) will be consumed by the Plant SCADA Server. If it is running as a Windows Service, it does allow one Client that is local to the machine to consume that license (you must run with /O argument or the citect.ini setting [Client]UseLocalLicense=1). So this could in theory be consumed and used by one Access Anywhere Session. But I think this might not work, with the additional Control Client license (hosted on the AEL Server), since any additional Access Anywhere sessions will also run with the "UseLocalLicense" setting and won't ever try to communicate with the AEL Server.

What we typically see in these types of architectures is the following:

1 Server License

250 Client Pack (Control Client and/or View Only types)

So when the Plant SCADA Server consumes the Server license, it also grabs the 250 Client pack. This will then be made available to local client sessions (like Access Anywhere sessions or other RDP clients) via the "UseLocalLicense" setting. They could also be made available to remote client machines via the "Floating License Mechanism" - basically the client when connecting to the Server will ask for a license over its connection.

There is a TechNote I'd recommend you take a look at: https://softwaresupportsp.aveva.com/en-US/knowledge/details/000034663?lang=en_US

Kind regards

Olivier