Randy I ran into this when I was at Sage. I got a workaround put into the code for this scenario. It was put in early 4.xx but should still be available today.
Remember the old SET MAS90FID=Txxx that you had to add way way way back when? Then later you didn't have to b/c the Txxx was auto assigned by MAS. Then it was abandoned all together (yay!).
So today on start up (unless they've removed it), if it detects both Terminal Server and Mas200(as in Advanced / Premium), it will first check for a MAS90FID in case you created one yourself and if found becomes
coSession'WorkstationName$ and the
Station column you see in Master Console.
IOW, while in your RDP / RDS session, go to Control Panel > System > Advanced tab > Environment Variables > add a User env var (not System env var) called MAS90FID for the user you are logged into Windows as. The rules are:
* Can't be more than 30 chars
* No spaces or uncommon symbols (it's my own rule actually)
* Recommend upper-casing the value
* It does NOT have to be the old Txxx vals like T101. For example:
- MAS90FID = BIGLEBOWSKI3
- MAS90FID = CHIEFBOTTLEWASHER2
So in the end create a MAS90FID for each distinct Windows user ID that will use Terminal Server in the way you described it.
------------------------------
Alnoor Cassim
Free Agent Developer and Consultant
CallForHelp.biz
Email:
alnoor@callforhelp.bizOrange County, CA
------------------------------
Original Message:
Sent: 06-19-2019 11:43
From: Kevin Moyes
Subject: Mas200 4.30 - workstations on as terminal server
Check Master Console... are there any users using different client machines, but with the same name (as appears in MC)? If so, rename one of them.
------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------