Tuesday, December 27, 2016

Maximum number of items that can be serialized or deserialized in an object graph is '65536- Office365

During the generating the Office 365 users license report, i got following PowerShell error:

The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameter http://provisioning.microsoftonline.com/:ListUsersResult. The InnerException message was 'Maximum number of items that can be serialized or deserialized in an object graph is '65536'. Change the object graph or increase the MaxItemsInObjectGraph quota. '. Please see InnerException for more details.


Solution

Every WCF service comes with its own bindings, behaviors and other preferences, applying appropriate changes requires of every single WCF service. We can change .NET Framework configuration globally for your system. This solution should permanently solve problem for all applications using WCF services.

We need to modify the machine.config -files, please follow the below steps:

Check your powershell version with $psversiontable.psversion.tostring()

Move to folder that corresponds your powershell version C:\Windows\Microsoft.NET\Framework*\*\CONFIG



Modify machine.config., Add below line


Most of case it will resolve the issues, if not reboot the server.

Happy Learning!

Thanks.

Sunday, December 18, 2016

Update for Skype for Business, December, 2016

Microsoft has released an update for Microsoft Skype for Business 2016. The version number of this update is 16.0.4471.1000.




Download Update for Skype for Business 2016 (KB3127980) 64-Bit Edition


Download Update for Skype for Business 2016 (KB3127980) 32-Bit Edition



Caution: I recommend to test updates in a test environment prior to implementing them in production. if you do not have the test lab, hold out a few days check the TechNet forum for any issues.

Tuesday, December 13, 2016

Update Rollup 22 for Exchange Server 2007 Service Pack 3

Update Rollup 22 for Microsoft Exchange Server 2007 Service Pack 3 (SP3) was released on December 13, 2016. Before you install this update rollup, see the Installation instructions.

This update includes time zone updates for Exchange Server 2007 SP3. For more information about daylight saving time (DST), go to Daylight Saving Time Help and Support Center.


Download Update Rollup 22 for Exchange Server 2007 Service Pack 3





Caution: I recommend to test updates in a test environment prior to implementing them in production. if you do not have the test lab, hold out a few days check the TechNet forum for any issues.

Update Rollup 16 for Exchange Server 2010 Service Pack 3

Update Rollup 16 for Microsoft Exchange Server 2010 Service Pack 3 (SP3) was released on December 13, 2016. Before you install this update, you must remove all interim updates for Exchange Server 2010 SP3. Also, see this important information about how to install this update.

This update includes time zone updates for Exchange Server 2010 SP3. For more information about daylight saving time (DST), go to Daylight Saving Time Help and Support Center.


Download Update Rollup 16 For Exchange 2010 SP3 (KB3184730)




Caution: I recommend to test updates in a test environment prior to implementing them in production. if you do not have the test lab, hold out a few days check the TechNet forum for any issues.

CU 15 for Exchange Server 2013

Cumulative Update 15 for Microsoft Exchange Server 2013 was released on December 13, 2016. Several nonsecurity issues are fixed in this cumulative update or a later cumulative update for Exchange Server 2013. This release includes support for Windows time zone updates released through October 2016.

Following Issues that this cumulative update fixes:





References : https://support.microsoft.com/en-us/kb/3197044

Caution: I recommend to test updates in a test environment prior to implementing them in production. if you do not have the test lab, hold out a few days check the TechNet forum for any issues.

CU 4 for Exchange Server 2016

Cumulative Update 4 for Microsoft Exchange Server 2016 was released on December 13, 2016. Several nonsecurity issues are fixed in this cumulative update or a later cumulative update for Exchange Server 2016. This release includes support for Windows time zone updates released through October 2016.



Following issues that the cumulative update fixes:


Download CU 4 for Exchange Server 2016 (KB3177106)

Reference : https://support.microsoft.com/en-us/kb/3177106

Caution: I recommend to test updates in a test environment prior to implementing them in production. if you do not have the test lab, hold out a few days check the TechNet forum for any issues.

Sunday, December 11, 2016

Office 365- Fatal error TooManyLargeItemsPermanentException has occurred

BACKGROUND

During the Office 365 migration project, when moving mailboxes to Exchange Online, the Remote Move Request fails with the following error message:

Error: This mailbox exceeded the maximum number of large items that were specified for this request.

When viewing the log file for the mailbox migration, you see the following details:

Fatal error TooManyLargeItemsPermanentException has occurred.



CAUSE

The message size limits for Exchange Online migrations is 150 MB. It was 35 MB prior to January 2015.

If larger items than 150 MB are attempted to be moved through a default Remote Move Request initiated from the EMC wizard, the job will fail with the error message above because Exchange Online refuses the messages due to their size.

If you have mailboxes containing messages that are +150 MB in size, we have n still migrate these mailboxes but we will need to define the Exchange that it should simply skip the large messages that are refused and not abort the complete move request when encountering them.


RESOLUTION

First of all connect Office 365, Azure PowerShell.

If you have single user than use below cmdlet:

New-MoveRequest -Remote -Identity User.Name@Domain.com -RemoteHostName 'ews.companydomain.com' -RemoteCredential $OnpremAdmin -TargetDeliveryDomain 'tenantdomain.mail.onmicrosoft.com' -BadItemLimit 50 -LargeItemLimit 30 

When you want to set the Auto Suspend than you can use:

New-MoveRequest -Remote -Identity User.Name@Domain.com -RemoteHostName 'ews.companydomain.com' -RemoteCredential $OnpremAdmin -TargetDeliveryDomain 'tenantdomain.mail.onmicrosoft.com' -BadItemLimit 50 -LargeItemLimit 30  -SuspendWhenReadyToComplete


If you want to migrate bulk users in CSV, use below cmdlet:

Import-CSV "C:\temp\user.csv" | foreach {New-MoveRequest -Remote -Identity $_.alias -RemoteHostName 'ews.companydomain.com' -RemoteCredential $OnpremAdmin -TargetDeliveryDomain 'tenantdomain.mail.onmicrosoft.com' -BadItemLimit 50 -LargeItemLimit 30}


With Auto Suspend option:

Import-CSV "C:\temp\user.csv" | foreach {New-MoveRequest -Remote -Identity $_.alias -RemoteHostName 'ews.companydomain.com' -RemoteCredential $OnpremAdmin -TargetDeliveryDomain 'tenantdomain.mail.onmicrosoft.com' -BadItemLimit 50 -LargeItemLimit 30 -SuspendWhenReadyToComplete}


Thanks You!

Happy Learning.