• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. lperoma
    3. Topics
    L
    • Profile
    • Following 0
    • Followers 0
    • Topics 9
    • Posts 40
    • Best 3
    • Controversial 0
    • Groups 0

    Topics created by lperoma

    • L

      Solved Update to working-1.6 fails with mysql: unrecognized service

      Linux Problems
      • • • lperoma
      6
      0
      Votes
      6
      Posts
      321
      Views

      L

      @Tom-Elliott Success. I switched to single-user with init 1, and installing systemd-sysv worked fine.

      As this is a machine upgraded from debian 11, maybe it wasn’t using systemd. Installation of 1.6 worked no problem Thanks,

    • L

      Solved Attempting to join domain: The parameter is incorrect, code = 87

      FOG Problems
      • • • lperoma
      2
      0
      Votes
      2
      Posts
      147
      Views

      L

      This worked for me :

      Domain name: subdomain.domain.tld
      OU: OU=Computers,DC=SUBDOMAIN,DC=DOMAIN,DC=TLD
      AD DEFAULT USER: adminuser
      Domain Password: supersecret
      Name Change/AD Join Forced reboot?: cheked

      Not sure if I was doing anything wrong, I tried too many things, but this now works. Thanks.

    • L

      Solved Could not mount /dev/sda3: Metadata kept in Windows cache, refused to mount.

      FOG Problems
      • • • lperoma
      4
      0
      Votes
      4
      Posts
      211
      Views

      L

      @george1421 This is correct. It works fine. Thanks,

    • L

      Solved Chainloading failed, hit 's' for the iPXE shell

      FOG Problems
      • • • lperoma
      10
      0
      Votes
      10
      Posts
      539
      Views

      L

      I have the impression this issue has something to do with DHCP server in the gateway competing with proxydhcp in the fog server.

      I have updated DHCP settings in Unifi to allow / block DHCP traffic (DHCP Guarding). I have included FOG’s dhcppxory address and seems to be working ok now.

    • L

      Solved PXE Boot Error - "Kernel Panic" Issue "XZ decompressor ran out of memory"

      FOG Problems
      • • • lperoma
      19
      0
      Votes
      19
      Posts
      1.3k
      Views

      P

      I was able to find a work around after running into this issue. In FOG Settings under TFTP Server update the “TFTP PXE KERNAL 32” to bzImage and “PXE BOOT IMAGE” to init.xz. I was able get thing working after that.

      53e33ef4-25c1-496f-85c4-e3ff864a9aeb-image.png

    • L

      Solved KMV installation can not locate images folder upon image deploy or capture.

      FOG Problems
      • • • lperoma
      11
      0
      Votes
      11
      Posts
      701
      Views

      S

      @lperoma Thanks for the update. Good to hear you found this and were able to fix it. Well done! This is beyond FOG itself and it would have taken a lot of posting forth and back to figure this out for us. Although I don’t know much about virtiofs I can imagine it causing problems when being exported as NFS (as FOG does).

    • L

      Fog migration

      FOG Problems
      • • • lperoma
      3
      0
      Votes
      3
      Posts
      259
      Views

      L

      @sebastian-roth Thanks Sebastian! That solved all issues!

    • L

      Solved Adobe Acrobat Reader snapin not working

      Windows Problems
      • • • lperoma
      6
      0
      Votes
      6
      Posts
      1.1k
      Views

      george1421G

      @astrugatch said in Adobe Acrobat Reader snapin not working:

      If I recall correctly the Acrobat exe installer has an MSI baked inside of it.

      There is two ways to grab the MSI.

      7zip will sometimes open self extracting installers so you can grab the contents. Launch the .exe program but stop at the eula, possibly one later question. Then go to your temp directory The contents of the installer should be in a guid named directory in your temp. The alternate location might be in ProgramData\adobe path.
    • L

      Solved Snapin Update Fail after upgrading to 1.5.7

      FOG Problems
      • • • lperoma
      6
      0
      Votes
      6
      Posts
      552
      Views

      S

      @lperoma The grep error can be ignored.

    • 1 / 1