Monday - Visit Genoa Schools to troubleshoot issues with DL. After all connections were re-seated, system worked fine. Talked with early childhood program there and the local tech to discuss network connectivity. As Trish and I left, the cables for the network connection were arriving via courier. We then went to Texarkana schools to meet with their distance learning facilitator. Everything was fine technically. I met with Technology Clerk and TCC regarding new scheduling implementation. There will be a meeting between the three of us and the Director on Friday to hammer out some details and iron out issues with the program. I went to the Hope ECH to connect interactive whiteboard, test networking, reset printer connections.
Tuesday - Will be at Arch Ford Co-op for statewide tech meeting
Wednesday - Will be in Conway for a statewide grant program meeting
Thursday - Office
Friday - Office
Showing posts with label distance learning. Show all posts
Showing posts with label distance learning. Show all posts
Monday, August 20, 2012
Tuesday, January 24, 2012
January 23-27, 2012
Monday - Office
Tuesday - Office
Wednesday - Bradley
Thursday - Genoa (possibly)
Friday - Office
Monday, spent the morning in the office then headed to Fouke to look at a DL problem. Turns out, they do not have a mic mixer for their ceiling mic. Talked to the tech support folks, they will be in touch. From there, headed to Prescott to look at their DL issue (remote control). I thought the problem was related to the plate in the top of the C20, but instead, the issue was much simpler. Inside Tandberg remote battery compartments is a switch. The switch regulates how much power is being used for the IR output. By default, it is set on low. That works well for close-up remote needs and/or incandescent lighting. For fluorescent, though, you need to flip the switch to HIGH power. So, I flipped the switch and it works great. I had forgotten that was even in the battery compartment until yesterday.
Tuesday, heading out to Hope ECH to troubleshoot connectivity and SmartBoards. We'll see what the rest of the day holds...
Problem at Hope ECH is directlt related to a coupler being used between two pieces of network wire. I will most likely run a new line so that we do not have this problem in the future.
The smartBoard problem was a result of screen resolution to the projector. I adjusted the resolution so that the display would show the entire desktop area, filling the projection screen (it had been "squished" due to a much higher resolution). This fixed the SmartBoard problem.
Installed Apple TV on the TV in the Asst Director's office. AppleTV, at the time of this writing, does not have alive weather program. Seriously!? Lame. So, I contact Weather.com to encourage them to work with Apple on getting a channel on the system. No, I am not going to jailbreak the AppleTV. I shouldn't have to, and besides, this is a company installation.
Worked with Prescott via phone regarding their technology survey results.
Worked with UACCH regarding an RUS grant for which we are a partner. They needed a specific invoice and copy of payment for the grant. I ran that over as soon as I had a copy.
Working on other daily tasks as well - email, phone calls, etc.
Tuesday - Office
Wednesday - Bradley
Thursday - Genoa (possibly)
Friday - Office
Monday, spent the morning in the office then headed to Fouke to look at a DL problem. Turns out, they do not have a mic mixer for their ceiling mic. Talked to the tech support folks, they will be in touch. From there, headed to Prescott to look at their DL issue (remote control). I thought the problem was related to the plate in the top of the C20, but instead, the issue was much simpler. Inside Tandberg remote battery compartments is a switch. The switch regulates how much power is being used for the IR output. By default, it is set on low. That works well for close-up remote needs and/or incandescent lighting. For fluorescent, though, you need to flip the switch to HIGH power. So, I flipped the switch and it works great. I had forgotten that was even in the battery compartment until yesterday.
Tuesday, heading out to Hope ECH to troubleshoot connectivity and SmartBoards. We'll see what the rest of the day holds...
Problem at Hope ECH is directlt related to a coupler being used between two pieces of network wire. I will most likely run a new line so that we do not have this problem in the future.
The smartBoard problem was a result of screen resolution to the projector. I adjusted the resolution so that the display would show the entire desktop area, filling the projection screen (it had been "squished" due to a much higher resolution). This fixed the SmartBoard problem.
Installed Apple TV on the TV in the Asst Director's office. AppleTV, at the time of this writing, does not have alive weather program. Seriously!? Lame. So, I contact Weather.com to encourage them to work with Apple on getting a channel on the system. No, I am not going to jailbreak the AppleTV. I shouldn't have to, and besides, this is a company installation.
Worked with Prescott via phone regarding their technology survey results.
Worked with UACCH regarding an RUS grant for which we are a partner. They needed a specific invoice and copy of payment for the grant. I ran that over as soon as I had a copy.
Working on other daily tasks as well - email, phone calls, etc.
Wednesday, January 4, 2012
Wednesday
When I arrived, I started working on building a report for target testing data. The data was sent in Excel, which I imported into Access, created a count query and a report to go with it, then converted the report to pdf for distribution to appropriate personnel.
Drove to Fouke with the Distance Learning Coordinator to look at a couple of tech issues in the DL lab.
We installed a HDMI cable to connect a 2nd TV to the codec. The image appears the same on both monitors. This is not normally what happens. After quite a bit of experimenting, there was no way to get the image to show in-class on one screen and incoming on the other. There must be a setting somewhere I am missing. I will check out a similar system at another campus, take notes and revisit the system at Fouke.
We installed a document camera on the codec. For some reason, when selecting "presentation," the system switches to a dual-screen mode showing the far site and near site but does not switch to the document camera. Using the remote, however, the facilitator can switch to the document camera manually. While not ideal, this will serve to meet the needs until we get the remote/configuration figured out.
Talked briefly with the Technology Coordinator and Ass't TC regarding tech plans, e-rate, A-Plus learning, and connecting Macs into the Active Directory.
Visited with the Supt and other staff before we left campus.
At the office, I worked on grant evaluation procedures, e-rate, and addressed/replied to work-related emails.
Drove to Fouke with the Distance Learning Coordinator to look at a couple of tech issues in the DL lab.
We installed a HDMI cable to connect a 2nd TV to the codec. The image appears the same on both monitors. This is not normally what happens. After quite a bit of experimenting, there was no way to get the image to show in-class on one screen and incoming on the other. There must be a setting somewhere I am missing. I will check out a similar system at another campus, take notes and revisit the system at Fouke.
We installed a document camera on the codec. For some reason, when selecting "presentation," the system switches to a dual-screen mode showing the far site and near site but does not switch to the document camera. Using the remote, however, the facilitator can switch to the document camera manually. While not ideal, this will serve to meet the needs until we get the remote/configuration figured out.
Talked briefly with the Technology Coordinator and Ass't TC regarding tech plans, e-rate, A-Plus learning, and connecting Macs into the Active Directory.
Visited with the Supt and other staff before we left campus.
At the office, I worked on grant evaluation procedures, e-rate, and addressed/replied to work-related emails.
Tuesday, October 18, 2011
10/07/11 - 10/18/11
10/7 - Had an aerohive demo for possible wireless solution at the co-op main building. Took care of general troubleshooting and other daily tasks.
10/10/11 - Installed new CIV systems at Blevins as part of RUS Grant.
10/11/11 - Installed new CIV systems at Prescott as part of RUS Grant. Also worked with Doug on a couple Sharepoint issues that seem to center on a webpart for slideshows. The java script used evidently clashes in some systems with the code for rich-text editing. Working to find another slideshow solution.
10/12/11 - Met with the Business, Technology, and Education Advisory Council for UACCH. Had a very open, frank conversation regarding skills needed, classes and topics to be taught. Met with Curtis Stout Company to evaluate a possible Crestron solution for the co-ops main conference center.
10/13/11 - Met with various staff and performed daily tech activities, troubleshooting etc.
10/14/11 - Went to Bradley to help with various issues: SmartBoard, graphics issues, wireless, and other areas of needed assistance.
10/17/11 - Performed daily tech activites, upgraded iPad to iOS5, worked on two laptops and replaced a desktop. Checked one of the smartphones for problems. Temporary solution was to disable shortcut keys. Phone is eligible for upgrade/replacement.
10/18/11 - Replaced a bulb in Hope ECH classroom, present to the board the "App of the Month" - AudioNote, examined an older laptop for possible replacement.
10/10/11 - Installed new CIV systems at Blevins as part of RUS Grant.
10/11/11 - Installed new CIV systems at Prescott as part of RUS Grant. Also worked with Doug on a couple Sharepoint issues that seem to center on a webpart for slideshows. The java script used evidently clashes in some systems with the code for rich-text editing. Working to find another slideshow solution.
10/12/11 - Met with the Business, Technology, and Education Advisory Council for UACCH. Had a very open, frank conversation regarding skills needed, classes and topics to be taught. Met with Curtis Stout Company to evaluate a possible Crestron solution for the co-ops main conference center.
10/13/11 - Met with various staff and performed daily tech activities, troubleshooting etc.
10/14/11 - Went to Bradley to help with various issues: SmartBoard, graphics issues, wireless, and other areas of needed assistance.
10/17/11 - Performed daily tech activites, upgraded iPad to iOS5, worked on two laptops and replaced a desktop. Checked one of the smartphones for problems. Temporary solution was to disable shortcut keys. Phone is eligible for upgrade/replacement.
10/18/11 - Replaced a bulb in Hope ECH classroom, present to the board the "App of the Month" - AudioNote, examined an older laptop for possible replacement.
Thursday, October 6, 2011
10/3/11 - 10/6/11
Monday - came to office until 10:30am then went home sick.
tuesday - Genoa Central middle school and elementary school video installs. Then, went to the high school to work on two video systems there. Reconfigured main DL for 100/Full connectivity and changed IP information on the new system for virtual field trip use (or class use via V2IU connection in Little Rock).
Wednesday - Attended ACOOP training on new DRP software from state. in the afternoon, installed the portable video unit for the co-op. Went to UACCH to help with that video unit install. Hit a few glitches there, but got them ironed out. Left UACCH with installer and headed to Nevada Schools. There, we installed the new video unit.
Thursday - Spent most of the day providing tech support to Fouke for a new server application install. Also handled email correspondence regarding video issues at Bradley. Scheduled the monthly area tech meeting. Talked with several vendors. Set up an on-site visit for Prescott on Friday after a meeting I have with a wireless (wifi, not cell) vendor. Installed a new network printer in the specialists' area. Hunted down a rogue wireless access point on the network. Well, "rogue" is a bit strong. It was one that had been misconfigured and I set it to right. Explored a couple of iPad apps for tech usage, but found them lacking (sorry, the names of the apps escapes me just now). Oh yeah, had to hunt down a telephone extension issue that turned out to be an issue with the placards we use to display people's extensions - a lot of troubleshooting and wire-moving for not, it seems. Emailed to several lists - cooptc, sys_admin, etc regarding various issues and topics. Experimented with various DHCP scenarios on our server. Researched various ISA 2006 settings and scenarios, user permissions issues, etc.
tuesday - Genoa Central middle school and elementary school video installs. Then, went to the high school to work on two video systems there. Reconfigured main DL for 100/Full connectivity and changed IP information on the new system for virtual field trip use (or class use via V2IU connection in Little Rock).
Wednesday - Attended ACOOP training on new DRP software from state. in the afternoon, installed the portable video unit for the co-op. Went to UACCH to help with that video unit install. Hit a few glitches there, but got them ironed out. Left UACCH with installer and headed to Nevada Schools. There, we installed the new video unit.
Thursday - Spent most of the day providing tech support to Fouke for a new server application install. Also handled email correspondence regarding video issues at Bradley. Scheduled the monthly area tech meeting. Talked with several vendors. Set up an on-site visit for Prescott on Friday after a meeting I have with a wireless (wifi, not cell) vendor. Installed a new network printer in the specialists' area. Hunted down a rogue wireless access point on the network. Well, "rogue" is a bit strong. It was one that had been misconfigured and I set it to right. Explored a couple of iPad apps for tech usage, but found them lacking (sorry, the names of the apps escapes me just now). Oh yeah, had to hunt down a telephone extension issue that turned out to be an issue with the placards we use to display people's extensions - a lot of troubleshooting and wire-moving for not, it seems. Emailed to several lists - cooptc, sys_admin, etc regarding various issues and topics. Experimented with various DHCP scenarios on our server. Researched various ISA 2006 settings and scenarios, user permissions issues, etc.
9/29-9/30 2011
Thursday, Sept 29 - Spent part of the day off and on researching and ordering various replacement items and equipment. Spent the better part of the morning meeting with the Director and Assistant Director over various issues - parking light timer, surveillance video, personnel matters, etc.
Cleaned my office since I had been out much of the previous few days. While doing so, I answered emails, conducted support via phone and text. a LOT of emails regarding distance learning connectivity and quality issues.
Friday, Sept 30 - Honestly, I don't remember what I did. A review of emails dated from that day shows a LOT of troubleshooting various distance learning network issues with a couple of schools - Bradley in particular. This was done through DIS, the school, and other personnel related to the process (AT&T, UACCH, etc).
I updated the trainer for an upcoming ACOOP training (the training took place on Oct 5).
I also spent a bulk of Friday at Blevins working on a variety of network, server, and desktop issues.
Cleaned my office since I had been out much of the previous few days. While doing so, I answered emails, conducted support via phone and text. a LOT of emails regarding distance learning connectivity and quality issues.
Friday, Sept 30 - Honestly, I don't remember what I did. A review of emails dated from that day shows a LOT of troubleshooting various distance learning network issues with a couple of schools - Bradley in particular. This was done through DIS, the school, and other personnel related to the process (AT&T, UACCH, etc).
I updated the trainer for an upcoming ACOOP training (the training took place on Oct 5).
I also spent a bulk of Friday at Blevins working on a variety of network, server, and desktop issues.
Tuesday, September 27, 2011
Testing, testing. Is this thing on?
Monday, Trish and I headed to Bradley with various equipment in tow. Our goal: test the local network for video connectivity issues.
I borrowed a fiber/CAT5 tester from the local college's telecommunications department. Once we arrived, we hooked the tester up to one run of fiber. the tester consists of two end pieces - once each end of the cable to be tested is plugged into each end of the fiber, the system runs a variety of tests. the first test checks for the maximum throughput speed (up to 1000Mbps). The next series of tests runs 'dummy data' between the connections in an effort to see what actual traffic the line can handle.
Over the course of several hours (most of the day, actually), we ran tests on each of the four fiber connections (each one for a different video system). Each and every time, the tests came back with flying colors - 1000Mbps and "pass" every other test. We also tested the CAT5 connections to ensure they, too, were operating at maximum ability. They were. Again, 1000Mbps and "pass" all the other tests.
This tells me that the issue is not a local one. However, just to be sure, we also swapped out the core switch that connects the various video systems to the rest of the world. After swapping out the switch, everything ran just as it had before. Again, this indicates to me that the issue is not a local one (or at least not a local one that I can tell).
While there, we also went to each distance learning classroom and configured the laptops for connectivity, printing, etc. We finished in each room except for Lab #3. That will get done next time I am at the school (thinking Wednesday).
Anecdotally, we noticed that the data connectivity seemed to be running pretty slowly (I downloaded required software and it showed to be running at T1 speeds versus the 10Mbps they have added). Something seems amiss on the data side.
the school is set up such that the data traffic and the compressed video traffic are not on the same LAN. once the data hits the router, it is no longer a school-fixable issue - we call in the support from the state folks.
once back at the co-op (about an hour leftof the work day), I kicked out an email to appropriate personnel regarding our findings at Bradley. I also created a quick network map of the video LAN to help with troubleshooting and forwarded that on to DIS personnel.
I borrowed a fiber/CAT5 tester from the local college's telecommunications department. Once we arrived, we hooked the tester up to one run of fiber. the tester consists of two end pieces - once each end of the cable to be tested is plugged into each end of the fiber, the system runs a variety of tests. the first test checks for the maximum throughput speed (up to 1000Mbps). The next series of tests runs 'dummy data' between the connections in an effort to see what actual traffic the line can handle.
Over the course of several hours (most of the day, actually), we ran tests on each of the four fiber connections (each one for a different video system). Each and every time, the tests came back with flying colors - 1000Mbps and "pass" every other test. We also tested the CAT5 connections to ensure they, too, were operating at maximum ability. They were. Again, 1000Mbps and "pass" all the other tests.
This tells me that the issue is not a local one. However, just to be sure, we also swapped out the core switch that connects the various video systems to the rest of the world. After swapping out the switch, everything ran just as it had before. Again, this indicates to me that the issue is not a local one (or at least not a local one that I can tell).
While there, we also went to each distance learning classroom and configured the laptops for connectivity, printing, etc. We finished in each room except for Lab #3. That will get done next time I am at the school (thinking Wednesday).
Anecdotally, we noticed that the data connectivity seemed to be running pretty slowly (I downloaded required software and it showed to be running at T1 speeds versus the 10Mbps they have added). Something seems amiss on the data side.
the school is set up such that the data traffic and the compressed video traffic are not on the same LAN. once the data hits the router, it is no longer a school-fixable issue - we call in the support from the state folks.
once back at the co-op (about an hour leftof the work day), I kicked out an email to appropriate personnel regarding our findings at Bradley. I also created a quick network map of the video LAN to help with troubleshooting and forwarded that on to DIS personnel.
Friday, September 23, 2011
Thursday and Friday
Thursday - Met at Arch Ford Co-op to learn about the online testing component of D2SC's program.
Friday - Headed to Bradley to downgrade the software on the new codec. Still had quality issues, so examined and changed settings on various media converters, switches, etc. The quality improved on the receiving end (that is, what we could see) but was still awful on the transmitting end (what the other sites saw). We've got some kind of issues going on there.
While testing, I ended up contacting ASMSA about a class that was not coming up and after some more troubleshooting, they had to delete the system from their MCU. After that, the MCU found the Bradley equipment again and everything (other than quality) seemed to be working.
I went around and checked various connection settings n the other three systems. I also helped troubleshoot a desktop problem which turned out to be a loose cat5 end at the desktop.
I am borrowing a fiber/copper tester from the local college and will head to Bradley on Monday so that I can run various tests.
Friday - Headed to Bradley to downgrade the software on the new codec. Still had quality issues, so examined and changed settings on various media converters, switches, etc. The quality improved on the receiving end (that is, what we could see) but was still awful on the transmitting end (what the other sites saw). We've got some kind of issues going on there.
While testing, I ended up contacting ASMSA about a class that was not coming up and after some more troubleshooting, they had to delete the system from their MCU. After that, the MCU found the Bradley equipment again and everything (other than quality) seemed to be working.
I went around and checked various connection settings n the other three systems. I also helped troubleshoot a desktop problem which turned out to be a loose cat5 end at the desktop.
I am borrowing a fiber/copper tester from the local college and will head to Bradley on Monday so that I can run various tests.
Thursday, September 22, 2011
Tuesday, Wednesday, and breaking through
Tuesday, Trish and I traveled to Fouke to meet with the SKC installer. When we arrived, he had already assembled most of the equipment. While he was finishing up, I started dismantling the old system - pulling wires out of the ceiling, etc. We employed some of the football players to pull the large screen TV off the table. The maintenance guy helped with some of the ceiling cabling work.
The system needed a ceiling mic adapter and the one that was sent to the school was a 'do-it-yourself' soldering job. Not happening. In the meantime, we ran into the same problem that we had in Bradley: no go on connectivity. I had DIS on the phone and they tried all kinds of troubleshooting. In the end, we hooked up the old system to get classes going again. Frustration levels were getting higher.
Back at the office, I worked on our firewall issues, and had to delete and recreated our Sharepoint Central Administration site. I'm not sure what happened there. As best I can figure, there was a SQL glitch preventing the site from actually displaying. A few command line entries and a server reboot later, it was back and happy!
Wednesday, met SKC and DIS at Genoa. We spent much of the morning troubleshooting connectivity issues when trying to add the new system into the mix. Turned out to be a bad switch. In the meantime, this new system had the same problems already seen: no connectivity. Luckily, Max with DIS brought a system with him - same model but running older software. He connected his system and it fired right up! So, Chris (SKC) downloaded a downgrade and pushed it out to the video unit. I am SEVERELY condensing time here, but once the new (er, old) software was dropped into place, the system fired up. Well, they also had to UNPAIR the touch panel from the codec. In any case, we had both systems up and running by about 1:30pm or so. Chris and I headed to Fouke. The software was installed and that system worked great! Also, Chris had received the correct cabling for the microphone and we connected it during class. The teacher said everything sounded fine and we left at the end of the day, knowing what we needed to do to the Bradley system. I will take care of that on Friday.
The system needed a ceiling mic adapter and the one that was sent to the school was a 'do-it-yourself' soldering job. Not happening. In the meantime, we ran into the same problem that we had in Bradley: no go on connectivity. I had DIS on the phone and they tried all kinds of troubleshooting. In the end, we hooked up the old system to get classes going again. Frustration levels were getting higher.
Back at the office, I worked on our firewall issues, and had to delete and recreated our Sharepoint Central Administration site. I'm not sure what happened there. As best I can figure, there was a SQL glitch preventing the site from actually displaying. A few command line entries and a server reboot later, it was back and happy!
Wednesday, met SKC and DIS at Genoa. We spent much of the morning troubleshooting connectivity issues when trying to add the new system into the mix. Turned out to be a bad switch. In the meantime, this new system had the same problems already seen: no connectivity. Luckily, Max with DIS brought a system with him - same model but running older software. He connected his system and it fired right up! So, Chris (SKC) downloaded a downgrade and pushed it out to the video unit. I am SEVERELY condensing time here, but once the new (er, old) software was dropped into place, the system fired up. Well, they also had to UNPAIR the touch panel from the codec. In any case, we had both systems up and running by about 1:30pm or so. Chris and I headed to Fouke. The software was installed and that system worked great! Also, Chris had received the correct cabling for the microphone and we connected it during class. The teacher said everything sounded fine and we left at the end of the day, knowing what we needed to do to the Bradley system. I will take care of that on Friday.
Tuesday, September 20, 2011
Mondays are... Mondays
Spent Monday morning working on various issues at the co-op. I created an installation checklist for the CIV systems that some of my area schools are receiving through an RUS grant. Turns out, much of the information I had was incorrect. Lovely.
I had to then battle a firewall issue in which Blackboard chatting is being blocked at the co-op. I have yet to figure out just which rule is preventing the chat. Even disabling most of the rules has not cured the problem. Frankly, after the bottlenecks and other issues, I think it's getting close to time to ditch ISA 2006 for good. The main issue is that it routes the 6 or so web sites we run through one IP. I prefer it that way so that we keep our servers out of the public hacking eye (er, mostly). In any case, it is time to research something else.
I spent the afternoon at Bradley, helping them work on a few issues before their new video system arrived. Once it did, we unboxed it. We waited for the installer to get there, but it was now 2:30 or so, and we decided to put the thing together ourselves. I had to leave just after three to pick up my daughter, so I left the folks working on it. The installer came just before three. I got a call later that night that the system would not register nor connect to the state video network. I will be going back to Bradley within the next day or so to get it working.
I ran back to the co-op for a quick stop after Bradley on my way to pick up my daughter from church. I had a switch at the office I wanted to take home to troubleshoot. Turns out, the switch just needs to be "decommissioned." It's loud (fans), has bad ports (at least one set of four) and it keeps rebooting itself. At least now I know!
I had to then battle a firewall issue in which Blackboard chatting is being blocked at the co-op. I have yet to figure out just which rule is preventing the chat. Even disabling most of the rules has not cured the problem. Frankly, after the bottlenecks and other issues, I think it's getting close to time to ditch ISA 2006 for good. The main issue is that it routes the 6 or so web sites we run through one IP. I prefer it that way so that we keep our servers out of the public hacking eye (er, mostly). In any case, it is time to research something else.
I spent the afternoon at Bradley, helping them work on a few issues before their new video system arrived. Once it did, we unboxed it. We waited for the installer to get there, but it was now 2:30 or so, and we decided to put the thing together ourselves. I had to leave just after three to pick up my daughter, so I left the folks working on it. The installer came just before three. I got a call later that night that the system would not register nor connect to the state video network. I will be going back to Bradley within the next day or so to get it working.
I ran back to the co-op for a quick stop after Bradley on my way to pick up my daughter from church. I had a switch at the office I wanted to take home to troubleshoot. Turns out, the switch just needs to be "decommissioned." It's loud (fans), has bad ports (at least one set of four) and it keeps rebooting itself. At least now I know!
Monday, September 19, 2011
9/14-9/16 2011
Wednesday - Met with the Board of Directors regarding CIPA, Internet Safety, RUS Grant CIV system installs, monthly tech meetings, Website requirements, Disaster recovery training.
After the meeting, I went to Blevins to help with various network related issues. We also tried to hunt down a rogue wireless device, but by then school was out. I believe the device is a 'hockey puck' portable wifi spot that someone brought and plugged in to the network. We will try again another day.
Thursday - Met with Jeff Madlock of Hope Schools regarding disaster recovery testing, policy, Apple Lion server and other tech-related issues.
Also met with representatives from Howard Technology regarding a touch panel control unit for our conference rooms. They will put together a quote and get back to me. In the meantime, I will call in 2 or 3 other vendors for quotes as well.
Had some issues in the computer lab, so I spent the bulk of the afternoon ironing those out. For the most part, Parallels would not print. Installed correct network printer drivers on the machines and took other measures to help keep the lab up and running. Mostly, I disabled some software updates and changed a few settings to help make the virtual environment more stable and efficient (memory settings, full-screen options, etc)
Friday - Spent the day in Fouke. We installed Server 2008 on two servers, created a secondary Domain Controller, and did some troubleshooting in a lab. We had to make a few changes to the DHCP settings, and they will need to make some more as well, as the pool has filled up. It is amazing how many devices they have! Talk about tech in schools! We also took care of some other network issues (DNS, subnets, etc)
After the meeting, I went to Blevins to help with various network related issues. We also tried to hunt down a rogue wireless device, but by then school was out. I believe the device is a 'hockey puck' portable wifi spot that someone brought and plugged in to the network. We will try again another day.
Thursday - Met with Jeff Madlock of Hope Schools regarding disaster recovery testing, policy, Apple Lion server and other tech-related issues.
Also met with representatives from Howard Technology regarding a touch panel control unit for our conference rooms. They will put together a quote and get back to me. In the meantime, I will call in 2 or 3 other vendors for quotes as well.
Had some issues in the computer lab, so I spent the bulk of the afternoon ironing those out. For the most part, Parallels would not print. Installed correct network printer drivers on the machines and took other measures to help keep the lab up and running. Mostly, I disabled some software updates and changed a few settings to help make the virtual environment more stable and efficient (memory settings, full-screen options, etc)
Friday - Spent the day in Fouke. We installed Server 2008 on two servers, created a secondary Domain Controller, and did some troubleshooting in a lab. We had to make a few changes to the DHCP settings, and they will need to make some more as well, as the pool has filled up. It is amazing how many devices they have! Talk about tech in schools! We also took care of some other network issues (DNS, subnets, etc)
Thursday, August 25, 2011
08/25/2011
Went to the office first. Helped set up a CIV with DVD recording. Headed to Bradley.
Dropped off math manipulatives for the high school and a bag of snacks for the ECH program. I am a man of many hats and talents!
In Bradley, talked with various DL personnel regarding connection issues, quality issues, etc. All the issues seem to be outbound-related. That is, the quality and connections are perfectly fine coming INTO the campus, but the other end(s) of the CIV are getting pixellation, stuttering, etc.
The tech and I ran a few local tests - internal network calls only, and everything ran smoothly, looked good, sounded good. The issue appears to be external, but we will see what DIS says after their testing and analysis.
The tech and I worked on several other issues: server backups, network wiring traces, hardware/software troubleshooting, etc.
I left Bradley and headed to the Lewisville ECH. They are having connectivity issues, but the bigger items are related to the computer being put on the school's local domain. That seems to have messed with some of the permissions and settings for the local user (even when not logged into the domain). I am working on those and think i have most of them pinned down and fixed.
After Lewisville, I went back to the office to drop off equipment I picked up and to pick up equipment to take with me to the Prescott schools, which i will be visiting in the morning.
Dropped off math manipulatives for the high school and a bag of snacks for the ECH program. I am a man of many hats and talents!
In Bradley, talked with various DL personnel regarding connection issues, quality issues, etc. All the issues seem to be outbound-related. That is, the quality and connections are perfectly fine coming INTO the campus, but the other end(s) of the CIV are getting pixellation, stuttering, etc.
The tech and I ran a few local tests - internal network calls only, and everything ran smoothly, looked good, sounded good. The issue appears to be external, but we will see what DIS says after their testing and analysis.
The tech and I worked on several other issues: server backups, network wiring traces, hardware/software troubleshooting, etc.
I left Bradley and headed to the Lewisville ECH. They are having connectivity issues, but the bigger items are related to the computer being put on the school's local domain. That seems to have messed with some of the permissions and settings for the local user (even when not logged into the domain). I am working on those and think i have most of them pinned down and fixed.
After Lewisville, I went back to the office to drop off equipment I picked up and to pick up equipment to take with me to the Prescott schools, which i will be visiting in the morning.
Monday, August 15, 2011
8/12/11
Started the day by working on several co-op issues before attending our annual "back to school" staff meeting. During the meeting, I had several calls from a district regarding distance learning issues. After I presented my part regarding network ethics, changing passwords, etc, I worked with our DL Coordinator and their tech to try and solve the problems.
After an hour or so, I decided I would head down to Bradley to help them. I had already told Prescott I would come there to help with THEIR distance learning issues. I called Prescott to let them know I would be late. About the time I got to my car, Bradley called to tell me they got it working. I headed to Prescott. On the way, Bradley called and things were not working, but we thought we could solve them over the phone. We were half right. I told them I would be there Monday.
In Prescott, the tech and I had to do some network restructuring to get their new DL system online, but it went smoother than expected! That opened up time to look at several other issues they were having. We knocked a few of those out, and the tech gave me permission to install Triptico on my wife's computer! Awesome!
After an hour or so, I decided I would head down to Bradley to help them. I had already told Prescott I would come there to help with THEIR distance learning issues. I called Prescott to let them know I would be late. About the time I got to my car, Bradley called to tell me they got it working. I headed to Prescott. On the way, Bradley called and things were not working, but we thought we could solve them over the phone. We were half right. I told them I would be there Monday.
In Prescott, the tech and I had to do some network restructuring to get their new DL system online, but it went smoother than expected! That opened up time to look at several other issues they were having. We knocked a few of those out, and the tech gave me permission to install Triptico on my wife's computer! Awesome!
Wednesday, August 10, 2011
8/10/11
Went to the office in order to help get a couple workshops up and going. After that, headed to Fouke.
At Fouke, I helped correct a few issues with the server - dns, dhcp, looked into some sophos issues. Then went to the business lab to determine why some machines were not joining her domain. After troubleshooting dns, tcpip, forwarding, lookups etc, I finally found the culprit - incorrect subnet mask on her server. The district had recently switched subnets and this server still had the old mask. Once that was fixed, the machines joined in with no problems! Awesome.
After that, helped troubleshoot some issues with a new Xirrus installation. Well, tried to help anyway. After poking around inside the configuration program for several arrays, we managed to get everything to look correctly as far as configs, but still have issues in one building with at least two (if not three) arrays. We even pushed the radios to 5ghz-only mode and that did not work. I called our local sales guy who said he would call the Xirrus reps and get someone to fix it. The tech had already spent more than 10 hours of phone time and webex time trying to solve the issue (among other issues).
During my time at Fouke, I also took several phone calls - from Blevins and Bradley - regarding troubleshooting etc. i also handled a multitude of text messages throughout the day relating to various school issues from various districts (blevins, fouke, the co-op itself, mainly).
I helped the district set up a template for active directory users and set up shares for home folders. Oh, also repartitioned a drive to make better use of the storage space.
On the way home, I spent time on the phone with the rep who sold Xirrus, talked to my director, and had conversations with Blevins and our DL coordinator.
At Fouke, I helped correct a few issues with the server - dns, dhcp, looked into some sophos issues. Then went to the business lab to determine why some machines were not joining her domain. After troubleshooting dns, tcpip, forwarding, lookups etc, I finally found the culprit - incorrect subnet mask on her server. The district had recently switched subnets and this server still had the old mask. Once that was fixed, the machines joined in with no problems! Awesome.
After that, helped troubleshoot some issues with a new Xirrus installation. Well, tried to help anyway. After poking around inside the configuration program for several arrays, we managed to get everything to look correctly as far as configs, but still have issues in one building with at least two (if not three) arrays. We even pushed the radios to 5ghz-only mode and that did not work. I called our local sales guy who said he would call the Xirrus reps and get someone to fix it. The tech had already spent more than 10 hours of phone time and webex time trying to solve the issue (among other issues).
During my time at Fouke, I also took several phone calls - from Blevins and Bradley - regarding troubleshooting etc. i also handled a multitude of text messages throughout the day relating to various school issues from various districts (blevins, fouke, the co-op itself, mainly).
I helped the district set up a template for active directory users and set up shares for home folders. Oh, also repartitioned a drive to make better use of the storage space.
On the way home, I spent time on the phone with the rep who sold Xirrus, talked to my director, and had conversations with Blevins and our DL coordinator.
Monday, July 25, 2011
07/25/2011
Drove straight to McRae Middle School to deliver several boxes of binders and books for a workshop taking place there today.
At the office, I talked with the presenter for a pocket camera workshop and we needed to update the software on the cameras being used. So, me and the DL coordinator and the presenter fired up Windows in Parallels and installed the correct software.
After that, Trish (DL Coordinator) and I headed to Bradley. in Bradley, we connected a new swicth and media converters to the video network in preparation for new equipment coming through an RUS grant. Once that was done, we went to the closet where the fiber terminated to install another media converter and switch. This allows for the video system to come online and for 24 computers to be installed in the new dl room.
After that, we went to an extsing dl room in order to disassemble a video system in order to reconfigure the hardware arrangement. The remote for the system would not work because the equipment had been installed backward in the podium. We fixed that, ran a couple test calls, and tied up loose wires, etc.
In the next dl room, we tied up loose wires and verified that things were working. The touch panel is having issues and we may need to update the software in both the codec and the touch panel this year.
There were three netbooks giving the local tech fits, so I helped get those situated and joined them to the domain.
I am scheduled to return on Tuesday with a Windows 7 DVD to reinstall software on a laptop and to run cabling for the new dl room.
At the office, I talked with the presenter for a pocket camera workshop and we needed to update the software on the cameras being used. So, me and the DL coordinator and the presenter fired up Windows in Parallels and installed the correct software.
After that, Trish (DL Coordinator) and I headed to Bradley. in Bradley, we connected a new swicth and media converters to the video network in preparation for new equipment coming through an RUS grant. Once that was done, we went to the closet where the fiber terminated to install another media converter and switch. This allows for the video system to come online and for 24 computers to be installed in the new dl room.
After that, we went to an extsing dl room in order to disassemble a video system in order to reconfigure the hardware arrangement. The remote for the system would not work because the equipment had been installed backward in the podium. We fixed that, ran a couple test calls, and tied up loose wires, etc.
In the next dl room, we tied up loose wires and verified that things were working. The touch panel is having issues and we may need to update the software in both the codec and the touch panel this year.
There were three netbooks giving the local tech fits, so I helped get those situated and joined them to the domain.
I am scheduled to return on Tuesday with a Windows 7 DVD to reinstall software on a laptop and to run cabling for the new dl room.
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.
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.
Thursday, November 18, 2010
Thursday
Busy day so far today. It is roughly 10:00 am, and I've had two conference calls and a CIV test. I met with the Early Childhood Coordinator regarding the installation of cameras and Skype for her teachers. The plan is to use Skype for parent meetings in order to avoid the driving from our main office to the school sites when face-to-face is not necessarily imperative. It looks VERY promising! I also made the appropriate modifications to the bosses' bookcases in order to hook up their LCD TVs. Once the TVs were hooked up, I fielded a call from Blevins regarding a non-deleting icon. That was an interesting adventure.
Evidently, the user dragged a message from Groupwise onto the desktop, thinking it wuold save a copy of the message. Instead, it created a .GWI file that would do nothing. When the user tried to delete it, it wuld not delete and instead get caught in an infinite "deleting" loop.
After a bit of research, and trial and error, I came across a post about a program I had forgotten about: Unlocker. Unlocker is a great tool that will show you what process(es) are holding the selected file(s) and then give you options to rename, remove, etc. You can find it here: http://ccollomb.free.fr/unlocker/
Once Unlocker was installed, we selected "Delete" from the drop-down and then played it safe with the least intrusive option (I cannot recall the exact wording). Ultimately, though, they got the same inifinte loop until they clicked the "Kill Process" button. As soon as they did, the icon disappeared and the process stopped! Excellent!
I had used unlocker before, though I cannot remember what the circumstance was. Now, I've used it twice with great success!
Let's see what the rest of the day holds.
Talked with the local cable company regarding pricing and installation. They will send a letter of proposal and we can decide from there whether or not we want the service.
I am also looking into using a dish-based service.
Received a call from Prescott's early childhood program - her main computer died. It seems all of these out-of-warranty Dells that the ECH programs have are dying lately. Not good! I'll be heading there Friday to swap out computers.
Fielded calls from Blevins regarding USB issues on several computers and regarding sites blocked by the state content filtering system.
Took care of general office duties as usual.
Near the end of the day, I decided to try and set up the security camera system for email notifications (that is, notify me when an 'event' happens). Still working on that one.
Evidently, the user dragged a message from Groupwise onto the desktop, thinking it wuold save a copy of the message. Instead, it created a .GWI file that would do nothing. When the user tried to delete it, it wuld not delete and instead get caught in an infinite "deleting" loop.
After a bit of research, and trial and error, I came across a post about a program I had forgotten about: Unlocker. Unlocker is a great tool that will show you what process(es) are holding the selected file(s) and then give you options to rename, remove, etc. You can find it here: http://ccollomb.free.fr/unlocker/
Once Unlocker was installed, we selected "Delete" from the drop-down and then played it safe with the least intrusive option (I cannot recall the exact wording). Ultimately, though, they got the same inifinte loop until they clicked the "Kill Process" button. As soon as they did, the icon disappeared and the process stopped! Excellent!
I had used unlocker before, though I cannot remember what the circumstance was. Now, I've used it twice with great success!
Let's see what the rest of the day holds.
Talked with the local cable company regarding pricing and installation. They will send a letter of proposal and we can decide from there whether or not we want the service.
I am also looking into using a dish-based service.
Received a call from Prescott's early childhood program - her main computer died. It seems all of these out-of-warranty Dells that the ECH programs have are dying lately. Not good! I'll be heading there Friday to swap out computers.
Fielded calls from Blevins regarding USB issues on several computers and regarding sites blocked by the state content filtering system.
Took care of general office duties as usual.
Near the end of the day, I decided to try and set up the security camera system for email notifications (that is, notify me when an 'event' happens). Still working on that one.
Tuesday, November 16, 2010
Tuesday
Stopped in Prescott first thing to drop off a DVD of the tech plan training we had on Friday. The tech had not made it to the office yet, so I dropped in to one of the DL labs since she was having trouble switching to her document camera.
Her system has been acting up, so I wired a bypass from the document camera to the codec (bypassing the touch panel module since it is out). I then showed the facilitator how to use the remote to switch between the various input devices (main camera, doc cam, etc).
After that, I visited with the tech for a bit. We talked about a whole range of topics (filters, wireless, web servers, etc). Before I left, we worked on his DNS server, Firewall and Sharepoint server to route traffic from their old web address to their new web server. We had previously set up a redirect page, but now we moved to actual IP resolution. The next step was to have him call DIS and make the change in the state DNS server(s).
Once I arrived at the office, I had several meetings planned out. First was one with DataCove for email archiving. After that, I met with IK Electric regarding phone systems, network security, and data aggregation/firewalling/content filtering.
Near the end of the day, Harry Dickens happened by so I visited with him at length about iPads, apps, and trainings that he had done recently at several of our area schools.
Her system has been acting up, so I wired a bypass from the document camera to the codec (bypassing the touch panel module since it is out). I then showed the facilitator how to use the remote to switch between the various input devices (main camera, doc cam, etc).
After that, I visited with the tech for a bit. We talked about a whole range of topics (filters, wireless, web servers, etc). Before I left, we worked on his DNS server, Firewall and Sharepoint server to route traffic from their old web address to their new web server. We had previously set up a redirect page, but now we moved to actual IP resolution. The next step was to have him call DIS and make the change in the state DNS server(s).
Once I arrived at the office, I had several meetings planned out. First was one with DataCove for email archiving. After that, I met with IK Electric regarding phone systems, network security, and data aggregation/firewalling/content filtering.
Near the end of the day, Harry Dickens happened by so I visited with him at length about iPads, apps, and trainings that he had done recently at several of our area schools.
Monday, November 15, 2010
Last Week
Monday (11/8) - general office work, as usual, so far as I can remember.
Tuesday (11/9) - 1/2 day at Blevins School District, worked on fiber connections. Had to hunt down a few lines to figure out how the connection for the new admin building met up with the current demarc location.
1/2 Tuesday, Wednesday, Thursday (11/9,10,11) - I was out sick.
Friday (11/12) - Back in office for a morning training on new tech plan development (CIV from ADE). That was followed by a local area tech meeting. The afternoon was spent cleaning/organizing the technology closet.
Tuesday (11/9) - 1/2 day at Blevins School District, worked on fiber connections. Had to hunt down a few lines to figure out how the connection for the new admin building met up with the current demarc location.
1/2 Tuesday, Wednesday, Thursday (11/9,10,11) - I was out sick.
Friday (11/12) - Back in office for a morning training on new tech plan development (CIV from ADE). That was followed by a local area tech meeting. The afternoon was spent cleaning/organizing the technology closet.
Subscribe to:
Posts (Atom)