[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! 😛

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

Please check the tutorial forum. I have a start to finish guide on making a universal image - [url]http://fogproject.org/forum/threads/how-to-create-a-universal-windows-xp-image-using-mysysprep-exe-and-vm-ware.616/[/url]

Dude… sounds like the host is not registered with FOG. but at the sime time, looks like it is.

Have you tried to remove the host and re-add it?

Or… jump into the database and see what is happening?

Look here for some information regarding pxe/tftp over vpn.

[url]http://fogproject.org/forum/threads/tftp-issues.823/#post-4112[/url]

Solved with help of another forum. Using the GUI sysprep does not read the unattended.xml file. You must use the command line and the unattend option. I’m amazed I am the first to have this issue.

While researching this I came across an article which talked of how memdisk booting large files can cause memory errors because of the nested memory method it uses. Rather than using memdisk for your kernel and the Windows 7 disk for the init file, you might look for other options such as booting grub4dos.

I can now confirm that the problem has nothing to do with fog. A few testruns later it seems sysprep or some other think did it. A direct copy from original to target was successful. Even running sysprep afterwards was successful.

I am stumped. Any ideas?

Well, unfortunately I get stuck right at the get-go. The image takes on VM, but I can’t use my keyboard or mouse at the log-in screen to even do anything. I’ve tried a few things, but can’t get it to work. Could this be because we have never syspreped any images before uploading them to fog for deployment?

Have you considered a Fog snap-in to run post imaging that might execute whatever commands you need to enable the 2nd monitors?

If you don’t have overlapping subnets between the two networks it may be easier to setup routing so that both networks can see and use the fog server.

I don’t know if there is a way to make Fog work the way you are proposing using another interface.

[quote=“eric0626, post: 3807, member: 357”]KMS does not use SID, but it uses CMID instead. Thus, you don’t have to sysprep the image if you want to KMS, you can just simply rearm the OS before uploading the image.[/quote]

Eric, you are right about the fact that KMS does not use the SID, but CMID instead. This does not change the fact that sysprep is necessary, as CMID is also changed by sysprep. Having the same CMID on all computers results in KMS not counting.

Rearming the computer will create a new CMID, but this is not supported by MS. The recommended way is to rebuild your image with sysprep /generalize and no <SkipRearm>. The last note on the [URL=‘http://support.microsoft.com/kb/929829’]KB929829 [/URL]might be confusing though.

Regards, Bjorn

Also is it possible that the SATA controllers are configured differently? You might pop into the BIOS and check that out and confirm that they are all set the same as the laptop you built the image on.

Try to check the command file for the machine in question.
/tftpboot/pxelinux.cfg/01-XX-XX-XX-XX-XX-XX (The file is named after the MAC of the machine)

Within that file check to make sure all settings are correct. Like DNS=(should be your DNS on Your network and not the remote DNS)

Another thing to check: is there something broadcasting on the remote network that could interfere with the traffic?

I have a bunch of these ST250LT007 Seagate drives (the same Momentus line of drives, but with no encyption) and they work just fine. However, 4K advanced format drives are not supported in FOG yet. You’d have to use FOG .33 (beta still) to image those drives. That is what I am using now and it is working. The beta is not “feature complete” yet, but 4K drive imaging works.

I’d recommend downloading the beta release to a spare system and doing a few image tests. You could report your success/failures to this forum post:

[url]http://fogproject.org/forum/threads/bugs-in-fog-0-33.631/page-4#post-3691[/url]

If you need help getting the latest beta release down, just let me know.

Have you tried setting the image type to “multiple partition image - single disk (not resizeable)”? This usually works for everything.

[quote=“astrouga, post: 3670, member: 907”]Sounds like you need to modify your existing DHCP server so it can point to your FOG server:

[url]http://www.fogproject.org/wiki/index.php/Modifying_existing_DHCP_server_to_work_with_FOG[/url][/quote]

This should do the trick