Accurate time in a domain environment is essential for authentication between clients and servers to work correctly. Kerberos v5 protocol requires a tolerance of less than 5 minutes, anything more than this and you will get authentication errors.
I’ve recently been investigating a a server who’s time leaped 28 days into the future! So wanted to start auditing the Windows Time service to see what made the change.
So in this blog post I’ll show you how to enable Windows Time service auditing.
For the next couple of posts I’ll be looking into AD security and auditing. In this article we’ll look at how to use Get-ADUser to list all recently created accounts.
With the increasing number of cyber attacks, security is at the top of most IT departments agenda. There are many checks you can perform to make sure AD is safe and secure, and that only valid or approved modifications have been made to user accounts. I’ll look at AD auditing in a future post, but this will be a handy snippet of PowerShell to help you identify recently created AD accounts, and a bonus bit of code to identify recently modified accounts!
I recently had to make some bulk changes to calendar permissions in Office 365, the client wanted the Default user permission to be set to Reviewer rather than AvailabilityOnly. So in this post I’ll walk you through how I went about making bulk permission changes to the Default user for the calendar folder for all users in Office 365.
I’ve been working on a simple PowerShell command today to import into our endpoint management solution so we can alert on disks with low diskspace. It’s been a while since I’ve dabbled with PowerShell, and it reminded me just how flexible it is and much I love it!
So I thought I would walk you through the evolution of the command I ended up with.
In this blog post we’ll look at how to install the latest version of Exchange 2016 on Windows Server 2016. At the time of writing the current version of Exchange 2016 is CU3.
When Exchange 2016 was first released it wasn’t possible to install it on the Windows Server 2016 Technical Previews due to some missing features in the OS that it relies upon, but now Windows Server 2016 has been released to manufacturing, installation of Exchange 2016 on WIndows Server 2016 is supported.
The demo environment I am using includes a Windows Server 2016 domain controller that is running at the Windows 2016 forest and domain level, and a Windows Server 2016 member server.
In the demo environment no previous versions of Exchange have been installed so as part of the installation the Exchange 2016 we will upgrade the AD Schema.
Finally before we start, always test in a demo environment before deploying in Production!