Re: [foxboro] RE : Barriers to migration to Windows

There is a common workgroup, called "Workgroup", that all MESH boxes are =
by default a part of.  You can connect all your MESH AW D: drives by =
attaching to the D$ share on each box (which works because the "Fox" =
user is an administrator).  It's tedious to set up on each box, but once =
you do, you can do remote file transfers to any box on the MESH using =
the standard Explorer.  You can also use XCOPY to copy to any IP address =
using the \\servername\share UNC pathname.  Our Golden Eagle facility =
developed a remote file copy Visual Basic script to copy files around.  =
It works very well.  You need to specify your MESH hosts IP addresses in =
a hosts file that resides in the same directory as the VB script, but =
that's not too hard, and it allows you to use the 2nd Ethernet port to =
copy the files if you want (which you should if they are large files).

Tim Lowell
Control Systems Engineer
Tesoro Petroleum Company
210-283-2929 (w)
210-253-0225 (c)
tlowell@xxxxxxxxxxx

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] =
On Behalf Of tom.vandewater@xxxxxxxxxxxxxx
Sent: Wednesday, August 29, 2007 12:09 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] RE=A0: Barriers to migration to Windows

        This is an interesting thread indeed.  USB drives on MS AW's.  When we =
=3D
moved to the MESH and AWXP's we immediately realized that the Windows =
=3D
boxes appeared to be intentionally isolated from access to other boxes, =
=3D
(even other Windows boxes on the MESH.  Unless I'm missing something, =
=3D
there is no way to do even a basic file transfer or remote login to the =
=3D
MS AW's unless you take matters into your own hands.  Given a fast new =
=3D
network, you might have expected that Foxboro would have provided some =
=3D
way to keep common system files and shared graphics updated between =3D
boxes.  It wasn't obvious to me.  We immediately started using USB =3D
drives to handle all of these administrative transfers.  FTP and Telnet =
=3D
services are by default disabled and Foxboro doesn't create a common =3D
workgroup that would allow sharing via the standard MS capability.
        All this makes me ask, are there any large scale MS/MESH users out =3D
there?  Please chime in.  What have you done to share files between the =
=3D
MS AW's/WP's?  Have you enabled FTP and/or TELNET services?  Have you =
=3D
established an MS workgroup to share files between AW's?  If so, is it a =
=3D
Foxboro approved method?  Did you go-it-alone and break any of the =3D
Foxboro apps?  Given my perceived lack of connectivity between MS AW's =
=3D
it is even harder for me to understand what the drivers are to migrate.  =
=3D
I am far from being Foxboro MS savvy so don't hesitate to enlighten me =
=3D
on how I can better use/administer the boxes running on this platform.  =
=3D
My reply might sound cynical but my intent is really bent at learning =
=3D
how to optimize/utilize the two MS AW's that we MUST have on site to =3D
support the MESH stations.

Tom VandeWater
Control Systems Developer/Analyst
Dow Corning Corporation
Carrollton, KY   USA

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] =
=3D
On Behalf Of Ron Schafer
Sent: Wednesday, August 29, 2007 12:30 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] RE=3DA0: Barriers to migration to Windows


At ver 8.3 (server & 390G) The USB does work also. In this case the kbd =
=3D
=3D3D
and mouse are usb, so diabling the port is not an option. Also, our =
=3D3D
monitors are usb hubs. Since we keep our stations in locked =3D3D
cabinets(isolated) nobody can access the usb ports! But...the usb ports =
=3D
=3D3D
on the monitors hub for the Kbd/Mouse have two extra ports as well as =
=3D
=3D3D
its really easy to unplug the mouse and plug in a memory stick....so =
=3D3D
disabling the usb is really kinda impossible. This leaves a hole in =
=3D3D
security!=3D3D20

How would you address this issue? Use PS2(not shipped from Foxboro)

Pc --->usbkvm--->monitor/4porthub--->mouse
                                 \-->keyboard
                                 \--> open port
                                 \--> open port
I was thinking superglue or bubblegum....:))

Is there software that will limit the type of device that can be =3D3D
detected by usb ports? That would only allow keyboards and mice?

Ronald G. Schafer
10026 Old Ridge Rd.
Ashland Va. 23009
804-227-4034
=3D20
=3D20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
=3D20
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         =3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
to unsubscribe:      =3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
=3D20
=20
=20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
=20
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: