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?
Friday, August 20, 2010
08/19/2010
Thursday brought a day of meeting, installing security cameras, and working with the phone guy. I wanted to program our phone system myself, but quickly realized I did not have the time or patience right now to do so. We ran into an issue yesterday where the third caller (if the other two lines were taken) was left in a no-answer zone. Luckily, the phone tech had us fixed in a jiffy. Of course, the fix changes the way our system works, so I'll be educating our folks on how calls are handled now.
The day's end brought Vikki and I to the phase of our job that involves the sprinkler system. The sod came in yesterday, so we had to figure out the scheduling so the sprinklers would cycle through (we have multiple zones) to water each area for a specified time, then repeat the cycle. I'll know when I get to work on Friday if we did it right. Actually, we ran a test (set it for 5 mins each zone, twice) and passed. Let's see how we do on the real "exam!"
What will Friday bring? I am not even going to venture a guess. I am *hoping* to finish security cameras and hook up the compressed video system in the distance learning lab. Anything on top of that is gravy.
The day's end brought Vikki and I to the phase of our job that involves the sprinkler system. The sod came in yesterday, so we had to figure out the scheduling so the sprinklers would cycle through (we have multiple zones) to water each area for a specified time, then repeat the cycle. I'll know when I get to work on Friday if we did it right. Actually, we ran a test (set it for 5 mins each zone, twice) and passed. Let's see how we do on the real "exam!"
What will Friday bring? I am not even going to venture a guess. I am *hoping* to finish security cameras and hook up the compressed video system in the distance learning lab. Anything on top of that is gravy.
Wednesday, August 18, 2010
08/18/2010
8a-9a - Set up the conference room for the 11:30 staff/welcome to the new school year meeting.
9a-11:15a - Went with Trish Brown (DL Coordinator) to a school to troubleshoot distance learning equipment. Turns out that district had a connectivity issue that was local to their network. The switches and fiber connections had to be reset. Once that was done, the system connected just fine. Additionally, the remote would not work through the camera system, so I disconnected and rebooted the camera. Worked like a champ!
11:30a-1:00p - Staff meeting/Welcome back
1:00p - 4:15p - various network/technology installs and troubleshooting. Turns out we also have an air unit in another part of the building not working. When the air guys were at the office on Tuesday, I knew there was another system out in addition to the one they worked on, but I wasn't sure where. I know where now. That means another service call. UGH. I grabbed a box of cable, RJ45 ends, and tools to take to the house.
5:00p-7:00p - At the house, I made enough patch cables to finish off the RJ45 ends I had left. i also connected to our new phone system to look through the web-based configuration system. I can say with utmost certainty that it is complex and VERY cryptic. The installer tried to warn me. I should have listened. I will call the company this week (Friday?) to get some pointers.
9a-11:15a - Went with Trish Brown (DL Coordinator) to a school to troubleshoot distance learning equipment. Turns out that district had a connectivity issue that was local to their network. The switches and fiber connections had to be reset. Once that was done, the system connected just fine. Additionally, the remote would not work through the camera system, so I disconnected and rebooted the camera. Worked like a champ!
11:30a-1:00p - Staff meeting/Welcome back
1:00p - 4:15p - various network/technology installs and troubleshooting. Turns out we also have an air unit in another part of the building not working. When the air guys were at the office on Tuesday, I knew there was another system out in addition to the one they worked on, but I wasn't sure where. I know where now. That means another service call. UGH. I grabbed a box of cable, RJ45 ends, and tools to take to the house.
5:00p-7:00p - At the house, I made enough patch cables to finish off the RJ45 ends I had left. i also connected to our new phone system to look through the web-based configuration system. I can say with utmost certainty that it is complex and VERY cryptic. The installer tried to warn me. I should have listened. I will call the company this week (Friday?) to get some pointers.
08/17/2010
8a-4p - More moving, more network patching, more general helping out. The air conditioning guys came down to look at one of the systems. Turns out is had bad wiring. I really can't remember what all happened on Tuesday. I do know that at 3pm, I headed up to a school that was having problems with connecting to distance learning provider. As it turns out, the school could connect to three other providers. I recommended the school contact the one provider that wasn't able to connect and have them troubleshoot their issue(s).
Tuesday, August 17, 2010
08/16/2010
8a - 430p
Mainly spent the day patching phones from the phone system to their assigned ports. Er, that was the plan anyway. Spent much of the morning over at the old building picking out things that still needed to be moved. After lunch, I went back to the patching. According to the folks that ran the wiring, there is a scheme they followed: From the first jack on the lft, go around the room in sequential order (so, if room 115 has three jacks, the first on left is 115/1, then 115/2, and 115/3. I should be able to look at the phone jacked into the wall, determine the jack number based on room and location and plug in the patch wire in the wiring closet. As it turns out, however, not every room follows the pattern. Add to that, some rooms are even labeled incorrectly (one jack in room 224 actually terminates as 113/2). AUGH! I spent a lot of time using the FOX and HOUND to find which wires went where.
By using the device (FOX shown above), I can plug a wire from the wall into the FOX then use the HOUND (which generates a high-pitched tone) to figure out where the cable lands in the closet. Best invention EVER!
Of course, LOTS of other things came up during the day as we are still moving things in, trying to get things organized, etc. I am putting myself under a lot of pressure to get things done quickly. My boss is pretty laid back about it.
Mainly spent the day patching phones from the phone system to their assigned ports. Er, that was the plan anyway. Spent much of the morning over at the old building picking out things that still needed to be moved. After lunch, I went back to the patching. According to the folks that ran the wiring, there is a scheme they followed: From the first jack on the lft, go around the room in sequential order (so, if room 115 has three jacks, the first on left is 115/1, then 115/2, and 115/3. I should be able to look at the phone jacked into the wall, determine the jack number based on room and location and plug in the patch wire in the wiring closet. As it turns out, however, not every room follows the pattern. Add to that, some rooms are even labeled incorrectly (one jack in room 224 actually terminates as 113/2). AUGH! I spent a lot of time using the FOX and HOUND to find which wires went where.
By using the device (FOX shown above), I can plug a wire from the wall into the FOX then use the HOUND (which generates a high-pitched tone) to figure out where the cable lands in the closet. Best invention EVER!
Of course, LOTS of other things came up during the day as we are still moving things in, trying to get things organized, etc. I am putting myself under a lot of pressure to get things done quickly. My boss is pretty laid back about it.
Sunday, August 15, 2010
08/14/2010
7a-7p - Moved items from old location to new.
On Saturday, the 14th, a TON of folks showed up at the co-op (both sites) to help get things moved. We started at 7am and worked all day with a pizza break for lunch (Thank you, Lindy and Phoebe!) and then at 3pm, everyone was released to head for the house. I stayed on in order to work with BCS (phones). Though my plan was to patch in phone and data, things took a little longer than I had anticipated, so by 7pm, I simply ran out of steam.
By far and away, the hardest part of Saturday (for me) was dismantling the equipment in the old Conference Room. We have an original Smart Sympodium cart. It has been around so long, I can't even find an accurate picture of one online! I need to take picture for posterity. It is big and bulky and weighs a TON! Okay, maybe not a ton, but a good could hundred pounds. Good thing it is on casters. The cabinet not only houses the electronics for the Sympodium (a Smart Board in a lectern, basically) but it also houses the distance learning equipment for the conference room. The weight of the thing doesn't compare to the sheer number and bulk of the wiring attached to it. And all those wires (cameras, power, video, sound, data, etc) ran through the ceiling grid. Over the years, other wires had also been strung up there, so everything was "a hot mess," as some folks say. With my assistant's help, though, we eventually got everything we needed (for the most part. I plan to have our Smart rep move some of the other equipment).
There is still lots to do, but I cannot believe how quickly the majority of the equipment, furniture, and "stuff" got moved. Amazing.
On Saturday, the 14th, a TON of folks showed up at the co-op (both sites) to help get things moved. We started at 7am and worked all day with a pizza break for lunch (Thank you, Lindy and Phoebe!) and then at 3pm, everyone was released to head for the house. I stayed on in order to work with BCS (phones). Though my plan was to patch in phone and data, things took a little longer than I had anticipated, so by 7pm, I simply ran out of steam.
By far and away, the hardest part of Saturday (for me) was dismantling the equipment in the old Conference Room. We have an original Smart Sympodium cart. It has been around so long, I can't even find an accurate picture of one online! I need to take picture for posterity. It is big and bulky and weighs a TON! Okay, maybe not a ton, but a good could hundred pounds. Good thing it is on casters. The cabinet not only houses the electronics for the Sympodium (a Smart Board in a lectern, basically) but it also houses the distance learning equipment for the conference room. The weight of the thing doesn't compare to the sheer number and bulk of the wiring attached to it. And all those wires (cameras, power, video, sound, data, etc) ran through the ceiling grid. Over the years, other wires had also been strung up there, so everything was "a hot mess," as some folks say. With my assistant's help, though, we eventually got everything we needed (for the most part. I plan to have our Smart rep move some of the other equipment).
There is still lots to do, but I cannot believe how quickly the majority of the equipment, furniture, and "stuff" got moved. Amazing.
Saturday, August 14, 2010
08/13/2010
8am - 5pm = Moved equipment from old location to new.
Connected T1's to switch and turned on all servers. The power outlet installed does not accommodate the UPS we have, so the electrician will have that fixed on Monday. The servers are operating on single PSU's for now, which is fine. The mail server had a small issue, but I believe that was related to the SQL server not being fully booted when the mail server came online. Once necessary services were started, we were golden!
Work starts on Saturday at 7am!
Connected T1's to switch and turned on all servers. The power outlet installed does not accommodate the UPS we have, so the electrician will have that fixed on Monday. The servers are operating on single PSU's for now, which is fine. The mail server had a small issue, but I believe that was related to the SQL server not being fully booted when the mail server came online. Once necessary services were started, we were golden!
Work starts on Saturday at 7am!
Thursday, August 12, 2010
08/12/2010
8a- 930a - Helped a school district set up a redirect from their old website to their new one. Also helped the tech get ConsoleOne and NWADMIN32 running on his workstation. We also looked at a connectivity issue in the computer lab and got it resolved.
10a - 4pm - Drove back to co-op and spent the day breaking down a couple labs, moving and packing, etc.
4p-5:30p - Shut down servers and router, loaded up the equipment and moved it to the new building. We had a bit of a scare during the move. Friday will tell us if everything still works the way it should.
10a - 4pm - Drove back to co-op and spent the day breaking down a couple labs, moving and packing, etc.
4p-5:30p - Shut down servers and router, loaded up the equipment and moved it to the new building. We had a bit of a scare during the move. Friday will tell us if everything still works the way it should.
Wednesday, August 11, 2010
08/11/2010
8a-915a - Went to one of our early childhood sites to set up the computer, smartboard, sound etc.
915a-930a - Met with Health Liaison regarding a workshop. Presenter needed a speaker system. Met with presenter (tech from one of our area schools) about their upcoming switch to Exchange Server. I am hoping to be able to get down there for "hand-holding" if possible.
While I was at the early childhood site, there was a staff meeting at the main office. We begin moving this weekend.
950a - Helped get the presenters hooked up with their presentation and on the wireless mic system.
10:00a-1030a - Email & co-worker discussions
1030a - Met with Director and Assistant Director then went to new building to check status of T1 Demarc placement. At some point yesterday, I talked with our phone installer and let them know that they should be able to come out on Friday to install our upgraded phone system. I forgot to document that yesterday.
Network Demarc looks good, though I now have a concern that we will not have enough facilities for our phone services. This should be interesting come Friday. Have I said that already?
11:30-Noon - Continued cleaning/packing the office for the big move.
1:00p-2:00p - Continued to pack and clean office.
2p-330p - Email, phone support, spam filter configuration/quarantined message cleanup
3:30-4:45p - Met with Director, Assistant Director and other personnel regarding packing and prepping for the move! Wahoo!!
915a-930a - Met with Health Liaison regarding a workshop. Presenter needed a speaker system. Met with presenter (tech from one of our area schools) about their upcoming switch to Exchange Server. I am hoping to be able to get down there for "hand-holding" if possible.
While I was at the early childhood site, there was a staff meeting at the main office. We begin moving this weekend.
950a - Helped get the presenters hooked up with their presentation and on the wireless mic system.
10:00a-1030a - Email & co-worker discussions
1030a - Met with Director and Assistant Director then went to new building to check status of T1 Demarc placement. At some point yesterday, I talked with our phone installer and let them know that they should be able to come out on Friday to install our upgraded phone system. I forgot to document that yesterday.
Network Demarc looks good, though I now have a concern that we will not have enough facilities for our phone services. This should be interesting come Friday. Have I said that already?
11:30-Noon - Continued cleaning/packing the office for the big move.
1:00p-2:00p - Continued to pack and clean office.
2p-330p - Email, phone support, spam filter configuration/quarantined message cleanup
3:30-4:45p - Met with Director, Assistant Director and other personnel regarding packing and prepping for the move! Wahoo!!
Tuesday, August 10, 2010
08/10/2010
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.
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.
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)