Microsoft Ignite kicks off on Monday, and I can’t wait for another year of immersion in all of the enterprise technologies that Microsoft has to offer. If you are still struggling to sort through the 1500+ sessions available, let me persuade you to check out my top 5 anticipated sessions for the week.
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.
Office 365 Groups, sometimes referred to as Unified Groups, have been around for a while now. Groups are excellent for collaboration, and allowing the end user to be in control of their own collaboration experience. Groups are bad news for IT workers who need control or are resistant to change. The latter group of IT workers will need to get on board though as it is evident that much of the Microsoft Office 365 ecosystem will be intertwined with Groups going forward.
For the past year, I have restricted group creation in production. There are a multitude of reasons for not using Groups upon their initial release but, ultimately, it was lack of enterprise controls. Most of those limitations have been remediated and the time for Groups is now.
In an effort to keep some form of structure around Groups, using a multi-domain approach is useful.
Since Microsoft Teams were released after (and are built on) Office 365 Groups, Microsoft has provided a quick solution for adding Teams functionality to an existing Group. (NOTE: A Group must have less than 999 members for the conversion to be successful.) This solution can be completed in just a few simple clicks.
On March 14, 2017 Microsoft officially launched Teams for Office 365. While all users who were licensed with a qualifying Office 365 license automatically received the Teams tile in the app launcher, Microsoft provided a global way to control access. The default setting was OFF. Additionally, a note was included that the control was only temporary.
“Temporary” is subjective, and in this case (at least for Education customers), seems to Continue reading