If the clients are just running MES without any other apps, you can create a logon script for the relevant users as below, that calls
the app and waits for it to close before logging off the user.
Copy the text into something like runmes.vbs, and set it as logon script for relevant users (I put relevant users into a new OU and create a GPO for them, so can restrict access to items in start menu etc.)
I'm running this for some handheld pda barcode scanners, so you'd need to change the run path to use the MES shortcut.
--
set wshShell = wscript.createobject("wscript.shell")
'Run the app
return = wshShell.Run("""D:\Program Files\Epicor Software\Client\client\MfgSys.exe"" -HH /config=liveauto.mfgsys /skipcheck",0,True)
'Run logoff utility
wshShell.Run "c:\windows\system32\logoff.exe"
--
the app and waits for it to close before logging off the user.
Copy the text into something like runmes.vbs, and set it as logon script for relevant users (I put relevant users into a new OU and create a GPO for them, so can restrict access to items in start menu etc.)
I'm running this for some handheld pda barcode scanners, so you'd need to change the run path to use the MES shortcut.
--
set wshShell = wscript.createobject("wscript.shell")
'Run the app
return = wshShell.Run("""D:\Program Files\Epicor Software\Client\client\MfgSys.exe"" -HH /config=liveauto.mfgsys /skipcheck",0,True)
'Run logoff utility
wshShell.Run "c:\windows\system32\logoff.exe"
--
--- In vantage@yahoogroups.com, Chris Thompson <chriselectrix@...> wrote:
>
> Is there any way to get a thin client (that is connected to a server via
> terminal services) to log off or shut down when Epicor MES is exited?
>
>
>
>
> ________________________________
> From: brucewbrannan <bruce.brannan@...>
> To: vantage@yahoogroups.com
> Sent: Wed, 9 February, 2011 20:25:58
> Subject: [Vantage] Re: Vantage - Shopfloor terminals
>
> ÂÂ
> We bought a cheap server for our terminal server. We evaluated WYSE clients but
> found the HPs were better priced. The HPs also come with free software to manage
> them all remotely, including imaging on the fly. Once you get one configured
> properly, you can also back its configuration up to a flash drive, pop in
> another one, and restore it. All you have to do then is change the unit's name
> or customize the RDP ID and/or password if you desire.
>
> Check out the HP t5325 clients. They ran $180 each when we bought them. I think
> I set them up with the kiosk mode, which gave the users no local things to
> click. When you turn them on, they immediately load the RDP client to the
> terminal server. If there's a power outage or interruption, the MES portion
> continues on the terminal server and the thin clients simply resume the RDP
> connection when it comes back online. They work great. Haven't had a problem
> with them and been running for a year now.
>
> They also offer a wireless adapter that can be plugged in to the USB port but we
> haven't tested it.
>
> --- In vantage@yahoogroups.com, Chris Thompson <chriselectrix@> wrote:
> >
> > Hi All
> >
> > Our shopfloor terminals are gradually dying.
> >
> > Originally they were ex-office PCs which we used.
> >
> > We are looking to replace a couple of them and were considering some of these
> > very small form factor units (low budget due to low spec).
> >
> > At present we have Epicor MES installed on the PC directly.
> >
> > An option would be to us TS to a server but it starts getting messy for the
> > users as there are more things to press and more things that can go wrong.
> >
> > What you you use?
> >
> > What would you recommend?
> >
> > Thanks.
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>