PowerShell: Must have Microsoft Online Services Sign-In Assistant

September 15, 2013 Leave a comment

I posted “Office 365 and PowerShell” a few weeks back and since then have been digging into the various ways PowerShell helps manage Office 365 installations. You’ll find a robust command set that can automate a wide number of deployment and management operations.

Setup (was) pretty straightforward the last time I did it (a few months back): download and install the Microsoft Online Services Sign-In Assistant for IT Professionals Beta and the appropriate cmdlets (please see my prior article) and you’re ready to go.

Now, I’ve rebuilt my system since then, so it’s time to do it over again. However, this time, I had mixed results. I installed the RTW version of the Online Services Assistant with a reboot. Then, I ran the installation program for the cmdlets .. then I got this:

“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”

Huh? :: mutter ::  Didn’t I just do that?

So, after a lot of uninstalls, reinstalls, reboots and more reinstalls, I ascertained there is a system check between the Beta and RTW bits that is failing. Some Bing-ing, Google-ing and swear-ing .. I came across a social post on MSDN: “Cannot install Azure Active Directory Module for Windows PowerShell. MOSSIA is not installed”, installing the Beta and then the RTW, but with an added registry fix that increases one parameter to the later version to satisfy the system check.

The fix seems to work, and the author of the post provided two .reg files: one to make the change and the other to undo it. My suggestion (as Microsoft will certainly distribute newer versions) is to perform the Beta and RTW installs, then export the registry settings so you can revert, just in case.

HTH.

Filed under Architecture, Cloud, Office 365

About Michael Coates
I am a pragmatic evangelist. The products, services and solutions I write about fulfill real-world expectations and use cases. I stay up-to-date on real products I use and review, and share my thoughts here. I apply the same lens when designing an architecture, product or when writing papers. I am always looking for ways that technology can create or enhance a business opportunity .. not just technology for technology's sake. My CV says: Seasoned technology executive, leveraging years of experience with enterprise and integration architectural patterns, executed with healthy doses of business acumen and pragmatism. That's me. My web site says: Technology innovations provide a myriad of opportunities for businesses. That said, having the "latest and greatest" for its own sake isn't always a recipe for success. Business successes gained through exploiting innovation relies on analysis of how the new features will enhance your business followed by effective implementation. Goals vary far and wide: streamlining operations, improving customer experience, extending brand, and many more. In all cases, you must identify and collect the metrics you can apply to measure your success. Analysis must be holistic and balanced: business and operational needs must be considered when capitalizing on a new technology asset or opportunity.

Leave a comment