Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
MDT 2012 + Windows XP

Answered MDT 2012 + Windows XP

  • Thursday, November 29, 2012 1:11 AM
     
     
    Sign In to Vote
    0

    I think I have lost my mind. I have no issues creating a reference workstation in Win7 and capturng it using MDT 2012.

    I have searched the Internet and there doesn't seem to be any step-by-step guides on how to to sysprep and then create a task sequence that will actually capture the image and then allow it to be imported back into the OS to be pushed out and re-deployed in masses. Maybe this can be the start of that helping guide?!?

    We have about 400 student lab workstations that still use a WinXPSP3 image. Currently deployed using GHOST. I have been tasked with moving everything over to MDT 2012 then to add in WDS to take advantage of the 'multicasting' feature. I have tried everything, but everytime I capture my reference workstation and apply it the new system just keeps blue screening and re-booting. I am currently building this in a DEV (VMware workstation) environment before I promote it into PROD. Another saving grace is that we are currently putting together a VDI proposal, so that might save me from pulling out the rest o my hair :)

    This is the guide I have followed to prepare my sysprep.inf file within the task sequence: http://www.deployvista.com/Default.aspx?tabid=78&EntryID=130

    I don't know if another option could be the following:

    1) Create the reference workstation (add all the software/updates etc...)

    2) SYSPREP it the old fasioned way

    3) Boot in using WinPE then use imageX to capture the .WIM

    4) Import it into MDT 2012 and prepare it to be deployed

    Any help or suggestions would be greatly appreciated!

    ZT

     

All Replies

  • Thursday, November 29, 2012 10:00 AM
     
     
    Sign In to Vote
    0

    What is the BSOD error code? The most likely one will be a 0x0000007B which relates to missing mass storage drivers.

    With XP + MDT (any version) you need to apply all your mass storage drivers pre-sysprep and then apply your NIC + Video + Sound drivers at deploy time. W7 allows for mass storage installation at deploy time, as does SCCM but as you're not using either of those so you do have to consider your drivers.

    If thats not the BSOD code you get then post more details.

    Andrew

     
  • Thursday, November 29, 2012 3:39 PM
     
     
    Sign In to Vote
    0

    Once the reference workstation is built is there anything that needs to be imported into C:\sysprep on the physical system? I think this is where I might be getting confused.

    From my understanding all the sysprep.inf modifications should be taking place from within the 'task sequence'. I have created a 'CaptureXP' sequence. Then I go into 'OS Info' and edit the sysprep.inf there. I added in all my 'mass storage' devices. Within my 'task sequence' I then disabled the 'Add Mass storage drivers for sysprep...'.

    Boot into the reference workstation and connect to the Deploymentshare$ go to 'Scripts' and launch 'LiteTouch.vbs'. I enter in my credentials and away it goes. It allows me to capture the .WIM file. When I try deploying it is where I run into issues. I will try once again and get the BSOD errror.

    ZT

     
  • Thursday, November 29, 2012 3:58 PM
     
     
    Sign In to Vote
    0

    Bingo...looks like a mass storage driver issue at the moment. Any clue what would be used when I am only using VMware Workstation to build a DEV environment? I am trying to source a physical test workstation so I can try on that.

    ZT

     
  • Thursday, November 29, 2012 5:52 PM
     
     Answered
    Sign In to Vote
    1

    This is the problem

      - "then disabled the 'Add Mass storage drivers for sysprep...'."

    You want that to be enabled. Import your mass storage (VMSCSI in this case) to your Out Of Box drivers and re-run the sequence to capture the image. This will copy the relevant files to the machine and populate your sysprep.inf file automatically. You most certainly can make changes manually to sysprep but if you're not sure what you're doing then I'd suggest not doing so for the time being.

    You will need to add mass storage drivers for all variants of hardware that you are working with - likely just your VMWare SCSi drivers and the Intel storage matrix drivers.

    Any time you add a new model that has a SATA controller that isnt already supported, you will need to re-create your base image.

    • Marked As Answer by ZoeTaite Tuesday, December 18, 2012 8:36 PM
    •