How to renew SSL Ceritificate in Send connector in Exchange Server 2013

I have hybrid environment with Exchange server 2013 CU8 and Office 365. Every thing was working fine but after expiring of Public SSL, mail flow from internal users to office 365 and external domains was stopped.
After looking into it more, came to know that send connector was using SSL certificate which was expired, So after renewing SSL certificate, download it on the servers and import it on the server in required certificate store.
then start to assign it to the Send connector
took the following steps.

1. First note the thumbprint of new SSL certificate
2. Note the name of Send connector
3. Use following command to assign it to send connector

$cert = Get-ExchangeCertificate -Thumbprint bbbbbbkhkkjkj1cee4ca68khy28c5b27ut67e7dopu

$TLSCert = "<i>$($cert.Issuer)<s>$($cert.Subject)"

Set-SendConnector -Identity "Default send connector" -TLSCertificateName $TLSCert

after that mail flow start working 

How to renew SSL certificate in Receive connector in Exchange Server 2013

I have hybrid environment with Exchange server 2013 CU8 and Office 365. Every thing was working fine but after expiring of Public SSL, mail flow from external domains and office 365 stop.
After look into it more i came to know that receive connector was using SSL certificate which was expired, So after renewing SSL certificate, i download it on the edge server and import it on the server in certificate store.
then start to assign it to the Receive connector
took the following steps.

1. First note the thumbprint of new SSL certificate
2. Note the name of Receive connector
3. Use following command to assign it to receive connector

$cert = Get-ExchangeCertificate -Thumbprint bbbbbbkhkkjkj1cee4ca68khy28c5b27ut67e7dopu

$TLSCert="<i>$($cert.Issuer)<s>$($cert.Subject)"

Set-receiveConnector -Identity "Default internal receive connector EDGEServer" -TLSCertificateName $TLSCert

after that mail flow start working 

How to renew SSL certificate in exchange server 2013 hybrid environment

I have hybrid environment with Exchange server 2013 CU8 and Office 365. Every thing was working fine but in coming few days public SSL was getting expired. so started working on it to renew it, and took the following steps.

1. Purchase New SSL Certificate from a Public Certificate Authority 
2. Create CSR on one on-premises Exchange Server
3. Upload the CSR on Public Certificate Authority site and create Public SSL against it
4. Download that certificate to the server from whom CSR was generated and install it on that server
5. Export that Certificate from that server and import it on all servers in the environment
6. Assign that Certificate to required Cervices (IIS, SMTP, etc)  
7. Replace the old Certificate with new Certificate in the Send connector of the environment
8. Replace the old Certificate with new Certificate on both edge servers receive connectors
9. Rerun the Hybrid configuration wizard to replace the old certificate with new one

 

how to resovle "'Subtask CheckPrereqs execution failed: Check Tenant Prerequisites Deserialization fails due to one SerializationException" error

I have hybrid environment with Exchange server 2013 CU8 and Office 365. Every thing was working fine but in coming few days public SSL was getting expired. so after renewing the public SSL on the on premise servers, i start rerunning the hybrid configuration wizard as the old certificate was used in it.
But while rerunning the hybrid configuration wizard from the on premises ECP i got the following error.
After looking it more on the internet i came to know that i should download  the latest Hybrid Configuration Wizard  available on ("http://aka.ms/TAPHCW"). after trying this new tool the wizard was completed without this error. 

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.ADMultiValuedProperty`1[[Microsoft.Exchange.Data.SubscribedPlanDetails, Microsoft.Exchange.Data, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]],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.ObjectReader.GetType?(BinaryAssemblyInfo assemblyInfo, String name)? at System.Runtime.Serialization.Formatters.Binary.ObjectMap..ctor?(String objectName, String[] memberNames, BinaryTypeEnum[] binaryTypeEnumA, Object[] typeInformationA, Int32[] memberAssemIds, ObjectReader objectReader, Int32 objectId, BinaryAssemblyInfo assemblyInfo, SizedArray assemIdToAssemblyTable)? at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectWithMapTyped?(BinaryObjectWithMapTyped record)? at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run?()? at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize?(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)? at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize?(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)? at Microsoft.Exchange.Compliance.Serialization.Formatters.TypedBinaryFormatter.Deserialize?(Stream serializationStream, SerializationBinder binder)? at Microsoft.Exchange.Data.SerializationTypeConverter.DeserializeObject?(Object sourceValue, Type destinationType)? The type to be ?(de)?serialized is not allowed: Microsoft.Exchange.Data.Directory.ADMultiValuedProperty`1[[Microsoft.Exchange.Data.SubscribedPlanDetails, Microsoft.Exchange.Data, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]],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.ObjectReader.GetType?(BinaryAssemblyInfo assemblyInfo, String name)? at System.Runtime.Serialization.Formatters.Binary.ObjectMap..ctor?(String objectName, String[] memberNames, BinaryTypeEnum[] binaryTypeEnumA, Object[] typeInformationA, Int32[] memberAssemIds, ObjectReader objectReader, Int32 objectId, BinaryAssemblyInfo assemblyInfo, SizedArray assemIdToAssemblyTable)? at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectWithMapTyped?(BinaryObjectWithMapTyped record)? at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run?()? at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize?(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)? at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize?(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)? at Microsoft.Exchange.Compliance.Serialization.Formatters.TypedBinaryFormatter.Deserialize?(Stream serializationStream, SerializationBinder binder)? at Microsoft.Exchange.Data.SerializationTypeConverter.DeserializeObject?(Object sourceValue, Type destinationType)? ?'. Additional troubleshooting information is available in the Update-HybridConfiguration log file on server MBXCAS located at C:\MSExchange2K13\Logging\Update-HybridConfiguration\HybridConfiguration_5_9_2017_13_9_8_636299321480526847.log.Microsoft.Exchange.Compliance.Serialization.Formatters.BlockedTypeException: The type to be ?(de)?serialized is not allowed: Microsoft.Exchange.Data.Directory.ADMultiValuedProperty`1[[Microsoft.Exchange.Data.SubscribedPlanDetails, Microsoft.Exchange.Data, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]],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)? 

 

