Newbie to Sysprep



  • Hi all,
    I’m just getting into syspreping and I have some questions…

    I have a PC setup exactly how I want it (WinXP_Pro_OEM_SP3)). I’m going to upload it to fog as a backup. Then I plan on running sysprep.

    I’m also just reading into the [URL=‘http://driverpacks.net’]Drivers Pack[/URL] website. And trying to copy some of the suggestions in [URL=‘http://fogproject.org/forum/threads/how-to-create-a-universal-windows-xp-image-using-mysysprep-exe-and-vm-ware.616/’]this tutorial[/URL].

    [1] I really don’t care about image size, but if I just beef up this image with all the drivers possible, could I potentially have a universal setup built off of a real PC, instead of a VM PC like in the provided tutorial? I’m assuming updating the image would mean having to deploying the pre-syspreped image, updating it, then re-syspreping it which is where having the VM would be ideal.

    [2] I also was wondering if I really need to use the sysprep.inf file to give an admin account password since the image im making already passworded it, or would syspreping remove this password so I then need the sysprep.inf to give it back?

    [3] Also the create random computer name should be fine because fog will then rename it after the image is deployed right?

    [4] We also just use the Product Keys on the Dell boxes we have. I should just be able to use the same code on every PC since it will auto activate because of the OEM Bios correct? I mean, we’ve never syspreped before and never had an issue with all the XP machines using the same image with the same product key/activation.

    I know this is a lot, but I’ve read so much that its all just one big blurry confusing mess on exactly what is possible with sysprep. It seems like everyone has their own opinion on how to do it, which doesn’t seem to help with the confusion! :P

    I’m just trying to make a setup that possibly works with more than one hardware configuration if at all possible.

    Thanks for any answers.
    -SMoRZ3



  • [quote=“SMoRZ3, post: 4501, member: 1375”]Hi all,
    I’m just getting into syspreping and I have some questions…

    I have a PC setup exactly how I want it (WinXP_Pro_OEM_SP3)). I’m going to upload it to fog as a backup. Then I plan on running sysprep.

    I’m also just reading into the [URL=‘http://driverpacks.net’]Drivers Pack[/URL] website. And trying to copy some of the suggestions in [URL=‘http://fogproject.org/forum/threads/how-to-create-a-universal-windows-xp-image-using-mysysprep-exe-and-vm-ware.616/’]this tutorial[/URL].

    [1] I really don’t care about image size, but if I just beef up this image with all the drivers possible, could I potentially have a universal setup built off of a real PC, instead of a VM PC like in the provided tutorial? I’m assuming updating the image would mean having to deploying the pre-syspreped image, updating it, then re-syspreping it which is where having the VM would be ideal.

    [2] I also was wondering if I really need to use the sysprep.inf file to give an admin account password since the image im making already passworded it, or would syspreping remove this password so I then need the sysprep.inf to give it back?

    [3] Also the create random computer name should be fine because fog will then rename it after the image is deployed right?

    [4] We also just use the Product Keys on the Dell boxes we have. I should just be able to use the same code on every PC since it will auto activate because of the OEM Bios correct? I mean, we’ve never syspreped before and never had an issue with all the XP machines using the same image with the same product key/activation.

    I know this is a lot, but I’ve read so much that its all just one big blurry confusing mess on exactly what is possible with sysprep. It seems like everyone has their own opinion on how to do it, which doesn’t seem to help with the confusion! :p

    I’m just trying to make a setup that possibly works with more than one hardware configuration if at all possible.

    Thanks for any answers.
    -SMoRZ3[/quote]

    #1. In theory yes, however it’s easier in a VM due to you being able to roll back changes, make updates, or test things out. You will want to build your image on the OLDEST hardware to make it the most compatible (if it’s xp)

    #2. Yes you need a sysprep.inf answer file to give the admin password the correct info

    #3. If you have the fog client installed it will rename the pc to what ever is in the database. The add-in Capone (google it) can also do advanced imaging options based off of DMI info

    #4. Don’t worry about product keys if you are using an oem disk. You need to have 3 things correct if you use an oem copy of xp for sysprep.

    A. OEM hardware (dell / hp / compaq / etc.)
    B. An oem slp key - [url]http://technet.microsoft.com/en-us/library/bb457078.aspx[/url]
    C. The proper oembios files (this happens when you run the oemscan.exe snapin)

    you need to sysprep due to having a unique SID, otherwise you have issues.

    Enjoy



  • I am assuming you downloaded the Windows Automated Installation Kit…which holds the Windows System Image Manager program. If this is the case make sure in your unattend file that you set the password value for the administrator account. If its blank then sysprep will strip the password and you will be prompted to provide one during the Windows installation. This is done in pass 7 under the Microsoft-Windows-Shell-Setup_neutral component…subheader is UserAccounts.

    I am not aware of FOG being able to uniquely name the computers after being imaged. If that is a possibility I would sure like to know…because that would sure simplify my issues that I am having.

    You should not have any issues with the product keys for Windows since they are part of an OEM license. One thing you need to make sure of is that all drivers are defaulted to the original drivers (of your motherboard) that self-install when your machine boots. If you install any additional/updated drivers then your Windows key will be invalid after booting your sysprep’d/imaged machines. You can try the PnpSysprep component and see if you have any luck with that. It is supposed to make all drivers persist through the Windows install.


Log in to reply
 

465
Online

39010
Users

10725
Topics

101897
Posts

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