To quickly get all ‘Failed Move-Requests’ you can run the following one liner. Get-MoveRequest | Where-Object {$_.Status -eq “failed”} To Remove all ‘Failed Move-Requests’ you can run the following: Get-MoveRequest | Where-Object {$_.Status -eq “failed”} | Remove-MoveRequest #ThatLazyAdmin
Using Active Directory to meet Regulatory Compliances When it comes to meeting compliance, many Administrators settle for simply auditing event logs. By default, Event Viewer records all events that are generated on a Windows Server. However, is simply storing logs an efficient way to meet compliance? Most compliance mandates require a particular report to…
Express installation of Azure AD Connect Tool Can be downloaded from Here Sign in as a local administrator to the server you wish to install Azure AD Connect on. You should do this on the server you wish to be the sync server. Navigate to and double-click AzureADConnect.msi. On the Welcome screen, select the box agreeing…
Windows Server 2012 and Windows Server 2012 R2 prerequisites The prerequisites that are needed to install Exchange 2016 on computers running Windows Server 2012 or Windows Server 2012 R2 depends on which Exchange role you want to install. Read the section below that matches the role you want to install. Role: Mailbox server role. Let’s…
Enable Remote Desktop Using PowerShell Open an elevated Windows PowerShell session and run the following commands. This first one creates the fDenyTSConnections value and sets it to 0 (off). This makes sense, because we don’t want to deny Terminal Services (TS) connections. Set-ItemProperty -Path ‘HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server’ -Name fDenyTSConnections -Value 0 Set Network Level Authentication for…
Prepare Active Directory and domains for Exchange 2016 The first step in getting your organization ready for Exchange 2016 is to extend the Active Directory schema. Exchange stores a lot of information in Active Directory but before it can do that, it needs to add and update classes, attributes, and other items. If you’re curious…
Exchange 2010 MessageTrackingLog: Error Access Denied Message Tracking in Exchange 2010 Stopped and you received the following Error in EventViewer. “MessageTrackingLogs: Failed to write logs because of the error: Access to the path ‘MSGTRK20170329-8.LOG’ is denied..” Let’s Start by reviewing the Current configuration for Message Tracking. Get-TranSportServer |ft Name,MessageTrackingLogEnabled,MessageTrackingLogPath,MessageTrackingLogMaxAge,MessageTrackingLogMaxDirectorySize, MessageTrackingLogMaxFileSize,MessageTrackingLogSubjectLoggingEnabled Now that you have your…
Exchange Deployment Assistant Quick Overview Exchange deployment tool creates a custom step by step checklist to help you deploy Exchange in different types of scenarios. The tool can be found Here. Click on Launch the Deployment Assistant. From the next screen you will have 3 different options to choose from On-Premises ,Hybrid ,Cloud Only. Details…
Deploy Active Directory Domain using PowerShell Let’s start by Setting the PowerShell Execution Policy to Unrestricted Set-ExecutionPolicy Unrestricted Next we will rename the server and install Prereq features. #rename the computer $newname = “LAB-DC-01” Rename-Computer -NewName $newname -force< #install features $featureLogPath = “c:\softlib\Shell\poshlog\featurelog.txt” New-Item $featureLogPath -ItemType file -Force $addsTools = “RSAT-AD-Tools” Add-WindowsFeature $addsTools Get-WindowsFeature |…
On April 13 of last year, Microsoft announced the deprecation of “Windows Azure Active Directory Sync (DirSync)” and “Azure Active Directory Sync (Azure AD Sync)” and that it was time to start planning to upgrade to Azure AD Connect. They have also announced that end of Support for DirSync & AzureAD Sync will be on…
Execution of Scripts is Disabled on this System When you try and run a #PowerShell Script and you are faced with the Error “Execution of Scripts is Disabled” The quick work around for this is to change the current Execution Policy using the following. Lets Change the Execution Policy by running a #OneLiner Set-ExecutionPolicy Unrestricted…
Clean MailboxDatabase Command no longer Valid on #Exchange 2013 Clean-MailboxDatabase Command has been decommissioned for Exchange 2013 and replaced with Update-StoreMailboxState http://technet.microsoft.com/en-us/library/jj860462(v=exchg.150).aspx Update-StoreMailboxState require the GUID of a mailbox to execute so it usually easier to run in combination with Get-MailboxStatistics like the example below Get-MailboxStatistics -Database MDB02 | ForEach { Update-StoreMailboxState -Database $_.Database -Identity $_.MailboxGuid…