Monday, November 14, 2011

How to Capture a Syspreped Image with SCCM 2007

With SCCM, gone are the days where you install an OS on bare metal (or VM), configure it manually to your liking, running sysprep then testing and deploying your systems.  Now everything is completly automated via Task Sequences, which are really Cool !!!


Call me old fashioned, but I rather enjoy the manual process of building an Image, making changes to the configuration, the user interface, helper-apps that need to be installed for LOB apps, etc.  If you use SCCM there is an easy way for you to do this without having to jump through too many hoops!  Here is how I do it:

1) Install and Build the OS to your liking.  To date I have done this with Win XP, Server 2003 R2, Server 2008, Server 2008 R2 and Windows 7.  Do not configure an Administrator Password !

2) If you are building an image for XP or 2003 and you are building a custom default profile, please referr to this KB:

3) When ready, Sysprep your OS (if you are doing this with Hyper-V, backup the VHD first so you can go back if needs be).  Make sure the OS shuts down after syspreping!

4) In SCCM, build a Custom Task Sequence that is accessible to boot media.  Once its created, edit it and do the following:
 --- Add A Task Sequence Variable.  Configure as followed:
              Name: Point to Windows Directory
              Task Sequence Variable: OSDTargetSystemRoot
              Value: C:\Windows (or whatever installation folder you have selected)
--- Add "Capture Operating System".  Configure according to your environment

5) Advertise your Custom Task Sequence and use it to capture the system image

Once its captured you can import it into SCCM and you are good to go !

Tuesday, April 5, 2011

MED-V Image Gotchas!

A few things to note when building your XP image for MED-V.

1) You MUST use Windows Virtual PC to build the Image! My laptop has 2008 R2 installed on it so I can use Hyper-V. Since VPC doesn't allow for 64-bit guest OS's this is the best option for me for development purposes. I have tried VMWare Player in the past but the performance isn't up to par. The Windows XP SP3 VM for MED-V requres the VPC Integration Features installed before it is packaged ... the Hyper-V Integration Components are very different and don't cross over very well.

2) Follow the MED-V Help file for building the Windows XP SP3 VM The Help file included with MED-V 2.0 will tell you all the patches and registry mods you need to apply so the VM works properly. Don't try to be the hero!

Monday, March 28, 2011

MED-V Deployment Start to Finish

I love working on new and exciting things. Virtualization has definatly come a long way since i started in IT. It used to be the cool thing to use when learning a new OS or method, but now its basically everywhere! Virtual Servers, Virtual Applications, Cloud-based Virtualization ... all of which is very exciting. With a Windows 7 upgrade underway, more and more Application Compatability issues have come out of the wood work ... Apps that are soo old they don't even register in Add/Remove Programs in XP. We thought about Windows XP Mode but balked at the thought of basically doubling our system management workload. Bring on MED-V ... I'm going to try to Blog about the whole process from start to finish. Hopefully someone will find it usefull, or be able to point out where i've gone horribly wrong. This'll be fun!

Wednesday, January 12, 2011

Configuring for Multiple Timezones in an SCCM Task Sequence

**Update**  I have since found a better way to do this as this method actually doesn't work during imaging due to the limited WMI options in WinPE.  Please check out my updated post:

I've been trying to find this for an extremely long time!!!

Just a simple WMI condition

Select * from Win32_NTDomain WHERE ClientSiteName LIKE "%ADSiteName%"

HUGE thanks to this site: