Monday, May 16, 2011

The rest of Monday

Connected with DIS, ADE and AT&T via CIV (heh-heh, just wanted to throw in a couple more three-letter things there) at 10am.  No one had trouble seeing or hearing our site.  We got the familiar "vaseline" effect (a weird smearing of video image that disappears almost as quickly as it appears).  Did some troubleshooting as follows:

* Moved the connections to different ports on same switch.
* Unplugged the switch then plugged it back in.
* Moved connections to a different switch.
* Hooked up a different codec (different brand, even)

Every item above resulted in the same effect - not working.  Pixelation, smearing, etc.

Brought Max at DIS on board.  After much discussion, I ran a cross-over cable directly from the codec to the router.  No connection at all.  Fixed crossover cable.  Got connection. (call that one 'operator headspace.')

SAME RESULTS!  This was both good and bad news.  Why?  Because it meant the problem was NOT on our network!  That's the good news.  The bad news: I can't fix it.  I have to rely on others to get it fixed.  Bad news...  Good news?  Max is in charge and this is his number one priority since this has been unresolved since we moved into the building in August.

After more discussion, I threw in the possibility that the router itself was the problem, even though the testors saw no real packet loss.  Max said he would check the processors in the router to see if they are pegging out at maximum, then trace routes back to DIS to see where the problem was originating.  We didn't have a loss problem so much as a latency issue.  I guess that means a whole different set of troubleshooting steps for those involved.

I relocated the codec into the tech closet so Trish could scan target tests.

I spent the res of the day evaluating quotes for pocket cameras, creating a new user in email, answering emails and phone messages regarding various issues and questions, worked out the schedule for the area tech meeting on Thursday.  I had to help a user get her email password reset - weird issue there. Her login takes her to a different page than everyone else.  I am convinced she was logged in under a different IE session.  She could not exit her session (something to do with COPA, I think), so I just reset her password and had her put in a new one.  I also worked on a machine that had freeze.com on it.  UGH, I wish users would not install things like "coupon finders" etc.  I know, I can set our system to not allow such things, but I keep hoping education will win out!  Pipe dream? Surely, not.

I managed to squeeze in some other things, though right now they seem to have left my brain.  Let me say that having the tech offices upstairs and the labs downstairs certainly has me getting in my exercise!!  Up the steps, down the steps, repeat for at least half the day.

Monday

Got to the office and immediately installed memory in all the macs in our lab. At ten, I am to meet over the distance learning system with tech support from little rock to figure out what our connection problems are.

Thursday, May 12, 2011

Thursday

Started the day by dropping in at the office to finish setting up the fouke early childhood computers.after that, headed to install them.

From there, headed to little rock for TIE training.

Wednesday, May 11, 2011

More Wednesday

After I got back to the office, I had to reinstall printers on the mini lab computers.  What happened to them? Who knows.  Once that was done, I spent a bit of time trying to find the recovery discs for the fouke computers that I worked on at home (more in a bit).  I found some system discs that would work, but they are the 'official' discs.  Should be okay though.

I answered several emails about a bid for pocket cameras, along with another about STIN lookup for Ideas.  I want to note that I am fielding calls for ideas logins/stins from folks not in my service area.  Evidently, someone somewhere said "David Henderson is you point of contact."  That is a direct quote from my sister-in-law who lives and work in Little Rock.

At home, I spent three hours trying to clean up the infected machine to no avail.  Next step is to blow everything away and start from scratch.  Since I am leaving work early on Thursday to head to the TIE meeting, I have to get the computer done so I can get it back to the classroom.  Thursday will be a long day full of serious mileage on the car and new tires.

Wednesday

Drove to fouke to work on early childhood computer. It has a malware infection I could not isolate. After hooking up a different computer for the teacher to use, the second one acted up. Have to bring both computers back to the office.

Well, so much for that. Had to get new tires on my car. Will have to work on those computers at home in order to get them back to the classroom tomorrow.

Fielded several calls regarding ideas login, network switch issues at a school, codec problems at another school, and met briefly with our apple outside sales rep.

And, it is only 130pm!

Whew!

Tuesday, May 10, 2011

May 10, 2011

Started the day setting up an iPad for our G/T Specialist.  That was followed by a 3-hour training that I held for our staff that have received iPads.  The training went very well, covering everything from the basics of logging in to the store to settings to downloading apps and grouping things together. We looked at a variety of Apps and talked about ways in which the device would (or would not) be useful for every day computing, depending on the function of the person and the apps that might help (or not).

In the afternoon, I held training for staff on the new Google Apps mail that we have now. Lots of good discussion regarding mail, contacts, groups (for distribution), filters, labels, and more.

Vikki and I also performed the monthly elevator fire test. It passed.

Monday, May 9, 2011

Well, THAT didn't work.

So much for a dialy reminder to post. So, let's play some catch-up.

I spent much of the last few weeks moving our email, calendars, and contacts from Exchange to Google Apps. I plan to detail our move in a "gray paper." What's that? Well, a White paper is usually a how-to on the methods of doing something correctly. I made a lot of mistakes and ran into more than a fair share of obstacles in our move to GA, so it won't be a sparkling white paper. Instead, it'll be a bit gray.

We also finally received our new server from Dell. I plan to start setting it up this week.

Other events as of late include a state tech coordinator meeting at the new building for the south central co-op in camden.

I also held a training last week for staff covering iPads and our new Google Apps system. The training went VERY well - lots of discussion and learning!

On April 27, two techs from Prescott and a tech from Fouke and I all went to Dallas for a condensed MacTech training. While it turned out to be focused on private businesses, we still learned a lot of things that translate to the education field. Once of the topics included documenting everything we do so that we can justify to our clients the reasons for charges, fees, etc. That hit home. I am charged with keeping a log of the things I do so that my "clients" (or in this case, those in charge of the funding for my position) can see that my budget is worth saving/having. Basically, it is a record that should show I am way underpaid for all the things I do day-in and day-out, not to mention the other projects that come up at a moment's notice.

It was because of that one session alone that I begin this week with a renewed focus on proving my worth. I am not sure this blog will be the best format for that, though. I want something that will keep everything organized by date and allow quick entries, rather than verbose explanations.

I'll just have to see how this goes. of course, blogger has features that allow for such organization, I believe. Stay tuned!