Laptop Institute, Tablets, and Servers

Our student workers got the rest of the tablets imaged yesterday, so at least that is done! One month from today we have the opening faculty in-service. It's going to be a crazy month.

Went to the Laptop Institute in Memphis from Sunday thru Wednesday. It was a fantastic conference. I highly recommend it to anyone if there school is even remotely considering a one-to-one program. My biggest takeaway of the conference is the realization that putting a tablet in the hands of every McAuley student will make a type and a level of learning possible that was never possible before. I know it will do a lot to transform the way in which I teach.

We're trying to get the Dyknow server up and running. Yesterday I got Windows 2003 installed and patched on the VMware server. Jeff and I couldn't get the Windows 2003 server to boot from the CD for several hours. I'm new to VMware so I played around with it trying to get it to boot from the iso images didn't work, neither did the host device or the Client device. Then I realized I was trying to boot the Client Device while running Remote Desktop to the Virtual center server. One hop too many. When I closed the remote desktop and opened the Virtual Infrastructure Client I was able to boot from the Client Device CD and install Windows 2003. I got in patched before I left at 7:30PM.

Jeff called our Dyknow support person today to ask about setting up two network cards on a Windows 2003 server and set up training. He ended up disabled the second network card so we could get on with the installation. Jeff, Jon and I then tried to install Microsoft SQL 2005. Note the word tried. Another road block. While it was installing from disk 2 it gave the message that SQL.cab was corrupt or missing. Jeff started the download of the second disk from CDWG after 5:30. I hung around since I still had some things to finish up. When I got the download to complete I made the CD and got the same error. Apparently other people have had issues installing MS SQL 2005 on VMware. I Googled it and found we weren't the only people to get the error. I may go in tomorrow and see if I can figure it out.