With that kind of stuff, you need to make suggestions, discuss, decide, then issue a change order/control, then implement, as opposed to suggest, then change order about 5 min-1 hour before implement at 5 pm. Sometimes that is what they do in our bldg with XP patches handed down from on high. Not good when you create more problems for other people. We just say "Thank You I/O Lab in Ft. Collins, CO."
-----Original Message----- From: Jon Pruente Sent: Tuesday, January 09, 2007 5:08 PM
As I understand it they've got some big iron off 435 and 63rd for a main data center. They've got a second, fail over, site in St. Louis that they physically test once a month (as in kill connections here and see if STL picks up) and a whole bunch of smaller setups all over. They've got some machines that have been *on* for about 30 years. I really do hope they've got good security too, but with their history in the industry, I think they do. I'm fairly sure that's why my friends project only made the suggestion of what to change, and would allow the local admin for each machine to have the final decision of what to change.
Jon.