how to fix a corrupted rds licenses database?












0















The problem



A license database for remote desktop in Windows 2012 got corrupted as helpdesk executes several times an script in powershell used to install licenses for Windows 2008 R2 and then for Windows 2012



The troubleshooting



Reviewing the licenses installed on the system, several entries were found some for Windows 2012 and others for Windows 2008.



We tried the following procedures in order to delete the licenses:



Removing and adding back the RDS role - nothing happened, as soon as the role was installed, the same corrupted database emerged



Rebuilding database - we tried all options... nothing happened



Executing some PS commands - nothing happened



More googling... basically the same commands as in the previous link - nothing happened










share|improve this question



























    0















    The problem



    A license database for remote desktop in Windows 2012 got corrupted as helpdesk executes several times an script in powershell used to install licenses for Windows 2008 R2 and then for Windows 2012



    The troubleshooting



    Reviewing the licenses installed on the system, several entries were found some for Windows 2012 and others for Windows 2008.



    We tried the following procedures in order to delete the licenses:



    Removing and adding back the RDS role - nothing happened, as soon as the role was installed, the same corrupted database emerged



    Rebuilding database - we tried all options... nothing happened



    Executing some PS commands - nothing happened



    More googling... basically the same commands as in the previous link - nothing happened










    share|improve this question

























      0












      0








      0








      The problem



      A license database for remote desktop in Windows 2012 got corrupted as helpdesk executes several times an script in powershell used to install licenses for Windows 2008 R2 and then for Windows 2012



      The troubleshooting



      Reviewing the licenses installed on the system, several entries were found some for Windows 2012 and others for Windows 2008.



      We tried the following procedures in order to delete the licenses:



      Removing and adding back the RDS role - nothing happened, as soon as the role was installed, the same corrupted database emerged



      Rebuilding database - we tried all options... nothing happened



      Executing some PS commands - nothing happened



      More googling... basically the same commands as in the previous link - nothing happened










      share|improve this question














      The problem



      A license database for remote desktop in Windows 2012 got corrupted as helpdesk executes several times an script in powershell used to install licenses for Windows 2008 R2 and then for Windows 2012



      The troubleshooting



      Reviewing the licenses installed on the system, several entries were found some for Windows 2012 and others for Windows 2008.



      We tried the following procedures in order to delete the licenses:



      Removing and adding back the RDS role - nothing happened, as soon as the role was installed, the same corrupted database emerged



      Rebuilding database - we tried all options... nothing happened



      Executing some PS commands - nothing happened



      More googling... basically the same commands as in the previous link - nothing happened







      remote-desktop terminal-services rds






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 18 '16 at 16:53









      Jonathan PérezJonathan Pérez

      3626




      3626






















          1 Answer
          1






          active

          oldest

          votes


















          0














          The answer



          After several spent time we were able to recreate the database doing the following:



          1.- Remove the RDS role



          2.- Delete or rename the folder C:WindowsSystem32LServer (this is where the database file lives)



          3.- Install the RDS role - the LServer folder will be created from the scratch so no license will be there



          Extra



          4.- Just in case, enable the feature RD Connection Broker if the server is intended for supporting several connections



          I hope this helps anyone out there






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            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%2fsuperuser.com%2fquestions%2f1028042%2fhow-to-fix-a-corrupted-rds-licenses-database%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            The answer



            After several spent time we were able to recreate the database doing the following:



            1.- Remove the RDS role



            2.- Delete or rename the folder C:WindowsSystem32LServer (this is where the database file lives)



            3.- Install the RDS role - the LServer folder will be created from the scratch so no license will be there



            Extra



            4.- Just in case, enable the feature RD Connection Broker if the server is intended for supporting several connections



            I hope this helps anyone out there






            share|improve this answer




























              0














              The answer



              After several spent time we were able to recreate the database doing the following:



              1.- Remove the RDS role



              2.- Delete or rename the folder C:WindowsSystem32LServer (this is where the database file lives)



              3.- Install the RDS role - the LServer folder will be created from the scratch so no license will be there



              Extra



              4.- Just in case, enable the feature RD Connection Broker if the server is intended for supporting several connections



              I hope this helps anyone out there






              share|improve this answer


























                0












                0








                0







                The answer



                After several spent time we were able to recreate the database doing the following:



                1.- Remove the RDS role



                2.- Delete or rename the folder C:WindowsSystem32LServer (this is where the database file lives)



                3.- Install the RDS role - the LServer folder will be created from the scratch so no license will be there



                Extra



                4.- Just in case, enable the feature RD Connection Broker if the server is intended for supporting several connections



                I hope this helps anyone out there






                share|improve this answer













                The answer



                After several spent time we were able to recreate the database doing the following:



                1.- Remove the RDS role



                2.- Delete or rename the folder C:WindowsSystem32LServer (this is where the database file lives)



                3.- Install the RDS role - the LServer folder will be created from the scratch so no license will be there



                Extra



                4.- Just in case, enable the feature RD Connection Broker if the server is intended for supporting several connections



                I hope this helps anyone out there







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 18 '16 at 16:53









                Jonathan PérezJonathan Pérez

                3626




                3626






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • 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%2fsuperuser.com%2fquestions%2f1028042%2fhow-to-fix-a-corrupted-rds-licenses-database%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







                    Popular posts from this blog

                    "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

                    Alcedinidae

                    Origin of the phrase “under your belt”?