Exchange Microsoft Office 365 PowerShell

Enable a Remote Mailbox in Office 365

So I recently ran into an issue where I had a user who’s Local AD account had been deleted but their Office 365 Mailbox was still showing up. We tried to bring the user account back, however the AD recycle bin was not enabled. So we had to create a brand new account for the user and then work from there.

We originally planned to create a new mailbox and let the user start from scratch. However we ran into an issue were the old mailbox would not go away, and it was preventing us from migrating a new mailbox into Exchange Online for the user.

I then found the following Exchange Management Shell command which will allow you to connect the local AD account to the Exchange Online Mailbox.

Enable-RemoteMailbox USERNAME -RemoteRoutingAddress [email protected]

After running the command the user is now able to log in with their new AD account and have access to their mailbox.

I hope you found this post helpful, and if you did, please share it with your friends.

The Woes of being a SysAdmin…..

So last night I was called into our Data Center due to an outage. Once everything came back up we noticed an issue with our Exchange Archive Server which lives at that Data Center. From outlook we were not able to access our In-Place Archives, however we could do it from OWA (Weird Right?)

This morning I looked into the issue further and when I tried to open the Exchange Management Shell on that server I got this message 3 times.

New-PSSession : [ServerName.domain.local] Connecting to remote server ServerName.Domain.local failed with the following error
message : [ClientAccessServer=ServerName,BackEndServer=ServerName.Domain.local,RequestId=2de56d73-34a8-46a9-9bdd-5c023e960cb5,
TimeStamp=8/6/2018 3:14:08 PM] [FailureCategory=Cafe-SendFailure]  For more information, see the
about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
    + FullyQualifiedErrorId : -2144108477,PSSessionOpenFailed

So I tried to google this error message and let me tell you, if you try, good luck. There was literally no information about it. I then ended up googling this part of the message:


This let me to a Microsoft Answers thread which guided me to look at another blog which then said to check the SSL Binding on both the Website and Exchange Back end in IIS on the host. I discovered the the Exchange Back end did not have a binding for port 444. So I pointed it to the proper certificate and after and IIS reset it worked like magic.

Clients are not receiving emails from Exchange

So I had a client call in today and say that they are not receiving emails. That is as descriptive as it gets sometimes, so the first thing I did was check their Mail Gateway which caches email if their Exchange server is not running. So I looked and there is nothing in the queues, so that tells me that things are making it’s way to Exchange.

I then go and open the Exchange Management Shell which will tell me really quickly if the problem is what I think it is. So I fire it up and here is what I get

Note: If you try to open the web console you may have similar issues.

Having seen this message before with this particular client I know now that I have a time sync issue on my hands.

The First thing I look at is the time on the Exchange server.

Then I check the time on one of the Domain Controllers which is the PDC Emulator.

Then I check one of the other Domain Controllers and I find this.

As you can see the time difference is greater than 5 minutes which will cause your Exchange Server to be very unhappy.

Once you fix the time issue you can then try to reopen the Exchange Management Shell and you will see that you can connect without an issue.

Let me know if this was helpful by leaving a comment below.

thank you

Exchange 2016 Back pressure issue

So my biggest challenge over the last few months is dealing with an Exchange 2016 server that keeps having issues with Back pressure. I have never heard of this as a thing before but I have been working on a resolution which has been very very time consuming. I hope to do a post about it soon to discuss it more once this is behind me.

Install Exchange 2013 SP1

I don’t know about you but I really like where Microsoft is going with their installers these days. Back when I first stated in the field and had to install Exchange 2007 there were so many prerequisites that needed to be installed before you could even start to do the installation. They have now made it to where the system will at least tell you which items you need to install rather than send you on a wild goose chase. 
I started this particular post as documentation notes for an Exchange Server that I stood up in my Lab at work. Originally it was not meant to be a functioning Exchange server but as time went on it evolved into one. 
I am going to skip all of the previous steps about how to setup and configure your Server installation. However if you need instructions on that you can find it here:
How to build a Server 2012 R2 Server
We start with having the installation files mounted to the CD/DVD Drive.
Double Click on the blue Exchange 2013 Icon to launch the Wizard.

Of course if you at User Account Control (UAC) enabled you are going to get this message. Click Yes to continue.

Checking for Updates is optional but I always like to make sure that I am working with the latest version of the software to avoid issues (unless there is a known issue).

Once the updates check is complete you can click Next to continue.

Now you just need to be patient until the files are copied to the proper working directory or install directory. Once that completes you then have to wait while the setup is initialized.

Once all of that is done you can begin the installation by clicking Next.

Accept the licensing agreement and click Next.

You will now be presented with the option to use or not use recommended settings. For this server I went with recommended. Click Next to continue.

You will now get to choose your Server Roll Selections. The most common roles for the kind of server that I am working with here would be Mailbox role, Client Access role (not sure why they are not checked off in this image.) Click Next to Continue. 

Here you can decide what directory you would like to install the Exchange application. This also includes the default mailbox stores. Click Next to continue.

Next you have the opportunity to name your organization. You are only able to do this once and you are only presented with this screen if you do not have exchange running in your environment at all. Click Next to continue. 

If you so choose you can enable Malware protection setting which allows Exchange to scan for Malware in your emails. For me I chose no as we have other products we use for that, and this server is not accessible from the internet for email. Click Next to Continue. 

Now with all of those configurations behind you, it is now time for the readiness check. Click Install to begin. 

Once the readiness check is complete you may be presented with items that need to be resolved before you can continue. Once you have them all taken care of you can

As you can see all of the issue have now been resolved and you can now click Install to continue. 

Once you click install the setup pretty much runs unattended until it completes. If you do what I did and go out to lunch instead of taking more screenshots you may just skip all the waiting and see my next screenshot.

As you can see the installation completed and you are now ready to launch the Exchange Admin Center by clicking the check box and clicking finish.

Once you click Finish on the previous Screen Internet Explorer (or your default web browser is opened) and you are now able to log in.

Please let me know if you found this helpful in the comments below. This was a rather large guide and I paired down a few things to keep it where it is.