• Fog Snapins

    5
    0 Votes
    5 Posts
    2k Views
    R

    @george1421 Excellent information! thank you!

  • Host Pending MAC create multi mac address!

    Moved Unsolved
    9
    0 Votes
    9 Posts
    3k Views
    Tom ElliottT

    What I’m trying to say, is how to appropariately fix the problem in rc-10.

    The problem, as you’re seeing it, is NOT a bug, rather a fix of an older bug. The only reason it “didn’t” do this in the past was because it was broken.

  • BZImage...No such file or directory when trying to start an image

    Solved
    33
    0 Votes
    33 Posts
    14k Views
    ryan.mckenzieR

    @george1421 great thank you! I will continue to work on this 760 and not try to confuse them again! lol

  • Strange network activity and peeks during multicast

    7
    0 Votes
    7 Posts
    2k Views
    F

    @Junkhacker thx for comment 🙂

  • Error $this->_kernel = sprintf ?

    Solved
    21
    0 Votes
    21 Posts
    6k Views
    Tom ElliottT

    @todachuy2406 The sprintf you keep referring two had nothing wrong with it.

    It was simply your using pxelinux.0 that was causing the problem with the booting.

  • FOG Imaging Doesn't Respect Max Client Setting

    7
    0 Votes
    7 Posts
    3k Views
    Wayne WorkmanW

    @MikeoftheLibrary After reading that, there’s another thing I forgot to mention. Each multicast session only goes as fast as the slowest host. So if one of them has bad RAM or a failing disk or bad patch cable, this would slow down every host in that multicast task. This could be your issue - and most likely is since you’re using business grade network equipment.

  • Change default /images directory

    Unsolved
    13
    0 Votes
    13 Posts
    9k Views
    x23piracyX

    Hi,

    in order to @george1421 's post, because of the may incoming space issue i have the main fog server on a vm with only 50gb of storage and an additional physical storage node with 4tb raid storage that will also went on a backup tape each week. our vm’s on esx also have a backup each week.

    Regards X23

  • Lenovo m72 image issues

    Unsolved
    20
    0 Votes
    20 Posts
    7k Views
    Jaymes DriverJ

    @wlsnfmly said in Lenovo m72 image issues:

    The only change I made was to go back to the default undionly.kpxe option

    This really is the recommended file.

    Please let us know if you experience further issues with your systems pxe booting. I am not exactly certain why you experienced the issues you did, but I am glad you were able to resolve them.

  • Kernel panic in Centos 7

    Unsolved
    2
    0 Votes
    2 Posts
    2k Views
    george1421G

    Just to be clear, you were able to deploy to this same computer with a version before RC10 but now you get this kernel sync panic?

    Tell us a bit more about the target computer.
    What manufacturer and model is it?
    What firmware mode is it in Legacy (bios) or uefi?
    What specifically do you have set for dhcp option 66 {next-server} and dhcp option 67 {boot-file}?

    The error says that the kernel (bzImage) did not identify the virtual hard drive (init.xz). While its possible something happened to the init.xz file during the installation of RC10. I have to think something else is at fault here.

  • snappin doesn't work

    Unsolved
    39
    0 Votes
    39 Posts
    15k Views
    JJ FullmerJ

    Also, for debugging.
    If you put the script into a function and add [cmdletBinding()] you can run it with -debug
    which means you can add lines like Write-Debug “variables is $variable”; that will only show up when -debug is specified and will pause for you. You can also add Write-Verbose “messages”; that only show
    i.e. to do it while still running it as a ps1 script with arguments you’d have to be a little tricky. If you mad the script a .psm1 and added a export-modulemember -function funcName; line at the end and then ran this in a ps console ipmo -Force -Global \path\to\psm1; you could then run your script as a function that you can import into any script or console and add the -Debug and or -Debug lines directly when running the function

    param ( [String]$programme, [switch]$debug, [switch]$verbose ) function installProgramme { [CmdletBinding()] param ( [String] $programme ) $user = "install" $pwd = "1234500000000000000000000000000000000000000000000000000000AAAA=" $serveur = "\\fileserver.istic.univ-rennes1.fr\partage" $cert = $(Get-ChildItem cert:\CurrentUser\TrustedPublisher | where {$_.Subject -eq "CN=ISTIC/ESIR Signature"}) $tab_key = @() foreach ($i in $cert.SerialNumber.ToCharArray()){$tab_key += [convert]::ToInt16($i,16)} $password = ConvertTo-SecureString -key $tab_key -string $pwd $credential = New-Object -TypeName system.management.Automation.PSCredential -ArgumentList $user, $password Write-Verbose "Attempting to mount $serveur..."; #net use p: $dossier_partage /p:n /u:$($credential.GetNetworkCredential().username) $($credential.GetNetworkCredential().password) if (!(Test-Path -Path p:)){ $net = new-object -ComObject WScript.Network $net.MapNetworkDrive("p:", $serveur, $false, $credential.GetNetworkCredential().UserName,$credential.GetNetworkCredential().password) } Write-Debug "Check if P is mounted..."; #lorsque l'on lance un script powershell, si il y avait des espaces dans le nom, cela ne passait pas #lorsque l'on faisait un start-process et ce nom en argument. Donc on utilise plutot le nom court $prog_court = (New-Object -ComObject Scripting.FileSystemObject).GetFile($programme).ShortPath write-host "$(hostname):Dossier de l'installer $($dossier_installer)" write-host "" write-host "$(hostname):lancement de $($programme)" write-host "$(hostname):lancement de $($prog_court)" #start-process -FilePath $programme -wait -NoNewWindow $dossier_installer = $((get-item -path $programme).DirectoryName) if (!(Test-Path -Path "$dossier_installer\logs_fog_install")){New-Item -ItemType directory -Path "$dossier_installer\logs_fog_install"} $extension = (get-item -path $programme).Extension if ($extension -eq ".bat" -or $extension -eq ".cmd") { #write-host "$env:COMPUTERNAME:C'est un script bat" start-process -FilePath $prog_court -wait -NoNewWindow -RedirectStandardOutput ${dossier_installer}\logs_fog_install\${env:COMPUTERNAME}_log.txt -RedirectStandardError ${dossier_installer}\logs_fog_install\${env:COMPUTERNAME}_error.txt } if ($extension -eq ".ps1") { #write-host "$env:COMPUTERNAME:C'est un script powershell" $policy = Get-ExecutionPolicy Set-ExecutionPolicy AllSigned start-process -FilePath PowerShell -Arg $prog_court -wait -NoNewWindow -RedirectStandardOutput ${dossier_installer}\logs_fog_install\${env:COMPUTERNAME}_log.txt -RedirectStandardError ${dossier_installer}\logs_fog_install\${env:COMPUTERNAME}_error.txt Set-ExecutionPolicy $policy } #net use p: /delete $net.RemoveNetworkDrive("p:") } #create string to run function $runFunc = "installProgramme $programme"; if($debug){ $runFunc += " -Debug"; } if($verbose) { $runFunc += " -Verbose"; } $runFunc += ";"; Invoke-Expression $runFunc;
  • Booting from .ISO

    Unsolved
    4
    0 Votes
    4 Posts
    2k Views
    george1421G

    @ukke Again, fog 1.2.0 is 4 years old.

    If you want/need to support Win10, GPT formatted disks, UEFI firmware, or NVMe (M.2) drives then you will want to be on FOG 1.3.x. As a caveat, I do have to say that FOG 1.3.4 has a but when upgrading from 1.2.0. You should have better success upgrading to 1.3.5-RC6 or higher. Or wait until 1.3.5 is released.

    You can use 1.2.0 but you will have to manually build the menu.

  • Fog Client doesn't update (no rename, ad join)

    Solved
    4
    0 Votes
    4 Posts
    949 Views
    x23piracyX

    to solve this in future i will add a “net time…” command to my first logged on user.

  • Upgrade version

    Unsolved
    52
    0 Votes
    52 Posts
    29k Views
    Wayne WorkmanW

    @mimi1255 If your current issues are not related to the original problem in this thread, please start a new thread - and we will gladly help you there.

  • Network Boot does not work anymore (no FOG Problem!)

    Solved
    10
    0 Votes
    10 Posts
    3k Views
    Wayne WorkmanW

    @x23piracy said in [SOLVED] Network Boot does not work anymore (no FOG Problem!):

    It a shame i must say i dont know the differences between the different boot files 😞

    https://wiki.fogproject.org/wiki/index.php?title=Filename_Information

  • mysql

    31
    0 Votes
    31 Posts
    12k Views
    Wayne WorkmanW

    This is older but it’s still accurate:
    https://wiki.fogproject.org/wiki/index.php?title=Modifying_existing_DHCP_server_to_work_with_FOG

    Also, @george1421 and @Jaymes-Driver thanks for picking this thread up, that’s team work. 🙂

  • Start on fog with windows 10

    Unsolved
    11
    0 Votes
    11 Posts
    4k Views
    Tom ElliottT

    @mimi1255 That only partially solves the problem. Now your network, as far as I can tell, is handing out boot files for UEFI machines. This will cause unexpected things whenever you get new systems in as most are now coming with default settings of UEFI enabled systems. While you are correct that you will need to turn off secure boot, this will not (at least I don’t think so) fix the problem you were seeing when you were UEFI booting the system.

  • Multicast doesn't work

    Unsolved
    8
    0 Votes
    8 Posts
    3k Views
    Jaymes DriverJ

    @Almeida

    @Tom-Elliott said in Multicast doesn't work:

    As a mode of reference, this typically occurred because of the storage node network interface. If it couldn’t match the interface, the files couldn’t be found to enable the command.

    As @Junkhacker stated you would be best to update to the newer series of FOG as many of these things have been corrected for and we have more direct capabilities to help troubleshoot.

    I’d recommend the 1.3.5-RC’s particularly if your Server OS is Ubuntu flavored.

    I can recommend Ubuntu 14.04 or 16.04. FOG installed with out a hitch!

  • New DHCP Server - Client TFTP Error

    Solved
    15
    0 Votes
    15 Posts
    6k Views
    E

    @x23piracy I will. Thank you.

  • Image 0.00 iB

    Unsolved
    2
    0 Votes
    2 Posts
    823 Views
    Wayne WorkmanW

    Depends on if the capture completed or not. If it completed, the files are gone. If it didn’t complete, then the old image should still work without doing anything special.

    What is the latest version of FOG? We need exacts, numbers. The latest version changes daily, sometimes even more often.

    In FOG 1.3.x, there is a feature called “Protected” for images, use this for any image you don’t want accidents to happen to:

    0_1487255455742_Protect Image.png

  • FOG Client Action Text is missing (empty)

    Solved
    10
    0 Votes
    10 Posts
    3k Views
    x23piracyX

    @Joe-Schmitt no interaction with fog client then triggering the snapin.

115

Online

12.4k

Users

17.4k

Topics

155.9k

Posts