• Permission denied with SMB share for image capture.

    Unsolved
    4
    0 Votes
    4 Posts
    4k Views
    A

    OK thanks you. Finaly, I’ve up my VM size and problem solved :P.
    My windows server is in prod, I can’t make tests on it.

    Thanks you guys 🙂

  • WS 2008 and UEFI PXE

    Unsolved
    4
    0 Votes
    4 Posts
    1k Views
    george1421G

    @Grizzly In the long run, you will not be sorry you upgraded. Plus extended support for 2008 is only for just a few short years.

  • Updating/Downgrading kernel from gui sends me back to the Dashboard - home page

    Solved
    4
    0 Votes
    4 Posts
    923 Views
    T

    @Tom-Elliott Thanks, that worked!

  • Storage Node Disk stats not showing up on dashboard.

    Solved
    7
    0 Votes
    7 Posts
    3k Views
    S

    Just a quick update. I am not sure why it happened but I am glad it has. I decided to rerun the installer script on my Storage node this morning and low and behold, when I logged into the management interface under the “storage node disk usage” drop down appear the storage node disk stats. I can not explain it may be some can but the problem is resolved.

  • User self deployment, howto force one image only?

    Unsolved
    3
    0 Votes
    3 Posts
    1k Views
    george1421G

    One might think FOG is pretty close to what you want today. If you go into the quick image menu FOG today displays a list of all images, but the default image assigned to that workstation is selected by default. So FOG knows the defined image for that computer, the trick (solution) is to not have fog show all the other images. After the menu timeout the defined image is started if no one touches the keyboard.

    While I’m sure it not as easy as this, but if you could find the sql commands used to display that menu, one might be able to tweak it to only show the assigned image.

    This was just an idea, without any basis of fact in the code.

  • Trying to add clonezilla to PXE Menu!

    Solved
    11
    0 Votes
    11 Posts
    6k Views
    x23piracyX

    @bootsnspurs said in Trying to add clonezilla to PXE Menu!:

    @george1421 This code worked for me. Thank you.

    Thanks Tom also.

    please mark as solved 🙂

  • Kernel Offset disabled end Kernel panic not syncing: VFS unable to mount root fs

    Unsolved
    7
    0 Votes
    7 Posts
    8k Views
    george1421G

    @craigtighe Can/Will you confirm the exact settings of dhcp option 66 and 67?

    dhcp option 66 must be the IP address of the new FOG server
    dhcp option 67 should be undionly.kpxe (or undionly.kkpxe) Make sure its spelled correctly. Using pxelinux.0 WILL generate a kernel sync error. That is known, fog moved away from syslinux quite a few years ago.

    And as Junkhacker said, if you could snap a clear picture with a mobile and place it here we can see the context of the error too.

  • 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
    4k 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
    19k 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
    8k 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
    10k 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
    10k 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
    20k 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
    1k 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
    37k 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.

80

Online

12.7k

Users

17.6k

Topics

156.8k

Posts