remote desktop licensing error with windows server 2008 r2Useful Command-line Commands on WindowsRemote Desktop to Win 2008: Error in License protocolHow to boot other Remote Desktop usersError when connecting to Windows Server 2003 using Remote DesktopRemote Desktop session on Windows Server 2003Remote desktop session ends abruptly with a “protocol error”Windows Remote Desktop protocol errorCorrupted RDP CertificateWhy can't my Remote Desktop Server make proper use of the licensing server?Windows Server 2016 on Azure: “Remote Desktop licensing mode is not configured”

Multi tool use
Multi tool use

What does the behaviour of water on the skin of an aircraft in flight tell us?

Relativistic resistance transformation

Is there a rule that prohibits us from using 2 possessives in a row?

What if you don't bring your credit card or debit for incidentals?

Select row of data if next row contains zero

Asking bank to reduce APR instead of increasing credit limit

Can The Malloreon be read without first reading The Belgariad?

How should I push back against my job assigning "homework"?

Why were the Night's Watch required to be celibate?

How to write a vulnerable moment without it seeming cliche or mushy?

Is there a term for this?

Opposite of "Squeaky wheel gets the grease"

Does Peach's float negate shorthop knockback multipliers?

How can an eldritch abomination hide its true form in public?

Are there mythical creatures in the world of Game of Thrones?

Is having a hidden directory under /etc safe?

Coding Challenge Solution - Good Range

How did the Zip Chip and RocketChip accelerators work for the Apple II?

How do I truncate a csv file?

Rotated Position of Integers

If a massive object like Jupiter flew past the Earth how close would it need to come to pull people off of the surface?

The qvolume of an integer

Modern approach to radio buttons

Why is there a need to modify system call tables in Linux?



remote desktop licensing error with windows server 2008 r2


Useful Command-line Commands on WindowsRemote Desktop to Win 2008: Error in License protocolHow to boot other Remote Desktop usersError when connecting to Windows Server 2003 using Remote DesktopRemote Desktop session on Windows Server 2003Remote desktop session ends abruptly with a “protocol error”Windows Remote Desktop protocol errorCorrupted RDP CertificateWhy can't my Remote Desktop Server make proper use of the licensing server?Windows Server 2016 on Azure: “Remote Desktop licensing mode is not configured”






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








0















we have windows server 2008 R2 installed on our server. we use remote desktop to access it via LAN from 8 -10 client machines (6 different users). While this setup was working correctly for the past year.The following error occurs on SOME of the client machines
"Disconnected due to an error in licensing protocol"
Can I know how to fix this? if there is a problem with licensing why does it occur only on some client machines? (all clients use windows 7)
Thanks.



Never mind. I was able to do it with the following steps:
First delete the registry folder MSLicensing from the client machine.
Next, Run Remote desktop in administrator mode.










share|improve this question













migrated from stackoverflow.com Sep 15 '11 at 7:13


