• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. abos_systemax
    3. Topics
    A
    • Profile
    • Following 0
    • Followers 0
    • Topics 19
    • Posts 132
    • Best 4
    • Controversial 0
    • Groups 0

    Topics created by abos_systemax

    • A

      Unsolved FOG - Listen on two NICS

      FOG Problems
      • • • abos_systemax
      7
      0
      Votes
      7
      Posts
      1.2k
      Views

      Tom ElliottT

      @Fimlore Yes, only changing the “IP” to point at the relevant VLan’s. I’m sure there’s more stuff that would need to be worked out of course, but at least you can see it can be worked out. And I’m typically just a message away.

    • A

      Solved Remove a Registry Key

      Windows Problems
      • • • abos_systemax
      23
      0
      Votes
      23
      Posts
      5.2k
      Views

      george1421G

      @maouu Here is how we deploy with PDQ Deploy (sorry I don’t use snapins but the install function is similar:

      @Echo Off start /wait dfmirage-setup-2.0.301.exe /verysilent /norestart REM Hack to determine arch of this system IF EXIST C:\Windows\SysWOW64\diskpart.exe GOTO :x64 :x86 msiexec /i tightvnc-2.7.10-setup-32bit.msi /qn /norestart ADDLOCAL="Server" SERVER_REGISTER_AS_SERVICE=1 SERVER_ADD_FIREWALL_EXCEPTION=1 SERVER_ALLOW_SAS=1 SET_USEVNCAUTHENTICATION=1 VALUE_OF_USEVNCAUTHENTICATION=1 SET_PASSWORD=1 VALUE_OF_PASSWORD=<SetMe!!> SET_USECONTROLAUTHENTICATION=1 VALUE_OF_USECONTROLAUTHENTICATION=1 SET_CONTROLPASSWORD=1 VALUE_OF_CONTROLPASSWORD=<SetMe2!!> SET_IPACCESSCONTROL=1 VALUE_OF_IPACCESSCONTROL="192.168.0.0-192.168.255.255:2,0.0.0.0-192.167.255.255:1,192.169.0.0-255.255.255.255:1" SET_REMOVEWALLPAPER=1 VALUE_OF_REMOVEWALLPAPER=1 :x64 msiexec /i tightvnc-2.7.10-setup-64bit.msi /qn /norestart ADDLOCAL="Server" SERVER_REGISTER_AS_SERVICE=1 SERVER_ADD_FIREWALL_EXCEPTION=1 SERVER_ALLOW_SAS=1 SET_USEVNCAUTHENTICATION=1 VALUE_OF_USEVNCAUTHENTICATION=1 SET_PASSWORD=1 VALUE_OF_PASSWORD=<SetMe!!> SET_USECONTROLAUTHENTICATION=1 VALUE_OF_USECONTROLAUTHENTICATION=1 SET_CONTROLPASSWORD=1 VALUE_OF_CONTROLPASSWORD=<SetMe2!!> SET_IPACCESSCONTROL=1 VALUE_OF_IPACCESSCONTROL="192.168.0.0-192.168.255.255:2,0.0.0.0-192.167.255.255:1,192.169.0.0-255.255.255.255:1" SET_REMOVEWALLPAPER=1 VALUE_OF_REMOVEWALLPAPER=1 :Exit REM Install done, errors generated by msi will be reported to installer net stop "TightVNC Server" net start "TightVNC Server" rmdir /s /q "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\TightVNC\"

      I’m pretty sure if you reinstall with the new parameters they will overwrite what is in the registry. I know this ISN’T what you are looking for, but it works for us.

    • A

      Solved Could not boot: No such device

      FOG Problems
      • • • abos_systemax
      22
      0
      Votes
      22
      Posts
      6.7k
      Views

      A

      @george1421 Bookmarked!

    • A

      Solved Question Regarding IPXE Boot Sequence

      FOG Problems
      • • • abos_systemax
      10
      0
      Votes
      10
      Posts
      3.5k
      Views

      Wayne WorkmanW

      @abos_systemax #wiki worthy

    • A

      Solved NFS volume failed to mount

      FOG Problems
      • • • abos_systemax
      24
      0
      Votes
      24
      Posts
      4.3k
      Views

      A

      @Wayne-Workman I will. I did not pay much attention to it because I assumed that I installed 1.3… but during our Q&A, i slowly realized that there might be an issue with my initial install, especially when I noticed that the FOG client that loaded was 1.2, not 1.3 (but that skips so darn fast that I noticed only after 3 reboots…)

    • A

      XenServer and FOG

      General
      • • • abos_systemax
      6
      0
      Votes
      6
      Posts
      2.0k
      Views

      F

      Well we have run FOG on xen (it is not the Citix xenserver product) for years. Currently on 1.2 but just today made a copy of the VM to upgrade to 1.3 (We need Vista and to a lesser degree XP). We use it to process old PCs going out the door, DBAN wipe, Bios updates, asset tag removal, and imaging with the OEM OS. We have probably processed over 5,000 PCs (and some Macs, different story) over the years.

      Do you have specific questions or just researching?

    • A

      Solved Windows partition size

      Windows Problems
      • • • abos_systemax
      2
      0
      Votes
      2
      Posts
      800
      Views

      A

      I solved it… I restored the partition again but now with the option ‘Single Disk - Resizeable’ … now the partition shows up as it should.

    • A

      Solved Fatclone.C: Filesystem isn't in a valid state

      FOG Problems
      • • • abos_systemax
      23
      0
      Votes
      23
      Posts
      7.7k
      Views

      A

      @abos_systemax said in Fatclone.C: Filesystem isn't in a valid state:

      @Wayne-Workman

      I kind-a-fixed it by booting to Windows PE, clean the disk with diskpart, create a 100MB parititon and a ‘the rest’ partition; then restoring only partition 2 with FOG, then rebooting to Windows PE to create a bootstore… now Windows can Boot.

      I now face another issue, but I’ve posted that in the Windows Issues forums (https://forums.fogproject.org/topic/9177/windows-partition-size)

      — fixed that issue as well…

    • A

      Solved FOG - boot to FOS - rcu_sched self-detected stall on CPU

      FOG Problems
      • • • abos_systemax
      27
      0
      Votes
      27
      Posts
      7.0k
      Views

      Wayne WorkmanW

      @abos_systemax said in FOG - boot to FOS - rcu_sched self-detected stall on CPU:

      I assumed that it used bzImage for UEFI because UEFI doesn’t really support x32?

      It does. There aren’t a lot of UEFI systems that are 32 bit, but they are out there.

      Are you using the boot files that come with fog and are you serving them from the FOG Server? Could these files be obsolete or are you shuffling things around? I only ask because the filename you give in your dhcpd.conf file is not where that file actually is located on a 1.3.0 RC fog server by default.

      At any rate, if you’re serving these boot files from a FOG server on 1.3.0 RC, the PXEClient:Arch:00006 filename should instead be: filename "i386-efi/ipxe.efi";

      Also, if you wanted, you could simply replace all of your classes in your dhcpd.conf file with these (standard FOG isc-dhcp classes):

      class "UEFI-32-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006"; filename "i386-efi/ipxe.efi"; } class "UEFI-32-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002"; filename "i386-efi/ipxe.efi"; } class "UEFI-64-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007"; filename "ipxe.efi"; } class "UEFI-64-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008"; filename "ipxe.efi"; } class "UEFI-64-3" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009"; filename "ipxe.efi"; } class "Legacy" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000"; filename "undionly.kkpxe"; } class "SURFACE-Pro-4" { match if substring(option vendor-class-identifier, 0, 32) = "PXEClient:Arch:00007:UNDI:003016"; filename "ipxe7156.efi"; } class "Apple-Intel-Netboot" { match if substring (option vendor-class-identifier, 0, 14) = "AAPLBSDPC/i386"; option dhcp-parameter-request-list 1,3,17,43,60; if (option dhcp-message-type = 8) { option vendor-class-identifier "AAPLBSDPC"; if (substring(option vendor-encapsulated-options, 0, 3) = 01:01:01) { # BSDP List option vendor-encapsulated-options 01:01:01:04:02:80:00:07:04:81:00:05:2a:09:0D:81:00:05:2a:08:69:50:58:45:2d:46:4f:47; } elsif (substring(option vendor-encapsulated-options, 0, 3) = 01:01:02) { # BSDP Select option vendor-encapsulated-options 01:01:02:08:04:81:00:05:2a:82:0a:4e:65:74:42:6f:6f:74:30:30:31; filename "ipxe.efi"; next-server x.x.x.x; } }
    • A

      Unsolved IPXE error 0x7f048283 on Lenovo m700

      FOG Problems
      • • • abos_systemax
      5
      0
      Votes
      5
      Posts
      1.9k
      Views

      Wayne WorkmanW

      @abos_systemax said in IPXE error 0x7f048283 on Lenovo m700:

      we are not allowed to update the firmware because it is not our own hardware.

      If it were me, I’d do it anyways on just one to see. It’s easier to beg for forgiveness than ask for permission. It’s afterall the manufacturer’s firmware update. The update can not come from anywhere else literally, and 99% of the time firmware updates fix problems.

    • A

      Is it possible to image a client from USB, without the FOG server?

      General Problems
      • • • abos_systemax
      8
      0
      Votes
      8
      Posts
      3.5k
      Views

      A

      @utopia Thanks for your ‘essay’ (reply). I tried the other way around not very long ago (a ConeZilla image to FOG) but that did not work out very well and I ended up restoring the CZ image to a device and capturing in with FOG so I don’t think that FOG and CZ are interoparable yet.

      I will likely use your method to provision our engineer at the location, thank you.

    • A

      Quick Registration --> Return to iPXE boot menu instead of reboot

      Feature Request
      • • • abos_systemax
      8
      0
      Votes
      8
      Posts
      2.3k
      Views

      A

      @Tom-Elliott Thanks for that reply.
      I am only (really) interested in the Serial/MAC address combination of the devices that I boot, so I’ll develop a bootmenu.php that posts these values to my own database and waits for the user to create a multicast task then.

      Is it possible to remove the auto reboot feature however? (replace it with a … press any key to continue), that way the engineer can still quick register, but doesnt need to be present (and thus can move on to start/register different machines)

    • A

      Solved Multicast Session on wrong eth-port

      Bug Reports
      • • • abos_systemax
      17
      0
      Votes
      17
      Posts
      3.5k
      Views

      D

      @Tom-Elliott Yes, it is working now.
      Thanks,

    • A

      Solved Groups can no longer hold more than one member (Trunk 7825)

      FOG Problems
      • • • abos_systemax
      3
      0
      Votes
      3
      Posts
      680
      Views

      A

      Thanks. this seems to be my case

    • A

      unable to boot HP z240 in UEFI

      Hardware Compatibility
      • • • abos_systemax
      38
      0
      Votes
      38
      Posts
      25.9k
      Views

      george1421G

      @csurepair You should really start your own thread because the conditions could be different.

      Things that we would need to know is the version of FOG you have installed (on or about the cloud on the management home page).

      What is your dhcp server?

      Is the HP in uefi or bios (legacy) mode?

      Since you are getting to the download of bzImage, it probably safe to assume you have the correct iPXE kernel loaded into dhcp option 67.

      Are you using dnsmasq in your environment?

    • A

      Solved shutdown after image with postdownloadscripts

      FOG Problems
      • • • abos_systemax
      7
      0
      Votes
      7
      Posts
      2.0k
      Views

      S

      Tom is absolutely right about shutdown before the job actually finishes is not a good idea.

      But just in case people want to do other things in the postdownloadscript and run into the same “command is unknown” issue. My guess is that the PATH environment is not properly set within the scripts. So you’d need to call /sbin/shutdown to make it work…

    • A

      Trigger a script directly after partclone that requests input and copies a folder

      FOG Problems
      • • • abos_systemax
      30
      0
      Votes
      30
      Posts
      7.8k
      Views

      JunkhackerJ

      just to give you some more information to work with, in addition to the “hosts” table, there is also the associated “inventory” table that contains hardware information about all registered hosts, including the serial number

    • A

      Solved FOG trunk upgrade - Image upload fails

      FOG Problems
      • • • abos_systemax
      8
      0
      Votes
      8
      Posts
      1.9k
      Views

      S

      @george1421 Thanks for testing and letting us know. Seams to work with the latest trunk so I am marking this solved now. Please let us know if you feel images are not moved properly (please check FTP first!).

    • A

      Solved Chaining FOG from ipxe.efi (x64)

      FOG Problems
      • • • abos_systemax
      21
      0
      Votes
      21
      Posts
      9.9k
      Views

      S

      @abos_systemax said:

      I believe you, but theory and practice are different beasts 🙂

      Sure they are! That’s why I suggested to give FOG trunk a try! Kernel 3.19.3 might boot some of your UEFI machines but will fail with those having more recent NICs! This is not just a theory. We have seen different people posting about those issues several times a week in the last months!

    • 1 / 1