Monday's work day began at 9:30am because I had to repair the plumbing in my mother's house. That's a story for another blog.
Much of the day was spent working on various issues at the new building, though I also answered email and phone calls from a couple of the schools.
We should be getting our projectors set up this week for the conference rooms and labs. During my lunch hour, I swapped out the temporary (read, ugly) telephone patch cables for new ones. This will help make moving extensions and troubleshooting connections easier down the road. Plus, it just looks nicer.
I also finally set up my own computer on my desk. It's a small step, but at least it is a step toward getting my own office area set up. For some reason, my computer now thinks it has the ability to display three monitors. Not sure what happened there, but I'll troubleshoot that later. In the meantime, I was able to configure the system for the two monitors I have connected. Though it might be "nice" to have three screens, I don't *need* three. Really. Two is just fine.
I ended the day by sifting through 30,000 emails that had been caught in our spam filter. Making a note: fix the system so users can check their own spam. I believe the issue is ISA Server related.
Tuesday, August 31, 2010
Friday, August 27, 2010
Friday, August 27, 2010
I'm sure I mentioned this before, but not all my posts will have the date, since I generally refer to the date in the post, and the posts publishing date are attached to the post itself. Then again, I may keep with this formula. We'll see.
Reconnected the CIV equipment in the lab since we had a GT videoconference. Moved the projector from that room to the "APSCN Mini Lab" we now have, since there was another APSCN workshop today.
Turns out, we were left off the room list for the videoconference, so through a bit of detective work in order to determine the actual NAME of the event, AT&T got us scheduled in! It's good to know the right number to call and to have a solid working relationship with those that can help get things done!
I made a run to the local hardware store to buy nuts for the bolts I am using for our switch racks. I don't know what the deal is, but the bolts I have are about a hair's width too skinny. Seriously. I have to screw them into the rack, but as soon as I let go of a switch, the screws pop out as if they are too small! Bizarre!
Several of us loaded up and went to the old building to clean up another several loads. At this time, I've got all the technology I can think of moved. I've got folks coming to help with Smart Board transfer, but that should do it!
Back at the office, I started moving switches around and using the nuts I bought to keep the bolts in place. Extra steps, but well worth it.
At 1:00 or so, I headed to Blevins to help with more troubleshooting. This time, I brought the FOX & Hound with me! Man, that makes all the difference in the world. They have wires going to places that do not necessarily match where people *think* they go. With the Fox & Hound, we traced out several connections and were able to get the trouble taken care of! Awesome!
At 3:30, I headed home. As I got close to the house, my phone rang and it was the office trying to get a couple of digital copiers set up on the network. I either have bad wiring, or misconnected wiring, or something. The tech could not get things working. Guess that'll be the project I start off with on Monday.
As yes, that reminds me. At various points throughout the week, I have been emailing back and forth with Bradley Schools. They are having connectivity issues. I am going to quickly get things up and going at the office on Monday, then head down south to see what I can do there.
When is human cloning coming?
Reconnected the CIV equipment in the lab since we had a GT videoconference. Moved the projector from that room to the "APSCN Mini Lab" we now have, since there was another APSCN workshop today.
Turns out, we were left off the room list for the videoconference, so through a bit of detective work in order to determine the actual NAME of the event, AT&T got us scheduled in! It's good to know the right number to call and to have a solid working relationship with those that can help get things done!
I made a run to the local hardware store to buy nuts for the bolts I am using for our switch racks. I don't know what the deal is, but the bolts I have are about a hair's width too skinny. Seriously. I have to screw them into the rack, but as soon as I let go of a switch, the screws pop out as if they are too small! Bizarre!
Several of us loaded up and went to the old building to clean up another several loads. At this time, I've got all the technology I can think of moved. I've got folks coming to help with Smart Board transfer, but that should do it!
Back at the office, I started moving switches around and using the nuts I bought to keep the bolts in place. Extra steps, but well worth it.
At 1:00 or so, I headed to Blevins to help with more troubleshooting. This time, I brought the FOX & Hound with me! Man, that makes all the difference in the world. They have wires going to places that do not necessarily match where people *think* they go. With the Fox & Hound, we traced out several connections and were able to get the trouble taken care of! Awesome!
At 3:30, I headed home. As I got close to the house, my phone rang and it was the office trying to get a couple of digital copiers set up on the network. I either have bad wiring, or misconnected wiring, or something. The tech could not get things working. Guess that'll be the project I start off with on Monday.
As yes, that reminds me. At various points throughout the week, I have been emailing back and forth with Bradley Schools. They are having connectivity issues. I am going to quickly get things up and going at the office on Monday, then head down south to see what I can do there.
When is human cloning coming?
Thursday, August 26, 2010
Set up the distance learning lab so APSCN folks could use the computers for training. Since our projectors and TVs are not here yet, this entailed hooking up a projector for the presenter and making sure the lab computers had the required programs.
Spent some time "unwrapping" all the iMacs in the new computer lab (pulling off all the plastic sheeting that Apple covers the monitors, keyboards and mice with - not to mention the apple logo pn the back of the screens. Really, is all that necessary!? I picked up some needed supplies at Elliot Electric and went to work on several connection-related issues.
At 3:00pm, I left to deliver Target Testing Answer Sheets to Prescott.
Spent some time "unwrapping" all the iMacs in the new computer lab (pulling off all the plastic sheeting that Apple covers the monitors, keyboards and mice with - not to mention the apple logo pn the back of the screens. Really, is all that necessary!? I picked up some needed supplies at Elliot Electric and went to work on several connection-related issues.
At 3:00pm, I left to deliver Target Testing Answer Sheets to Prescott.
Wednesday, August 25, 2010
Wednesday, August 25, 2010
Got to the office at 8am and helped get one of the literacy specialists connected to the network. I'll be glad when all the jacks are 'hot' and people can just plug and play. Well, okay, I'm not actually making every plug a 'hot one.' That way, if someone randomly just plugs in, they can't get anywhere on our network. Just a thought.
After that, I headed to the old building to load the van with old tech stuff to be hauled off to the recycling center in Prescott. After the round-trip, I still had a van-load of technology to load up and haul off, plus we had a load of papers that needed to be taken for shredding.
I loaded the van with tech trip #2 and made the trek back up the road to drop off round 2. My boss asked if I would swing by the old building on the way back in to town to grab some of the dollies located there. I did and headed for the new building. Once there, the dollies were unloaded.
We've got some hired help working for us, so I was allowed to take one with me back to the old building to load the papers for shredding. We loaded it up, headed to Prescott one last time, and after a bit of waiting on their employee to help us, we dropped off the paper then made the trek back to the co-op.
Once back, I connected one of the copiers to the network. Turns out, it needs some kind of module to print. The tech will be back on Thursday to hook it up.
I left the office at 4pm.
After that, I headed to the old building to load the van with old tech stuff to be hauled off to the recycling center in Prescott. After the round-trip, I still had a van-load of technology to load up and haul off, plus we had a load of papers that needed to be taken for shredding.
I loaded the van with tech trip #2 and made the trek back up the road to drop off round 2. My boss asked if I would swing by the old building on the way back in to town to grab some of the dollies located there. I did and headed for the new building. Once there, the dollies were unloaded.
We've got some hired help working for us, so I was allowed to take one with me back to the old building to load the papers for shredding. We loaded it up, headed to Prescott one last time, and after a bit of waiting on their employee to help us, we dropped off the paper then made the trek back to the co-op.
Once back, I connected one of the copiers to the network. Turns out, it needs some kind of module to print. The tech will be back on Thursday to hook it up.
I left the office at 4pm.
Tuesday, August 24, 2010
I got to the office and was met at the door with a few requests. In one case, the early childhood area was still having air problems. I decided the problem was a closed door to a room with a return air vent. I opened the door and told them to let me know how things went. I still need to check on that.
I ran a wire from the same room with the return air duct to a digital copier so the ECH folks could share it and print to it.
I had not heard from the folks that ran our video security system, but I had an idea: The only way into the conference room was through one wall. So, I got the 8-foot ladder and hiked up it. Sure enough, I found the wiring above the tiles. As it turns out, the wires run to LEFT instead of the right, as was indicated in an initial diagram. On top of that, it makes a turn back toward the center of the room. Now, had this been the status quo for the other runs, I would have started there the other day. Ah, well, the important thing is that I got the camera installed just in time for an afternoon staff meeting.
At 1:30pm, I drove to Blevins to help their tech troubleshoot connectivity issues. One of their main switches was blinking rapidly and rhythmically. While it might look cool, it only means there is a problem on the network. Rapidly blinking lights are normal. Rhythmically blinking lights are okay if you know everyone is basically doing the same thing (say, all access some interactive web site or something). But, when paired together, it's usually a bad sign.
I started unplugging connections, trying to get the lights to STOP blinking rhythmically. That failed. Even with one connection, the pattern was the same. This indicated the switch itself had gone bad. To test this, the tech and I moved the connections to a variety of "spare" switches he had. Everything seemed to be working to a point. The computer lab and a part of one hallway were not getting connectivity. Let the hunt begin!
Turns out there is a run from the switch to the computer lab. From the lab, there is a run to a classroom that feeds the rest of that part of the hallway. Let's just say it took quite a while to come up with that conclusion. let's also say that old buildings with uber-thick fiberglass insulation is not a fun combination.
We determined that the connection to the lab from the main switch was not behaving. The cure was to run a NEW wire. Did I mention fiberglass insulation? Oh, and dust? And other "stuff" we're not going to mention? He and I looked like we had just escaped from the cotton candy factory (though not all the "cotton candy" was pink...). The key is that when all was said and done (around 5:00pm), it all worked!
At 5:15pm, I headed for the house.. Er, the school where my wife works to pick up the kids. Now, how does this tie in to work? While in my wife's room, she told me her SmartBoard wasn't making any sound. I did some troubleshooting and determined that the audio for the board was showing up as an "unknown" USB device. FYI, on systems with a Smart Board, there is often an "USB Audio Device" that can be selected. My wife's computer did not have this. It is a driver issue, but she does not have enough rights as a user to install the driver. While this could have spelled the end of the issue as far as I could help, I pushed on. Turns out, SOME teachers had an RCA-Headphone wire that connected their sound to the speakers on the board. So... I found a teacher that had BOTH - the USB *and* the adapter. Since they had the USB working, their adapter was not plugged in. I borrowed the adapter and connected it to my wife's computer. When the projector is *on* now, she has sound.
I will email the tech at the district so he knows what's going on.
I ran a wire from the same room with the return air duct to a digital copier so the ECH folks could share it and print to it.
I had not heard from the folks that ran our video security system, but I had an idea: The only way into the conference room was through one wall. So, I got the 8-foot ladder and hiked up it. Sure enough, I found the wiring above the tiles. As it turns out, the wires run to LEFT instead of the right, as was indicated in an initial diagram. On top of that, it makes a turn back toward the center of the room. Now, had this been the status quo for the other runs, I would have started there the other day. Ah, well, the important thing is that I got the camera installed just in time for an afternoon staff meeting.
At 1:30pm, I drove to Blevins to help their tech troubleshoot connectivity issues. One of their main switches was blinking rapidly and rhythmically. While it might look cool, it only means there is a problem on the network. Rapidly blinking lights are normal. Rhythmically blinking lights are okay if you know everyone is basically doing the same thing (say, all access some interactive web site or something). But, when paired together, it's usually a bad sign.
I started unplugging connections, trying to get the lights to STOP blinking rhythmically. That failed. Even with one connection, the pattern was the same. This indicated the switch itself had gone bad. To test this, the tech and I moved the connections to a variety of "spare" switches he had. Everything seemed to be working to a point. The computer lab and a part of one hallway were not getting connectivity. Let the hunt begin!
Turns out there is a run from the switch to the computer lab. From the lab, there is a run to a classroom that feeds the rest of that part of the hallway. Let's just say it took quite a while to come up with that conclusion. let's also say that old buildings with uber-thick fiberglass insulation is not a fun combination.
We determined that the connection to the lab from the main switch was not behaving. The cure was to run a NEW wire. Did I mention fiberglass insulation? Oh, and dust? And other "stuff" we're not going to mention? He and I looked like we had just escaped from the cotton candy factory (though not all the "cotton candy" was pink...). The key is that when all was said and done (around 5:00pm), it all worked!
At 5:15pm, I headed for the house.. Er, the school where my wife works to pick up the kids. Now, how does this tie in to work? While in my wife's room, she told me her SmartBoard wasn't making any sound. I did some troubleshooting and determined that the audio for the board was showing up as an "unknown" USB device. FYI, on systems with a Smart Board, there is often an "USB Audio Device" that can be selected. My wife's computer did not have this. It is a driver issue, but she does not have enough rights as a user to install the driver. While this could have spelled the end of the issue as far as I could help, I pushed on. Turns out, SOME teachers had an RCA-Headphone wire that connected their sound to the speakers on the board. So... I found a teacher that had BOTH - the USB *and* the adapter. Since they had the USB working, their adapter was not plugged in. I borrowed the adapter and connected it to my wife's computer. When the projector is *on* now, she has sound.
I will email the tech at the district so he knows what's going on.
Monday, August 23, 2010
Monday, August 23, 2010
I started the day at Prescott Schools trying to figure out what was wrong with their video equipment. As it turns out, there are several sites around the state having connectivity issues on the DL network. That would have been handy to know before trying it our own.
In one classroom, I reconnected their back-of-the-room monitor. During the troubleshooting session, the local tech and I examined various network switches to make sure we had no collisions, drops etc. The drops appeared to come from outside their local network, leading us to the conclusion that it was a larger issue (as stated above, it is a larger issue), and we appear to have been correct.
Once I returned to the new building, I began installing the microphone shield for the distance learning lab, and I also ran a test with two sites to make sure the system was working for a conference we have on Tuesday.
A group of us went to the old building to load vehicles with boxes that are still at that location. There is still much work to be done there.
Once back at the new building, I helped unload the boxes and put them where directed.
Throughout the day, I did various troubleshooting. I installed one user's connection (the user had moved her computer and thus had no connection), connected a modem into the phone system in order for us to be able to do Medicaid billing. I installed a switch to provide more access to a place where there was none. I also have a could of wall jacks that need to checked, as they appear not to be working. My guess is that paint got into the jacks during the 'touchup' phase.
I took several phone calls and offered tech support by phone while doing the other things above during the day.
In one classroom, I reconnected their back-of-the-room monitor. During the troubleshooting session, the local tech and I examined various network switches to make sure we had no collisions, drops etc. The drops appeared to come from outside their local network, leading us to the conclusion that it was a larger issue (as stated above, it is a larger issue), and we appear to have been correct.
Once I returned to the new building, I began installing the microphone shield for the distance learning lab, and I also ran a test with two sites to make sure the system was working for a conference we have on Tuesday.
A group of us went to the old building to load vehicles with boxes that are still at that location. There is still much work to be done there.
Once back at the new building, I helped unload the boxes and put them where directed.
Throughout the day, I did various troubleshooting. I installed one user's connection (the user had moved her computer and thus had no connection), connected a modem into the phone system in order for us to be able to do Medicaid billing. I installed a switch to provide more access to a place where there was none. I also have a could of wall jacks that need to checked, as they appear not to be working. My guess is that paint got into the jacks during the 'touchup' phase.
I took several phone calls and offered tech support by phone while doing the other things above during the day.
8/20/2010
Friday brought another day of installation, troubleshooting, etc, getting things set up in the new building. I apologize for not having a more detailed break-down of what happened, but there is so much going on with the new move, I am lucky to know where I am at any given moment in time. Surely things will slow down eventually. Right?
Subscribe to:
Posts (Atom)