Erik Hilton

It’s been a long time since I last posted.  The reason can be summed up in a single word: upgrades.

When I became the IT Director at our school district, we are on the cusp of the Vista/Windows 7 transition and were staying with Windows XP.  We were not as behind as some places I’ve seen, but we were certainly due for some new technology.  I was surprised to learn that there was a near phobia of talking about changing anything.  I mean anything, from desktops to laptops, away from XP or looking at alternative software among the staff that had been in place for several years.  To their credit, I now completely understand this fear.

Our network was set  up around desktop-based Windows XP machines.  It worked great for that, but when more and more mobile devices began to creep into the network, it needed some adjustment.  It was also designed to be very secure, everything was locked down and complex security was everywhere.  The problem was, we continued to have the same problems with virus infections, spyware and all of the crap that makes its way into computers, in spite of this security.

It seemed to me that since we were still getting the junk, there was no sense having to trip over the security so much.  Last summer, I worked with an outside consultant and we significantly dialed back the security across many areas.  We decided a year ago, that the following year we would perform major upgrades.  We called it the “Etch-a-Sketch” approach and were just going to shake the thing and start over.  In July, that process began and this is the true story of how I aged ten years in the last two months.

The beginning of the end started with hard drive upgrades.  We upgraded hard drives in our virtual machine host, one by one, until we had all eight disks in the RAID array the same size.  Prior this this, I ensured we had good backups, even had snapshots of the virtual machines on an external hard drive.  Worst case scenario, a day of downtime to copy all of them back, no problem.  Somehow, about three days after the last rebuild happened, the controller decided “Oh, hey, check out all this new space!  Let’s use it!  Here you go, you’re welcome.”  Now, ordinarily, that would be great.  However, the VMWare host couldn’t see a single partition greater than 2TB.  VMWare OS ran on an embedded flash drive, and was still running happily along, except that all of the machines were suddenly invisible.

No problem, we’ll just split the drive into two partitions to make VMWare happy, put all of our machines back and we’re back in business.  As it happened, this was on a Friday, so I had the whole weekend.  It wouldn’t even affect that many people.  If only it were that easy.  The first malfunction included the external hard drive where I stored all of these virtual machines decided that it was going to quit.  No warning, no click of death, it just wouldn’t spin up.  No biggie, I could still just reinstall the multiple servers since I was upgrading them to Server 2008 anyway  and then just restore the docs from Crashplan.  It would take a bit longer, but it was summer and there weren’t that many people who would be affected.  The only problem was that the Crashplan backup server decided that it would be SUPER helpful to corrupt all of the backup sets and not report it for days. For every server.  So the backup failed, the backup to the backup failed, and I had four VMs that said “unavailable.”

I opened a case with VMWare support.  They worked on it for hours with no luck.  Finally, as a crazy approach, I booted the server from a Clonezilla CD, cloned the vmfs to a (working) external hard drive.  Since I was dead in the water anyway, I re-partitioned the RAID set into two equal sizes, made the adjustment in VMWare to span both partitions and I was back in business.  I then cloned my original vmfs image back onto the first partition and all was well with the world.  It was a bit of a hack, but it worked.

Next was a primary domain controller upgrade.  This was a serious upgrade, new hardware, new OS, new configuration, new Active Directory.  The works.  We set it up, plugged it in the network and powered off the old one.  Since it was summer time, a single controller would be just fine for DHCP, DNS and the basics of networking.  Now, you may be asking, what about the existing machines, what of their fate?  Since it was summer, there were less than a dozen staff working consistently.  I planned the upgrade with the time we could give them newer computers.  It was upgrade/migration combination.  For the most part, it went pretty smooth.

The second part was to move networking equipment into a new rack about three feet to the right of its present location.  I know enough about networking to know that I should call someone who knows, so this was approached with a cautious optimism.  It’s just unplugging and plugging in, what could possibly go wrong?  Again, we moved and installed the new equipment into this with little or no fuss, fired it back up, and of course no Internet.  All fiber connections to buildings, internal network were just great.  24 hours of troubleshooting later and the culprit was PIX firewall.  This experience taught me, and a subsequent switch encounter confirmed, that the solution to DOA Cisco products is to simply turn them off and on repeatedly and eventually they will work.  It may take 30-40 times, but eventually they will regain consciousness and begin functioning again.

That nightmare safely behind us, it was time to move on to file and print servers.  Throw in several hundred student user accounts, a Mac OS upgrade for all student and staff computers, along with replacing dated teacher computers with newer equipment, and that’s where the blur begins.

Oh, did I mention the installation of 140 virtual NComputing terminals, which required setting up and configuring 5 physical hosting servers.  Yeah, that too.  Although I will say that if I could replace every machine in the entire district with those terminals and give staff iPads for mobility, I would do it in an instant.  No more laptops, a classroom “teacher terminal” and iPads with Dropbox, Google Docs and iCloud.  One or two high powered physical Remote Desktop servers to manage.  Nirvana.

Throw in a couple of failed courseware upgrades for good measure.  Oh yeah, and when it finally does get fixed after an hour and  half of downtime for the 20+ students waiting on it, the Windows Remote Desktop server would choose that exact instant to decide that it was counterfeit and end all of the remote desktop sessions.  Good times.

Did I mention that a shipment of laptops was lost somewhere in Fedex land?  They arrived a week late, one week before school started.  By that time we had a steady backlog of 100 tickets a day, plus the crush of unfinished projects and a leap to Windows 7, new teachers, and a new food service point of sale system.  One day I will look back on this and laugh.  It may be a day in a very distant future.

What I learned from this experience is that upgrades should be done incrementally, not in leaps and bounds.  It has also helped me to understand my physical and mental limitations.  I would give anything for a slow day at work.  Sometimes you just need those days where you can work on projects you want to do to improve, rather than play fireman.  It seems all we’ve done is put out fires.  I am tired.  I am physically and mentally drained.   As the school year is well under way, things are beginning to settle into a manageable pace.  I will leave you with this piece of advice: upgrades suck.

I have experimented in the past few weeks with repairing iDevices.  It’s been a difficult learning experience for me because I do not like to admit failure, nor do I like to continue doing something that I cannot seem to master.  Repairing iDevices past 3rd Generation iPod Touch devices seems to be just one of those things.

I have repaired iPod Touch devices up to 3rd generation with little or no problems. The crux of the issue is the LCD screen and glass/digitizer assembly.  It’s a difference in design that makes all of the difference for me.  The 2nd and 3rd generation devices have the glass/digitizer as a unit that simply snaps in over the LCD.  Once you remove the old assembly, you can just attach a cable, click the new one in place and you’re back in business.  The 4th generation devices have the LCD attached to the glass/digitizer assembly and are quite difficult to connect as the digitizer cable is underneath the main logic board.  This involves removing the top of the main logic board, rear facing camera and cover plates just to connect the cable.

Then comes the fun of replacing the glass and attaching it to the iPod. There is a clip at the top that must be lined up correctly, and a very thin strip of adhesive that is needed along the sides.  It’s a sticky, tedious, slow and difficult process.  I am also fairly sure that my supplier of screens has an abnormally high rate of failure.  Of the three screens I’ve ordered, two have failed like this:

I ordered three screens at a time, and they must have been of low quality.
For each of these, I ended up having to send in to a repair facility – DigiExpress – for the repair to be completed.  In both cases, I simply passed on the cost to the customer.  All of them have been repaired with no issues and my customers are happy.

It occurred to me that I was doing a lot of work for nothing and discovered that DigiExpress has an affiliate program. It would be much simpler for me to just direct my customers directly to them.  I have a bit of a reputation in my circles as they guy who can fix just about anything, so this is another tool in my bag of tricks.

If you have the desire to do it yourself, here are some videos. I will warn you, though, it can be quite tedious.

iPod Touch 4th Generation

iPod Touch 2nd/3rd Generation

As I look at the computers we have available for our students, I am concerned because some of them are older models running Windows XP.  I realize that XP is still somewhat alive, but the sun is low on the horizon.  Most of these are having the various failures that often happens with XP, and they all have the signature degraded performance.  They are begging for a reinstall.

The question is a reinstall of what?  None of them have the horsepower to run Windows 7, nor does my budget have the dollars need to pull off such a task.  Each and every one would require RAM upgrades at the absolute minimum.  It’s a considerable investment and one I’m not sure is cost effective.

The frustration is that there is technically nothing wrong with these computers.  They are all quite capable machines, and certainly up to the challenge of running web based apps.  The only thing lacking on them is a modern operating system.

I am a huge fan of Linux, and used it at home almost exclusively until the time I became a Mac convert.  I’m in the beginning stages of researching this as an option, but it sure looks like desktop Linux is the obvious answer.  Modern features, security, reliability and all of the features we need in a lab.

This option would buy us a few years before it’s time to retire these machines.  The majority of what the students are doing is web based, and the rest could be handled, I believe.  The students need a good, reliable and web-capable machine.  I will post more on this as the progress continues.

This week has been a struggle of getting Lion to play nicely with Windows Server 2003 based print queues.  After numerous visits to a variety of forums, trying everything from forcing them out with Workroup Manager to IP Printing, I have found a (somewhat) simple solution.

Scenario:  I would add a printer that was hosted on a Windows share, send a print job and the printer would act like it was going to print, then pause.

It usually would never prompt me to enter a username and password (as required with Windows Server, even when group EVERYONE can print.) and would just set the print queue to paused.  Having had an issue with Keychain entries not working, my first step was to delete any keychain entries for the printers, which made no difference.

The logs would be generally full of this type of error:

Backend returned status 1 (failed)
[Job 58] Printer stopped due to backend errors; please consult the error_log file for details.
[Job 58] End of messages
[Job 58] printer-state=5(stopped)

This didn’t help much because I was consulting the error_log file, and this was the error. I tweaked just about every imaginable setting, even attempting to add it via the localhost:631 web based CUPS interface.  No matter what I tried, I never got much further than this.

Eventually it dawned on me to check the config files using the command line.  One thing I noticed right away was that in the /etc/cups/printers.conf file, there was a line called AuthInfoRequired and the value was negotiate.  I had an old printer that was working that I had added prior to the Lion upgrade, and that value was set to username,password instead of negotiate.  Surely it can’t be this easy.  I made the change in vi, saved it, tried again and it still failed.  It then occurred to me that since I was modifying this file, I needed to restart cups.   Even after this, it never prompted me for the username and password, which made me believe it wasn’t the solution and I moved on.

Fast forward three days and it’s 3:30 on Friday afternoon.  I just kept going back to that printers.conf file knowing there had to be something with that one difference.  Nothing else I found in three days of working on this was different, that was the only piece.  I tried it again, and made sure I cleared out every Keychain entry for the variety of printers I had tried.  I completely cleared my printer list and started fresh.  Step by step, here is what I did:

1. Cleared all references to the printer out of Keychain.
2. Deleted the printer(s)
3. Click + to add Other Printer or Scanner.
4. Click the Advanced Tab.  (If Advanced Tab isn’t available, Control-Click in the toolbar and choose Customize Toolbar and drag the advanced button to the toolbar)
5. Under Type choose Windows printer via spoolss
6. In the URL, make it smb://servername/printername
7. Give it a Name in the Name: field.  I stuck with the same name just for kicks, but it shouldn’t make a difference.
8. Choose the printer driver/model and click Add.
9. Jump over to Terminal and edit /etc/cups/printers.conf and change the AuthInfoRequired negotiate to AuthInfoRequired username,password using vi or text editor of choice.
   
10. Save the changes and restart the computer
11. Print a test page and you should be prompted to enter Windows credentials.  Save them in Keychain and bask in the glory of a functioning printer.

If you are not familiar with how printers.conf looks, each printer is included in a section that will start with <Printer the_printer_name_here> and all settings between that tag and </Printer> apply to that printer.  If you have multiple printers, you may have to scroll through it to locate it.  The AuthInfoRequired is about three lines down, directly under the UUID field.

By now, you’re probably wondering why didn’t I just click Windows and add it there.  For whatever reason, when I did, it would eventually show the domain, but only one or two random computers.  Thinking it was taking a bit to scan the network, I let it sit and think.  Nothing.  Once the server happened to be one of the random computers that showed up, so I clicked the printer and added it with no problems, just as in Snow Leopard.  For whatever, reason it doesn’t work the same in Lion, especially (it seems) when the server is on a different subnet than the client machine.

As background of why I discovered this, we moved away from central print queues due to some networking/territorial disputes/politics on our Macs and moved to strictly IP based printing.  If the printer was not networkable, we would use direct USB connections.  We are now moving to a managed printing system that requires it to go through a server to track page counts for supply replenishment and billing.  We are also moving toward using PaperCut to monitor and eventually attempt to reduce unnecessary printing.  Both of these tasks require a hosted print queue.

The IP based printing works flawlessly.  With my Snow Leopard machines, moving to the Windows print queues has been painless and worked (so far) without any problems.  Part of the problem with our old way of managing them had to do with some integration issues with the Macs.  Over the course of the past few months, I believe we’ve solved most of them.

I was surprised to a new little button in iTunes a few days ago called iTunes Match.  I have not heard much of this other than it being an add-on to the iCloud offering. I have not been one to jump on the bandwagon of storing music in the cloud, so that is probably why I have not paid much attention to it.  However, I have been sufficiently impressed with iCloud except that I did not read a warning message and deleted a bunch of my contacts by accident.  Luckily, I know most numbers and addresses so I was able to rebuild it.  That aside, the idea of syncing my music with iTunes quality, DRM-free tracks is appealing.

Back Story

The bulk of my music collection represents CDs we have ripped, most of which were not ripped all in the same month or year, let alone in the same format or bit rate.  In fact, we would do a song here or there, a whole album here, another song there and so on.  It’s also possible that it was done on multiple computers at different encodings and with different formats.  For instance, one song on an album may be AAC, while another is MP3, and yet another may be (shudder) WMA.  For quite some time we were a mixed OS household – a couple of Windows XP machines and Ubuntu.  It didn’t start out being on portable players, it was more of having a song available as we sat at the computer and didn’t want to hunt for a CD.

The same goes for purchased music.  Through the years I have purchased music from a variety of sources online.  Some has been shackled with DRM and some in mp3 format, again, all in different bit rates and volumes.

Through the past few years, we have been through a variety of mobile devices and eventually became a strictly iPod and Apple household.

The Apple Household

We are completely Apple, right down to an Apple TV and a pair of iPhones.  I know that some do not like the complete integration of everything media-related into iTunes, but I actually find it very useful.  In my past computing experience with other devices, it was a multi step process to get media onto the device. One of the aspects of iTunes that I love is that I can plug any of my devices into it and it will sync what I tell it to do.  Everything is in one place and I find that simple and wonderful.

The Conversion

I took some time to prep my library and made sure that everything was what I wanted to match and available in the cloud.  There were some tracks that I had downloaded from free samples, artist mailing lists and various other (legal) sources.  Some of those tracks are very good and I would like to have them available in iCloud, but not all.  If nothing else, this prompted me to clean out the junk in my iTunes library.

The experience of scanning my library was pretty simple and took only a few minutes.  It went through about 3100 songs and matched all but about 250.  Some of those were just not available in iTunes, but some of them did have corresponding tracks in the iTunes store.  I hit Google and found a variety of solutions, but this one in the Apple community forums offered the solution that worked for me for the majority of my match problems.  On the second page is a suggestion to convert to AAC for those that are simply not fixed by deleting and re-adding.

One thing that I noticed is that the meta tags seemed to make a difference in the matching.  From what I read on various sources before I started this, it seemed as though they didn’t make a difference so I didn’t pay a lot of attention.  However,  I had one album that just would not match and I realized that there was a typo in the album name.  Once I fixed that and added to iCloud again, it worked like a charm.

Getting back to my hodgepodge of track bit rate and format, I was particularly excited about the ability to re-download music in the higher bit rate in the AAC format.  It brings me back to the first time I was burned by DRM.  I can’t even remember which service it was – it’s long gone now – but it was in some Windows Media DRM format.  Long story short, I got an e-mail that my music was going to stop working unless I burned it to a CD.  So I did, and then re-ripped it to mp3.  As you can imagine, the tracks sounded like crap.  As luck would have it, this particular album was one that I could match and download in the original quality in DRM free AAC format.

I have a couple of CDs that were in 128 bit encoding, but I cannot re-rip them because the original disks have been damaged in one of our moves.  It’s not music I listen to frequently, so really not worth re-purchasing.  Again, this is going to be great to make the format of my music library more consistent and high quality.  That alone is worth the annual price and the time.  I am sure I will also appreciate it at work or when we are traveling to have access to our entire iTunes collection from our mobile devices.

All in all, I think this is a great service and will be sharing my thoughts as I use it more.

Today I had to make a very difficult decision.  At the beginning of the year we updated most of our student computers in one building to OS X Lion.  Our district participates in the Apple program to get the latest updates for all Apple software and the move to Lion was a natural step.

In the beginning I noticed some problems with Wifi staying connected.  My computer would randomly drop the wifi connection and sometimes just seemed to just “hang” a bit.  I knew from experience that with the first version of a major software upgrade sometimes you have to put up with a few bugs.  All in all, though, it was a good trade because I really did (and do) like Lion.

Shortly after the problems seemed to increase in frequency, 10.7.1 came along that had a fix to supposedly solve the wifi issues.  For the computers I used regularly, it did solve them.  For others, we had a few workarounds such as PRAM and SMC reset, removing the network and adding it again, changing the location, adding odd DNS entries, believe me, we tried them all.  For most machines, various gyrations of this solved the issues and they have remained trouble free.  Once in a while I run into issues where my computer will not connect after waking up, but that is the exception.

We had some lingering issues with student MacBooks (which are different models – Late 2009) and sometimes entire classes would be put on hold because of the issues of this dropping wifi and the inability to log in.  It has finally reached a critical point because the MacBooks are just not getting used because they don’t work.  This was a critical problem because this was why we decided on Apple for our student computers, they were very low maintenance and reliable.  For the past two years, they have been and I have become quite the Apple snob.

Today, I sat during an entire period and discovered the login issues we had in one particular class were due to corrupted mobile accounts on the local computer.  That was a simple fix, delete the mobile account, have the student sign on again to re-create the account and we were back in business.  Certainly, this is not the best situation, but one with a simple fix. The computers stayed connected during the entire hour and we thought we had a solution.  I was pleased because I thought we had finally resolved it.

The next class period rolled around, and the wifi disconnected on most of the students before they could even log in.  What makes this more difficult is that the wifi would reconnect if I logged in with the local administrator account.  However, when you rely on a directory server to authenticate network users, that doesn’t do a whole lot of good.  Determined to figure out why Lion was doing this, I pulled out every one of the machines and tried to update them one last time just to make sure that we were on 10.7.2 and all new updates.  Long story short, I couldn’t even stay connected long enough to complete downloading updates.

After about 30 minutes of this, I made the decision to take them all back to Snow Leopard.  I imaged about five computers, tested them out, and no problems whatsoever.  I was not at all surprised, but I was extremely disappointed.  I feel like we are going backwards and I don’t know what other option we have.  Just limping along like this is not an option.  It doesn’t seem to affect anything and nothing has changed with our wifi infrastructure.  The common problem is Lion and there is just no way around it.  We have made a significant investment in technology and it all needs to work like it did before.  When a student grabs a notebook, they should open it up and log in.

Today I imaged the entire 30 machines in that cart back to Snow Leopard and we will make plans to do the same for the remaining 60-90 machines that have Lion.  I had already determined that our XServe would not be making the jump to Lion any time soon because the server version of Lion is not what I had hoped.  I had such high hopes for our student computers and the ability to use some of the features in Lion.  I remain a Lion fanatic on my work and home computers, but for our students, not so much.

Apple, if you read this, I am begging you to figure this out.  There is no explanation I can see, and the forums are full of this same type of complaint.  Nothing has changed with hardware or configuration and yet we see these problems.  I will be here waiting for a fix and be the first one to try it out.

