Set-SCOMLicense : Requested registry access is not allowed

 

My colleague Kåre has already blogged about how to set the Operations Manager 2012 license, to be read here.

However, I have experienced this command fails – even when running from an elevated Operations Manager Shell – giving error about registry access:

clip_image002

 

Solution:

Instead of spending hours messing up the the security in registry, simply run Windows Powershell as Administrator, and import the Operations Manager module, by using the “Import-Module OperationsManager” cmdlet. When this has been imported, run the Set-SCOMLicense command and you should succeed:

clip_image004

By | 2012-12-11T13:38:37+00:00 December 11th, 2012|Operations Manager (SCOM)|18 Comments

About the Author:

Michael Skov
Yet another guy loving the System Center products. My primary focus is on Operations Manager, which i have worked with for some years now - still loving it.Certifications:Microsoft Certified Solution Expert Private Cloud (MCSE)Microsoft Certified Solutions Associate Windows Server 2008 (MCSA)Microsoft Certified Technology Specialist Windows Server 2008 R2, Server Virtualization

18 Comments

  1. Matt February 7, 2013 at 16:59 - Reply

    Worked like a charm, thanks! 😀

  2. Susantha Silva February 11, 2013 at 11:27 - Reply

    Thanks dude, this really saved me 🙂

  3. Michael Skov February 11, 2013 at 11:39 - Reply

    You’re welcome, glad I could help 🙂

  4. Marlon June 7, 2013 at 23:08 - Reply

    I followed the instructions but for whatever reason it never goes through. It just moves the cursor to the next line after I type Y for yes and hit enter. I’ve left it for hours with no results.

    Please help if you can.

    Thanks,
    Marlon

    • Xavier June 24, 2015 at 19:22 - Reply

      Did you ever figure it out? Im having the same issue.

      • TomC October 6, 2015 at 13:04 - Reply

        I had the same issue with the command freezing. It needs access to the DB not just the registry on the local server. Once the command ran i restarted the local server and it worked. Make sure you know local admin password of the server before you restart if you mess with the time or you might not be able to get on. Once it worked i sorted time again. Made sure time services and hyper-v time services were re-enabled. Hope this helps someone.

  5. Michael Skov
    Michael Skov June 10, 2013 at 12:05 - Reply

    Hi Marlon
    That sounds more like a local Powershell issue. Have you tried running the Powershell as another user? Alternatively, if you have a secondary management server, try running it from there.

    • Xavier June 24, 2015 at 19:21 - Reply

      Im having the same issue Marlon was having, I have followed the administrator powershell and import-module suggestions and same result.

  6. […] Requested registry access is not allowed […]

  7. Binoy Das March 18, 2014 at 16:25 - Reply

    Thank you, it worked perfectly and saved lot of time.

    Thanks,
    Binoy Das

  8. Luke G. December 5, 2014 at 23:26 - Reply

    Perfect! I tried under every account I could think of, and just couldn’t get it to work using the Operations Manager Shell. I wish I’d seen your blog a few hours ago. 🙂

    Thanks!

  9. Donny February 26, 2015 at 21:39 - Reply

    Big Help, thanks for the post. SCOM tries to get you to give up right till the end.

  10. […] found this solution on Michael Skov his blog, which can be found here. Many thanks Michael for sharing this […]

  11. Andy June 5, 2015 at 11:44 - Reply

    Thanks – worked perfectly. I still can’t work out why I can’t launch Ops Mgr Shell as Administrator. That would have been quicker.

  12. Simon September 30, 2015 at 12:27 - Reply

    Thanks that worked first time been trying for hours

  13. Matt Gerber January 17, 2017 at 23:37 - Reply

    THANK YOU! I don’t even know how much time you just saved me.

  14. Eduard January 29, 2017 at 22:24 - Reply

    thank you man. cool solution 🙂

Leave A Comment