none
Cannot install Azure Active Directory Module for Windows PowerShell. MOSSIA is not installed

    Question

  • On my Windows Server 2008 R2, when trying to install Windows Azure Active Directory Module for Windows PowerShell i got the following error message (although Microsoft Online Services Sign-In assistant version 7.0 is installed) 

    "In order to install Windows Azure Active Directory Module for Windows PowerShell, you must have Microsoft Online Services Sign-In Assistant version 7.0 or greater installed on this computer"

     NB : on  a french server  "Pour installer le Module Windows Azure Directory pour windows PowerShell, l'Assistant de connexion de Microsoft Online Service 7.0 ou version ultérieure doit être installé sur cet ordinateur".

    Tried to uninstall/ /repair / ... Microsoft Online Service Sign-In assistant, but not helped....


    Etienne Bailly | SharePoint Consultant | My Blog

    Saturday, June 15, 2013 3:56 PM

Answers

All replies

  • Maybe thats your solution:

    http://community.office365.com/en-us/forums/148/p/169890/497288.aspx#497288

    Somemismatch on dependency check, the Beta-version of the sign-in assistant fixed the problem for me and the guys on the thread.

    Wednesday, June 19, 2013 10:55 AM
  • 

    Dear Freinds, i am also struggling with this problem i have installed the latest suggested BETA from the link but face the same issue.

    I tried this on This is really frustrating as this has become a challenge for me infront of management.

    Please advise possible solutions, how to get module loaded manually in PS or some other better thing.

    Thursday, June 20, 2013 6:44 PM
  • Same issue here on Windows 8.  What's up Microsoft???

    Thursday, June 27, 2013 6:20 PM
  • The workaround solution is to install instead the Microsoft Online Services Sign-In Assistant for IT Professionals BETA

    http://www.microsoft.com/en-us/download/details.aspx?id=39267

    Etienne.


    Etienne Bailly | SharePoint Consultant | My Blog

    • Marked as answer by TitouB Tuesday, July 09, 2013 9:26 AM
    Tuesday, July 09, 2013 9:26 AM
  • Hello all,

    I too experienced same error but JFYI yesterday I've found that applying workaround described below before installing AADM for WinPS (Azure Active Directory Module for Windows PowerShell) indeed worked perfectly.

    Because others might too dislike to use MOS SIA Beta (Microsoft Online Services Sign-In Assistant build 7.250.4551.0) in their production environments, I'm sharing my solution here to provide such alternative while having MOS SIA RTW (Microsoft Online Services Sign-In Assistant v2.1 but build 7.250.4303.0 when installed).

    A) To temporarily change MOS SIA RTW version copy at least 6 lines below inside Notepad and save file as TempVerMOSSIA.reg, then double click it to merge changes into registry, then install AdministrationConfig-xx.msi (which means AdministrationConfig-fr.msi for Etienne, or AdministrationConfig-en.msi for english readers, for me it was  AdministrationConfig-it.msi)

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSOIdentityCRL]
    "MSOIDCRLVersion"="7.250.4551.0"
    "MSOIDCRLVersion_Default"="7.250.4303.0"

    B) To restore original MOS SIA RTW version just copy at least 6 lines below inside Notepad and save file as RevertVerMOSSIA.reg then double click it.

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSOIdentityCRL]
    "MSOIDCRLVersion"="7.250.4303.0"
    "MSOIDCRLVersion_Default"="7.250.4303.0"

    I hope this can help, like it did for me.

    Regards

    Rob


    • Proposed as answer by _RobMer_ Wednesday, August 07, 2013 1:29 AM
    • Edited by _RobMer_ Wednesday, August 07, 2013 1:30 AM corrected a typo
    Wednesday, August 07, 2013 1:29 AM
  • Thanks a lot, it worked for me perfectly.

    J

    Friday, August 23, 2013 3:31 PM
  • The beta fixed MSOL Powershell, but broke Lync my ability to sign in to Lync.
    Tuesday, September 17, 2013 3:21 PM
  • Works like a charm!

    No existen imposibles sino incapaces

    Friday, September 27, 2013 3:36 PM
  • Registry fix worked for me. Thanks for posting it.

    Phil

    Monday, November 18, 2013 1:54 PM
  • So here we are 6 months later.... now I'm on Server 2012R2... are we still having to hack the register or run beta in our production? I'm having the same stupid issue....still

    -SuperDale

    Tuesday, November 26, 2013 5:43 AM
  • The "MSOIDCRLVersion"="7.250.4551.0" hack does work but please? What is this? Microsoft?
    Wednesday, November 27, 2013 5:14 PM
  • Registry fix worked for me. Thanks
    Monday, January 27, 2014 3:45 PM
  • Running Windows2012R2 and not able to make reg. hack work either.  Followed steps above...  Any suggestions?
    Wednesday, February 12, 2014 3:50 PM
  • Wednesday, February 12, 2014 6:14 PM
  • I was through the same pain with Win8 Pro and installed the BETA version of MSOL Sign-in assistant helped.

    On Win7 I don't have this issue and worked with RTW version fine.

    Thursday, February 20, 2014 4:22 AM
  • This is such baloney.  I went through the whole reg hack with the beta version and that resolved the first error message.  Then it said I needed .NET Framework 3.51 SP1 or greater.  When I attempted to install .NET 4 it said I already had that or a higher version on my Win 8.1 PC. Control Panel said it was .NET 1.1 so I uninstalled that rebooted and tried 4 again.  Same message. Then I tried 3.5. That did it.

    Come on Microsoft!  We need these tools to run PowerShell with Office 365.  Why make it so hard?

    Thursday, March 06, 2014 10:33 PM
  • The beta online services sign-in assistant worked for me also.  Server 2008R2.
    Monday, April 07, 2014 4:07 PM
  • it has always been hard, or fraught with issues. I had to fight with my anal admin, whose (correct) policy it is to refuse to install something that says "beta". Almost sabotaged the whole adopt

    What is interesting is the role of the service, it installs.

    Its essentially a credential store, talking to the STS at the outset so apps, like lync or outlook, might NOT need to wait around on the STS. Similarly, powershell app. This has to "evolve" now, with the whole token store concept for native apps, based on JWTs, and offline access when tokens control DRM-ed content.

    I sometimes feel like its old US antitrust issues that PREVENT microsoft from doing things right, here.

    Monday, April 07, 2014 7:21 PM