Over the past two weeks, my team and I have had the opportunity to get some training using Apple’s professional development program.  We have one more two-day session next week.  This is an excellent resource and I cannot speak highly enough about Apple’s Professional Development program.  It’s not cheap, but it’s well worth the money. For us, we are wrapping up some spending of technology training dollars that was part of a grant I obtained.  Initially, I had wanted to include several teachers in this training to increase the amount of people to help build a training program.  However, I ran into the same problem I have had for most of the year: getting time to get teachers in a training environment is all but impossible.  I understand the difficulty in taking teachers out of the classroom.  For these two sessions, there simply weren’t enough substitutes to go around.  This time of year is busy with other training throughout the district.

My team and I have all of this valuable information, resources that would really help teachers in their classrooms.  All we would need is an hour here or there to be effective.  Besides money, time is the other scarce resource.  Earlier in the year, I provided some after hours training opportunities for our staff.  It was a total of 8 hours, two hours per evening and we provided recertification credit.  We did not have many takers, and the second round of classes, we only had one or two people enrolled.  I opted to take a different approach and create some video tutorials and post them in our district Moodle.  If a person went through all of the material I created, they would be able to get the same information as we covered in the class, possibly even more.

It occurred to me that these video tutorials were a very powerful medium.  I was able to obtain some video equipment so we can produce some high quality professional videos.  Now the hard part is getting people to find time to watch them.  It is especially difficult this time of year as the weather warms up.  When my day is done, all I want to do is work on my new blog, so I completely understand.  Lately, my interest in technology in my downtime has faded significantly.  I know it’s because it’s beginning to warm up, the days are longer, and my passion for growing food is renewed by the time of year.

I’ve been struggling to figure out two problems, one personal and one for work, but both nearly identical. It’s a question of backups. At home, I have an Apple Time Capsule that backs up automatically using Time Machine on all of our Macs. This works great and is completely effortless on my behalf. If my computer were to crash or fall in the bathtub tomorrow, I would be secure in knowing my data was protected. Forever the pessimist, though, I asked myself what if the house burns down or is carried away in a tornado? Then I would be out everything. I have had this nagging desire to have an offsite backup solution for quite some time. Previously, I would burn DVDs of family pictures and other memories and take them to the home of a relative periodically. Sometimes months (or a year) would elapse before I would add to the collection, so in the event of a catastrophe I would be completely out of luck.

I kept hearing advertisements for some of these third party sites like Carbonite and Mozy. I love the idea of automated offside backup, but just have a distrust of dumping all of my personal data off to the cloud and having no control over it.  For my work it’s easier to accept because most of what I do is a matter of public record anyway.

CrashPlan was another provider that I heard several times. I downloaded a trial version and was fully expecting to just bite the bullet and sign up for the hosted offside backup and wait the months it would take for a complete backup to take place over the Internet.  What I discovered, however, is that CrashPlan lets you back up to other computers over the Internet for free.  The backup is encrypted on the drive and in transit (according to them) and you can build your own automated offsite backup.  So here is what I did:

1. I backed up to my 2TB External Drive on each of my home computers. It took several days.
2. I installed Crashplan on my work computer and added it to my CrashPlan account, but not backing up anything on it.
3. I then took the hard drive from home to work. Using the process to copy a backup archive, I made my work computer a destination for my home computers.
4. I then removed the local folder destination on my home computers so that it wouldn’t report a failure.

All three of my home computers now do automated offsite backup to the hard drive on my desk.  It took some time for that initial backup on each computer, but that was the bulk of the time.  Seeding the backup by doing it locally saved months of uploading, and probably a nasty letter from my ISP since it represented about 1.5TB of data.  For me that solution didn’t cost anything extra because I already had the 2TB drive.

Now, on to the backup solution for work.  CrashPlan offers a Pro solution as well, and provides server software so you can host your own backups on site.  I see a possibility for this as a solution to some of our mobile computers, but for now, it’s going to solve the tape backup dilemma.  We still back up to tape, and someone takes that tape home on a rotating basis.  This works, but an automated solution would be much simpler and expandable.  Since we have a good network connection between our buildings, bandwidth would not be an issue.

