PowerShell: Must have Microsoft Online Services Sign-In Assistant

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.


Office 365 and PowerShell

I’ve been getting back into the weeds of Office 365 of late, building out training materials and preparing for certification. It’s been a bit on the geeky-fun side, but not all the time .. there are a lot of moving parts, and not a lot of time to debug (I do have a real job).

That said, Office 365 Wave 15 (released back in February) has added massive functionality to the web-based administration user interface, bits and pieces that make user, group, security and application administration a (relative) breeze. Of course, there are times when a UI isn’t practical:

  • Lots of Users
  • Lots of Groups
  • Lots of Security settings

.. who needs to lather, rinse, repeat (and repeat, and repeat) when dealing in volumes? Well, no one. Of course, there are several customized administrative tasks you perform that you’ll perform multiple times .. suggesting an automated methodology that befits your organization. For that, there’s PowerShell. Windows PowerShell provides:

  • “Cmdlets” for performing common tasks, including access to system-level resources, the Registry, the file system the Windows Management Instrumentation (WMI) interfaces (and more!).
  • Task-based scripting language support for command-line tools.
  • Common syntax and naming conventions, allowing easy flow control between cmdlets: the output from one cmdlet can be used as the input to another cmdlet.
  • An extensible interface allowing for custom tools and utilities.

While someone could devote an entire series of articles on PowerShell (or a career!), I’m focusing more on getting PowerShell to streamline Office 365 administrative tasks. The good news: there are lots of cmdlets to perform common on- and off-premises Office 365 tasks from your IT Administrator workstation, but a bit of setup is required. For starts:

  • Download and install the Office 365 Sign-in Assistant.  Select the 32- or 64-bit version for your workstation.
  • Then, you need the Office 365 cmdlets. Select the 32-bit or 64-bit version for your workstation.
  • Managing Windows Azure Active Directory for your Office 365 installation? PowerShell can help there with the Windows Azure AD PowerShell Module. The best part? The commands therein are included with the Office 365 cmdlets, above.
  • From there, it’s time to do some learning .. here’s where I started:

Some cool recent releases to extend, and make you more productive:

Okay .. all these thoughts captured, it’s back to work for me. Enjoy your foray into PowerShell .. please drop me a note if you see / learn something interesting, or if I may assist.

%d bloggers like this: