Announcement

Collapse
No announcement yet.

Deploying A Windows 2008 SP2 x86 resulting in a failed Sysprep

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Deploying A Windows 2008 SP2 x86 resulting in a failed Sysprep

    Dear all,

    I'm having trouble with deploying 2 Windows 2008 SP2 x86 templates:

    Windows 2008 SP2 Enterprise x86
    Windows 2008 SP2 Standard x86

    All other Windows 2008 work fine except for those two.

    While they still are VM's the Network List Service is started automatically but when converted to a template and deployed this service is disabled hence the Sysprep won't run (fails).

    I've been searching the net like crazy but haven't found anything to solve this problem yet...

    We're running on VMWare vCenter Server v4.1.0 and vSphere Client v4.1.0

    Does any of you know how to solve this problem?


    Thanks in advance,

    Dennis

  • #2
    Re: Deploying A Windows 2008 SP2 x86 resulting in a failed Sysprep

    The Sysprep configuration, is it included in the template?
    Marcel
    Technical Consultant
    Netherlands
    http://www.phetios.com
    http://blog.nessus.nl

    MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
    "No matter how secure, there is always the human factor."

    "Enjoy life today, tomorrow may never come."
    "If you're going through hell, keep going. ~Winston Churchill"

    Comment


    • #3
      Re: Deploying A Windows 2008 SP2 x86 resulting in a failed Sysprep

      No it's not included, we have existing customization specifications, there for it needs the service to be started.

      Comment


      • #4
        Re: Deploying A Windows 2008 SP2 x86 resulting in a failed Sysprep

        Sysprep for Windows 2008 should be included in the template itself.
        http://d3planet.com/rtfb/2010/05/18/...osoft-sysprep/
        Marcel
        Technical Consultant
        Netherlands
        http://www.phetios.com
        http://blog.nessus.nl

        MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
        "No matter how secure, there is always the human factor."

        "Enjoy life today, tomorrow may never come."
        "If you're going through hell, keep going. ~Winston Churchill"

        Comment


        • #5
          Re: Deploying A Windows 2008 SP2 x86 resulting in a failed Sysprep

          That's also a way of putting it...

          Though, VMWare has an option to customize specifications. Such as generate a new SID etc.

          There's this vbs script that must be run once, and it's located on another server. There for it needs the Network List Service to be enabled...

          The main problem is that during the converting and deploying this service becomes disabled, making the script unable to runonce (like Sysprep).

          Comment


          • #6
            Re: Deploying A Windows 2008 SP2 x86 resulting in a failed Sysprep

            Which customization are you referring to?
            Can you make a screenshot of it?
            Marcel
            Technical Consultant
            Netherlands
            http://www.phetios.com
            http://blog.nessus.nl

            MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
            "No matter how secure, there is always the human factor."

            "Enjoy life today, tomorrow may never come."
            "If you're going through hell, keep going. ~Winston Churchill"

            Comment


            • #7
              Re: Deploying A Windows 2008 SP2 x86 resulting in a failed Sysprep

              Not sure what use a screenshot will be, but i could make one tomorrow...

              In vSphere you go to management and you select Customization Specification.

              I think we have our own (vbs) Script that it must run through... Though the script isn't the problem...

              It's the Network List Service that get's disabled preventing the Sysprep or script from running...

              I'm 100% sure that the Network List Service is the problem, but I cannot seem to find a reason why it automatically turns to disabled when converted to a template and being deployed...

              Comment


              • #8
                Re: Deploying A Windows 2008 SP2 x86 resulting in a failed Sysprep

                I believe you that the Network List Service is the problem
                However I'm not sure if you are deploying it using the correct method

                Btw, this might also help after sysprep.
                http://technet.microsoft.com/en-us/l...14(WS.10).aspx
                Using Setupcomplete.cmd and enter an sc command to configure the service as automatic and start it?
                Marcel
                Technical Consultant
                Netherlands
                http://www.phetios.com
                http://blog.nessus.nl

                MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
                "No matter how secure, there is always the human factor."

                "Enjoy life today, tomorrow may never come."
                "If you're going through hell, keep going. ~Winston Churchill"

                Comment


                • #9
                  Re: Deploying A Windows 2008 SP2 x86 resulting in a failed Sysprep

                  It should be the correct method

                  My other templates use the same method So that should'nt be the problem.

                  My other templates are:
                  Win 2K8 R2 Datacenter
                  Win 2K8 R2 Web
                  Win 2K8 R2 Enterprise
                  Win 2K8 R2 Standard
                  Win 2K8 SP2 Core x64
                  Win 2K8 SP2 Core x86
                  Win 2K8 SP2 Enterprise x64
                  Win 2K8 SP2 Enterprise x86 (problem one)
                  Win 2K8 SP2 Standard x64
                  Win 2K8 SP2 Standard x86 (problem one)

                  All work except for those two... So the method should be correct

                  Comment

                  Working...
                  X