locked
sid, sysprep a machine question RRS feed

  • Question

  • Hi,

    When I update my image I use a vm that I have installed our current deployimage on and make updates, then I sysprep it and capture it at the same time. Will this not create a new sid? Can I only do this 3 times?

    I found this article: http://system-center.me/miscellaneous/sysprep-your-windows-os-for-more-then-3-times/

    I even make a snapshot so I go back everytime I have to make a new image. Is this an working way of making an image or does the sid not get renewed? Can I check is that the case in cmd? Also my boss said that the previous worked made is so gpo update scripts dident work? How can I make sure I don't fail the same mistake? How did he even manage to do that?

    Is it ok to have a snapshot of a win7 and win10 on same virtual machine and just revert to that snap and install a new software and the capture the wim and mount it?

    /Kjell


    Tuesday, September 29, 2015 2:32 PM

Answers

  • When I update my image I use a vm that I have installed our current deployimage on and make updates, then I sysprep it and capture it at the same time. Will this not create a new sid? Can I only do this 3 times?

    I found this article: http://system-center.me/miscellaneous/sysprep-your-windows-os-for-more-then-3-times

    Kjell,

    the limitation happens if you sysprep a machine, create an image, deploy that image, then sysprep the deployed image, create a second image, deploy that second image (etc. 3 times)

    I even make a snapshot so I go back everytime I have to make a new image. Is this an working way of making an image or does the sid not get renewed? Can I check is that the case in cmd?

    Is it ok to have a snapshot of a win7 and win10 on same virtual machine and just revert to that snap and install a new software and the capture the wim and mount it?

    if your snapshot was taken before sysprep, you shouldn't be affected by this limitation. Also, please note that sysprep makes the computer "anonymous" and when you apply the captured WIM the Windows setup will generate new sids.

    Also my boss said that the previous worked made is so gpo update scripts dident work? How can I make sure I don't fail the same mistake? How did he even manage to do that?

    honestly, I'm not sure what issue you guys ran into, but I would suggest automating your image creation using an MDT task sequence (OS + apps + customization) so that you ensure that the image you are creating is clean.


    David Sebban | Nelite North America | My Blog : http://dsebban.wordpress.com | Follow me on twitter : http://twitter.com/davidsebban

    Tuesday, September 29, 2015 3:16 PM

All replies

  • Hi,

    you can add updates to your .wim file using DISM.

    Tuesday, September 29, 2015 2:44 PM
  • Hi!

    What is the difference? Between that and:

    Is it ok to have a snapshot of a win7 and win10 on same virtual machine and just revert to that snap and install a new software and the capture the wim and mount it?

    /Kjell

    Tuesday, September 29, 2015 2:52 PM
  • so many actions.

    not all apps can be installed via DISM, then i suggest you to use Audit mode.

    Tuesday, September 29, 2015 3:01 PM
  • When I update my image I use a vm that I have installed our current deployimage on and make updates, then I sysprep it and capture it at the same time. Will this not create a new sid? Can I only do this 3 times?

    I found this article: http://system-center.me/miscellaneous/sysprep-your-windows-os-for-more-then-3-times

    Kjell,

    the limitation happens if you sysprep a machine, create an image, deploy that image, then sysprep the deployed image, create a second image, deploy that second image (etc. 3 times)

    I even make a snapshot so I go back everytime I have to make a new image. Is this an working way of making an image or does the sid not get renewed? Can I check is that the case in cmd?

    Is it ok to have a snapshot of a win7 and win10 on same virtual machine and just revert to that snap and install a new software and the capture the wim and mount it?

    if your snapshot was taken before sysprep, you shouldn't be affected by this limitation. Also, please note that sysprep makes the computer "anonymous" and when you apply the captured WIM the Windows setup will generate new sids.

    Also my boss said that the previous worked made is so gpo update scripts dident work? How can I make sure I don't fail the same mistake? How did he even manage to do that?

    honestly, I'm not sure what issue you guys ran into, but I would suggest automating your image creation using an MDT task sequence (OS + apps + customization) so that you ensure that the image you are creating is clean.


    David Sebban | Nelite North America | My Blog : http://dsebban.wordpress.com | Follow me on twitter : http://twitter.com/davidsebban

    Tuesday, September 29, 2015 3:16 PM
  • For each version of an image, snapshotting, sysprepping and testing the result till you get what you like is acceptable, and that's how I do it.

    What the new philosophy of automating the build of a fresh image every time does, is get you out of the habit of patching, uninstalling or upgrading apps over and over, bloating the registry and leaving behind phantom crap that isn't associated with anything.

    Also, automating the build is self-documenting, and allows you to maintain a repeatable process, so every image starts from the same base. If you manually make edits and changes whenever you feel like it, then keep re-using that image over and over, in a few years you won't have any idea why things on your image are the way they are.

    • Proposed as answer by JoeZeppy Tuesday, September 29, 2015 3:35 PM
    Tuesday, September 29, 2015 3:34 PM
  • thanks! all answers are good answers =)

    Well I guess im just not good enough for making/package apps, I install maybe 10 apps and windows updates. I have placed an order for the mdt fundamentals volym 5 so maybe I will get better soon!

    I will now make a new deployment server called pxe2 and I will try to migrate or make new mdt server so I can install server2012 r2 because of better support for uefi. It seems like alot of work just to get better uefi support =).

    how can I even choose to boot from a second server with pxe boot? I mean it choose the IP that we have chosen to get broadcast?

    Wednesday, September 30, 2015 8:26 AM