• ClientUpdater

    13
    0 Votes
    13 Posts
    4k Views
    J

    Of course the way via snapin would be the alternative.

    I just wanted to try the clientupdater service for the first time and exactly the required file was forgotten in the sourcode ;(

  • PXE-T01: FIle not found eroor

    11
    0 Votes
    11 Posts
    4k Views
    A

    can you give me the wiki path for tftp issues

  • IPXE help

    16
    0 Votes
    16 Posts
    6k Views
    G

    Building A successfully gets DHCP addresses etc as well ?

  • IPXE boot menu password protected

    3
    0 Votes
    3 Posts
    3k Views
    H

    That was easy, Thanks!!!

  • Aditionnal storage node problem

    3
    0 Votes
    3 Posts
    1k Views
    G

    Hi, I haven’t solved it yet. Since I don’t have a lot of time to spend on that issue, I might use an external drive plugged in the ubuntu server to store image files.
    I’ll post a message if I manage to solve the problem 🙂

  • Image path not the same in log as it is storage node.

    10
    0 Votes
    10 Posts
    4k Views
    T

    I have determined the image path this storage node is using is the path from another storage group Master node. I have 2 storage groups and each have a Master node. Why would this be looking at the other storage group? I have verify the storage group is correct on the image.

  • Ubuntu 14.04 Fog Server 1.20 - Download (Deploy) image issue

    33
    0 Votes
    33 Posts
    14k Views
    K

    Update for everyone. I can Image Windows 7 just fine. Looks like it’s just Vista.

  • Change storage node, won't download image

    3
    0 Votes
    3 Posts
    1k Views
    H

    You need to add the subfolder and the subfolder/dev to the /etc/exports file, and then run exportfs -av

  • Unable to image after 1.2 upgrade, mysql pw issue

    1
    0 Votes
    1 Posts
    575 Views
    No one has replied
  • 0 Votes
    3 Posts
    2k Views
    A

    [quote=“cadyfish, post: 35529, member: 24458”]aboushard,

    Try post 8 in [url]http://fogproject.org/forum/threads/fog-is-inoperable-after-server-reboot.11460/[/url][/quote]

    I will try that.

  • Using Hard Disk: /dev/sda, then Processing Hard Disk: dev/sda...hung

    6
    0 Votes
    6 Posts
    3k Views
    C

    It seems like a lot of people run into issues like this when building an image on a physical machine. I would recommend by starting off by wiping all partitions out with a gparted disc and then making sure BIOS is set to legacy mode (at least until UEFI issues are resolved) and then install Windows. It would prevent issues like this from occurring

  • Kernel Panic - not syncing

    2
    0 Votes
    2 Posts
    1k Views
    A

    I just found the following thread:

    [url]http://fogproject.org/forum/threads/kernel-panic-not-syncing-lenovo-thinkpad-edge.10794/[/url]

    I’ll try hosting the files from another server to see if that helps. I’m also in the process of compiling my own init.xz.

  • PC's not imaging correctly after upgrade to 1.2

    2
    0 Votes
    2 Posts
    736 Views
    T

    resolved: bios hdd settings were set for raid, not ide.

  • Error deploying image

    4
    0 Votes
    4 Posts
    2k Views
    Tom ElliottT

    To simplify the commands, you can run:
    [code]touch /images/{,dev/}.mntcheck
    chmod -R 777 /images[/code]

  • FOG PXE boot problems

    1
    0 Votes
    1 Posts
    777 Views
    No one has replied
  • Error 0x040ee119 for Acer netbooks

    7
    0 Votes
    7 Posts
    3k Views
    J

    Brendan,

    You are brilliant.
    I downgraded one of our AO753’s from V1.24 to V1.16 and it works.
    The Acer Aspire 1830 is also an identical BIOS so the downgrade worked for them too (From V1.20 to V1.16).

    Tom, Not sure if any of this can help? But have amended the descriptions of each bios version below from the Acer website.

    Version - Description
    1.24 - BIOS (Well this isn’t much of a description)
    1.20 - Releases for support WiMAX
    1.16 - 1. Updates ROM to support LAN chip rev. B.

    Updates ME version to 6.0.42.1221.
    1.11 - Solves no display issue from S3 resume during OOBE at the first cycle of factory default preload.

    The zip files don’t appear to have an release notes or change logs.

    Regards,
    Jason

  • Changing FOG menu in 1.2.0

    8
    0 Votes
    8 Posts
    5k Views
    Tom ElliottT

    The reason why 1.2.0 direct upgrades seem to fail from 1.x.x to 1.2.0 is because 1.2.0 actually fixed some installer issues with the database things.

    Even in 0.32 the upgrade path still required one to edit the config file if you set a mysql password. Add to that, the fact you had two config files to edit. You had /opt/fog/service/etc/config.php and /var/www/fog/commons/config.php

    In 1.1.2 (i think) i moved the config.php to it’s own class file located in /var/www/fog/lib/fog/Config.class.php

    In 1.1.2 however, the installer was still having issues with passworded mysql databases. The FOG Team tried, during our move over from 1.0.0 rom 0.32, fixing a method to allow the password to be written into the now singular config file. This password was more related to the snmysqlpass field which is, in storage nodes, the database password for the fogstorage user. As the password didn’t seem to work right for the ftp user or the db user, we tried to use this field to set and hold the information for the ftp as this is more often the problem in 0.32. Then, finally I was able to fix the problem properly. The only problem I couldn’t fix were previously configured .fogsettings files. So, the fix, before you upgrade, is to edit the snmysqlpass with either blank or your mysql password. Run your installfog.sh file and all should work properly. And the upside is you won’t have to do this every time. If you already upgraded, edit the /var/www/fog/lib/fog/Config.class.php and enter either your blank or mysql password as needed. Edit the .fogsettings information as well.

    While editing the .fogsettings file will not fix issues automatically, it will help you in the future when you need to update/upgrade fog again.

  • Slowness in gui after 20 minutes

    9
    0 Votes
    9 Posts
    3k Views
    C

    There are two web options I could see that may slow down the UI if one you have a large host database or limited ram.
    FOG_USE_ANIMATION_EFFECTS
    FOG_HOST_LOOKUP

    Also if you upgrade from .32 it would work better if you wipe your mySQL database out

  • Fortigate Firewall Setting - FOG Server

    2
    0 Votes
    2 Posts
    2k Views
    C

    The following I believe are the ports that fog uses:
    FTP – tcp 20,21
    SSH – tcp 22
    TFTP – udp 69
    HTTP(s) – tcp 80,443
    Portmap – tcp/udp 111
    NFS – tcp/udp 2049
    Transfer ports – tcp/udp 1024 – 65535

    Depending on where your firewall is located you may not need to make changes to it though. For example if it is out on the DMZ it shouldn’t matter. You will need to configure DHCP in your switches though if not already done so. [url]http://www.fogproject.org/wiki/index.php/Modifying_existing_DHCP_server_to_work_with_FOG[/url]

  • Getting an operation not supported error.

    10
    0 Votes
    10 Posts
    3k Views
    C

    Tom - I have not tried that conf and will give it a try next time we have “down time” at work. Thank you for some input.

    Cadyfish - if this is what is in the wiki, we have tried that. Very time we restart dnsmasq with that other config, it crashes dnsmasq. The system logs really does not give me any input as to why (I could be looking at the wrong logs). That being said, I will also try this just in case I did miss something. THANKS!

102

Online

12.2k

Users

17.4k

Topics

155.6k

Posts