Posts made by ssx4life

To answer your question… “yes” but also possibly “no”

It all really depends on what you are attempting to use fog for in conjunction with WDS and how your network is segmented.

Long story short, in plain terms you can have only one DHCP server that controls or “points” to PXE that must be either FOG or WDS, not both.

You could use WDS for imaging and the fog client for software management, inventory, etc.

Or the reverse could be true and have WDS (if there is a client for it) do the management and image with fog.

Hope this answers your questions for you.

[quote=“ZeroSkillz, post: 11092, member: 3464”]Thank you this was very helpful.[/quote]

no problem.

enjoy

9 times out of 10 the limitation is on the client side if you load it via PXE into memory.

If your .iso exceeds the size of the client pc you run into issues with it not booting properly.

Hope this helps.

[quote=“ZeroSkillz, post: 10951, member: 3464”]Can you post how that was done? Thanks[/quote]

I don’t have a system in front of me to build a guide, but a quick and simple process is th efollowing.

1. Go to the CLIENT computer and log in as admin
2. Go go the c:\Program files\fog folder (I think it’s the fog folder)
3. Locate the .ini file that allows you to make changes to the client software (fog client)
4. Open the file in notepad
5. Locate the line of code that mentions forced task reboot (or something simlar to that).
6. By adjusting the code from a 0 to a 1 (or vice versa) it enables or disables the code for this.
7. Save the file in notepad + reboot the fog service (services.msc) fogclient - restart service.
   or
8. Safe the file in notepad + reboot the pc.

I should note that if you have the fog client as an image you would need to make this change PRIOR to capturing and deploying it. Otherwise you would need to go to every client and make the adjustment.

This might sound a bit silly, but do we really want to support windows 8? (I’m 1/2 kidding here)

It’s also helpful to point out that when you make a switchless .exe like this it can also be used for group policy or other deployment methods

I’ve recently been using sfx maker - [url]http://www.isoft-online.com/down/SFXMaker_1.3.1_Beta.zip[/url] to package and create installers for fog. Works great on larger installations of programs like Microsoft Office and Adobe CS products

Thanks again Andyroo for the guide.

[quote=“buckITall, post: 9087, member: 101”]One last quick question,
I’m using an OEM key given to me from my boss that I’m pretty sure he gets from MSDN subscription.
Will using this key run out if Imaging over and over different systems?
Or will the oemscan.exe help resolve my question?[/quote]

I’m sure you already resolved this but I wanted to leave a note in case anyone asks.

If you have an MSDN subscription you don’t want an oem image or oem media. You want a VLK key and VLK media.

Keep apples with apples.

OEM Scan assists with entering the required files (.bin / .dat / .cat / .sig files) to pass genuine advantage legally (in the same method that dell /hp / etc. pass it for oem copies of xp)

Thanks.

Not to leave people hanging or trying to pick up the pieces, but I have been absent from this project and many other items recently due to family issues, so I apologize for not keeping up with requests or being active on supporting this documentation at this time.

In regards to re-uploading the tftpboot folder perhaps another member can zip and upload one for you. I’m sorry I just don’t have time and or resources to dedicate to this currently.

If things change you’ll be the first to know. Feel free to PM me if you have any questions and I’ll try to get back to ya’ll when I have time.

Thanks in advance >_<

Not to leave people hanging or trying to pick up the pieces, but I have been absent from this project and many other items recently due to family issues, so I apologize for not keeping up with requests or being active on supporting this documentation at this time.

In regards to a VM tutorial perhaps someone could volunteer some time to look into this. However at this time I don’t have time and or resources to dedicate to this.

If things change you’ll be the first to know. Feel free to PM me if you have any questions and I’ll try to get back to ya’ll when I have time.

Thanks in advance >_<

You either need to change the bios settings to ACHI (from raid most likely) or you need to include the needed mass storage drivers (F6 during setup boot).

