Plant SCADA 2023 Deployment Client connection

I have been trying to configure a deployment server and client in Plant SCADA 2023 this week.

I have got to the point of the client connected to the system management service but continually get the following message every time I try to configure the client:

"Deployment client could not be registered with the System Management Servers Identity Manager.

Does anyone have some pointers on how to resolve this? I would expect that if the client can successfully connect to the System Management Server then it should not be a connection issue between the two machines.

Jacky Lang over 1 year ago
Hi Mitchell Leask

Are your Deployment and System Management Servers installed and configured in separate machines?

Are you using local Windows account to configure these two servers

If yes for both, you are experiencing a known issue in Plant SCADA 2023, and there is no workaround. Consider installing both servers on the same machine or use a domain account to install and configure them.

Hope this would help
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Mitchell Leask over 1 year ago in reply to Jacky Lang

Hi Jacky,

Thanks for the reply.

The deployment and System Management Servers are installed on the same machine.

I am using a local windows account to configure these servers.

Are there other troubleshooting steps I can take?

Thanks,

Mitch
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Jacky Lang over 1 year ago in reply to Mitchell Leask

In that case, you should use the same local account to configure the deployment client. The same local account should be created on all nodes with the same password. This is because the deployment configuration is using the current user context (Windows logon user) for authentication. Try to log on the client node with the same account you use to configure the servers.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Mitchell Leask over 1 year ago in reply to Jacky Lang

Just to bring this up to date.

The issue was resolved by installing Plant SCADA 2023 Update 08. It appears that it was a bug that has been fixed in the latest update.

Thank again for your help.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel