About Me

My photo
TsooRad is a blog for John Weber. John is a Skype for Business MVP (2015-2018) - before that, a Lync Server MVP (2010-2014). My day job is titled "Technical Lead, MS UC" - I work with an awesome group of people at CDW, LLC. I’ve been at this gig in one fashion or another since 1988 - starting with desktops (remember Z-248’s?) and now I am in Portland, Oregon. I focus on collaboration and infrastructure. This means Exchange of all flavors, Skype, LCS/OCS/Lync, Windows, business process, and learning new stuff. I have a variety of interests - some of which may rear their ugly head in this forum. I have a variety of certifications dating back to Novell CNE and working up through the Microsoft MCP stack to MCITP multiple times. FWIW, I am on my third career - ex-USMC, retired US Army. I have a fancy MBA. One of these days, I intend to start teaching. The opinions expressed on this blog are mine and mine alone.

2016/06/30

And in the darkness bind them – O365 PowerShell

A nifty quote, and only partially applicable here, but I have wanted to use that phrase for a long time, so this seemed like a good time.

Office 365, with Azure, MSOnline, Sharepoint, Skype Online, Exchange Online, all of that good stuff.  But managing the various interfaces can be a bit of a challenge. The web interfaces work OK, but for any serious, scaled out work, you will want to leverage PowerShell.  Now, we can do this via individual windows, but they all get jumbled up, and what is what?  And you need how many?  Just ONE won’t do?

Microsoft themselves offers up a TechNet article on how to get all the Office 365 services in a single window…. good luck keeping track of that.  Part of that article also shows the various single window methods.  Even I can figure out that part.  But there must be a better way.  Or perhaps a solution that better matches how I want to work.  As slick as the TechNet guidance is, that just don’t work for me.

Enter Brad Stevens, the Resident Bright Boy (RBB) on my team.  In conversation with him, the idea surfaced of creating a script that would open all the PowerShell requirements at once, label the windows, and possibly even give you the options of opening just what you wanted, yet remain ready to connect to the others.  Keep in mind that this script is his work, not mine.  I can write psuedo-code and create the concept all day long; actually coding the idea into reality is way past my skill set.  But, not his apparently!

A walkthrough

First off, I always run PowerShell as “administrator”  - it just solves so many problems!

image

Set your execution policy.  I always run my laptop in “unrestricted” – which is not the best choice for the uninitiated.  For this RBB script, you will want unrestricted.

image

Then, simply navigate to your script location and call it.  You will want to do [R] Run Once…

image

You will get this handy-dandy pick box to choose your level of functionality, and for entering those all-important credentials.

image

For the purposes of this article, I am going to hit them all, but the SPS window is going to have some red in it as I don’t have SharePoint setup in my tenant…

image

Selecting the “connect” button results in this:

image

You can close the windows individually, work in them all at the same time, etc.  Way better, IMHO, than having only ONE window and I am always having to open another while doing something else.  Why not have them all at once?  And they are cleverly labeled so you can look at the title bar and figure out what you are doing.

Remember that you can select one, like Skype, and then go back an redo things and select Exchange… the interface will stay open for you…

You can get it for yourself

The RBB has now posted the script on his blog so you can enjoy the goodness for yourself.

YMMV

No comments:

What Vacation Taught me

I took vacation this year; a formal thing with travel, schedule coordination, planned activities, and days full of interacting with others. ...