At my location I'm bordering on too much work to even handle. I covered for another location today though, and had two jobs when I came in, fixed those, maybe three more simple jobs, and then left two more going overnight that should take the other guy all of an hour to finish up. I've heard another location is even slower (normal for us is about 10 jobs going at any given time). In my own location though, I expect to be getting a lot of calls from customers asking if we're done with their computer yet, since I wasn't there to do any of the hardware related stuff all day today. When I left Saturday I think I had 30 something jobs going, and while im sure my coworkers knocked out as many as they could, its entirely possible that we checked in more jobs than we checked out since Mondays are our busiest day.
We had a couple of nice server projects this month too. One was an associate client we built a server for a few years ago. Server was acting up so we put a plan together to upgrade the hard drives and reload it with 2008R2. Their business line app is not supported on 2012. The original server was 2008. The VM would not start on the Datto appliance so we brought it back to the office, used disk2vhd and started the VM on our hyper-v server. Installed 2008R2 on the rebuilt server, then performed a migration. There were a couple of sketchy points along the way but everything worked out great in the end. We had replaced a failed hard drive in this server several months ago using Ghost to image it to a new drive. The server would not boot normally afterwards and we ended up booted in directory services restore mode to correct some database issues. We had the same issue with the VM after starting it on our hyper-v server. Something with this server just wasn't right. I've never run into imaging issues like that before. I'm puting finishing touches on a new hyper-v server this week for another client.
This week is so-so.
