Re: [foxboro] RE : Barriers to migration to Windows
- From: <tom.vandewater@xxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 29 Aug 2007 13:09:05 -0400
This is an interesting thread indeed. USB drives on MS AW's. When we =
moved to the MESH and AWXP's we immediately realized that the Windows =
boxes appeared to be intentionally isolated from access to other boxes, =
(even other Windows boxes on the MESH. Unless I'm missing something, =
there is no way to do even a basic file transfer or remote login to the =
MS AW's unless you take matters into your own hands. Given a fast new =
network, you might have expected that Foxboro would have provided some =
way to keep common system files and shared graphics updated between =
boxes. It wasn't obvious to me. We immediately started using USB =
drives to handle all of these administrative transfers. FTP and Telnet =
services are by default disabled and Foxboro doesn't create a common =
workgroup that would allow sharing via the standard MS capability.
All this makes me ask, are there any large scale MS/MESH users out =
there? Please chime in. What have you done to share files between the =
MS AW's/WP's? Have you enabled FTP and/or TELNET services? Have you =
established an MS workgroup to share files between AW's? If so, is it a =
Foxboro approved method? Did you go-it-alone and break any of the =
Foxboro apps? Given my perceived lack of connectivity between MS AW's =
it is even harder for me to understand what the drivers are to migrate. =
I am far from being Foxboro MS savvy so don't hesitate to enlighten me =
on how I can better use/administer the boxes running on this platform. =
My reply might sound cynical but my intent is really bent at learning =
how to optimize/utilize the two MS AW's that we MUST have on site to =
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] =
On Behalf Of Ron Schafer
Sent: Wednesday, August 29, 2007 12:30 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] RE=A0: Barriers to migration to Windows
At ver 8.3 (server & 390G) The USB does work also. In this case the kbd =
=3D
and mouse are usb, so diabling the port is not an option. Also, our =3D
monitors are usb hubs. Since we keep our stations in locked =3D
cabinets(isolated) nobody can access the usb ports! But...the usb ports =
=3D
on the monitors hub for the Kbd/Mouse have two extra ports as well as =
=3D
its really easy to unplug the mouse and plug in a memory stick....so =3D
disabling the usb is really kinda impossible. This leaves a hole in =3D
security!=3D20
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 =3D
detected by usb ports? That would only allow keyboards and mice?
Ronald G. Schafer
10026 Old Ridge Rd.
Ashland Va. 23009
804-227-4034
=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
- Follow-Ups:
- Re: [foxboro] RE : Barriers to migration to Windows
- From: Lowell, Timothy
- Re: [foxboro] RE : Barriers to migration to Windows
- From: Pulas, Philip
- Re: [foxboro] RE : Barriers to migration to Windows
- From: Pat Martens
- References:
- [foxboro] RE : Barriers to migration to Windows
- From: Ron Schafer
Other related posts:
- » Re: [foxboro] RE : Barriers to migration to Windows
- » Re: [foxboro] RE : Barriers to migration to Windows
- » Re: [foxboro] RE : Barriers to migration to Windows
- » Re: [foxboro] RE : Barriers to migration to Windows
- » Re: [foxboro] RE : Barriers to migration to Windows
- » Re: [foxboro] RE : Barriers to migration to Windows
- » Re: [foxboro] RE : Barriers to migration to Windows
- » Re: [foxboro] RE : Barriers to migration to Windows
- » Re: [foxboro] RE : Barriers to migration to Windows
- » Re: [foxboro] RE : Barriers to migration to Windows
- » Re: [foxboro] RE : Barriers to migration to Windows
- » Re: [foxboro] RE : Barriers to migration to Windows
- » Re: [foxboro] RE : Barriers to migration to Windows
- » Re: [foxboro] RE : Barriers to migration to Windows
- » Re: [foxboro] RE : Barriers to migration to Windows
- » Re: [foxboro] RE : Barriers to migration to Windows
- » Re: [foxboro] RE : Barriers to migration to Windows
- » Re: [foxboro] RE : Barriers to migration to Windows
- Re: [foxboro] RE : Barriers to migration to Windows
- From: Lowell, Timothy
- Re: [foxboro] RE : Barriers to migration to Windows
- From: Pulas, Philip
- Re: [foxboro] RE : Barriers to migration to Windows
- From: Pat Martens
- [foxboro] RE : Barriers to migration to Windows
- From: Ron Schafer