• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. jayphizzle
    3. Best
    J
    • Profile
    • Following 0
    • Followers 0
    • Topics 8
    • Posts 47
    • Best 5
    • Controversial 0
    • Groups 0

    Best posts made by jayphizzle

    • Endless windows key activation burning OEM keys

      Bug related to https://forums.fogproject.org/topic/6391/endless-windows-key-activation-burning-oem-keys

      @Jbob said:

      v0.9.10 has been released and addresses this issue.

      I updated to v.0.9.11 on a test client today.
      Looking at the log file i found the following lines:

       15.03.2016 11:55 HostnameChanger Checking Product Key Activation
       15.03.2016 11:55 Bus Registering ParseBus in channel Power
       15.03.2016 11:55 Bus Became bus client
       15.03.2016 11:55 Bus Registering OnNotification in channel Notification
       15.03.2016 11:55 Bus Registering OnUpdate in channel Update
       15.03.2016 11:55 HostnameChanger Windows has correct key but is not licensed
       15.03.2016 11:55 WinActivation Installing Product key
       15.03.2016 11:56 Process --> Exit Code = 0
       15.03.2016 11:56 WinActivation Activating Product key
       15.03.2016 11:56 Process --> Exit Code = 0
      

      These steps repeats every few minutes,

      Running slmgr.vbs /dli shows the following status:

      alt text

      Does the following lines in https://github.com/FOGProject/fog-client/blob/master/Modules/HostnameChanger/Windows/WinActivation.cs need to be changed so the german “lizenziert” will be recognized?

       public static bool IsActivated()
              {
                  var info = GetSLMGROutput("/dli");
                  var flattenedInfo = string.Join(" ", info);
      
                  return flattenedInfo.Contains("Licensed");
              }
      

      Suggestion by Quazz:

      @Quazz said:

      Might be safer to have the opposite check (check for unlicensed and only then try to activate rather than check for licensed and try to activate when that doesn’t match) to prevent keys from burning. I think people would prefer their computers not activating because of language issues rather than keys burning.

      posted in Bug Reports
      J
      jayphizzle
    • RE: Endless windows key activation burning OEM keys

      @Quazz said:

      Might be safer to have the opposite check (check for unlicensed and only then try to activate rather than check for licensed and try to activate when that doesn’t match) to prevent keys from burning. I think people would prefer their computers not activating because of language issues rather than keys burning.

      👍

      Can some mod mark the tread as unsolved?
      Or should i open a new thread?

      posted in FOG Problems
      J
      jayphizzle
    • RE: Endless windows key activation burning OEM keys

      @Tom-Elliott said:

      @Jbob I hope this was addressed with the release of 0.9.12, so I’m going to solve the thread for now.

      If this is still a problem please feel free to mark it as unsolved.

      I testet 0.9.12 today. The continuing key activation seems to be fixed.
      But i now have the problem that the activation does not work after reinstalling the system.

      21.03.2016 15:42 HostnameChanger Checking Product Key Activation
      21.03.2016 15:42 HostnameChanger Already activated with correct key
      

      But the host is still in the “30 days trial”

      alt text

      #EDIT#

      Created new thread for new bug.

      posted in Bug Reports
      J
      jayphizzle
    • RE: Migrate Hosts from 1.2 to dev-trunk

      @Sebastian-Roth said:

      The proposed fix is only able to jump in and recognize/modify the values being imported on the fly.

      Ah ok only during the import.
      Why i did not tried this 😒

      I tried it with a few hosts as you recommended - the productkey was successfull decoded from base64 and saved in AES.
      (i did not test ad passwords cause the last hosts where standalone devices)

      Thanks to @Sebastian-Roth and @Tom-Elliott for the quick (bug)fix!

      posted in FOG Problems
      J
      jayphizzle
    • RE: Uninstall FOG-Client (Service) after deploying with Snapin?

      @csieb could you please post/upload your fog logfile.

      posted in FOG Problems
      J
      jayphizzle
    • 1 / 1