Advice for re-doing vision client connection across many clients?

Ignition
,
1

Using Ignition 8.1.26.

I have a project that has about 70 vision clients. They were initially setup to find the gateway/project via IP but really they should be done by hostname as on occasion the servers have had to be moved to different machines/IP's but the hostname is consistent.

I am working with the companies IT team who should be able to remotely run PowerShell scripts on these computers and I think that is a viable way forward but it's been a while since I've done this, as I recall a json file with the project connection configuration so I am just asking for a refresher on what is necessary.

To the best of my recollection I think this is the right way -

  1. On one machine, make a connection via hostname to the target server.
  2. Copy that JSON file to a location that will be available to all 70 clients to copy over.
  3. Then on the client run the powershell script that will replace the current json that uses ip with this hostname json
  4. Delete and recreate the shortcut (though maybe unnecessary?)

Am I on the right path or missing anything here? I am looking for the simplest easiest way here. All the clients already have vision client launcher installed.

1 Like
2

You are on the right path. If the shortcuts are currently referring to a configured name within the json, you won't have to fix those.

1 Like
3 
# Local and network path for json files
$userProfile = [System.Environment]::GetFolderPath("UserProfile")
$localConfig = Join-Path $userProfile ".ignition\clientlauncher-data\vision-client-launcher.json"
$networkConfig = "Z:\somePath\vision-client-launcher.json"

# Replace local config with network version
Copy-Item -Path $networkConfig -Destination $localConfig -Force

I think this would be sufficient assuming that these clients are able to reach a network drive right?

That would be great if I don't have to fix the shortcuts. I will have to check how they are setup.

Here is the shortcut I have on my work computer for a local vision applicaiton - if they are setup like this
"C:\Users\BrianK\AppData\Roaming\Inductive Automation\Vision Client Launcher\visionclientlauncher.exe" -Dapp.home=C:\Users\BrianKarabinchak\.ignition\clientlauncher-data -Dapplication=psm4.Project

With the Dapplication being a name - then I should "just work" then right?

1 Like
4

I don't really do PowerShell, but looks OK.

1 Like