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

Including Windows 11 as operating system type

Scheduled Pinned Locked Moved
FOG Problems
4
7
1.2k
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.
  • F
    FGeyer
    last edited by Feb 9, 2023, 8:23 AM

    As my question rises in the head.
    Is it somehow possible to add my own operating systems for the imaging tasks?
    Background:
    We are using fog to deploy customer basic images and downloading specific drivers for every hardware we have and specific preinstall oobe’s for every operating system. So we need to add win11 to the operating system types under images.
    Is this anyhow possible?

    T 1 Reply Last reply Feb 9, 2023, 10:44 AM Reply Quote 0
    • T
      Tom Elliott @FGeyer
      last edited by Feb 9, 2023, 10:44 AM

      @FGeyer While it’s possible to add an OS, is this really a necessity?

      What I mean is the osID does do some actions based on the osID, but my question is it just about a display of Windows 11 as an option?

      FOS (the linux system that performs the actions of imaging) would need to be changed to include the new osID.

      Now, we could change the name of the existing value for Windows 10 to something like Windows 10 and beyond.

      If Windows 11 is absolutely necessary as a separate option (to my current knowledge this isn’t the case) we will work to add it as it’s own defined OS.

      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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

      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
      • F
        FGeyer
        last edited by Feb 9, 2023, 10:52 AM

        @Tom-Elliott This would be just one use case. Yes we want to use the osID for several other things too. For example we have some really exotic SLES installations that we want to treat seperately to normal linux distributions. So we just dont want to go the hacky way, mounting the os partitions and searching for special files so we can identify its a sles installation…

        For the Windows 11 thingie:
        We have very custom postdownload scripts that rely on the hardwarename/osID/ARCH/ stuff so adding own osID’s would make it much easier for us to differ between the Operating systems and unattended files.

        T 1 Reply Last reply Feb 9, 2023, 12:41 PM Reply Quote 0
        • T
          Tom Elliott @FGeyer
          last edited by Feb 9, 2023, 12:41 PM

          @FGeyer So, as I stated, the issue of adding a new operating system type isn’t difficult (from the UI) perspective, it’s all the fos code that relies on it.

          https://github.com/FOGProject/fos/search?q=osID

          Particularly regarding the resize and partition code.

          Modifying this code ultimately isn’t difficult either, but does require a rebuild of the FOS without ultimately adding to the value of the code.

          If, for example, from a base level at least, Windows 11 did things differently from Windows 10, this would likely already have been worked through or being worked on.

          Adding new image types makes sense when the processing of the generic base of FOG is dependent on the OS to be worked. Not as just a means to simplify customized “things”.

          I’m by no means trying to diminish your custom things and the value this could provide, just that this isn’t as simple as just adding an item to the Web side of things and you’re done. It impacts how the imaging system in general actually operates.

          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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

          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
          • F
            FGeyer
            last edited by Feb 9, 2023, 2:30 PM

            This post is deleted!
            1 Reply Last reply Reply Quote 0
            • S
              Sebastian Roth Moderator
              last edited by Feb 10, 2023, 2:24 AM

              @FGeyer @Tom-Elliott FYI we had a pretty similar topic on github a few months ago: https://github.com/FOGProject/fogproject/pull/503

              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
              • [[undefined-on, S Sebastian Roth, Feb 10, 2023, 2:24 AM]]
              • G
                greichelt
                last edited by Sep 6, 2023, 6:52 PM

                @FGeyer

                I know this is an old topic, but it looks like you don’t have a solution. I have this exact problem. It looks like @Tom-Elliott may consider this unnecessary (which may very well be true for other use cases), but for the sake of using @george1421 's awesome driver injection solution, it would be really nice to have. My workaround was to utilize OS type 4 for Windows 11 as I am not using it for anything. I updated the following line in “fog.custominstall”

                case $osid in
                5|6|7|9)

                to

                case $osid in
                4|5|6|7|9)

                Then I updated the following line in “fog.copydrivers”

                case $osid in
                5) osn=“win7” ;;
                6) osn=“win8” ;;
                7) osn=“win8.1” ;;
                9) osn=“win10” ;;

                to

                case $osid in
                4) osn=“win11” ;;
                5) osn=“win7” ;;
                6) osn=“win8” ;;
                7) osn=“win8.1” ;;
                9) osn=“win10” ;;

                Mark you image as OS type 4 and it works as it should. Hope this helps.

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

                302

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project