The type to be ‎(de)‎serialized is not allowed

Below is the error message when I tried to create Hybrid Configuration between my Exchange 2013 and Office 365.

Modify Exchange Hybrid

The wizard did not complete successfully. Please see the list below for error details.

Updating hybrid configuration failed with error ‎’Subtask CheckPrereqs execution failed: Check Tenant Prerequisites Deserialization fails due to one SerializationException: Microsoft.Exchange.Compliance.Serialization.Formatters.BlockedTypeException: The type to be ‎(de)‎serialized is not allowed: Microsoft.Exchange.Data.Directory.DirectoryBackendType,Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 at Microsoft.Exchange.Compliance.Serialization.Formatters.TypedSerializationFormatter.TypeBinder.BindToType‎(String assemblyName, String typeName)‎ at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Bind‎(String assemblyString, String typeString)‎ at System.Runtime.Serialization.Formatters.Binary.ObjectR

Enabling Hybrid Configuration On Exchange 2013/Office 365

Enabling Hybrid Configuration On Exchange 2013/Office365

If you have Exchange 2013 on premise and Office 365 setting is completed successfully, we can enable the hybrid easily.

I assume that Exchange 2013 is working very well and no need to health check. Also, Office 365 account has been created and domain name has been added to Office 365. Be careful that if cut over is not the subject, then you need to add only TXT record to validate the domain name. as you can see below that only TXT record has been added to my external DNs provider and domain name has been validated successfully.

In-Place Hold of Office 365

What are you going to do if a user who has a mailbox in Office 365 left your company? Of course your are going to disable or delete the account in Active directory.

Where can you see the numbers of inactive users. By the way, Microsoft says that If a user hasn’t logged in for more than 30 days, a user is inactive for Microsoft.

Exchange 2013 Completing Certificate Request

We have talked about requesting a certificate from Exchange 2013 in the last session

https://moonstarit.wordpress.com/2014/07/24/exchange-2013-certificate-request-process/

It is time to keep going to finalize the process.

Go to the folder where your certificate request has been saved and open it and copy everything in the notepad.

Exchange 2013 Certificate Request Process

Exchange 2013 Certificate Request Process

 

I have only one server in my domain and I am going to create a certificate request from this server. This server is my CAS and Mailbox server and it is connected to the Internet. As y’all can see that my Internet Explorer has certificate error.

First thing is to connect to EAC and then go to Servers>Certificate.

What is Hybrid Exchange and Office 365?

What is Hybrid Exchange and Office 365?

Many of you might have an Exchange server in your environment. If you have a plan to migrate users to Office 365, Microsoft gives you a chance to have a hybrid environment. So, what is this? Although you can have only Office 365 for your companies email system, you can have both, Office 365 and Office 365. You can keep some users on-premises and Office 365. There are 2 ways you can use Hybrid.

Re-Configuring Hybrid Configuration on Exchange 2010/2013

Re-Configuring Hybrid Configuration on Exchange 2010/2013

I am not sure that you need this solution because it is really extreme issue. My client has a unique system. Somehow Office 365 tenancy had a problem. It was licensing issue and Microsoft wanted us to create a new tenancy and they moved the license to new tenancy. Therefore, on Exchange 2010, we had to reconfigure Hybrid configuration. During the configuration, actually we thought that we would be straight, we got error message.

Using Power Shell to configure Receive Connector on Exchange 2013

Most of us still use GUI to configure or check receive connector. Since Exchange 2013 has been announced, we may start using power shell instead of GUI. Because GUI is web based now. If you have any problem on it, the best way to manage Exchange 2013 is to use Power shell.

Let’s have quick look same basic power shell commands

Our first basic command is Get-Receiveconnector

Receive Connector on Exchange 2013

After all SMTP addresses are added to accepted domains, we should configure receive connectors now. As you all know that HUB server role is no longer available. New role is embedded into CAS role that named Front End.

The important receive connector here is “Default Frontend Server name” Because both role, mailbox and CAS have been installed on same server and this server is on the secure zone but this connector receives email from anonymous client. I think this changes made due to Edge site server is no longer part of Exchange environment anymore.

Email address policy on Exchange 2013

When creating an email address, we should follow one policy that decided according to company rule. For example, some companies use firstname@domainname.com, some use first letter of first name + lastname@domainname.com

During Exchange 2013 installation, a default policy is created.

Let’s begin to customize it.

Connect to EAC and then open mail flow. You will see email address policies