Sysprep & fog



  • Hello Everyone,
    I had a quick question about syspreping my workstation. I am creating single image for all of my workstations, but what I do is use “windows setup mngr” to create a sysprep.txt file and reseal the process with a “MiniSetup” and “Pre-Activate” so that it can finish up on its own, but as soon as the workstation restarts I take an image of the harddrive.
    From there on whenever I want to image a new computer I deploy the image to the respective computer model and the windows setup runs. Has worked great, but has anyone had problems doing it this way?
    Even thought I have syspreped my machine and it says that the SID will change once it goes through the installation I want to make sure that on the next workstaion I deploy this image to a different SID# will be generated. Any advice or thoughts will be appriciated.
    Thank you in advance.



  • This post is deleted!


  • Yes. We join workstations to the domain using FOG after imaging has finished. This works great for us.



  • Do you join after you image them? I use the fog feature to join to AD and it works great, but I just want to make sure that I won’t have any issues with the duplicate SIDs.



  • That is almost exactly how I’ve imaged our Windows XP machines since we started using fog about 18 months ago. I’ve had no problems.

    I’m not sure about the “pre-activated” part. In Setup Manager, we use “fully automated set-up” and choose a workgroup (we [I]do not[/I] join it to a domain). When running Sysprep, we use the mini-setup option and choose reseal. The warning about SIDs can be ignored.

    We’ve noticed no issues using the above.


Log in to reply
 

417
Online

39.3k
Users

11.0k
Topics

104.6k
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.