Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
sysprep has never run on 2 production 2008 r2 machines and sysprep fails now

Answered sysprep has never run on 2 production 2008 r2 machines and sysprep fails now

  • Friday, September 21, 2012 11:00 AM
     
     
    Sign In to Vote
    0

    I have a template  and rolled out Windows Server 2008 R2 and after a while I suddenly discovered/understands that 2 of  the machines never has run sysprep. When I try to run sysprep (afterwards) manually I get "A fatal error error ocurred trying to run sysprep on the machine".

    I think I know why I have got this problem in the first place but for theese two already production machines, how do I do to be sure they have a new, unique SID ?

    What I can see you can not run the tool NewSid on a w2k8 r2 machine and sysprep fails ...

    Please help me out

    Sincerely

    \\Jonas B

     

All Replies

  • Friday, September 21, 2012 1:01 PM
     
     
    Sign In to Vote
    0

    Hi,

    I think its better to ask this question in below forum.

    http://social.technet.microsoft.com/Forums/en-US/w8itproinstall/threads

    Regards

    Praveen 

    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, September 21, 2012 5:34 PM
     
     Answered
    Sign In to Vote
    0

    This forum is for questions about Windows Server 2012 setup, not Windows Server 2008.  You might want to take this to the Windows Server 2008 general forum - http://social.technet.microsoft.com/Forums/en-US/winservergen/threads.

    Joining a system to a domain generates a new SID for use in the domain.  You may also want to read this very informative post by Mark Russinovich, the author of newsid - http://technet.microsoft.com/en-us/sysinternals/bb897418.aspx.  Sysprep does much more than simply ensure a new SID.

    I'm not sure from your description exactly what is happening.  Are you saying that you have a template that is NOT a sysprepped image?  Your template should be a sysprepped image so that you always start with a clean image.  You create more work for yourself when you start with a clone and then have to sysprep it each time.  It's less work and safer (as you found out) to have a sysprepped template.

    Secondly, there are some applications that can prevent sysprep from running properly.  That could very well be your problem.  At this point, your best plan of action would be to build your template, sysprep it, and recreate your two servers.

    tim