I love WDS and MDT–Install Server 2008R2 onto Legacy x64 Hardware!

Here was fun.  I’ve gotten my hands on some decent server hardware that had some caveats.

No DVD or ability to BOOT from DVD

No USB Booting ability


CPU was x64 capable

So in this scenario, normally you would scrap using Server 2008R2 or Server 2008 x64 because the media only exists on DVD format.  The alternate is to boot from USB but since the server can’t do that, forget it.


But if you have Windows Deployment Server at your finger tips and MDT 2010 none of this is a problem. Just create that image and awaaaaay you go.

“But Sean, what happens if it breaks?  I’m stuck right?”

Funny thing is … NO.

I was playing this weekend and if you learn how to build a standalone WinRE x64 or have access the DART and can build THAT image, the both fit on a Standard CDrom, with room to spare (which many older x64 servers DO in fact have, Cdroms)

I know this because my test environment was running off an older Dell server which (as my coworker would say) “Hacked up a hairball”, I lost my Domain (Yes, I was building new and hadn’t added my secondary and tertiary DC’s)

So to resolve this, I created a WinRE Cdrom from my x64 Windows 7 and repaired the environment from that.

Ok…. for production maybe NOT a GOOD idea (or maybe it is?  Trying to extend the budget on some older equipment?  Repurpose it as an RODC?)

Just food for thought.   But all of this was possible thanks for MDT (Free) and WDS (Just a free role in the Server 2008R2)


This blog post brought to you by the letter “M”

The Energized Tech

Remotely Enable Remote Desktop Manually

You’re stuck in a jam.  The remote workstation is on, the user isn’t there and you have a mandate.

“Install this software before you leave.” Of course the software just happens to be the one application you CAN’T just push.  It needs a local install.  “UGH!” your brain says to the world.

No problem.  As long as the computer is on your network, you can enable Remote Desktop access.

First you need to have local Administrative rights on the computer in question.

Launch REGEDIT and Choose File/Connect Network Registry


In the provided box, enter in the name of the computer


Once connected you’ll have a new option near the bottom.


Under the “2nd” HKEY-LOCAL-MACHINE (which is that nasty remote computer) Navigate to

HKEY-LOCAL-MACHINESystemCurrent Control SetControlTerminalServer

Edit the value called fDenyTSConnections and change from 1 to 0

change from 1 to 0


Now if you’re running Windows XP, you’re probably done and can happily remote in. 

With Windows 7 and Windows Vista there’s an extra step, you need to enable two rules on the Firewall

Navigate to the following registry key

HKEY-LOCAL-MACHINESystemCurrent Control SetservicesSharedAccessParametersFirewallPolicyFirewallRules

You’ll see a pile of values.  Find the one named “RemoteDesktop-In-TCP”


You’ll see a LOOOOOOOONNNNNG string of data in there.  Near the very beginning it will read something along the lines of what you see below


Edit the Active=FALSE to ACTIVE=TRUE so it reads as in the box below.  Click OK


Then execute the following command in a command prompt.


Where “COMPUTERNAME” is the NETBIOS name of the PC


SHUTDOWN –f –r –t 0 –m x.x.x.x

Where x.x.x.x is the IP address of the computer

Now you COULD probably trigger this via GPO and Preferences too.  But on the Enterprise why would you? Baaaaaad!

But in Small Business environments I have seen the need for this, so it COULD be set in those instances.   Of course you’ll have to remember add anybody who SHOULD be remoting to the local computer group “Remote Desktop Users

A handy thing to know how to do, especially if you are effectively “Locked away” from physical access to a managed machine.

The Energized Tech

SQL Saturday 93–Toronto Ontario !

Next Saturday ! 

September 17, 2011 is SQL Saturday #93


The Event is free, Lunch is $15 if you’d like a Tasty lunch.  A chance to meet greet other Professionals.  A day of solid training for Data Professionals.

And…. a small bonus. 

Rumor has it, the one, the only…. the BATCHman may make a special appearance at the Powershell session.

So register, and check it out now.  Heck a Saturday doing Nerdy stuff?  How can you go wrong?