For this Quick PowerShell post, I am going to cover something that I am learning to expand my skill set – Microsoft Identity Manager (MIM) 2016. I want to briefly cover different ways to create user accounts needed for a best practice installation of MIM. First, we will start with Microsoft’s code from the DOCS page, then cover a couple of variations I’ve seen as well as modified version of the script to help tailor the script to your needs.
Source – MIM Deployment – Set up a domain
Hated to see this when it affected Exchange on-premises for what seemed like ages. Now we have a similar issue occurring with PowerShell in Exchange Online. If, for some reason, you need to check the Get-Help of a cmdlet in Exchange Online, you will get a grand ol’ error message like this:
While this is non-functional, if you need information on the cmdlets, there is the new GitHub PowerShell reference pages located HERE. I would use that until its fixed.
As I was writing an article about Office support and Microsoft’s policy on its future, getting ready to Publish it, Microsoft moved the target. Office 2016 which had been slated to be an unsupported in October of 2020 has had its support officially extended to 2023. This is great news for those that are currently using Office 2016 for their Office 365 tenant. Looks like Microsoft took some flak from their customers on this change on their support stance.
A lot of ink has been written on this but it is important that anyone that has a tenant in Office 365 should be aware of these changes. Read the complete policy here:
“Office 2016 connectivity support for Office 365 services
In addition, we are modifying the Office 365 services system requirements related to service connectivity. In February, we announced that starting October 13, 2020, customers will need Office 365 ProPlus or Office 2019 clients in mainstream support to connect to Office 365 services. To give you more time to transition fully to the cloud, we are now modifying that policy and will continue to support Office 2016 connections with the Office 365 services through October 2023.”
For those companies and organizations that are still deploying and maintaining Exchange on-premises, you may be aware of the newest version of Microsoft’s flagship messaging product is now in preview – Exchange Server 2019. This latest iteration does bring about some significant changes and one interesting feature. Here is a quick summary of the changes being made:
Exchange Server on Windows Core
This has been an ask of many a client of mine when they upgrade to a new version of Exchange – Can I install it on Windows Core? Well, now you can. Windows Core will be a bit of an odd experience for those who are solely used to the Windows GUI for doing everything on the desktop for Exchange. However, I think Microsoft has positioned this well and has been actually preparing for this change since 2013 with the removal of the MMC and the addition of a web only interface for Exchange administration. A lot of administrators I work with do not log into their Exchange servers except for the occasionally weird issue that may arise. Otherwise most, if not all of their current operations can be done remotely:
- Event Log monitoring (log shipping/monitoring software)
- Remote PowerShell for running commands ‘locally’ on the server
- Web Interface for other configuration duties
I perform a lot of migrations to Exchange Online and do most of my work in PowerShell. As such, being able to work with all types of remote mailboxes for Exchange Online migrations is a boon to me as it is less time I have to spend in the GUI. Recently Microsoft added the ‘-Shared’ option to the New-RemoteMailbox cmdlet for Exchange 2013 CU21 and Exchange 2016 CU10. This now allows PowerShell to create a new remove mailbox in the cloud that is not a room equipment or user mailbox. While Shared mailboxes are not usually a significant number when considering all mailboxes in a migration, they are more visible as Shared mailboxes by their nature have more than user or viewer.
There are some caveats to the availability of the parameter for the New-RemoteMailbox cmdlet. From Microsoft’s documentation:
Over the past six or so years I’ve worked on providing a PowerShell script to make the installation process for Exchange 2013 and 2016 easier. The scripts will install the prerequisites, instead of having you look them up, round them up and then install them one at a time. With Exchange 2019 Preview being released in the past week or so, I thought it would be good to release a PowerShell script to handle it. While I’ve had one for my TAP installs, I needed to revamp it and my old script to make it fresh and new.
So today I am announcing that the script is ready for anyone to use.
Download it here: