Re: Thin Client ID

From: Dragon Lord (invalid_at_joke.com)
Date: 02/03/04

  • Next message: MikeB: "Re: CSV file and newb" 
    Date: Tue, 3 Feb 2004 13:34:48 -0500

    He prolly means a thin client as a Hardware Only pc, with main software
    loaded as firmware. Anything else is loaded from an external server through
    TCPIP. Its really just a bunch of crap. Its like a GUI cash register
    hooked up to a machine in the back. Its a semi fad, but the ID or Serial
    number is not as available as you think, the serial number of the thin
    client is actually dependant on the hardware you use. What you COULD do, is
    use the windows API functions to get the serial number of the "virtual" hard
    drive. Although, I don't know if this will be the same across all
    environments. You could also use the MAC address of the network card
    although, depending on the hardware, this is programmable.

    "J French" <erewhon@nowhere.com> wrote in message
    news:401fd2a8.93627679@news.btclick.com...
    > On 3 Feb 2004 08:03:01 -0800, delphi@fastacura.com (jbrouton) wrote:
    >
    > >In a thin client environment, where each client is logged on the same
    > >server (Windows) while running the same .exe, I would like to know
    > >which API call I have to make in order to have a "unique thin client
    > >id" that Windows uses to know where to send the information and from
    > >where to catch the input. I'd like to put a "unique name" on each one
    > >of the thin clients in order to know who asked to run this .exe.
    >
    > A bit more information is required
    > Is this a TCP/IP App ?
    > How thin is the 'client'
    >
    > >
    > >Exemple why I need it :
    > >if getThinClientName = "clientA" then
    > > doThis
    > >else if getThinClientName = "clientB" then
    > > doThat
    >
    > The code above is lethal - hard coding like that is diabolical
    > ( I know, I used to do it 17 years ago )

    It is nasty, but unfortunatly, thin clients, don't have a lot of computing
    power, and there is A LOT of software it can't run. Thin clients are just
    huge spy wear, for companies that don't need a lot of computing power. I
    had a job where a company had 500 thin clients in the office, for like sales
    reps and operators. Not programmers who need computing power. Plus, thin
    clients are A LOT cheaper than a regular computer, but you only really gain
    much if you have 500+ employees, cuz the Windows Server and licenses you
    need, can get expensive on that end.

  • Next message: MikeB: "Re: CSV file and newb"

    Relevant Pages

    • RE: Researching TS for new setup
      ... The main advantages of hardware thin clients is not the initial ... What do you want your users to do with a CD/DVD drive anyway? ... Is there a way to configure the logon ...
      (microsoft.public.windows.terminal_services)
    • Re: TS profiles
      ... Your way wou will need to pay: hardware, client OS licenses, TS CAL. ... With thin clients you will pay only thin hardware ... Terminal Services and Citrix Presentation Server user logging ...
      (microsoft.public.windows.terminal_services)
    • thin client replacement analysis
      ... I am presently doing a cost analysis of terminal server/ thin clients versus ... workstations. ... hardware, such as wyse terminals, need to be replaced? ...
      (microsoft.public.windows.terminal_services)