No announcement yet.

Point machine to internal KMS Server

  • Filter
  • Time
  • Show
Clear All
new posts

  • Point machine to internal KMS Server

    Good day all..

    I have a machine that is part of our domain, but because it is located outside of our offices, it uses an external DNS server provided by an ISP. The problem I am having is getting it to activate via our internal KMS server. Any suggestions on how I might accomplish this? TIA..

  • #2
    Re: Point machine to internal KMS Server

    Set up a VPN?
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    IT Trainer / Consultant
    Ossian Ltd

    ** Remember to give credit where credit is due and leave reputation points where appropriate **


    • #3
      Re: Point machine to internal KMS Server

      I beleive that these hosts only need to communicate with the KMS server at least once every six months. If this machine is that disconnected, is there a point to having it on the domain?

      In regards to maintaining its activation, can you simply use MAK (multiple activation key) for this computer?

      If you have several machines that are in this situation, the VPN recommendation would work best so that you can mitigate the KMS issue as well as any other challanges you may be having with the proper management of this domain joined computer (patch management, configuration management, etc...).
      buy vaporizers
      Last edited by [JM]; 24th January 2011, 18:10.
      JM @ IT Training & Consulting


      • #4
        Re: Point machine to internal KMS Server

        Thanks for the inital ideas.. Would it be possible to specify locally on the machine what my licensing servers IP/port info are..possibly a modification to the host file?

        @JM .. You are correct, our patching, troubleshooting and a few other key componenets are needed which is why they are part of the domain instead of stand alone.

        Thanks again for the assistance..


        • #5
          Re: Point machine to internal KMS Server

          Exposing your KMS servers to the internet is not a really good idea. The internet could use your KMS server to activate licenses.
          Assuming you make use of windows 7/2008R2, you could setup DirectAccess.

          MCITP sa, ea & va, [email protected]


          • #6
            Re: Point machine to internal KMS Server

            DirectAccess requires more then just windows 2008 or Windows7.
            You also need ipv6, pki an IMHO TMG or UAG or you need a passthrough to an onther machine. Even with TMG it is a bit of a hassle.

            The easiest solution is already being pointed out by Tom. Setup VPN, either client VPN or site-to-site VPN.
            Depending on the firewall you have, you might also think about SSL VPN
            Technical Consultant

            MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
            "No matter how secure, there is always the human factor."

            "Enjoy life today, tomorrow may never come."
            "If you're going through hell, keep going. ~Winston Churchill"