The Hub

So this weekend is going to be filled with the joys of working from home, to prepare for the oncoming semester.  Because of a single, very annoying line of code.

If I’ve done this right, I should have both the x86 and x64 builds of my Windows 7 image done by tomorrow.  It’s a minor change, but a big bug.

I’ve also learned how to edit more directly the OEM branding (where it says Windows 7 [Insert Edition Here]).  All I really wanted was a spot to add the simple text of what version of the build it was.  ASU does it, but I just can’t find where they did it.

Let’s get off on the right foot here.  I hold no grudge against any software company that has crafted a dynasty out of nothing.  The two major players are Apple and Microsoft.  In fact, for the most part, they are the ONLY players in the game.

Sure, I can argue that Linux is great, free, lightweight, and nice, but to be honest, they are just not as big as the top two contenders.

But, of course, there’s a misconception about the fight between the two.  It’s not Mac vs. PC. Read more

It’s an important distinction, in my mind.

A person who is driven has pre-set motivators to get a job done.  For example, someone at a workplace that is driven has the goal set for them; a paycheck, a promotion, etc…  Nothing that they’ve created for themselves.

The Driver, however, has the goal in mind, that they’ve set.  The path is their choosing, how to get there, what tools they use, orthodox or not.

In most workplaces, being the driver is difficult.  Keeping in line with the “industry standards” is part of the IT ideal, and is halting creativity in many organizations, trading the new and inventive for “stable and boxed” systems.  Holding off the pitchforks of the nay-sayers, the Driver has to produce quickly and efficiently.

Want a real world example?  Here’s one from my experience:

I’m setting up the deployment for Windows 7.  Unfortunately, the “industry standard” is to use SCCM and Sysprep.  However, there are some issues with deploying SCCM to our live environment that I can’t get into right now.  Sysprep has issues with what I’m telling it to do, to I’m ignoring it right now.

I know my goal: Deploy Windows 7 in as small an image as possible, without using Sysprep and SCCM (or ImageX, but that’s another matter entirely).

How am I doing it?  AutoIt scripting.  98% of the “sysprep” that I’m doing makes up for the lack of Microsoft Sysprep and SCCM/ImageX.  The other 2% is using Ghost Solution Suite for image deployment.

I can image a workstation in 8.5 minutes.  It’s roughly 5gb.  It’s not kosher in the setup, but the end result meets, if not exceeds the goal, and complies with the “industry standard” on the other side.

I am a Driver.  Are you?