• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Yanis-Sauve
    3. Topics
    Y
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 5
    • Groups 0

    Topics

    • Y

      Database upgrade

      Watching Ignoring Scheduled Pinned Locked Moved Feature Request
      2
      0 Votes
      2 Posts
      316 Views
      S

      @Yanis-Sauve said:

      I do the server updates, then a git pull each time.

      May I ask which git branch you are on? Run cd .../fogproject ; git branch to find out.

      For the database, do you think it would be possible to systematically display a page about the schema, update or not? I do get that sometimes the schema does not change, but each time I go through the fog install, I ask myself if everything is OK when no update page is displayed.

      While I understand your situation I don’t think we’d want to display the schema update page even though there is no update.

      If you are on dev-branch we might have an easier solution to this. We usually update the minor version number (1.5.7.x) every now and then - usually when bigger changes are pushed to the repo. I might just update this last digit of the version string ever time I push a change to the dev-branch. This way you see if it all worked by looking at the version number in the bottom right corner of the FOG web UI before and after updating.

    • Y

      Server migration - Name changing issues

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      15
      0 Votes
      15 Posts
      3k Views
      Wayne WorkmanW

      A year ago maybe I tried using a snapin to remove the old client and install the new one. I didn’t have any luck, I ended up using the hammer for it (group policy computer based startup script).

    • 1 / 1