• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. LJedi
    3. Posts
    L
    • Profile
    • Following 0
    • Followers 0
    • Topics 17
    • Posts 58
    • Best 4
    • Controversial 0
    • Groups 0

    Posts made by LJedi

    • Trunk 8093- Deploying Image Failing, Partition Size Error

      Trunk Version: 8093
      I am having an issue deploying an image. The deployment keeps failing because of a partition size error. I have included the screenshot of the error saying “Target partition size (525 MB) is smaller than source (525MB)”. The upload of this image was on an 80 GB HDD and the imaged was deployed to a different PC with the same size and specs as the upload computer HDD. If I put in a hard drive that is bigger than 80 GB, then the image deploys successfully. The Windows 10 image has two partitions, a 500 MB System reserved, and a 74.04 GB C://

      Here are the specs of the image I am trying to deploy:
      Operating System: Windows 10
      Image Type: Single Disk- Resizable
      Partition: Everything
      Compression: 7

      0_1465931602952_IMG_0902.JPG
      Any help will be fantastic!

      Thanks

      posted in FOG Problems
      L
      LJedi
    • RE: Fog Client Disjoin From Domain Feature

      @Wayne-Workman Can Fog join to a Workgroup instead of a Domain?

      posted in Feature Request
      L
      LJedi
    • Replication Issues

      For the past couple of weeks, I have been having issues with images replicating to other storage nodes. The Image Replicator logs tells me that “I am the only member, Image Name: Image01, Not syncing Image between group(s)”. In my environment, I have 4 storage nodes and 1 master. None of my 20 images are replicating. I did get them to replicate last week but I did do a capture today and that image is not replicating out to the other nodes. I do not know why this is not working it has work perfectly in the past but I cannot get it to replicate. All are running Trunk 7959. Any help I would greatly appreciate! Thanks!

      posted in FOG Problems
      L
      LJedi
    • Fog Client Disjoin From Domain Feature

      Hi all, I was wondering if in the future the Fog client will be able to disjoin computers from the domain. I think that this will be helpful if computers need to be moved from one location to another or if a disjoin/rejoin will resolve PC issues when a disjoin/rejoin is needed. Thanks.

      posted in Feature Request
      L
      LJedi
    • RE: Change Path For Images Trunk 7025

      Thanks @george1421 and @Sebastian-Roth for your help. For now I did what Sebastain mentioned and moved the images and that worked. George, when I get more time I will review your documentation and see if that is something that I would want to do in the future.

      Once again thanks!

      posted in FOG Problems
      L
      LJedi
    • Change Path For Images Trunk 7025

      I did a clean install Trunk 7025. Issue is that when I installed Trunk, it did not ask me to enter in a path to store images. My issue is that my images are on a ISCSI device and when I mount that ISCSI the path is /images/images.

      Is there a way to tell fog that the path is /images/images and not /images?

      Thanks.

      posted in FOG Problems
      L
      LJedi
    • Snapin Questions

      I am starting to play around with Snapins with Fog. The only thing is, I do not know how it works. While looking at the Wiki and other sources, I cant find a good “How-To” on how the snapins work and best practices. If someone can point me in the right direction, that would be great!

      posted in General
      L
      LJedi
    • RE: Client boot to HD goes to memtest.

      @Sebastian-Roth

      Fog Configuration --> FOG PXE Boot Menu Configuration --> Exit to Hard Drive Type

      Exit to Hard Drive Type was set to SANBOOT. I did change it to EXIT and that seems to fix the issue.

      posted in FOG Problems
      L
      LJedi
    • RE: Client boot to HD goes to memtest.

      I am also seeing this issue. I am running Trunk 5568. I have seen this issue in the past and when I restart the server that normally fixes the issue. After restart, it did not fix the issue. Below is my output on the boot.php. Thanks.

      #!ipxe
      set fog-ip 172.25.8.69
      set fog-webroot fog
      set boot-url http://${fog-ip}/${fog-webroot}
      #!ipxe
      cpuid --ext 29 && set arch x86_64 || set arch i386
      goto get_console
      :console_set
      colour --rgb 0x00567a 1 && colour --rgb 0x00567a 2 && colour --rgb 0x00567a 4 ||
      cpair --foreground 7 --background 2 2 ||
      goto MENU
      :alt_console
      cpair --background 0 1 && cpair --background 1 2 ||
      goto MENU
      :get_console
      console --picture http://172.25.8.69/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
      :MENU
      menu
      colour --rgb 0xff0000 0 ||
      cpair --foreground 1 1 ||
      cpair --foreground 0 3 ||
      cpair --foreground 4 4 ||
      item --gap Host is NOT registered!
      item --gap -- -------------------------------------
      item fog.local Boot from hard disk
      item fog.memtest Run Memtest86+
      item fog.reginput Perform Full Host Registration and Inventory
      item fog.reg Quick Registration and Inventory
      item fog.quickimage Quick Image
      item fog.multijoin Join Multicast Session
      item fog.sysinfo Client System Information (Compatibility)
      choose --default fog.local --timeout 3000 target && goto ${target}
      :fog.local || goto MENU
      :fog.memtest
      kernel memdisk iso raw
      initrd memtest.bin
      boot || goto MENU
      :fog.reginput
      kernel bzImage32 loglevel=4 init=/sbin/init initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=172.25.8.69/fog/ consoleblank=0 loglevel=4 mode=manreg
      imgfetch init_32.xz
      boot || goto MENU
      :fog.reg
      kernel bzImage32 loglevel=4 init=/sbin/init initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=172.25.8.69/fog/ consoleblank=0 loglevel=4 mode=autoreg
      imgfetch init_32.xz
      boot || goto MENU
      :fog.quickimage
      login
      params
      param mac0 ${net0/mac}
      param arch ${arch}
      param username ${username}
      param password ${password}
      param qihost 1
      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
      :fog.multijoin
      login
      params
      param mac0 ${net0/mac}
      param arch ${arch}
      param username ${username}
      param password ${password}
      param sessionJoin 1
      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
      :fog.sysinfo
      kernel bzImage32 loglevel=4 init=/sbin/init initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=172.25.8.69/fog/ consoleblank=0 loglevel=4 mode=sysinfo
      imgfetch init_32.xz
      boot || goto MENU
      :bootme
      chain -ar http://172.25.8.69/fog/service/ipxe/boot.php##params ||
      goto MENU
      autoboot
      

      Edited Formatting

      posted in FOG Problems
      L
      LJedi
    • RE: Trunk 5511 Log Viewer not working

      Updating Fog fixed this issue.

      Thanks,

      posted in Bug Reports
      L
      LJedi
    • Trunk 5511 Log Viewer not working

      After upgrading to trunk 511, log viewer is no longer working. I get the following error message:

      Fatal error: Uncaught exception ‘Exception’ with message ‘No Storage nodes enabled for this group’ in /var/www/html/fog/lib/fog/StorageGroup.class.php:29 Stack trace: #0 /var/www/html/fog/lib/pages/FOGConfigurationPage.class.php(616): StorageGroup->getMasterStorageNode() #1 [internal function]: FOGConfigurationPage->log() #2 /var/www/html/fog/lib/fog/FOGPageManager.class.php(67): call_user_func(Array) #3 /var/www/html/fog/management/index.php(24): FOGPageManager->render() #4 {main} thrown in /var/www/html/fog/lib/fog/StorageGroup.class.php on line 29

      posted in Bug Reports
      L
      LJedi
    • RE: Unable to use log viewer from interface

      I am also seeing this issue too running version 4980. This was working before upgrading.

      posted in FOG Problems
      L
      LJedi
    • RE: Change Fog Server Name

      For the “New Fog Client Service” which is an MSI, going though the MSI for server adress it has it by default as “fog-server” and not the reflected name change. With me changing the server name, will the default name on the MSI change also?

      upload-fbb669b2-8c66-46d2-9f60-348318123f09

      posted in General
      L
      LJedi
    • RE: Change Fog Server Name

      Thanks. After I change the host name of the server and download the new client, will that new client reflect the name change?

      posted in General
      L
      LJedi
    • RE: Change Fog Server Name

      I am using Kubuntu for the server.

      posted in General
      L
      LJedi
    • Change Fog Server Name

      Is there a way to change the fog server name from “fog-server” to a custom name?

      posted in General
      L
      LJedi
    • RE: Git Version 4822 Missing Inventory

      Verified that it is working. Thanks Tom!

      posted in FOG Problems
      L
      LJedi
    • Git Version 4822 Missing Inventory

      Under the Report Management for Full Inventory Export all the computers that are inventory with Fog are missing with the message “No results found”. I do have 10 + computers that are fully inventory with Fog. When I export the CSV file, that too is blank. This was working with a previous version of Fog. Any help would be appreciated. Thanks.

      posted in FOG Problems
      L
      LJedi
    • 1
    • 2
    • 3
    • 3 / 3