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

FOG 1.5.0 RC 13 and FOG Client v0.11.14 Released

Scheduled Pinned Locked Moved
Announcements
8
12
2.3k
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
    falko Moderator
    last edited by falko Feb 14, 2018, 4:49 PM Feb 14, 2018, 10:48 PM

    Tom, just upgraded (switched from working to dev) and the FOG_CLIENT_VERSION is still defined as 0.11.13 in system.class.php

    T 1 Reply Last reply Feb 14, 2018, 11:30 PM Reply Quote 0
    • T
      Tom Elliott @falko
      last edited by Feb 14, 2018, 11:30 PM

      @falko Fixed, please just repull. The binaries are updated already, just missed this one piece sorry.

      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

      F 1 Reply Last reply Feb 14, 2018, 11:34 PM Reply Quote 0
      • F
        falko Moderator @Tom Elliott
        last edited by Feb 14, 2018, 11:34 PM

        @tom-elliott cool, not sure if it’s just me/my setup but since moving to rc12/13 the server UI seems more responsive πŸ™‚

        1 Reply Last reply Reply Quote 0
        • F
          Foglalt
          last edited by Feb 22, 2018, 3:10 PM

          Hi!

          Are we coming close to stable release? Or is it far, needs more time to polish? πŸ™‚

          G 1 Reply Last reply Feb 22, 2018, 9:43 PM Reply Quote 0
          • X
            x23piracy
            last edited by Feb 22, 2018, 3:21 PM

            It’s a long way to 2.0 πŸ˜‰

            β•‘β–Œβ•‘β–ˆβ•‘β–Œβ”‚β•‘β–Œβ•‘β–Œβ–ˆ

            1 Reply Last reply Reply Quote 1
            • G
              george1421 Moderator @Foglalt
              last edited by Feb 22, 2018, 9:43 PM

              @foglalt Understand this is all subject to change, but I think the plan was RC13 to be the last before 1.5.0 stable was pushed out in a couple of weeks. Internal changes in Windows 10 1709 has caused unexpected delays with 1.5.0 being finalized. GUI performance improvements were pulled from 1.5.0 and moved into the 1.6.0 branch which should be released in the first half of 2018 (maybe).

              Fog 2.0 IS a bit out there yet. The devs have said that they are seeing some pretty impressive deployment speeds with the pre-alpha code.

              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 Feb 22, 2018, 11:19 PM Reply Quote 1
              • ?
                A Former User @george1421
                last edited by Feb 22, 2018, 11:19 PM

                @george1421 Just curious: what changed in 1709? Something related to partitioning?

                G 1 Reply Last reply Feb 22, 2018, 11:28 PM Reply Quote 0
                • G
                  george1421 Moderator @A Former User
                  last edited by Feb 22, 2018, 11:28 PM

                  @loosus456 They (M$) did something with disk structure, as well as other numerous changes under the hood. Some changes caused several rounds of rework to the fog client. I don’t have specifics, but based on some of the threads we’ve seen the issues started with 1709. I’d have to go back through the change log to pin point the fixes specifically related to 1709.

                  I think one from my testing was I had to move starting of the fog client from the setupcomplete.cmd to a first login step in the unattend.xml because the windows was doing some additional things after the setupcomplete.cmd. If the fog client was started too early (in the setupcomplete.cmd) I would end up with a botched install. This is different than all of the win10 releases before.

                  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 Feb 24, 2018, 5:47 PM Reply Quote 0
                  • ?
                    A Former User @george1421
                    last edited by Feb 24, 2018, 5:47 PM

                    @george1421 Are you talking more about the client than simply deploying an image? Will 1709, without the client, still deploy just fine with the current stable version of FOG?

                    In regards to the other stuff: yeah, there are several bugs related to SetupComplete.cmd and cleanup of defaultuser0 in 1709. Some of the issues were (apparently) fixed in the January cumulative updates, but I know of at least one person who continued to have related issues even with the update applied.

                    SCCM administrators are having the exact same issues, mostly with Task Sequences, which use some of the same mechanisms to work.

                    1 Reply Last reply Reply Quote 0
                    • M
                      MRCUR Testers
                      last edited by Feb 24, 2018, 6:26 PM

                      This is my first time using the new UI - wow! Huge upgrade.

                      1 Reply Last reply Reply Quote 0
                      • J
                        Joe Schmitt Senior Developer
                        last edited by Joe Schmitt Feb 24, 2018, 12:49 PM Feb 24, 2018, 6:48 PM

                        @loosus456 Deploying works fine, and the client issues that were present, should be all (or mostly) fixed with v0.11.14.

                        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.

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

                        258

                        Online

                        12.0k

                        Users

                        17.3k

                        Topics

                        155.2k

                        Posts
                        Copyright Β© 2012-2024 FOG Project