This Quick PowerShell blog article will cover how to test that a server can receive a remote PowerShell request (like Invoke-Command), how to add this ability an at the end remove the changes if need be as well. The reason I wrote this code is that I am in the process of creating health check scripts that sometimes need to run code locally on a server because the code cannot be executed remotely. An example of this would be using PowerShell to run the various BPA PowerShell cmdlets. These need to be executed locally on a server to get the proper BPA to run and leave results to be collected later. As such, PowerShell needs to invoke cmdlets on the remote server.
I wrote a script to gather Event Log data and posted it here – Quick PowerShell Stuff 17. That script would fail if WinRM or remote PowerShell sessions were not allowed to connect to a Domain Controller for example. What I needed was a more automatic way to fix this as I am now automating my health check data collection process.
What a great way to start off the new year…. an article on Office 365 and new regulations coming before mid-year 2018.
For my past two blog articles I’ve covered quite a bit of details on what Secure Score can offer you and your Office 365 tenant. What I wanted to do for this article is tie this in with the new and upcoming regulation called GDPR. GDRP stands for General Data Protection Regulation. The regulation initiative was passed by the EU in April of 2016 and it goes into effect on May 18, 2018. The regulation is not solely for companies in the EU, but is intended to protect personal data for people in the EU. This means that if you have customers in the EU or have dealings with the EU, GDPR will affect you.
*** WARNING *** – This is a long, long, long article.
This is the second in a series of articles on the Office 365 Secure Score feature. In the first article I covered the basic interface and usage of the Secure Score feature. In this article I will review it more in-depth and cover the practicality of the recommendations present in the ‘Tasks’ section. What does this mean? It means we are going to dive into as many tasks in-depth and examine them in-depth as well as determine what it actual means to put the item in place.
As we saw in the previous article, there is a list of tasks that Microsoft provides the Office 365 tenant administrator to assist them in securing their tenant to a greater degree than is the default or maybe even beyond the admins own knowledge level. The tasks listed in this article may or may not match what you see in your tenant.
Each task in the list expands to provide more information on the issue identified by Microsoft: Continue reading
If you have an Office 365 tenant and you have explored the Security and Compliance Center. On your dashboard, or home screen, you may have noticed an item called ‘Office 365 Secure Score’. It should look something like this:
Now, your score will be different (higher or lower) depending on the features you have enabled in Office 365 (due to licensing) or items that you may have already configured yourself. For the next two blog articles we are going to take a peek at this feature in Office 365 starting with an introduction in this article and a more in-depth article in the next few days.
Recently I had a customer who fell behind on their upgrades for Exchange 2013. The servers were running Exchange 2013 CU, which was released in May of 2014. The newest update was CU18 and required some work due to changes in .NET requirements over the past three years. With this upgrade scenario CU15 could be used as a bridge update, allowing us to traverse the gap for .NET versions, while still being supported.
At first I thought that this was a problem unique to Exchange 2013. Then a fellow MVP pointed out a change to the .NET support listed on Microsoft’s Exchange compatibility matrix. This led to research to find a more complete view of .NET requirements for all versions of Exchange. I was about to find this chart – HERE The chart looks like this:
During a migration with a client we ran the Hybrid Configuration Wizard, as is a usual process for a migration, we ran into an issue. The HCW validating the domain, using the required TXT record, and while federating the domain, the wizard got stuck on ‘Adding Federated Domain’, like so:
If you are looking for a script to help you install all the prerequisites for Exchange 2016 CU8 and above, I’ve just released my newest version, v1.12, of the script. Currently it is listed on the TechNet Gallery for download. Here is the new and updated menu for the script:
You can download the script by clicking on the image below:
But What About .NET 4.6.2?
Look for an updated version of the .NET 4.6.2 script for Exchange 2016 hopefully over the weekend.