Main Board > Thin Client/WindX

Client-side FID(0)

<< < (2/2)

Mike Hatfield:
in the past we had a requirement that a specific computer be assigned a specific fid so that a user could print to a specific printer but in the long run we found that to be cumbersome and restrictive.
We now have multiple methods of assigning fid.
A 'next' available from a fid pool
A range of fids dependant on a subnet
A specific fid based on computer id
A specific fid based on the user login - either from the local computer login name or domain login name or the application login name.
All this is controlled and assigned at the STARTUP or Application login.
Ultimately we don't really care what the fid actually is so long as it is unique.

Mike King:
Actually if you want to control FID(0) based on the workstation shortcut simply add -ID=XXX to the command line.

James Zukowski:
If we were using a command-line shortcut, that would work fine. We're using .windx files, and it doesn't seem to fit in anywhere.  :(

James Zukowski:
It turns out this discussion may be moot. I've been trying to get the id from the task process list to change according to the fid(0) of the workstation connecting with SimpleCS. It finally 'clicked' that that's the id for the host, not the client.

Other options now under consideration. Thanks to all for the different insights.

Navigation

[0] Message Index

[*] Previous page