Hello everyone.
I have a weird situation that i'm pretty sure is possible but i'm just running into a wall and I hope someone can show me the door.
Scenario:
A user has an office. The office has a front desk.
In the user's office, there is a PC and a networked printer.
There is also a TS that the user connects to from his PC in his office to work from (which prints to his networked printer in his office).
At the front desk, there is a thin client, and a networked receipt printer.
PRIOR to there being a thin client, this is how things worked:
when the user would connect to the TS, we relied on RDS to push the printer connections to the TS and the user can print fine. no problems here.
Now we introduced Thin Clients into the equation. Since you cannot install printers locally on a thin client, we are running into a problem. There are some catches though.
Right now, when the user connects to the TS from his office, and tries to print, everything works great. Now someone calls and the user has to go to the front desk (leaving his PC logged into the TS through RDS) and at the front desk, the user logs into the SAME TS with the SAME credentials and loads up a program to print a receipt. PROBLEM: no printers show up. Close program (not the RDS session) and re-open it, the printers show up (but they are more than likely from his session that originated in the office from the PC) This is a problem because when you close the program, it loses the receipt it was supposed to print and re-printing them is a pain in the arse.
The solution I have come up with is this:
Run a login script from the TS server, that looks at the user connecting in and gets the Thin Client name the user is connecting from and then maps a printer according to the name of the Thin Client logged into from. This would assure that users logging in from multiple front desk sites from multiple thin clients would get their respective receipt printer mapped before they opened the program that prints them and therefore be able to print the first time they need to.
My problem is I do not know how to find the name of the thin client (or pc for that matter) that the user RDS'd to the TS from.
If i was to get that name, i could write a script that basically says "if connecting from XXX (thin client name) then map XXX printer" and repeat that for each location.
My main question is: is there a way with a VBscript to determine the name of the computer(thin client) that connected to a server where the VBscript is run.
My main thing i'm avoiding is: having multiple copies of the same printer being mapped to the users PC in his office when he's not at the front desk using a thin client. because any scripts running on the TS will also run when he logs into the TS from his PC.
I suppose another question could be: How do I make the printers from session A copy over to session B for the same user, logged into the same TS , from 2 different PC's w/out having to open/close a printer window through a program first.
I know this is a crazy question and I hope I worded it properly and i'm sorry if my spacing is hard on the eyes, i just never know when to break a paragraph off into a new one and this way is easier to read than one big paragraph IMO.
Thank you so much for any help or leads in the right direction.
please ask if my scenario doesn't make sense.
Derek Conlon