The venerable Exchange Get-MailboxStatistics has been around for over ten years, but now it’s telling lies about Office 365 users. Well, just the last login date to their mailbox. The problem is that the world is a very different place to when Microsoft first introduced PowerShell in Exchange 2007. Mailboxes didn’t get so many visits from mailbox assistants then…
Teams now hides the Office 365 Groups that it creates from Exchange clients (Outlook, OWA, and the mobile apps). That’s as it should be for groups created for new teams. If you want to hide groups created for older teams, you can run the Set-UnifiedGroup cmdlet, but that soon becomes boring when you might have hundreds of groups to process. PowerShell to the rescue once again.
It is nice to have an Azure Active Directory Expiration Policy for Office 365 Groups, but it’s not so good that the policy functions exclusively based on age. Another problem is that administrators have no way of knowing when groups will expire. So we take out PowerShell, write a script, and hey presto, we have a report. We still need to solve the problem of creating a policy that functions based on activity rather than age, but that’s another day’s work.
PowerShell is a critical skill for Office 365 tenant administrators. A knowledge of PowerShell allows you to fix things that Microsoft leaves undone in apps like Exchange Online, SharePoint Online, and Teams. Sure, black holes exist for PowerShell (like Planner) and it is slow to process thousands of objects, but there’s nothing like a little script for getting things done.
In today’s Ask the Admin, Russell Smith shows you how to get started with the Chocolatey package manager for Windows.
In this Ask the Admin, Russell Smith shows you how to use the file resource and manage permissions on files and folders.
In today’s Ask the Admin, Russell Smith looks at the Chocolatey package manager for Windows, what it does, and how it can simplify software deployment on servers and end-user devices.
The Windows 10 Fall Creators Update and Windows Server 1709 include a beta OpenSSH server and client. In this Ask the Admin, I will discuss how OpenSSH differs from PowerShell Remoting.
In this Ask the Admin, Russell Smith uses a PowerShell script to populate Active Directory with test user accounts.
Microsoft announced the general availability of PowerShell Core 6.0 on January 10th. In this Ask the Admin, we will look at the roadmap for PowerShell and some of the dramatic changes since Microsoft announced that PowerShell will be open source.
Office 365 Groups (and Teams) can quickly become obsolete, but administrators need some help to find the underused groups. PowerShell comes to the rescue through a mixture of checks against the group mailbox, Office 365 audit log, and Teams compliance records. A nice HTML report is the result – and isn’t that always welcome.
We can use PowerShell for SPO by using any of the development environments provided by Microsoft. If you ask my recommendation about what tool to use, I would say Windows PowerShell ISE or Visual Studio Code. Finally, there are also third-party tools to run PowerShell scripts and modules for SPO.
The Teams PowerShell module is flawed, but that does not mean that you cannot do work with it. Here’s a primer of the most important cmdlets, together with a link to a rather interesting approach to finding out what Office 365 Groups are team-enabled.