Skip to main content

Using Thin Client I want to get the Windows users name and computer name from the client side, I am getting the user name and computer name from the server, I know I can get information using dll's such as Kernel GDI32 this particular dll is ADVAPI32.DLL and then I am calling GetUserNameA,  GetComputerNameA this works just file if the connection is a mapped drive to the server. I used one of the sample programs GETUSERNAMEANDOS.cbl to get the logic and into one of our standard programs. I have been able to get the other information from the kernel.dll in thin client but not the ADVAPI32.DLL, any ideas?

Using Thin Client I want to get the Windows users name and computer name from the client side, I am getting the user name and computer name from the server, I know I can get information using dll's such as Kernel GDI32 this particular dll is ADVAPI32.DLL and then I am calling GetUserNameA,  GetComputerNameA this works just file if the connection is a mapped drive to the server. I used one of the sample programs GETUSERNAMEANDOS.cbl to get the logic and into one of our standard programs. I have been able to get the other information from the kernel.dll in thin client but not the ADVAPI32.DLL, any ideas?

ACCEPT TERMINAL-ABILITIES FROM TERMINAL-INFO. Move CLIENT-MACHINE-NAME to some-ws-value
ACCEPT SYSTEM-INFORMATION FROM SYSTEM-INFO. MOVE USER-ID to some-other-ws-value

Using Thin Client I want to get the Windows users name and computer name from the client side, I am getting the user name and computer name from the server, I know I can get information using dll's such as Kernel GDI32 this particular dll is ADVAPI32.DLL and then I am calling GetUserNameA,  GetComputerNameA this works just file if the connection is a mapped drive to the server. I used one of the sample programs GETUSERNAMEANDOS.cbl to get the logic and into one of our standard programs. I have been able to get the other information from the kernel.dll in thin client but not the ADVAPI32.DLL, any ideas?

There is an issue with this in Thin Client it adds garbage to the end of the computer name and I reported it back to MF, also, these fields are left blank when running the software as a mapped networked drive, the cleanest solution was calling the advapi32.dll (which by the way must be lower case) and kernel.dll to get the necessary information, but thank you answering the posted question

Using Thin Client I want to get the Windows users name and computer name from the client side, I am getting the user name and computer name from the server, I know I can get information using dll's such as Kernel GDI32 this particular dll is ADVAPI32.DLL and then I am calling GetUserNameA,  GetComputerNameA this works just file if the connection is a mapped drive to the server. I used one of the sample programs GETUSERNAMEANDOS.cbl to get the logic and into one of our standard programs. I have been able to get the other information from the kernel.dll in thin client but not the ADVAPI32.DLL, any ideas?

There is an issue with this in Thin Client it adds garbage to the end of the computer name and I reported it back to MF, also, these fields are left blank when running the software as a mapped networked drive, the cleanest solution was calling the advapi32.dll (which by the way must be lower case) and kernel.dll to get the necessary information, but thank you answering the posted question

Using Thin Client I want to get the Windows users name and computer name from the client side, I am getting the user name and computer name from the server, I know I can get information using dll's such as Kernel GDI32 this particular dll is ADVAPI32.DLL and then I am calling GetUserNameA,  GetComputerNameA this works just file if the connection is a mapped drive to the server. I used one of the sample programs GETUSERNAMEANDOS.cbl to get the logic and into one of our standard programs. I have been able to get the other information from the kernel.dll in thin client but not the ADVAPI32.DLL, any ideas?

Just an additional information:
Thinclient adds a minus sign plus the system pid in hex to the machine name.
Terms & ConditionsAccessibility statement