So here is my solution:

1. I took an old PC desktop computer and installed Ubuntu 10.04 LTS, and enabled the remote desktop option so it can be headless.
2. Purchased two 2TB Hard Drives (~$150 each) and attached them to the PC, formatting them for Linux.
3. Installed CrashPlan Pro (part of a 30 day trial) and modified it to use those two external drives as storage.
4. Install CrashPlan Pro client on server and set the backup to automate.

Once the initial backup completes, I’ll move this setup to the network closet at one of the other schools.  I realize that if a fire or tornado wipes out both of our schools, well, we would have some data loss.  However, if this were to happen, the data loss would probably be the least of our problems as a school district.  Our Student Information and accounting systems are all hosted offsite, so all that would be lost is Active and Open Directory, network home folders and some share points.  I think it’s a risk that’s reasonable.

After the 30 day trial, we will purchase 5 seats for CrashPlan Pro.  There is a discount for educational institutions, and for that small fee we will no longer have to swap tapes.  The great thing about CrashPlan is that it will just run in the background and is automated.  It’s just one more thing the machine can do.

Here are some handy tips for those schools that do not have dedicated staff.

“Don’t:”

1. Trust salespeople.  About anything.  Ever.  If you remember none of these rules, write this one down and never forget it.
2. Buy a complete, all in one, web 2.0, interactive, fully intuitive, interactive learning and blah, blah blah from a company promising it for your web solution.  You can have a web site up and running for around $20 a month that will look professional and just about anyone can do it.
3. Buy hosted e-mail.  Google Apps for Education is Free.  7+GB of mail, hundreds of users.  Plus you get access to all of the other amazing features of Google Apps, too.
4. Care about Search Engine Optimization (SEO) – see Rule 1.  You can help your search engine rankings in ways that won’t cost anything.

“Do”

1. Consider Google Apps for Education
2. Hire a “techie” for questions.  Even if it’s only a couple of hours, you will make much better decisions if you have some knowledge of what those salespeople are trying to sell. (See Rule #1 above)
3. Consider Free/Open Source Software
4. Create social media sites for your school – Facebook and Twitter.  They are a fantastic (and free) way to communicate with your community and students.
5. Look at what other schools are doing.  You can learn a lot from others in your similar situation.  Many times, someone else has already made the mistakes that you are considering making.

It’s always exciting to be at the beginning of something new.  Our school district is embarking on many new areas, some exciting and some scary.  Whether it’s the technical side of implementing programs, or the being a part of the logistics of making sure it all works out, I just love new activity.  As I’ve said before, I’m not a teacher by trade, so the whole academics side of things is a new process for me.  However you look at it, though, change is unnerving for many people, regardless of their background.

On the one hand, you honor successes of the past and build on them.  On the other hand, you have to take a critical look at the past performance and be willing to face inadequacies and shortcomings in order to make the corrections.  It’s sometimes easy with technology to get caught up in the “if we just bought this” or “if only we had money for that” game that sometimes you can let it consume your strategy.  If that happens, instead of focusing on correcting the things you can, you get stuck in a defeatist attitude.  Even with what we have, it can always be better.

As I look at the many shortcomings of our technology infrastructure, I see that we have all of the makings of something great.  I was thinking a lot about it today in particular, since it was one of those days when everything seemed to be just itching for conflict.  I’ve been running this game of trying to tweak things just right, make adjustments here, and little corrections there.  I know others on my team have been doing the same thing.

Today it became even more clear that sometimes you just need to have a fresh start.  It really solidified my decision to make my task over the course of the next few months to take a look at the services, functions that we need and focus on making them work.  At some time – summer or a break – we’re going to shake the etch-a-sketch and just start drawing again.

Crazy, I know.  However, we’re reaching that critical point where the tweaking is taking as much time as a rebuild.  We’ve got workarounds for our workarounds when a simple redesign would solve the problem.  I think part of it is battling several years of patches and duct tape solutions that just build and build and then become entrenched ways of business.

Rather than spend energy focusing on workarounds, I want to spend energy building something great.