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]