Before I made it into the foyer of our new building, I was met at the door. Today would be busy. First, a question about setting up email on a smartphone immediately followed by a request to help get things going in the computer lab.
Once the Macs were turned on, logged in, and running, I went to my office to start the day. Frankly, I don't remember the order of things. This is a basic rundown of my day...
I got a printout from our bookkeeper for the 2010-2011 E-rate year regarding our wireless bills. I spent a long time culling through the printout in order to determine which phone payments were ineligible (Pre-K is not eligible for E-rate in Arkansas), which part of the remaining bills were ineligible (the staff pays a portion of the phone bill for their phones), and which part of the bill was ineligible due to equipment purchases (the cost of the phones is not eligible). Once all THAT was done, I jumped on USAC and started my BEAR form (probably one of the most aptly-named forms ever). Actually, it wasn't bad. Really.
I talked on the phone for an hour with a district regarding several issues they have, and we made a list for me to look at once I can get on-site: Auto-flat-forwarding in Groupwise, Google Apps, server specs, iPhone configuration utility, and a hose of thngs that I wrote down but can't remember just now for inclusion in this post.
I emailed our KEY guy about additional keys that need to be made for our building. He is out of pocket until after the holiday.
I took a message from a Verizon E-Rate rep about our 2009-2010 Alltel/Verizon reimbursements (or lack thereof) and HIS people were out until after the holiday.
Did I mention I had jury duty earlier this week? Well, I have to call on Monday to see if I have it again NEXT week.
I checked the timer on the parking lot lights. The timer is messed up and we've talked to an electrician and our architect about it. Seems to me this would be an easy fix. But, then I'm just the tech guy, right?
I installed Vineland-II on a laptop that was then used in a workshop on Friday. During the day, I checked in on the workshop to make sure things were going well. At one point, I realized that some additional software needed to be installed on the instructor's machine. In a lab of computers, the one at the front, away from the other machines, tends to get overlooked when rolling out a software install. that's what had happened here. Easy fix!
I served as mediator between a school and ADE regarding Cognos printing. Well, I did that until I put the two people in direct contact with each other. I don't mind serving as go-between on issues, but there comes a point where having the parties talk directly to each other makes more sense.
I still have to install the new server at the office. I have to figure out when *that* is going to happen. UGH.
I also had planned to help a school set up a new server, but with jury duty killing the day we had set up this past week, it looks like they are going to turn in a ticket to DIS. This is one of those times when I wished I had been able to help. At the same time, I hope it shows that we state techs have so much going on that it takes SEVERAL agencies just to keep the schools up and running technologically. While on paper it may seem as though there is "duplication of services," the simple fact is this: There is no duplication, rather there is a multi-facted system of support. In short, it takes a village to help our schools, and each member of that village brings different skills, perspective, and resources to the table.
We finally received a credit on our local/long distance bill from AT&T for E-rate in 2010-2011 up to this point.
I met with the Director, Assistant Director and several content specialists regarding some of the summer inservices coming up.
I posted new target testing information (guidelines and other documents) to the target testing web site and edited various web pages to make the new info easier to find.
I used a trick I found online to reset the battery on one of the Flip UltraHD cameras we have. It would not charge the battery. Here is the fix that worked: Remove the battery pack, plug the camera into the computer, once seen as a device put the battery back in (yes, while plugged into the computer), eject the device from the computer, plug the camera back in, watch the battery start to charge!
I posted several modules related to Common Core on the TIE web site for use in summer professional developments.
I helped several people obtain their SPIN so they could sign up for/log in to the IDEAS portal.
Talked with a Verizon rep regarding several phones having network-connectivity issues (read, phones showed NO service). The fix? Remove the battery and reboot - twice. Man, I have come to HATE these Samsung Fascinate phones. They are junk compared to the Motorola Droids we had prior to changing over. I am more patient about phones than anyone else on staff, and even I am at my wits end. For the record, I have contacted our account rep and am sending a list of phones and issues to her after the holiday.
I have been working on an E-Rate PIA request regarding Pre-K facilities in my service area. We do not count Pre-K students in the overall student counts sent to USAC, but a simple statement to that effect has no weight evidently. So, I get a list of Elementary schools and have to say whether the Pre-K program is inside the building, has its own building or both/neither. I have no idea what difference it makes. But, I play along as best I can. All this for plain old telephone service, long distance, and cell phones. Really? You'd think after all these years, basic Priority One requests would just "happen." Nope. Welcome to hoop-jumping 101.
Throughout the day, I answered emails, telephone calls... Oh wait, I forgot about this:
A school called to say they had received a letter from a nearby university's legal council regarding "hacking" of their library web site. In the letter, the school was accused of having three different IP addresses attempting to access the online library system. TWO of those addresses didn't even belong to the school The 3rd one was the router from the school, which means a computer on that campus was trying to. The campus? An elementary school. So, who would try this? ow about a former university student trying to get into the library through his/her previous account? Yeap. Now, the main issue I have is the fact that this became the school's problem. Maybe it's just me, but if someone is trying to "hack" the univ's system, that is the univ's issue, NOT the schools. Besides, had the univ actually, um, CALLED the school to talk about it first, the whole thing would have been cleared up in two seconds. Let's just say the district's legal council will most likely be sending a response.
At the end of the day, I updated some of the software in the computer and shut the machines down for the weekend.
Saturday, May 28, 2011
Thursday, May 26, 2011
Monday, Tuesday, and Wednesday
I spent the past three days serving as an alternate juror in a federal case.
During breaks/lunch/after hours, I spent time answering email, phone messages, and Monday night and Tuesday night, I posted pacing guides to the target web site, working well into the night.
During breaks/lunch/after hours, I spent time answering email, phone messages, and Monday night and Tuesday night, I posted pacing guides to the target web site, working well into the night.
Saturday, May 21, 2011
May 20, 2011 - of Phones and Codecs
On Friday, I got to the office and worked on general things, like answering emails, etc, until 9a. At 9a, I took Phoebe's phone to the Verizon store. Her phone has been acting weird ever since a foiled attempt to install FROYO on her Fascinate. The update downloaded, but when it tried to install, it would lock up at the "updating modem..." stage. After a random amount of time (which seemed to get longer with each subsequent attempt to update), a screen would pop up with something akin to "IP_UPDATE_FAILED" or something. In any case, the phone would revert back to OS 2.1-update 1. Well, that's not true, really. It was in some kind of limbo state - it would lose email, send messages with empty content and other weird things.
I walked into the Verizon store and told the guy that I needed the phone flashed back to its original state. I explained the update problem and that I had found a solution online but thought it was better that Verizon do it in case I messed something up. I did not want to void the warranty if things went wrong. He walked (verbally) through the steps I had explained and took the phone. He immediately started the update, as though I had not just explained that I had been down this road and it comes to a sudden dead end. So, he downloads the update and begins the install. I protest repeatedly, but to avail. He is determined that when HE does it, it will work. I realize he has no idea that I have a bit of technical knowledge, but I did my best to explain to him everything I had done and how his attempt to update will end in failure given he is doing EXACTLY what I did (even pulling the battery etc).
After about 45 minutes or so of watching the install sit frozen at the "updating modem..." screen, he tries to restart the phone in "factory reset" mode - which is what I wanted in the first place, remember. No go. The phone reboots and immediately begins the update installation. this, of course, freezes at the "updating modem..." stage. Rinse, repeat. Seriously. I think he rebooted 3 or 4 more times, trying to get it into factory mode. Nope. He pulls up our account to see about getting a new phone, but he can't touch our account because it is a government account. Lovely. He hands me the now BRICKED phone and tells me to call my rep for a new phone. Ummm, this is FRIDAY and this is my boss' phone. You want me to tell my boss that you just killed her phone and that she will be without for the weekend!? Nice.
Well, since the phone was hosed anyway, I figured I would give the steps I found online a whirl. After a bit of trial and error, I managed to get the phone in a "Downloading" mode (note image was found online at Android Forums and is property of its original owner):
In this mode, the phone is ready to accept image updates transferred from a computer. Before I go further, I want to say that there is a factory reset option. But, because the phone was bricked, it only showed a phone icon with a computer next to it and maybe an X or something. Basically, it was saying it couldn't be factory reset (because of the hosed update).
So, I put the phone into this update mode (sorry, you will have to Google that yourself. I am not responsible for what you do to your phone!), downloaded the necessary software and ROM image to get the phone back to out-of-the-box fresh, and held my breath.
After the install (which took about 10-15 minutes, I would guess), the phone rebooted and was as if I had just taken it out of the box, though it was also activated! Note: this wiped EVERYTHING off the phone (though not what was stored on the MicroSD card). So, you should backup your data apps before you try anything on your phone. Heck, you should back it up anyway. We use MyBackupPro. Others use Titanium Backup (or whatever it is called). In any case, the phone performed the first update (a minor one pushed out to all Fascinate users) and then I downloaded and installed the Froyo update. That is a LONG download. UGH. Anyway, it worked! Once that was done and installed, I reinstalled the apps from the MyBackupPro and set up the email and my boss was back in business. We "celebrated" by hitting the local Mexican place for lunch.
After lunch, I headed to Prescott to install the new TAM unit sent by Tandberg. We thought we were just getting the control unit. Instead, they sent a new codec AND control unit, already connected and ready to go. We swapped out the corresponding parts, set the IP info, and fired it up for a test call. It worked perfectly. Since the touch panel had been disconnected during the swap, I reprogrammed the audio/video settings and it all ran smoothly!
By the time we cleaned up, it was quitting time.
I walked into the Verizon store and told the guy that I needed the phone flashed back to its original state. I explained the update problem and that I had found a solution online but thought it was better that Verizon do it in case I messed something up. I did not want to void the warranty if things went wrong. He walked (verbally) through the steps I had explained and took the phone. He immediately started the update, as though I had not just explained that I had been down this road and it comes to a sudden dead end. So, he downloads the update and begins the install. I protest repeatedly, but to avail. He is determined that when HE does it, it will work. I realize he has no idea that I have a bit of technical knowledge, but I did my best to explain to him everything I had done and how his attempt to update will end in failure given he is doing EXACTLY what I did (even pulling the battery etc).
After about 45 minutes or so of watching the install sit frozen at the "updating modem..." screen, he tries to restart the phone in "factory reset" mode - which is what I wanted in the first place, remember. No go. The phone reboots and immediately begins the update installation. this, of course, freezes at the "updating modem..." stage. Rinse, repeat. Seriously. I think he rebooted 3 or 4 more times, trying to get it into factory mode. Nope. He pulls up our account to see about getting a new phone, but he can't touch our account because it is a government account. Lovely. He hands me the now BRICKED phone and tells me to call my rep for a new phone. Ummm, this is FRIDAY and this is my boss' phone. You want me to tell my boss that you just killed her phone and that she will be without for the weekend!? Nice.
Well, since the phone was hosed anyway, I figured I would give the steps I found online a whirl. After a bit of trial and error, I managed to get the phone in a "Downloading" mode (note image was found online at Android Forums and is property of its original owner):
In this mode, the phone is ready to accept image updates transferred from a computer. Before I go further, I want to say that there is a factory reset option. But, because the phone was bricked, it only showed a phone icon with a computer next to it and maybe an X or something. Basically, it was saying it couldn't be factory reset (because of the hosed update).
So, I put the phone into this update mode (sorry, you will have to Google that yourself. I am not responsible for what you do to your phone!), downloaded the necessary software and ROM image to get the phone back to out-of-the-box fresh, and held my breath.
After the install (which took about 10-15 minutes, I would guess), the phone rebooted and was as if I had just taken it out of the box, though it was also activated! Note: this wiped EVERYTHING off the phone (though not what was stored on the MicroSD card). So, you should backup your data apps before you try anything on your phone. Heck, you should back it up anyway. We use MyBackupPro. Others use Titanium Backup (or whatever it is called). In any case, the phone performed the first update (a minor one pushed out to all Fascinate users) and then I downloaded and installed the Froyo update. That is a LONG download. UGH. Anyway, it worked! Once that was done and installed, I reinstalled the apps from the MyBackupPro and set up the email and my boss was back in business. We "celebrated" by hitting the local Mexican place for lunch.
After lunch, I headed to Prescott to install the new TAM unit sent by Tandberg. We thought we were just getting the control unit. Instead, they sent a new codec AND control unit, already connected and ready to go. We swapped out the corresponding parts, set the IP info, and fired it up for a test call. It worked perfectly. Since the touch panel had been disconnected during the swap, I reprogrammed the audio/video settings and it all ran smoothly!
By the time we cleaned up, it was quitting time.
May 19, 2011
On Thursday, May 19, 2011, I met with the Director and Asst Director regarding the future of TIE (Technology Infused Education). It looks like the program will continue one way or another, which is great news for teachers in Arkansas.
I had my area tech meeting starting at 10am, so before that, I installed Impero Client on a couple workstations in the lab for a demo. Once the meeting started, I discussed the Arkansas Digital Sandbox, ArkansasIDEAS, and Arkansas iTunesU. We had a demo from Xirrus Wireless (more a presentation, really). We discussed summer workshops, summer tech workshops specifically. We also went over the changes to the tech plan inventory requirements along with AUP templates/guides provided by the state education department.
After the meeting, I worked with Blevins on their transition to Google Apps for quite some time.
Near the end of the day, I went to the Asst Director's house to work on a data transfer issue between the iPad app called "AudioNote" and the computer. Turned out to be a much easier process than I was trying to make it. Basically, AudioNote will let you copy the recorded files through iTunes' file-sharing feature. This serves to back up the data so one can free up the space on the iPad. The audio files play in Quicktime, and rumor has it they can also be converted using Audacity. If that's true, I never hit the right combo of import settings to get the audio to play in Audacity. The format, according to Quicktime, is IMA-4, 16 kHz, Mono. Audacity has only one IMA setting and it would not let me pull the file in. I tried a variety of other options and still the file came in as a screechy mess. To me, it sounded like the scene in 'Strange Brew" where Bob and Doug play a floppy disk on their record player. In any case, we found a workable solution.
I had my area tech meeting starting at 10am, so before that, I installed Impero Client on a couple workstations in the lab for a demo. Once the meeting started, I discussed the Arkansas Digital Sandbox, ArkansasIDEAS, and Arkansas iTunesU. We had a demo from Xirrus Wireless (more a presentation, really). We discussed summer workshops, summer tech workshops specifically. We also went over the changes to the tech plan inventory requirements along with AUP templates/guides provided by the state education department.
After the meeting, I worked with Blevins on their transition to Google Apps for quite some time.
Near the end of the day, I went to the Asst Director's house to work on a data transfer issue between the iPad app called "AudioNote" and the computer. Turned out to be a much easier process than I was trying to make it. Basically, AudioNote will let you copy the recorded files through iTunes' file-sharing feature. This serves to back up the data so one can free up the space on the iPad. The audio files play in Quicktime, and rumor has it they can also be converted using Audacity. If that's true, I never hit the right combo of import settings to get the audio to play in Audacity. The format, according to Quicktime, is IMA-4, 16 kHz, Mono. Audacity has only one IMA setting and it would not let me pull the file in. I tried a variety of other options and still the file came in as a screechy mess. To me, it sounded like the scene in 'Strange Brew" where Bob and Doug play a floppy disk on their record player. In any case, we found a workable solution.
Thursday, May 19, 2011
May 18, 2011
Note: I had the wrong date listed as the subject before. I was off May 17th. I went to Prescott on the 18th. Thanks. --David
Went to Prescott to work on their distance learning system (upgrade the codec and TAM). The room was not available until after lunch, so I headed to the office. Once there, I helped get folks into the APSCN program on the Macs. When the Macs fire up, our network goes to a crawl. I have to figure out if it is a Mac-thing or a Parallels-thing. Placed a call to DIS and eventually determined the problem is local (also discovered a couple other network-related issues thanks to the wonderful help I received! We have some of the best folks working for us at the state level.
While troubleshooting and waiting for phone calls from DIS, I hooked up my mini with a usb-to-serial cable to my own DL equipment to make sure everything would work once I got back to Prescott. I downloaded some additional software needed for the TAM upgrade. After the DIS call and other general email/troubleshooting, I headed back to Prescott.
The codec upgrade went smoothly. Well, once we had the FULL key codes. Turned out the printout cut off the last digit. Thank goodness for email. The codec upgraded from F2.3 to F9.0.2 (through various stages of upgrades) just fine, though very slow going even through a directly-connected CAT5 cable.
The TAM upgrade failed because I could never get the mini to talk to the TAM. After calling tech support, we determined that the TAM itself was bad. We were doing all these upgrades because the original thought was that the touch panel was bad. Looks like the tech folks on the support end missed that one until I stepped in. That is not "tooting my own horn," but rather a demonstration that over-the-phone troubleshooting sometimes just doesn't cut it.
I did get a nice compliment, though. I was told that I had gone above and beyond ("covered all the bases and then some," I was told) in trying to get things to work. That's how I am: I will exhaust every possible avenue if feasible. The downside to that is that I am wired such I will keep trying sometimes past the point of cost-effectiveness. That is, it may cost more in man-hours than the device is worth - or cost more in man-hours than it would cost to start over with a clean slate. Guess that's the techie in me.
Went to Prescott to work on their distance learning system (upgrade the codec and TAM). The room was not available until after lunch, so I headed to the office. Once there, I helped get folks into the APSCN program on the Macs. When the Macs fire up, our network goes to a crawl. I have to figure out if it is a Mac-thing or a Parallels-thing. Placed a call to DIS and eventually determined the problem is local (also discovered a couple other network-related issues thanks to the wonderful help I received! We have some of the best folks working for us at the state level.
While troubleshooting and waiting for phone calls from DIS, I hooked up my mini with a usb-to-serial cable to my own DL equipment to make sure everything would work once I got back to Prescott. I downloaded some additional software needed for the TAM upgrade. After the DIS call and other general email/troubleshooting, I headed back to Prescott.
The codec upgrade went smoothly. Well, once we had the FULL key codes. Turned out the printout cut off the last digit. Thank goodness for email. The codec upgraded from F2.3 to F9.0.2 (through various stages of upgrades) just fine, though very slow going even through a directly-connected CAT5 cable.
The TAM upgrade failed because I could never get the mini to talk to the TAM. After calling tech support, we determined that the TAM itself was bad. We were doing all these upgrades because the original thought was that the touch panel was bad. Looks like the tech folks on the support end missed that one until I stepped in. That is not "tooting my own horn," but rather a demonstration that over-the-phone troubleshooting sometimes just doesn't cut it.
I did get a nice compliment, though. I was told that I had gone above and beyond ("covered all the bases and then some," I was told) in trying to get things to work. That's how I am: I will exhaust every possible avenue if feasible. The downside to that is that I am wired such I will keep trying sometimes past the point of cost-effectiveness. That is, it may cost more in man-hours than the device is worth - or cost more in man-hours than it would cost to start over with a clean slate. Guess that's the techie in me.
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.
* 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.
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.
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!
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!
Subscribe to:
Posts (Atom)