• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Invalid OS ID (0) (determineOS) Args passed:0

    Scheduled Pinned Locked Moved Solved
    Bug Reports
    4
    5
    759
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      jjacobs
      last edited by

      Hi,

      Today I tried to install our computers using a unicast group deploy (Windows 10).
      When the imaging process starts I’m getting the following error:
      Invalid OS ID (0) (determineOS) Args passed:0
      https://www.dropbox.com/s/p1u6fvyaqqi2iat/IMG_20200827_122259.jpg?dl=0

      When I start the image process manually using the pxe boot menu of when I manually trigger every computer individually in the webinterface everything works fine.

      I’m using: 1.5.9-RC2.11 and bzImage Version: 4.19.123, bzImage32 Version: 4.19.123.

      I tried this on 5 different computers (HP and Dell and came out with the same result).

      How can I fix this issue?

      Kind regards,
      Johan

      george1421G 1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator @jjacobs
        last edited by

        @jjacobs said in Invalid OS ID (0) (determineOS) Args passed:0:

        unicast group deploy (Windows 10).

        This is the first I heard about unicast group deploy. How are you going about this? I’m not saying the feature is not in there, I just never heard of it.

        Looking at your picture, the parameters string is not complete, there is nothing that describes the image you are deploying. There is something surely broken here. The developers will need to know the exact steps you took so they can recreate the error.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        1 Reply Last reply Reply Quote 0
        • C
          Campig
          last edited by

          Had the same issue on 1.5.9-RC2.11, solved it by reverting this fix

          1 Reply Last reply Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by

            @jjacobs @Campig Thanks for reporting and looking into it. Don’t have the time to dig into it just now but will do.

            Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

            Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

            1 Reply Last reply Reply Quote 0
            • S
              Sebastian Roth Moderator
              last edited by

              @jjacobs @Campig Finally found the time to fix and test. It is fixed in the latest dev-branch. For the commit see here.

              Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

              Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

              1 Reply Last reply Reply Quote 0
              • 1 / 1
              • First post
                Last post

              151

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project