will this be posted in the svn along with the config?

thanks

Never mind, it’s working now. Restarting the Fog service isn’t enough. After rebooting the service is active. Note that the source of all services is included, with Visual 2008 project files, in the tarball at fog_0.32\FOG Service\src

while using google I came across on this site
[url]http://www.digital-anarchy.com/science-tech/20955-windows-7-unattended-installs-guide.html[/url]
The site really helped understand the unattend.xml file…

it Worked for me it may work for you…

Ran the sysprep with unattend file worked really well, exactly what I wanted…

That bit about little submitted code is really worrying. From surfing the forums I got the impression that Chuck and Jian were still quite active but I guess getting down to coding, or at least submitting code, hasn’t been happening much.

I’m also really surprised that the donations are so minimal. Then again, we haven’t donated anything. But still, with the value that FOG brings, I assumed that the donations would be flying in. Hmmm… Maybe some crowd-funding is needed.

Thanks for some transparency on this Bryce. We’ll be in touch.

Other information > FOG Settings > [FONT=Ubuntu][COLOR=#333333]FOG_HOST_LOOKUP[/COLOR][/FONT]

[FONT=Ubuntu][COLOR=#333333]Set the value to 0.[/COLOR][/FONT]

[COLOR=#000000][FONT=Calibri]Thank you so much i really appreciate this so much.[/FONT][/COLOR]
[COLOR=#000000][FONT=Calibri]I am using the php attached in the above this post, and also here is the fog file, what you can find at initmountdir/bin. Note: Is not .txt file, but without extension I am not able to upload it.[/FONT][/COLOR]

[COLOR=#000000][FONT=Calibri]Again thank you so much![/FONT][/COLOR]

[url=“/_imported_xf_attachments/0/225_fog.txt?:”]fog.txt[/url]

Fog 0.33 is in active development, the bug tracking thread can be found here:
[url]http://fogproject.org/forum/threads/bugs-in-fog-0-33.631/[/url]

fog client must be installed on hosts with ip or hostname of the server. If ip don’t work try hostname.

Hi,
When I install fog client with server hostname (not IP server), it seem’s OK. fog 252 must be defined in hosts file like :
10.1.1.252 fog252

OR! Is it possible to do a quick host register and then auto-image the laptop? Without any input on the server?

From [url]http://www.fogproject.org/wiki/index.php?title=Managing_FOG#Hosts[/url]

“After each registration the computer will automatically image and the [B]FOG_QUICKREG_SYS_NUMBER[/B] will incremented by 1.”

It’s not intuitive, but it is documented in the wiki, although not easy to find specifically. I look forward to you getting your wiki access and maybe we can work together to rearrange some of the documentation to make it easier to follow.

I glad 🙂
We use a fog 0.30 customized version :oops: But the LDAP validation, I think that is easy to migrate to a new version of FOG.
The “site” layer and technician rol, is much more difficult. Sorry.
I just started the migration of code from the old version to the new FOG version.

Easy 🙂 make a “deploy one snapin task” in Advanced Tasks Section

sweet, I will try to install this on fedora again… I currently got this working on centos 6.3, working flawless…
I goint to set a fedora set up now…

You can update the code to do it.
There are some elements: imagingLog table in FOG database, pre_Stage1.php and post_Stage3.php webservices. Those webservices are located in /var/www/fog/service.

When FOG makes a tasks, those tasks write a log in imagingLog table (make a checkin/checkout). Well, the fog script, that runs in the computer, calls to a webservice when the task begin. This webservice is pre_Stage1.php and makes the checkin. When the task ends, the script calls to post_Stage3.php to make a checkout. You must update the checkin and checkout functions to add the taskType in the imagingLog (you must add a new column in imagingLog table), and filter the task type. After this, you can make a personal report.

It does work across VLANs, with some notes. You have to have IP Helper or DHCP Relay enabled on the router, which you might already have if your current DHCP server can handle requests from all the VLAN’s. If you use ProxyDHCP, you’ll need to add an additional IP Helper/DHCP Relay to the router. You need good uplinks or your FOG performance will suffer. Make sure no uplinks are slower than the NIC speed of your FOG server.

If you plan to do mass deployments, you may slow down parts of the network that are sharing the switches between your FOG server and clients. Imaging 10 to 20 machines via unicast uses a lot of bandwith.

If you plan to multicast, make sure you setup and test your switches and routers so you don’t take down the entire campus network.