you can also slipstream them into your installation cd / dvd using an application like driverpacks base - [url]http://driverpacks.net/book/export/html/359[/url]

[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]

Not to throw you under the bus, but seriously try googling it next time. It’s on the beta version available on the main fog download page.

[quote=“afmrick, post: 4735, member: 417”]Yeah, the snapin agent is hard coded to wait 350-500 seconds in [B]fog_0.32/FOG Service/src/FOG_SnapinClient/MOD_SnapinClient.cs:[/B]
[CODE]126 try
127 {
128 Random r = new Random();
129 int intSleep = r.Next(350, 500);
130
131 log(MOD_NAME, “Sleeping for " + intSleep + " seconds.”);
132 System.Threading.Thread.Sleep(intSleep * 1000);
133 }[/CODE]
There’s a good posting on this at [URL=‘http://www.edugeek.net/forums/o-s-deployment/92417-how-modify-snapin-client-sleep-timer.html’]edugeek.net[/URL][/quote]

Correct. i’ve also gone one step further and downloaded the new snapinclient.dll that checks in every 30 seconds instead of 5. Saves time on imaging / etc. Check the wiki and main support pages on these forums for a copy of it.

[quote=“SMoRZ3, post: 4552, member: 1375”]Boon, Thanks for posting the “snap in” version of OEMScan. :)[/quote]

As a friendly reminder (I made that snapin). That if you run it as a snapin you will want to flag it for a reboot.

If you run the .exe as a stand alone and reboot it will also work (handy for a flash key)

Again… oemscan.exe will ONLY work on XP home / pro / MCE2K5, and will ONLY auto activate if you have an SLP key on oem hardware

Enjoy!

[quote=“boon, post: 4519, member: 833”]I’ve uploaded the files SSX4LIFE posted here:
[URL=‘https://docs.google.com/open?id=0B6xOimbg2JqVZnhQUjRSaWFoNHM’]sysprep.zip[/URL]
[URL=‘https://docs.google.com/open?id=0B6xOimbg2JqVS2R6bXFad1Rka28’]oemscan.exe[/URL][/quote]

Thanks boon for covering me while I was out of the states.

i got back today, and was about to upload them when I find you’ve taken care of it

thanks.

If your images begin in a VM then you can quickly take a snapshot using their built in tool.

If you built your image on the GX620 I think you are stuck (sadly). You could download an image to a PC (say your GX620 image) Run updates on it, and then re-upload it to the server.

Hope this helps.

this is possible

all you need to do is capture a VM BEFORE you run sysprep (or mysysprep.exe if using my guide). Then run sysprep, capture your image and roll it out to your equipment.

In 6 months from now if you want to update the image simply roll back to right before you ran sysprep (or myspsprep) and run updates, make changes. then RE-SAVE the image, run sysprep, upload, and deploy.

Hope that makes sense

edit to clarify if you are building a universal image this is possible. I’ve never pulled a hardware specific image into a VM, that’s a bit unique of an idea.

As an FYI you can go into your default.cfg file on the fog server and adjust the timeout on the menu as well. I have mine set to 30 seconds.

[quote=“SMoRZ3, post: 4430, member: 1375”]Does anybody know where you can get an XP Pro OEM disc? I have a Dell version, but it doesn’t take the Perserving OEM Actication key thats provided by Microsoft.

Basically the version I have cant be activated, so then i cant do updates which makes using the VM useless as far as saving time…

Thanks[/quote]

Legally we can’t distribute these due to copyright law.

Please post your MGADIAG.exe logs so we can better help you

[url]http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&sqi=2&ved=0CFIQFjAA&url=http%3A%2F%2Fgo.microsoft.com%2Ffwlink%2F%3Flinkid%3D52012&ei=qYzsT_L_O9L1qAH_lLzOBQ&usg=AFQjCNH5Zcs6VID448dqfDkoyf9nzmkx7w&sig2=RpxaEKLIe4K0Q8fzL-_D2Q[/url]