• 0 Votes
    4 Posts
    1k Views
    Jaymes DriverJ

    Would you mind leaving your information on what it is you did to solve your issue so that others in your shoes will be able to use this thread as a reference?

  • Unable to move image on Synology NAS

    6
    0 Votes
    6 Posts
    3k Views
    S

    Yes, right šŸ˜‰ Thank you for you effort!

    I will try.

    Happend on the systems where we tried to directly link to the NAS.

  • Can't logon to FOG website; database errors

    4
    0 Votes
    4 Posts
    2k Views
    Tom ElliottT

    Lol if only. Glad to be of help.

  • PXE Menu update failed.

    8
    0 Votes
    8 Posts
    3k Views
    S

    Followed those steps and it is now working perfectly aside from server errors on our part. Thank you so much for the help

  • FOG 0.32 and Windows 8 Image Upload Problems

    17
    0 Votes
    17 Posts
    8k Views
    C

    Updated link…

    [url]http://dinomite.net/blog/2007/setting-up-ubuntu-for-building-kernel-modules/[/url]

    There are some notes about steps that I did not need to perform since this guide is from 2007. But kernel compiling hasn’t changed that much theoretically, just the actual syntax of the commands.

  • 0 Votes
    1 Posts
    1k Views
    No one has replied
  • FOG 0.32, Win7 and blank drive issue

    5
    0 Votes
    5 Posts
    2k Views
    Jaymes DriverJ

    Awesome, glad you got it working!

    I’ve never personally had any luck using the NTFS Resizable with my image but I’m glad it worked for you!

  • Clamav scan error

    6
    0 Votes
    6 Posts
    2k Views
    C

    I agree with Tom. You need to expand the init.gz and mount it so you can look into the fog.clamav script and see if you can edit it to skip over non-NTFS partitions instead of throwing an error.

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

  • Issues with Dell Latitude 10 using fog

    2
  • DeployStudios, FOG, and Server 2008 DHCP

    8
    0 Votes
    8 Posts
    5k Views
    C

    ProxyDHCP and dhcp-relay for your router if you have separate subsets that need dhcp services. We have a central fiber switch that routes for our subnets and two dhcp-relay entries in for each vlan interface, one for standard dhcp services and one to forward dhcp broadcasts to the fog server.

  • FOG and More than 10 Unicast Clients

    8
    0 Votes
    8 Posts
    4k Views
    Tom ElliottT

    Yes, our storage node is set to allow 15 clients as well as the other two places specified, but it still doesn’t work in our setup. It’s not a huge deal for us though, as our images are fairly small and everything is gig-e.

  • FOG service not joining clients to the domain

    3
    0 Votes
    3 Posts
    2k Views
    L

    I noticed on about 5 of the last 15 computers I imaged, the time/date were incorrect. Verify the time is matched with the server and try joining again

  • PXE proxy not working

    6
    0 Votes
    6 Posts
    4k Views
    J

    I know this worked for me:

    [IMG]http://i.imgur.com/B2jfsfJ.png[/IMG]

  • 0 Votes
    25 Posts
    16k Views
    Tom ElliottT

    Sorry all,

    I forgot to read that you guys were having the issue with FOG 0.33b. I posted all of this information on FOG 0.33 Bugs forum as well.

  • Identity the installed revision

    2
    0 Votes
    2 Posts
    976 Views
    Tom ElliottT

    I don’t know of a method of confirming the actual svn revision. Maybe somebody else can be of more help in this regard.

  • Looping in attempt to image

    5
    0 Votes
    5 Posts
    4k Views
    A

    [quote=ā€œjdd49, post: 1803, member: 623ā€]Navigate to /tftpboot/pxelinux.cfg
    Delete the file with the name as the mac address of your host[/quote]

    tis worked fo me!

  • Unable to resolve names from pxe debug

    2
    0 Votes
    2 Posts
    2k Views
    Tom ElliottT

    fogclient.localdomain is just the name the PXE file system is using. The Reason your fqdn isn’t working is probably due to DNSMASQing is not configured for domain name distribution. I could be wrong, but I think you have to use IP for the imaging process. Using hostname is easier to remember, but it also requires DNS lookups to be accurate and updated quite regularly. Remember that the loading of FOG during pxe boot is a very minimal OS and it doesn’t mean that all components work as you expect. I’d stick with setting the IP for your <yourfogserver> section.

  • Client PXE boot fail

    8
    0 Votes
    8 Posts
    6k Views
    P

    I know this thread is a little stale by now but for the sake of posterity, I was having the same issue after rebooting my FOG server (running Ubuntu 12.04 64-bit). I found that issuing:
    [CODE]sudo service tftpd-hpa stop
    sudo service tftpd-hpa start[/CODE]
    brought everything back to life

    I also found that adding
    [CODE]/bin/sleep 30 && /etc/init.d/tftpd-hpa restart[/CODE]
    to rc.local didn’t help (in fact, I already had that in my rc.local), however
    [CODE]/bin/sleep 30 && /etc/init.d/tftpd-hpa stop
    /bin/sleep 30 && /etc/init.d/tftpd-hpa start[/CODE]
    did help. Don’t know why restart didn’t (maybe my server is too quick and needs some more time before it tries to restart the service - [FONT=Consolas]/bin/sleep 60[/FONT] perhaps?)

    For the record (and to help anyone who doesn’t really understand Linux very well), my /etc/rc.local file contents are as follows:
    [CODE]#!/bin/sh -e

    rc.local This script is executed at the end of each multiuser runlevel. Make sure that the script will ā€œexit 0ā€ on success or any other value on error. In order to enable or disable this script just change the execution bits. By default this script does nothing.

    /bin/sleep 30 && /etc/init.d/tftpd-hpa stop
    /bin/sleep 30 && /etc/init.d/tftpd-hpa start

    exit 0[/CODE]

  • Have to image 8 labs by Monday

    37
    0 Votes
    37 Posts
    20k Views
    Tom ElliottT

    I guess that would do it as well. Awesome man. Maybe try posting your findings into the tutorial section so others can troubleshoot their issues a little quicker as I’m sure this isn’t the only one to have happened.

  • Failed fog backup attempt still haunts

    3
    0 Votes
    3 Posts
    1k Views
    D

    The systems would come back with an error. Unfortunately I didn’t document what it was…I assumed the problem was that I removed the original images. The server only has 1tb of space and I still have several computers I want to have imaged before the inevitable happens.

167

Online

12.4k

Users

17.4k

Topics

155.9k

Posts