This question came from our site for professional and enthusiast programmers.
























    0















    we have windows server 2008 R2 installed on our server. we use remote desktop to access it via LAN from 8 -10 client machines (6 different users). While this setup was working correctly for the past year.The following error occurs on SOME of the client machines
    "Disconnected due to an error in licensing protocol"
    Can I know how to fix this? if there is a problem with licensing why does it occur only on some client machines? (all clients use windows 7)
    Thanks.



    Never mind. I was able to do it with the following steps:
    First delete the registry folder MSLicensing from the client machine.
    Next, Run Remote desktop in administrator mode.










    share|improve this question













    migrated from stackoverflow.com Sep 15 '11 at 7:13


    This question came from our site for professional and enthusiast programmers.




















      0












      0








      0








      we have windows server 2008 R2 installed on our server. we use remote desktop to access it via LAN from 8 -10 client machines (6 different users). While this setup was working correctly for the past year.The following error occurs on SOME of the client machines
      "Disconnected due to an error in licensing protocol"
      Can I know how to fix this? if there is a problem with licensing why does it occur only on some client machines? (all clients use windows 7)
      Thanks.



      Never mind. I was able to do it with the following steps:
      First delete the registry folder MSLicensing from the client machine.
      Next, Run Remote desktop in administrator mode.










      share|improve this question














      we have windows server 2008 R2 installed on our server. we use remote desktop to access it via LAN from 8 -10 client machines (6 different users). While this setup was working correctly for the past year.The following error occurs on SOME of the client machines
      "Disconnected due to an error in licensing protocol"
      Can I know how to fix this? if there is a problem with licensing why does it occur only on some client machines? (all clients use windows 7)
      Thanks.



      Never mind. I was able to do it with the following steps:
      First delete the registry folder MSLicensing from the client machine.
      Next, Run Remote desktop in administrator mode.







      windows windows-server-2008-r2 remote-desktop






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Sep 15 '11 at 5:54









      Samarth BharadwajSamarth Bharadwaj

      1113




      1113




      migrated from stackoverflow.com Sep 15 '11 at 7:13


      This question came from our site for professional and enthusiast programmers.









      migrated from stackoverflow.com Sep 15 '11 at 7:13


      This question came from our site for professional and enthusiast programmers.






















          2 Answers
          2






          active

          oldest

          votes


















          0














          Never mind. I was able to do it with the following steps:



          • First delete the registry folder MSLicensing from the client machine


          • Next, Run Remote desktop in administrator mode.






          share|improve this answer






























            0














            This problem made by some kind of caching of remote desktop licensing in clients you can solve this by remove the bellow key in registry:



            HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSLicensing


            It's much convenient to make a reg file and run it so .



            1. Make a empty text file

            2. Name it "mypatch.reg" or "mypatch.reg"


            3. Put bellow text in it and save it



               Windows Registry Editor Version 5.00

              [-HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSLicensing]


            4. Run it by dubble click on file!


            It should remove the key.






            share|improve this answer























              Your Answer








              StackExchange.ready(function()
              var channelOptions =
              tags: "".split(" "),
              id: "2"
              ;
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function()
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled)
              StackExchange.using("snippets", function()
              createEditor();
              );

              else
              createEditor();

              );

              function createEditor()
              StackExchange.prepareEditor(
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: true,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: 10,
              bindNavPrevention: true,
              postfix: "",
              imageUploader:
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              ,
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              );



              );













              draft saved

              draft discarded


















              StackExchange.ready(
              function ()
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f311637%2fremote-desktop-licensing-error-with-windows-server-2008-r2%23new-answer', 'question_page');

              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              0














              Never mind. I was able to do it with the following steps:



              • First delete the registry folder MSLicensing from the client machine


              • Next, Run Remote desktop in administrator mode.






              share|improve this answer



























                0














                Never mind. I was able to do it with the following steps:



                • First delete the registry folder MSLicensing from the client machine


                • Next, Run Remote desktop in administrator mode.






                share|improve this answer

























                  0












                  0








                  0







                  Never mind. I was able to do it with the following steps:



                  • First delete the registry folder MSLicensing from the client machine


                  • Next, Run Remote desktop in administrator mode.






                  share|improve this answer













                  Never mind. I was able to do it with the following steps:



                  • First delete the registry folder MSLicensing from the client machine


                  • Next, Run Remote desktop in administrator mode.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Sep 15 '11 at 7:14









                  Samarth BharadwajSamarth Bharadwaj

                  1113




                  1113























                      0














                      This problem made by some kind of caching of remote desktop licensing in clients you can solve this by remove the bellow key in registry:



                      HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSLicensing


                      It's much convenient to make a reg file and run it so .



                      1. Make a empty text file

                      2. Name it "mypatch.reg" or "mypatch.reg"


                      3. Put bellow text in it and save it



                         Windows Registry Editor Version 5.00

                        [-HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSLicensing]


                      4. Run it by dubble click on file!


                      It should remove the key.






                      share|improve this answer



























                        0














                        This problem made by some kind of caching of remote desktop licensing in clients you can solve this by remove the bellow key in registry:



                        HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSLicensing


                        It's much convenient to make a reg file and run it so .



                        1. Make a empty text file

                        2. Name it "mypatch.reg" or "mypatch.reg"


                        3. Put bellow text in it and save it



                           Windows Registry Editor Version 5.00

                          [-HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSLicensing]


                        4. Run it by dubble click on file!


                        It should remove the key.






                        share|improve this answer

























                          0












                          0








                          0







                          This problem made by some kind of caching of remote desktop licensing in clients you can solve this by remove the bellow key in registry:



                          HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSLicensing


                          It's much convenient to make a reg file and run it so .



                          1. Make a empty text file

                          2. Name it "mypatch.reg" or "mypatch.reg"


                          3. Put bellow text in it and save it



                             Windows Registry Editor Version 5.00

                            [-HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSLicensing]


                          4. Run it by dubble click on file!


                          It should remove the key.






                          share|improve this answer













                          This problem made by some kind of caching of remote desktop licensing in clients you can solve this by remove the bellow key in registry:



                          HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSLicensing


                          It's much convenient to make a reg file and run it so .



                          1. Make a empty text file

                          2. Name it "mypatch.reg" or "mypatch.reg"


                          3. Put bellow text in it and save it



                             Windows Registry Editor Version 5.00

                            [-HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSLicensing]


                          4. Run it by dubble click on file!


                          It should remove the key.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Dec 24 '15 at 16:56









                          MSSMSS

                          1313




                          1313



























                              draft saved

                              draft discarded
















































                              Thanks for contributing an answer to Server Fault!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid


                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.

                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function ()
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f311637%2fremote-desktop-licensing-error-with-windows-server-2008-r2%23new-answer', 'question_page');

                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              S20OqMINfhdJ9e4NQ,xubbAm,J6xz8Opm OSUoZu aSC8zB ECLif,7RewKMTT4OLudyoY71x8y2m7aiNBt
                              HMD4bMXgAqHC2ZmmO3sGoTkLZAPdiakvtzDVF6,j6 zg Col6yAN3XON W

                              Popular posts from this blog

                              RemoteApp sporadic failureWindows 2008 RemoteAPP client disconnects within a matter of minutesWhat is the minimum version of RDP supported by Server 2012 RDS?How to configure a Remoteapp server to increase stabilityMicrosoft RemoteApp Active SessionRDWeb TS connection broken for some users post RemoteApp certificate changeRemote Desktop Licensing, RemoteAPPRDS 2012 R2 some users are not able to logon after changed date and time on Connection BrokersWhat happens during Remote Desktop logon, and is there any logging?After installing RDS on WinServer 2016 I still can only connect with two users?RD Connection via RDGW to Session host is not connecting

                              Vilaño, A Laracha Índice Patrimonio | Lugares e parroquias | Véxase tamén | Menú de navegación43°14′52″N 8°36′03″O / 43.24775, -8.60070

                              Cegueira Índice Epidemioloxía | Deficiencia visual | Tipos de cegueira | Principais causas de cegueira | Tratamento | Técnicas de adaptación e axudas | Vida dos cegos | Primeiros auxilios | Crenzas respecto das persoas cegas | Crenzas das persoas cegas | O neno deficiente visual | Aspectos psicolóxicos da cegueira | Notas | Véxase tamén | Menú de navegación54.054.154.436928256blindnessDicionario da Real Academia GalegaPortal das Palabras"International Standards: Visual Standards — Aspects and Ranges of Vision Loss with Emphasis on Population Surveys.""Visual impairment and blindness""Presentan un plan para previr a cegueira"o orixinalACCDV Associació Catalana de Cecs i Disminuïts Visuals - PMFTrachoma"Effect of gene therapy on visual function in Leber's congenital amaurosis"1844137110.1056/NEJMoa0802268Cans guía - os mellores amigos dos cegosArquivadoEscola de cans guía para cegos en Mortágua, PortugalArquivado"Tecnología para ciegos y deficientes visuales. Recopilación de recursos gratuitos en la Red""Colorino""‘COL.diesis’, escuchar los sonidos del color""COL.diesis: Transforming Colour into Melody and Implementing the Result in a Colour Sensor Device"o orixinal"Sistema de desarrollo de sinestesia color-sonido para invidentes utilizando un protocolo de audio""Enseñanza táctil - geometría y color. Juegos didácticos para niños ciegos y videntes""Sistema Constanz"L'ocupació laboral dels cecs a l'Estat espanyol està pràcticament equiparada a la de les persones amb visió, entrevista amb Pedro ZuritaONCE (Organización Nacional de Cegos de España)Prevención da cegueiraDescrición de deficiencias visuais (Disc@pnet)Braillín, un boneco atractivo para calquera neno, con ou sen discapacidade, que permite familiarizarse co sistema de escritura e lectura brailleAxudas Técnicas36838ID00897494007150-90057129528256DOID:1432HP:0000618D001766C10.597.751.941.162C97109C0155020