none
Can't sysprep a Windows 2008 R2 RRS feed

  • Question

  • I'm trying to sysprep a virtual machine which is clone of another one. It has Windows Server 2008 R2, SQL 2008 R2 and some other applications. But when it restarts after syspreping it ends with BSOD: "Stop: c000021a {Fatal System Error} The Session Manager Initialization system process terminated unexpectedly with a status of 0xc000003a (0x00000000 0x00000000). The system has been shut down."

    Is there a way to fix it? Or maybe there is some other tool than sysprep which I could use to change this machines SID?

    Thursday, November 17, 2011 11:19 AM

Answers

  • Understood.  From my point of view trying to clone/syprep a production machine for use is generally a bad idea.  Once you deploy a machine in production and join to domain, who knows what security poilcies applied to machine or various variables which are out of your control.  I would urge you to go the MDT route in combination with offline servicing tool (the latter requires SCVMM I believe).  Together, you will save a ton of time and ensure quality control I know you want.

    http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=25175

     


    Dave Guenthner [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. http://blogs.technet.com/b/davguents_blog
    Thursday, November 17, 2011 12:05 PM
  • Hi,

     

    Towards your requirement, I noticed a similar thread for your reference:

     

    Title: Change SID

    URL: http://social.technet.microsoft.com/Forums/en-US/winserversetup/thread/f2334733-f0f2-4392-8598-a0090a0dfbe7/

     

    Regarding SIDs, Microsoft does not support images that are prepared using NewSID, we only support images that are prepared using SysPrep. Microsoft has not tested NewSID for all deployment cloning options.

     

    So I suggest that you could use the SysPrep tool to get the whole new SID. The following article is for your reference:

     

    Title: How to Use the System Preparation Tool (Sysprep.exe) to Perform Disk Duplication

    URL: http://support.microsoft.com/kb/298491

     

    Yes, just like the Dave mentioned, MDT will be your number one choice, it will help you deploy the OS faster and more effective.

     

    Regards,

    James
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Friday, November 18, 2011 9:10 AM
    Moderator
  • I gave up trying to clone a production machine and deployed a clean one. In that case sysprep worked without problem.
    Tuesday, November 22, 2011 8:40 AM

All replies

  • Tomek, is this machine a VM on VMWare or domain joined?  I mention this because sysprep is the only supported method of cloning and machine needs to be in a workgroup, and generalize checkbox from sysprep needs to be checked.  Typically customers use tools like Microsoft Deployment Toolkit to add quality control when building a reference machine for sysprep.  On the surface, it sounds like you have a machine running in production that you want to "clone".  Most customers use the gold reference image created from MDT and add automation to install whatever apps you need.  As s far as "fixing" an image, that may a dead end and I would go in a different direction.  The definition of the error is below.

    "This error occurs when a user-mode subsystem, such as WinLogon or the Client Server Run-Time Subsystem (CSRSS), has been fatally compromised and security can no longer be guaranteed. In response, the operating system switches to kernel mode. Microsoft Windows cannot run without WinLogon or CSRSS. Therefore, this is one of the few cases where the failure of a user-mode service can shut down the system.

    Mismatched system files can also cause this error. This can occur if you have restored your hard disk from a backup. Some backup programs might skip restoring system files that they determine are in use."


    Dave Guenthner [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. http://blogs.technet.com/b/davguents_blog
    Thursday, November 17, 2011 11:40 AM
  • Yes, it's VM on VMWare. And the source system is member of domain. But after cloning I disjoined it from domain, restarted and only then run sysprep.

    Usually we use a template from which we clone new machines. Of course these templates are just fresh installs only with basic configuration and updates applied. And after cloning there is no problem with sysprep. It is a first time I'm trying to sysprep a production machine and I wonder why it is not working.

    Thursday, November 17, 2011 11:49 AM
  • Understood.  From my point of view trying to clone/syprep a production machine for use is generally a bad idea.  Once you deploy a machine in production and join to domain, who knows what security poilcies applied to machine or various variables which are out of your control.  I would urge you to go the MDT route in combination with offline servicing tool (the latter requires SCVMM I believe).  Together, you will save a ton of time and ensure quality control I know you want.

    http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=25175

     


    Dave Guenthner [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. http://blogs.technet.com/b/davguents_blog
    Thursday, November 17, 2011 12:05 PM
  • Hi,

     

    Towards your requirement, I noticed a similar thread for your reference:

     

    Title: Change SID

    URL: http://social.technet.microsoft.com/Forums/en-US/winserversetup/thread/f2334733-f0f2-4392-8598-a0090a0dfbe7/

     

    Regarding SIDs, Microsoft does not support images that are prepared using NewSID, we only support images that are prepared using SysPrep. Microsoft has not tested NewSID for all deployment cloning options.

     

    So I suggest that you could use the SysPrep tool to get the whole new SID. The following article is for your reference:

     

    Title: How to Use the System Preparation Tool (Sysprep.exe) to Perform Disk Duplication

    URL: http://support.microsoft.com/kb/298491

     

    Yes, just like the Dave mentioned, MDT will be your number one choice, it will help you deploy the OS faster and more effective.

     

    Regards,

    James
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Friday, November 18, 2011 9:10 AM
    Moderator
  • Hi,

    Any Update?

    James


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, November 22, 2011 1:40 AM
    Moderator
  • I gave up trying to clone a production machine and deployed a clean one. In that case sysprep worked without problem.
    Tuesday, November 22, 2011 8:40 AM
  • This method worked for me.

    Fixed by clearing nodefaultdriveletter volume attribute via:

     

    1. use win2k8 iso to enter repair mode ...

    2. run command prompt

    3. diskpart

    4. list volume

    5. select volume 1

    6. attributes volume

    7. attributes volume clear nodefaultdriveletter


    It appears that cloning a running VM is the issue.  When I cloned from the VM when it was shutdown and then performed a sysprep with generalise and shutdown selected the resulting machine powers on without problem


    JJC

    • Proposed as answer by joe capuano Tuesday, May 22, 2012 5:48 PM
    Tuesday, May 22, 2012 5:48 PM
  • This method worked for me.

    Fixed by clearing nodefaultdriveletter volume attribute via:

     

    1. use win2k8 iso to enter repair mode ...

    2. run command prompt

    3. diskpart

    4. list volume

    5. select volume 1

    6. attributes volume

    7. attributes volume clear nodefaultdriveletter


    It appears that cloning a running VM is the issue.  When I cloned from the VM when it was shutdown and then performed a sysprep with generalise and shutdown selected the resulting machine powers on without problem


    JJC

    Really insightful!!

    -Web-ster!!

    Thursday, November 8, 2012 5:16 PM