Good day, I have had a couple of folks think this info is useful so figured I'd
post for all if it will help. Hopefully the formatting will look ok...
The thin client must have a unique "PC_Name". Write a batch file that runs at
startup of each of the thin clients to look at PC_Name and start chosen VM RDP
link you want to connect to in desired path.
Ex:
If %ComputerName%==PC_NAME
(Echo Please wait, connecting to VM_NAME
Timeout /T 10
Start c:\...\VM_NAME.rdp
Goto END)
:END
ECHO.
ECHO RDP Session Request Complete
Timeout /T 10
EXIT
Add more IF statements for all PC_NAMES and VM_NAMES in your system.
In DMCFG file (usr/fox/customer/hi) of VM, dedicate DMNAMES to above PC_NAME
for all DM's you want to run, whether 1,2, or 4. Ex for starting 4:
If your PCNAME is longer than 6 characters, use the screen variable where the
left side is your variable name and right is actual PC name;
SCREEN PCNAME PC_NAME
Then in DM section;
NAME VMNAME DMNAMA $PCNAME
NAME VMNAME DMNAMB $PCNAME
NAME VMNAME DMNAMC $PCNAME
NAME VMNAME DMNAMD $PCNAME
Create or modify existing 2nd_FV script (usr/fox/wp/data) to include;
If [$DMNAME = DMNAMA] #looks at 1st FV you dedicated to the PC_NAME
Then
/opt/fox/wp/Foxview/Foxview.exe & #Starts DMNAMB
/opt/fox/wp/Foxview/Foxview.exe & #Starts DMNAMC
/opt/fox/wp/Foxview/Foxview.exe & #Starts DMNAMD
Elif [$DMNAME = ... continue for any other client connections
Then
Else
Exit
fi
Call if not done already 2nd_FV script from FV_CMDS script (usr/fox/wp/data) by
adding line;
Dmcmd wp_applic /usr/fox/wp/data/2nd_fv
This will start all 4 Foxviews on the thin client, where you then move and save
locations as always the first time they run, and on each successive login all 4
Foxviews will open up where you last saved them. If the operator has any
trouble, he/she has to close the three successive screens that open after the
first, then close the first at which point the first screen will re-initialize,
and the next three will re-open in their positions.
HINTS:
I have reserved the first DM on all Host VM's so a single FV is available when
accessed from POSE of V90
I found it does not work to set the SCREEN variable from the DM Configurator.
I had to manually set it, then import DMCFG into the configurator for the
SCREEN variable to populate. If you don't you only get access to tie a
variable to a Fox station that is in the SYSDEF.
Use local group policy set for specific user to lock operator out of thin
client use other than RDP session start and logoff.
Lots of time spent in DM and AM configuration to get it just right.
Good luck, Happy Paddy's Day.
____________________
Tony Hough
Process/Control Systems Analyst
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Vandewater, Tom
Sent: Wednesday, March 08, 2017 7:16 PM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: [foxboro] Calling Dedicated Foxviews from VM's onto Dedicated Thin
Client Monitors
To All,
We are just getting our feet wet setting up Virtual Machines on a new
V91. Our goal is to replace many existing dual and quad head P92 Operator
workstations by using HP Quad Video Thin Clients, (Foxboro Part # P0928JY),
connected to the Virtual Machines running in the new V91. My questions are:
1. Can I automatically, (upon power up of the Quad Video Thin Client), open a
single RDP session from the thin client to a dedicated VM workstation, and then
open four dedicated and maximized Foxviews, one on each of the four monitors
connected to the Quad Video Thin Client?
2. If so, is there a Foxboro document that describes how to do it?
3. If no document exists, can someone explain how to do it?
Thanks for any help/guidance.
Tom VandeWater
Control Conversions, Inc.
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
