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

    New Client --- slmgr /rearm

    Scheduled Pinned Locked Moved
    Feature Request
    2
    2
    1.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.
    • Wayne WorkmanW
      Wayne Workman
      last edited by

      @Jbob @Developers

      If possible, I’d like the ability for the new client to issue the slmgr /rearm command after imaging but before domain joining.

      I was thinking it might be best to put it in FOG as a host setting and put it on the same page as the “join domain” checkbox.

      I’m running into a small issue with KMS licensing. I’m going to do some experimenting when I find the time, but I am thinking these issues can be resolved if I simply reset the CMID on the hosts.

      Specifically, here is my issue: http://blogs.technet.com/b/askcore/archive/2009/10/16/kms-host-client-count-not-increasing-due-to-duplicate-cmid-s.aspx

      But at the moment it’s a non issue because we use the Activation Helper Tool which generates a number of fake license requests to get the KMS minimum numbers up so that the KMS server starts issuing licenses to our actual clients. We are currently using MAKs for Windows activation but we are looking into using a KMS server for this as well and we are coming back to the CMID issue…

      it’s either this or sysprep… and I don’t want to sysprep and feel this feature should be easy to impliment into the new client.

      If it can’t be done, then I will play with the RunOnce registry feature to see if I can rearm clients the very first time they boot and then tell them to reboot. With the FOG Service set to delayed start, there should be ample time to rearm and reboot before the FOG client tries to domain join…

      We’ll see… but I’m hoping the @Developers will pull through for me lol.

      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!
      Daily Clean Installation Results:
      https://fogtesting.fogproject.us/
      FOG Reporting:
      https://fog-external-reporting-results.fogproject.us/

      1 Reply Last reply Reply Quote 0
      • JunkhackerJ
        Junkhacker Developer
        last edited by

        perhaps it’s time for a new version of fogprep
        one that will allow you to selectively do some of the things a sysprep would do for you, but without the parts you don’t want

        signature:
        Junkhacker
        We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

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

        192

        Online

        12.1k

        Users

        17.3k

        Topics

        155.3k

        Posts
        Copyright © 2012-2024 FOG Project