Date: Thu, 15 Apr 2004 08:38:33 -0500 Subject: Re: [Fwd: Re: Fwd: Dollar Bay Information] To: "Brian M. Slator" Cc: kerbaub@fargo.k12.nd.us, ericksc@fargo.k12.nd.us, westrbi@fargo.k12.nd.us, teikenj@fargo.k12.nd.us, , , ben.dischinger@ndsu.nodak.edu From: "John Steiner" Status: RO "Brian M. Slator" writes: >The idea from our point of view is to create no additional workload >for school district personnel. >For that reason we are in the process of training a "tech team" >(students taking my class, not the >ones you met but some others), in performing this installation. There >are two main steps on the >client machines, and several steps on the server machine. Dr. Slator: I know it might seem like we're 'looking the proverbial gift horse in the mouth' but I do have a few concerns regarding the file server install... 1. I was expecting that the server might just be one of our normal classroom workstations running a simple server "tool" during the class and shut down when class is over. The configuration you're proposing clearly involves a separate server box. We would have to "find" such a box. We do have some older equipment available but I'd need to know minimums for processor, RAM, hard drive space, operating system, etc. 2. Will we need to give this server a public IP number so it can be accessed from NDSU? Our district sits behind a firewall and if we have to "open" that wall for this server's public number, the operating system and open ports on the server are of major importance to us. We are concerned about viruses and hacker attacks. I'd like final say on the server OS as it will be up to us to protect it. If it's behind our firewall and protected from outside sources, we can more easily handle our own "in-district" hackers. 3. Who will be expected to have "root" password or administrative access to this server? How much training will Mr. Erickson require to provide basic administration of the server application? In the long-term, what kind of server OS support will be expected? 4. I'm also concerned about long-term data backup issues. Ideally, we'd like the server to somehow access the database as stored on our production servers so the data gets backed up in our enterprise. We may be able to implement an automated ftp solution of some type, but we need to consider this and other long-term support issues during the testing period. 5. Our help desk support for supplemental curricular applications in the school district is limited due to small staff size and a large network plant. We ask departments who wish to adopt dedicated applications to be a lot more self-sufficient in managing those applications than we ask for adoptions that are district-wide. I have a concern that we may not be able to dedicate the amount of time and energy this server might require and wonder if Mr. Erickson or others in his area would want to develop that expertise. As usual, I've been very verbose in saying simply that, "This server better be easy to manage, rock-solid and bullet-proof." John