Check for Autodiscover ServiceBindingInformation during the installation of Exchange — This way you can be alerted when the property is configured, and we can $Null it out.
Scenario: We are installing Exchange On-Premises on some new servers, and we want to minimize the amount of Security Alerts that pop up on users Outlook connections. The Security Alerts pop up because we do not put the servername on the public certificates AND Exchange wants to configure the autodiscover record with https://<local server name>/autodiscover/autodiscover.xml…
Scriptlets to check Recent Windows and Exchange updates/patches
Scenario: You have just updated your Exchange Servers (or Windows Servers) and you want to verify the successful install of the patches through logic.Solution: SCRIPTLETS:
Windows – Unable to join domain. “An account with the same name exists in Active Directory. Re-using the account was blocked by security policy”
Scenario: The error below was received when joining a new computer to a domain (the computer object was pre-staged in AD by creating the computer object and resetting it).Error: “An account with the same name exists in Active Directory. Re-using the account was blocked by security policy”Solution: Add the following Reg Key: Reg add HKLM\System\CurrentControlSet\Control\Lsa…
Error: 450 4.4.317 Cannot connect to remote server – 451 5.7.3 STARTTLS is required to send mail
Scenario: When attempting to send email from Exchange Online to Exchange On-Premises via Hybrid connectors, Exchange Online receives the following error message with a Defer Event: LED=450 4.4.317 Cannot connect to remote server [Message=451 5.7.3 STARTTLS is required to send mail]This error means is that a certificate that supports TLS is present on the receiving…
Renewing Certificate in a Hybrid Exchange On-Premises Environment (Concern of the SMTP Service)
Scenario: The third-party certificate is expiring and needs to be renewed on multiple Exchange On-Premises server that hosts IIS, SMTP, POP, and IMAP. There is concern about the hybrid components for successful SMTP Routing between Exchange On-Premises and Exchange Online since we are moving the SMTP Service to a different certificate.Solution: The components below will…
Purge emails from a mailbox that are protected by a Organizational Hold
Scenario: You need to remove messages from a mailbox, but the mailbox is protected under an Organizational Hold (but it could also be a LitHold or a InPlaceHold). Since the message is currently protected, it will not purge out of the mailbox until the hold is expired, or ever, depending on what type of hold…
Error: Couldn’t find unique request with the provided information when get-mailboxexportrequest
Scenario: When running a get-mailboxexportrequest (or get-mailboximportrequest, remove-mailboxexportrequest, or remove-mailboximportrequest) you get the following error:Couldn’t find a unique request with the provided information.This is a result of running two separate mailbox export requests on the same mailbox, and Exchange didn’t create a unique name for each of the export request jobs. Therefore it creates a…
Configure a Distribution Group to send a reply message every time (Not an Out-of-Office Message)
Scenario: You need a distribution group to send a ‘specific’ reply message back to the sender, every time a sender sends to it. An Out-of-Office message will not do because it will only send a reply one time. Note: Distribution Groups do not have this functionality, however there is a work around with using a…
Mailbox Dumpster (aka TotalDeletedItemSize aka RecoverableItems) hit the 100GB size quota due to a bloated recurring meeting
Scenario: You have a mailbox that is similar to the following scenario:-On a Hold: A mailbox is protected by a hold such as a Litigation Hold, eDiscovery/In-Place Hold, SCC Compliance Hold, etc.-Hit the Quota: The mailbox has either already hit, or is approaching, the mailbox dumpster 100GB quota-Item Count to Size Ratio doesnt make sense,…
Invoke-WebRequest : The underlying connection was closed: An unexpected error occurred on a send
Scenario: You receive the following error when you attempt to Invoke-WebRequest from PowerShell: Invoke-WebRequest : The underlying connection was closed: An unexpected error occurred on a send. Solution: Run the following in PowerShell to make sure it uses TLS1.2 [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
Loading…
Something went wrong. Please refresh the page and/or try again.
Follow My Blog
Get new content delivered directly to your inbox.
Ex-Shell 