As Office 365 Groups and Microsoft Teams continues to explode in popularity, the ability to explore and control resources in large scale is becoming more apparent. While there are some basic controls available, those specifically included in the Teams PowerShell Beta module leave a lot to be desired. The Teams module currently only allows you to get information about Teams that you are actually in, thus very limited in the benefits to an administrator.
One of the tasks I have come across is the need to get a list of Teams, along with the members and owners of each. Continue reading →
Along with an Office 365 subscription, you get Microsoft’s mail filtering solution Exchange Online Protection (EOP). You can also subscribe to EOP if you are running on on-premises mail solution.
One nice feature of EOP is that it can be configured to detect and block outbound spam. IF When a user account gets compromised (or maybe you have legitimate spammers) Microsoft can block the ability for the account to send any more outbound mail until you have addressed the account and unblocked it. This is great until you have an outbreak of compromised accounts, likely due to phishing victims, and need to remove multiple blocked addresses. So how can we do this?
While playing around with Office 365 Groups expiration and the AzureADPreview module in PowerShell, I ran into the error below:
The term ‘Get-AzureADMSDeletedGroup’ is not recognized as the name of a cmdlet, function, script file, or operable program.
After a bit of trial and error, and some searching I found an important note in the Azure Active Directory PowerShell Module documentation. The documentation notes that the preview module cannot be installed on the same machine as the production module. I didn’t seem to have an issue actually doing the installation using the PowerShellGet Module, and tab completion for the cmdlets even worked, but the cmdlets would not work.
Indeed, after uninstalling the production module (Uninstall-Module AzureAD), I was able to work with the preview cmdlets.
Ever need to quickly get the mac address for a device in Configuration Manager and don’t want to wade through the console to find it? My logic said that the Get-CMDevice cmdlet would do the trick. However, MAC isn’t one of the attributes returned.
Microsoft released a Rollup Update for Configuration Manager v1702 this week to address multiple issues. One specific issue that affected many deployments was related to operating system deployment:
Starting with System Center Configuration Manager, version 1702, unknown computers that are started from media or PXE may not find task sequences targeted to them. This issue may occur if the Previous button on the “Select a task sequence to run” page is selected on the unknown computer.
There are already great examples of how to install this update, but there are a couple of key gotchas I ran into during deployment.