Sage 100

When using RDP, in Master Console, it picks up the name of the client PC. Is there any way to get the Master Console to pick up the name of the server instead? If we have MAS open on both the server and a PC and when we close out of MAS on the PC, it causes any task we have open on the server to crash.

Robert it seems to me that if you did find a way to change it to use the server name, you may have a bigger problem. That might cause all users accessing rdp to have issues when another user exits MAS. I'm just speculating based on what you're already experiencing.

You may be correct. In this case, I'm trying to have something run at the accounting server. Unfortunately every time I close MAS from my machine, it closes the task (Unattended Bar Code Import).

OK gotcha. Do you need to start it on the accounting server via rdp?(I'm guessing you're remote to that server) Can you physically start it logged directly into the server or from another worksation that won't be running MAS? (Just brainstorming ideas.)

Logmein, GotoAssist?

Having it pickup the name of the remote PC is defintely by design. I think your best solution is to use a tool other than RDP for remote control of your Unattended Bar Code Import. If the server thinks it's running on the console, the session should pickup the Server ID. I am fortunate to have a Bomgar Server and Teamviewer available for remote control, so I haven't had the issue. When running RDP, there is a /admin switch that allows you to take over the console. I haven't ever checked that with MAS 90 to see if it would then pickup the server id. On 200, we have unattended VI jobs running on their own via scheduled batch jobs.

It's a Virtual Server on a Physical server on the other end of the facility from where most of the employees work. I tried the /admin switch and it's passing the workstation name through. Since the server isn't accessible directly from the outside, what would be the risks of setting up VNC on the server?

I just tried to change the Client Name environmental variable and then launch MAS, but that didn't work, so they must be using Windows API to determine the 'Station Name'

I have only used VNC at a customer's request and don't know anything about Logmein or GotoAssist. Whatever you use, you would need to beable to disconnect from your session instead of logging out. 90 or 200? On demand or scheduled? Can it just be run from a workstation?

It really needs to run all of the time. I has to be started manually because of some settings that have to be done (or I need to setup a macro program to run it). It could be run from a workstation but we'd run into the same problem. The server room has sufficient backup power where most of the offices don't.

Vnc should work to connect to the console session, assuming there is one. Someone would have to log into the console after each reboot of the server.

If it's virtual, couldn't you RDP to a server that hosts XenCenter/vCenter/Hyper-V Manager and use that to get to its console?

@SteveIwanowski I think it was doing the same thing there.

I am testing setting a system environment setting making the MASFID = ""MASServer"" at the user level. Let's see what happens.

Thanks to @AlnoorCassim! That seems to be working.

Back in 4.05 I wrote up a bug to this effect because of how some WinTerm and Windows CE devices were connecting (the API for TS was returning the same computer name across devices or return no computer name at all). The result of it was that if you are on MAS 200 and going through Terminal Services, you can use the old throwback MAS90FID environment variable. You would set it up in Control Panel / System / Environment Variables. And you don't have to make it equal to T1, T2, etc like in the past. So for BertoWud in the Master Console, for the MAS session going through TS / Citix, he would see MASServer in the Station column, which is different than the Station seen if MAS were started up directly on the server (woohoo).

Thanks everyone for the ideas.