Skip to Content

A quick general overview of client install

A user who is not familiar with client-server setup, may be wondering why do they get prompted sometimes during their application install to create a ‘Client’ folder “from which they can run ‘Client install’”?


Well, the client install is useful feature that many views users benefited from, it allows running the product from a network location; this will allow also multiple machines on the network to use the same resources. The how to is documented in the System Admin Guide; but just to give quick picture a client install simply allows the user to run an application placed on a mounted network drive, so it will allow the use of the application through the network.

 A user might be wondering why I need an installer to do that. Why can’t I just point a short cut to the exe on the network?

Because for the application to run, it will need things like environment values, registry entries, and some times assisting files, so if a user tried to just run the executable part from another machine it will not work, and that’s where the installer is useful, because it will create the environment values, registry entries shortcuts etc.. Necessary to run the application on machine

 How does it work?

I will explain this using Label Studio as an example but there are number of products that support this feature (refer to the system admin guide), suppose you are installing Label Studio on Machine (A), then during the installation you will be prompted to create a ‘Client’ install folder, and if you answered ‘Yes’, then a folder named ‘Client’ will be placed on machine (A) and it will be placed on the same folder where Label (or your application) is installed for example if you are installing label studio on c:\pw\ then a folder C:\PW\Client will be created, this folder contains the setup files to perform a ‘Client’ install on another machine.

So if you want to run this application from another Machine (B), you will need to:

1-Map the a network drive on Machine (B) pointing to the folder in which the application is installed on machine (A) or a parent folder (for example if your application is installed on c:\pw\ls) then map either ‘c:\pw ‘or ‘c:\’ to a network drive on your machine (B) for example Z: drive.

2-Then on machine (B), navigate to the client installer folder on the newly mounted network drive (for example on Z:\client\setup.exe) and run the client setup.

The installer will create the setup, environment values, registry entries and shortcut necessary on machine (B) (client) which will allow you to run the application residing on machine (A) (server).

To learn more about client setup refer to the ‘System Administrator’s Guide’.

Be the first to leave a comment
You must be Logged on to comment or reply to a post.