ResNet thought they were solving last year’s virus problem that plagued the university’s network. They thought forcing students to download certain protective software before gaining access to the network was a good idea.

They thought it would keep out pesky computer worms that bog down the network.

Clearly, they didn’t think at all.

The solution that was put into place – an online program that scans your system to make sure it is safe to be put on the network – was not thought all the way through.

If ResNet had put enough thought into the new process, they would have warned students of the necessary upgrades before they arrived on campus and probably prevented the mess altogether.

Letters or e-mails could have been sent to students who planned to live on campus alerting them of the new process before they moved in.

Maybe then masses of students wouldn’t be without a connection to the network.

ResNet also should have been better prepared to provide assistance to students who encounter trouble –

especially at a university where “Students come first.”

Picking up the phone won’t do any good – callers will go straight to a voice mail system, which is full most of the time. Students needing help must go directly to the ResNet office and wait in line for help.

ResNet coordinator Lisa Moore said over 75 computers were dropped off at her office Monday to be worked on.

Moore even said the ResNet staff is learning the new protective system as they go along.

A system so imperative to students should not be implemented until all the kinks are worked out. The beginning of the semester when students need computer access is neither the time to learn a new system nor fix it.

ResNet has tried to solve one problem by creating another and caused a huge inconvenience that – with proper planning – could have been prevented.

Reach The Progress at