Storage drive appearing as RAW in Windows Server 2008 R2

I faced an issue that a storage drive assigned from DS 3400 was appearing in RAW format.
i was unable to open it, initialize it and it asking every time to format it. as it was not in NTFS format and Windows was unable to open it, RAW format was unknown for it.

Actually the was that, the server was restarted and the IQN was changed of the server due to some issue.
after putting the IQN again in Storage issue was resolved.

The IQN of a server you can find as below.
Open ISCSI initiator and then go to Favorite Targets and there you will see the IQN.

The IQN you will put in below path on the DS3400 storage.
Open DS3400 storage console (i have IBM DS storage Manager 10)--> here you have to open the required storage, -->Host Mappings Tab-->select the required host group--->right click on Drive and select-->select Manage host port Identifiers-->Add Host port identifier information (This value and the value on server should be the same)


P.S: possibility of this is

if you rename the server.
if you change the IP.
if there is network device between SAN and Server which malfunction.


 

The operation couldn't be performed because object 'd7f5dfd8676fd' couldn't be found on 6fd87ere8fy7.prod.outlook.com

The operation couldn't be performed because object 'd7f5dfd8676fd' couldn't be found on 6fd87ere8fy7.prod.outlook.com

Few days back i moved a user from its OU (OU1) which was synchronizing with Office 365 to another OU (OU2) which was not synchronizing with Office 365.
after that i faced few issues with this user, the issue was below.
(1) was unable to receive email but can sent emails, mails for this user were stuck in Queue
(2) in Office 365 admin Center getting errors when checking its properties, which was as below.
The operation couldn't be performed because object 'd7f5dfd8676fd' couldn't be found on 6fd87ere8fy7.prod.outlook.com
(3) in portal.office.com also getting some errors

This issue was resolved in this way

1. Move this user to another OU (OU2) which was not synching with office 365
2. Then start ADsync syncing and when it complete
3. Then move again the user to the old OU (OU1) in which this user was in start.
4. Then start again the syncing manually
5. And the issue was resolved.

 

The UMMailboxPolicy policy assigned to the mailbox in the source forest couldn‎'t be mapped to the policy in the target forest

I have hybrid environment with Exchange server 2013 and office 365. i was trying to migrate a mailbox from on premises to office 365. but was getting the following error and migration was failing.
the reason was that the user was enabled for UM and a UM policy was applying on it, which was not exist in office 365. so as a work around i just went to exchange control panel, search this user mailbox and disable the Unified Messaging in Phone and Voice Features, in mailbox feature of this user.
then tried to migrate again and was able to migrate this time.

Unified Messaging: Disabled

Error: MigrationPermanentException: Mailbox ‎'username@domain.com‎‎' in the source forest is currently enabled for Unified Messaging but it can‎'t be enabled for Unified Messaging in the target forest for the following reason: The UMMailboxPolicy policy assigned to the mailbox in the source forest couldn‎'t be mapped to the policy in the target forest. Wasn‎'t able to find a UMMailboxPolicy policy using ‎'‎(SourceForestPolicyNames Equal Dial_Plan Default Policy)‎‎' as a filter in target forest. Please fix the problem or disable the mailbox for Unified Messaging before you try the operation again. --> Mailbox ‎'username@domain.com‎' in the source forest is currently enabled for Unified Messaging but it can‎'t be enabled for Unified Messaging in the target forest for the following reason: The UMMailboxPolicy policy assigned to the mailbox in the source forest couldn‎'t be mapped to the policy in the target forest. Wasn‎'t able to find a UMMailboxPolicy policy using ‎'‎(SourceForestPolicyNames Equal Dial_Plan Default Policy)‎‎' as a filter in target forest. Please fix the problem or disable the mailbox for Unified Messaging before you try the operation again. --> The UMMailboxPolicy policy assigned to the mailbox in the source forest couldn‎'t be mapped to the policy in the target forest. Wasn‎'t able to find a UMMailboxPolicy policy using ‎'‎(SourceForestPolicyNames Equal Dial_Plan Default Policy)‎‎' as a filter in target forest.
Report: user@domain.com Download the report for this user