8:30a - 9:45a - Worked with Prescott schools during their Pinnacle software update. The update was performed via remote desktop session from tech support with Pinnacle. Ran into a couple snags during the configuration phase, but between the three of us, figured everything out and the software is ready for the 2010 school year rollover!
10:00a-12noon - Taught teachers how to access their new classroom portals, including posting announcement, events, photos, etc. Also discussed adding students and creating groups based on class periods, dropping students into those groups, then setting permissions so students could only participate in their assigned period discussions, etc.
12:00-12:15p - Talked to AT&T about moving the T1 connections. He had mistakenly been told to move the lines TODAY! Whoa! I am glad he called me! He said he would put everything in place and then we would be able to "flip the switch" on Friday to get connectivity to our new building.
1:00p-2:00p - Helped user recover distribution list that had been mistakenly deleted. Talked with Phoebe about the upcoming move, the convo with AT&T, and other issues related to the new building.
2:00p-2:20p - Talked with Bradley administrative assistant regarding her limited access to perform certain functions on her computer. Walked her through the process of adding her to the local admins group. Once done, she had access to all the software she needed to run (signage, Office, etc).
2:40-3:45p - Worked with Bob Cochenour at Western Co-op regarding a business-facing Facebook page. We set up the page then spent a considerable amount of time trying to lock down the page to meet their needs. Evidently, there is some 'super-secret' to getting Facebook to "let" you do that. Apparently, there is a "whitelisting" process that can provide this. Of course, actually getting support from facebook is impossible to find. It amazes me that we, as a society, allow ourselves to post and host personal information on a site that provides no easy means for contacting the people that run the show. There is something not right about that, I think.
During this process, I also helped one of our users with her login and password. I anticipate several folks needing that help as they return to schools after being off in the summer (and not checking email).
3:45p-4:00p - Called Bradley schools to talk with HS Principal regarding the IP addresses for their video systems. Apparently, DLC had to cancel a few of their classes at the last minute. Luckily, ASMSA stepped in and will provide the needed classes. I also gave her the phone number to ArkansasIDEAS because she has a teacher that could not log in. I tried to locate the teacher with the STIN lookup tool that state techs have access to, but she did not appear in the database.
This site serves as public record of my activities as Technology Coordinator for Southwest Arkansas Education Co-op. This site will be used in conjunction with travel forms, calendars, minutes and other pertinent data, when used together, to build a robust view of the services I perform which help my main office, participating school districts, statewide initiatives, and the furthering of K12 education in Arkansas.
Tuesday, August 10, 2010
Monday, August 9, 2010
08/09/2010
8:00am - Helped a couple presenters get set up for presentations. The phone rang, and the tech from one district called to let me know that the power had gone out over the weekend, and now the server had an "IP Conflict" error on the screen. This is never a good sign and usually means a computer on campus is infected with software that makes that computer think *it* is the server.
I was able to remote into their server from my office and I could see the server was trying to acquire an IP address on a secondary network card. That is not normal for a server, as servers should have assigned addresses. I checked the settings and everything seemed okay. The tech unplugged all the wires from the main switch (including the router at one point, which gave us both a chuckle since suddenly my connection dropped!), and then plugged them back in one-by-one until the error message came back up again. Or, that was the plan. The error never came back up.
8:45am - I had to interrupt the phone call in order to help one of the presenters. After that, I met briefly with the Early Childhood Coordinator to talk about our upcoming office move.
8:55am - I called the tech back at the school. Everything looks good, right? Nope. The server still showed it was trying to get an address. I disabled that card, and then PINGed the server's address. BINGO! Another machine was using the same address. One-by-one, I had the tech unplug a connection, then I would PING again. When she unplugged her tech workstation, the PINGs stopped replying. We found the culprit!
I had the tech check the properties and sure enough, under "Alternate Configuration," the workstation had been set to use the server's IP address. I have no idea how or why that was set like that. I had her change the setting back to "Private" and the conflict went away. I re-enabled the network card on the server and everything worked great. Almost.
The tech machine would no longer get an address from the server. When all else fails, reboot. After the computer rebooted, it grabbed a new address and everything worked fine so far as we can tell! Wahoo!
Now, at some point, we need to flush DNS and DHCP so the server can attribute the correct names with the correct addresses, but that's something we can do later. They don't really do anything using DNS internally, so it does not "actually" affect their network. (Yes, I know that's not exactly right, but for the pinch, it works).
*Mental mistake on my part: I did not fully understand that her tech machine (located next to the server) was the one giving the error as well. This would have saved some troubleshooting steps - namely, we would not have had to unplug each of the connections at the switch. Call it a learning experience.
9:30am - Finished the phone conversation with the tech, typed up the summary above, then called Asus because I have yet to receive the shipping instructions to send back the 1201N I worked on last week. I gave the tech my RMA number. he was very friendly and sent a new email out with the information. Now, I just have to wait to see if it gets here. If it is not here by noon, I will call back with my yahoo address.
9:45am - Called AT&T to let them know the address our new building changed - not the physical location, mind you, just the numbers associated with our new building. This may be one of those times where *not* saying anything would have been the right path to take. Guess we'll find out come Friday when the services are scheduled to be moved.
10:00am - Began installation of OpenOffice in the computer lab for a training taking place tomorrow.
10:45am - During install, called to Director's office to meet regarding a spreadsheet to keep track of Medicaid billing forms. The meeting also covered topics related to moving into the new building.
11:00am - Returned to computer lab to finish OpenOffice installation.
11:30am - Returned a phone call to AT&T about the new building address. And, just as I had suspected earlier, I have muddied the waters. There now seems to be confusion about physically moving the wiring that is already in place at our new building. So much for trying to do the right thing....thus far. We'll see how it goes from here. Had to leave a message. Will wait for return call.
11:40 - Began cleaning out SPAM filter. 12:10pm - finished (also had a brief meeting with the Workforce Ed coordinator regarding upcoming move during that time)
Around 1:00pm, I took a package over to the UPS store to have the malfunctioning laptop sent off to ASUS. Turns out the reason I was not getting the RMA information is because the email comes from a .TW domain, and we block those. Good thing I have an alternate offsite address to use.
Around 1:15pm, I headed over to the new building. I spent over two hours working with the alarm guys, elevator guy and meeting with the Director about other issues.
At 3:20pm, I made it back to the co-op to wrap up the day. Whew!
I was able to remote into their server from my office and I could see the server was trying to acquire an IP address on a secondary network card. That is not normal for a server, as servers should have assigned addresses. I checked the settings and everything seemed okay. The tech unplugged all the wires from the main switch (including the router at one point, which gave us both a chuckle since suddenly my connection dropped!), and then plugged them back in one-by-one until the error message came back up again. Or, that was the plan. The error never came back up.
8:45am - I had to interrupt the phone call in order to help one of the presenters. After that, I met briefly with the Early Childhood Coordinator to talk about our upcoming office move.
8:55am - I called the tech back at the school. Everything looks good, right? Nope. The server still showed it was trying to get an address. I disabled that card, and then PINGed the server's address. BINGO! Another machine was using the same address. One-by-one, I had the tech unplug a connection, then I would PING again. When she unplugged her tech workstation, the PINGs stopped replying. We found the culprit!
I had the tech check the properties and sure enough, under "Alternate Configuration," the workstation had been set to use the server's IP address. I have no idea how or why that was set like that. I had her change the setting back to "Private" and the conflict went away. I re-enabled the network card on the server and everything worked great. Almost.
The tech machine would no longer get an address from the server. When all else fails, reboot. After the computer rebooted, it grabbed a new address and everything worked fine so far as we can tell! Wahoo!
Now, at some point, we need to flush DNS and DHCP so the server can attribute the correct names with the correct addresses, but that's something we can do later. They don't really do anything using DNS internally, so it does not "actually" affect their network. (Yes, I know that's not exactly right, but for the pinch, it works).
*Mental mistake on my part: I did not fully understand that her tech machine (located next to the server) was the one giving the error as well. This would have saved some troubleshooting steps - namely, we would not have had to unplug each of the connections at the switch. Call it a learning experience.
9:30am - Finished the phone conversation with the tech, typed up the summary above, then called Asus because I have yet to receive the shipping instructions to send back the 1201N I worked on last week. I gave the tech my RMA number. he was very friendly and sent a new email out with the information. Now, I just have to wait to see if it gets here. If it is not here by noon, I will call back with my yahoo address.
9:45am - Called AT&T to let them know the address our new building changed - not the physical location, mind you, just the numbers associated with our new building. This may be one of those times where *not* saying anything would have been the right path to take. Guess we'll find out come Friday when the services are scheduled to be moved.
10:00am - Began installation of OpenOffice in the computer lab for a training taking place tomorrow.
10:45am - During install, called to Director's office to meet regarding a spreadsheet to keep track of Medicaid billing forms. The meeting also covered topics related to moving into the new building.
11:00am - Returned to computer lab to finish OpenOffice installation.
11:30am - Returned a phone call to AT&T about the new building address. And, just as I had suspected earlier, I have muddied the waters. There now seems to be confusion about physically moving the wiring that is already in place at our new building. So much for trying to do the right thing....thus far. We'll see how it goes from here. Had to leave a message. Will wait for return call.
11:40 - Began cleaning out SPAM filter. 12:10pm - finished (also had a brief meeting with the Workforce Ed coordinator regarding upcoming move during that time)
Around 1:00pm, I took a package over to the UPS store to have the malfunctioning laptop sent off to ASUS. Turns out the reason I was not getting the RMA information is because the email comes from a .TW domain, and we block those. Good thing I have an alternate offsite address to use.
Around 1:15pm, I headed over to the new building. I spent over two hours working with the alarm guys, elevator guy and meeting with the Director about other issues.
At 3:20pm, I made it back to the co-op to wrap up the day. Whew!
Friday, August 6, 2010
08/06/2010
Today is the last "free Friday" we have at the office. Well, it's not really "free," since we worked four 10-hour days prior to today, but this is the last Friday the offices are closed.
Later this afternoon, I plan to VPN into the network, perform a bit of weekend maintenance on the servers, and call it a weekend.
Weekend maintenance generally includes system testing that I like to do during the day hours and also some general cleanup on the servers that can't be done while folks are in the office using them heavily.
I hope everyone has a great weekend!
Later this afternoon, I plan to VPN into the network, perform a bit of weekend maintenance on the servers, and call it a weekend.
Weekend maintenance generally includes system testing that I like to do during the day hours and also some general cleanup on the servers that can't be done while folks are in the office using them heavily.
I hope everyone has a great weekend!
Thursday, August 5, 2010
08/05/2010
At 7:00am, I left my house and traveled 15 miles to the Blevins School District. There, I met with the Superintendent briefly to discuss the school's web site situation. He informed me that they were looking into a hosted scenario, most likely going with a particular vendor as the host. We also discussed an upcoming staff development in which a shared folder was needed. I left the office and sought out the school technology coordinator.
At approximately 7:20am, I met with Mr. Allen at the Blevins High School in order to locate the Technology Coordinator (turns outs he had an appointment and would not be in). We talked about the shared folder and the Windows 98 machine that currently runs the ConsoleOne software for adding users, etc. The floors were being waxed, so I did not have access to the appropriate room.
At approximately 7:30am, I met with Mrs. Lee in the Elementary building to discuss the school's potential new web site host. We talked about the teacher who had started to redevelop the site and Mrs. Lee let me know that she would tell the teacher of the impending changes.
Around 8:00am, I left Blevins and drove 15 miles back to Prescott, as I would be presenting a workshop on the school's new Sharepoint-based web site. During the drive, I spoke with the Blevins Technology Coordinator and filled him on my site visit. Since I arrived back in Prescott early, I helped the local technology coordinator with several issues on their web site. I also researched various ways to connect Outlook to their Sharepoint site.
At 9:30am, the Prescott Tech and I walked to the Elementary School to troubleshoot a fiber connectivity issue. Though we could not resolve the issue, we did manage to eliminate possible reasons for the problems.
At 10:00am, the tech and I headed to the lab to conduct the workshop with teachers. During the training, teachers learned how to post announcements, pictures, assignments, etc to their individual pages. They also learned how students will be able to turn in electronic assignments through the web site.
At 12:00pm, I drove from Prescott to Hope (our main office). When I arrived at approx 12:30pm, I helped the various CIV programs get underway, performed a cleanout of the SPAM quarantine system, and met with Phoebe regarding several building-related issues (re: new building).
Throughout the afternoon, I answered phone calls regarding tech support, answered email re: the same.
At approximately 2:15pm, the Supt for Fouke came in and we visited about his technology improvements rolled out this summer. I offered assistance and will be visiting the campus once our office move is complete. While meeting with him, the principal from Genoa came in and we began a discussion regarding podcasting with video. The plan is to have two or three teachers record their lessons as they teach them. After approximatelt 4 1/2 weeks, the teachers (or techs or students, depending on who will do final editing) will be trained on editing the video for distribution. The most likely channel will be Arkansas iTunesU. Both the Supt from Fouke and the Principal from genoa left satisifed with our visit.
From approx 2:45pm - 3:00pm, I wrote out this documentation. The time from 3:00pm - 5:00 (our summer office hours) will be added to this post later in the evening.
3:00pm - 3:35pm, checked email, answered several phone calls and discussed various building-related topics with Distance Learning Coordinator.
3:35pm - 3:50pm, I talked on the phone with Asus tech support regarding an ongoing issue with a 1201N laptop we have. After explaining the various steps (not to mention length of time - in WEEKS) I have taken, the tech agreed that the unit should be sent in for warranty work. While on hold for RMA, I restored the unit to factory specs (thus removing any work-related information). At the completion of the call, I emailed my boss to let her know the status.
Around 4:00pm, I talked with the teacher at Blevins regarding the web page changes, hosting etc. We talked for about 5 minutes and had a brainstorming session. It went pretty well. There is much to do on that front though.
At about 4:05pm, the High School Principal from Bradley met me (along with other personnel) and said she appreciated everything I did and do for her school! Wahoo! It was a wonderful compliment! We don't always get the "atta boys" and I am not one who seeks that kind of thing out, but it's nice to know that people notice what we do!
From 4:15 - 4:25, I spoke with Mrs. Lee at Blevins regarding their choice for web hosting, and I was very pleased with sample sites I had seen. factor in the post e-rate pricing, and I saw it as a win-win all around. I think the teacher that had already created content could easily copy/transfer the info into the hosted solution if they go with it.
LOOKING AHEAD:
Next week should prove to be quite full. I understand there is a meeting with the general contractor about elevator inspection and at the end of the week, we move our data and phone lines. I am very nervous about it as I have never done anything like this before.
At approximately 7:20am, I met with Mr. Allen at the Blevins High School in order to locate the Technology Coordinator (turns outs he had an appointment and would not be in). We talked about the shared folder and the Windows 98 machine that currently runs the ConsoleOne software for adding users, etc. The floors were being waxed, so I did not have access to the appropriate room.
At approximately 7:30am, I met with Mrs. Lee in the Elementary building to discuss the school's potential new web site host. We talked about the teacher who had started to redevelop the site and Mrs. Lee let me know that she would tell the teacher of the impending changes.
Around 8:00am, I left Blevins and drove 15 miles back to Prescott, as I would be presenting a workshop on the school's new Sharepoint-based web site. During the drive, I spoke with the Blevins Technology Coordinator and filled him on my site visit. Since I arrived back in Prescott early, I helped the local technology coordinator with several issues on their web site. I also researched various ways to connect Outlook to their Sharepoint site.
At 9:30am, the Prescott Tech and I walked to the Elementary School to troubleshoot a fiber connectivity issue. Though we could not resolve the issue, we did manage to eliminate possible reasons for the problems.
At 10:00am, the tech and I headed to the lab to conduct the workshop with teachers. During the training, teachers learned how to post announcements, pictures, assignments, etc to their individual pages. They also learned how students will be able to turn in electronic assignments through the web site.
At 12:00pm, I drove from Prescott to Hope (our main office). When I arrived at approx 12:30pm, I helped the various CIV programs get underway, performed a cleanout of the SPAM quarantine system, and met with Phoebe regarding several building-related issues (re: new building).
Throughout the afternoon, I answered phone calls regarding tech support, answered email re: the same.
At approximately 2:15pm, the Supt for Fouke came in and we visited about his technology improvements rolled out this summer. I offered assistance and will be visiting the campus once our office move is complete. While meeting with him, the principal from Genoa came in and we began a discussion regarding podcasting with video. The plan is to have two or three teachers record their lessons as they teach them. After approximatelt 4 1/2 weeks, the teachers (or techs or students, depending on who will do final editing) will be trained on editing the video for distribution. The most likely channel will be Arkansas iTunesU. Both the Supt from Fouke and the Principal from genoa left satisifed with our visit.
From approx 2:45pm - 3:00pm, I wrote out this documentation. The time from 3:00pm - 5:00 (our summer office hours) will be added to this post later in the evening.
3:00pm - 3:35pm, checked email, answered several phone calls and discussed various building-related topics with Distance Learning Coordinator.
3:35pm - 3:50pm, I talked on the phone with Asus tech support regarding an ongoing issue with a 1201N laptop we have. After explaining the various steps (not to mention length of time - in WEEKS) I have taken, the tech agreed that the unit should be sent in for warranty work. While on hold for RMA, I restored the unit to factory specs (thus removing any work-related information). At the completion of the call, I emailed my boss to let her know the status.
Around 4:00pm, I talked with the teacher at Blevins regarding the web page changes, hosting etc. We talked for about 5 minutes and had a brainstorming session. It went pretty well. There is much to do on that front though.
At about 4:05pm, the High School Principal from Bradley met me (along with other personnel) and said she appreciated everything I did and do for her school! Wahoo! It was a wonderful compliment! We don't always get the "atta boys" and I am not one who seeks that kind of thing out, but it's nice to know that people notice what we do!
From 4:15 - 4:25, I spoke with Mrs. Lee at Blevins regarding their choice for web hosting, and I was very pleased with sample sites I had seen. factor in the post e-rate pricing, and I saw it as a win-win all around. I think the teacher that had already created content could easily copy/transfer the info into the hosted solution if they go with it.
LOOKING AHEAD:
Next week should prove to be quite full. I understand there is a meeting with the general contractor about elevator inspection and at the end of the week, we move our data and phone lines. I am very nervous about it as I have never done anything like this before.
Subscribe to:
Posts (Atom)