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.

Friday, November 25, 2016

Does Office 365 back up make sense

Today, many organization messaging services are mission-critical, if messaging system is down than productivity will be down and it will direct effect on business revenue. All of the redundancy, security and fault tolerance in the world cannot help when it comes to a damaged, corrupt, or lost database, backing up the critical data in Exchange Servers is a necessary operational task for all organizations.

As part of the disaster recovery planning, it is important that we have understand how to correctly backup the Exchange Servers. What happens when we delete an email? We have 14 or 30 days to recover it from the dumpster and afterwards it’s gone forever.

Now most of the customer moving to Exchange online (Office365) and its again critical how to recover the deleted emails. If you have Office 365 plans E3 or E4, then you can set the dumpster to keep deleted emails forever. However, if the size of the dumpster is limited then the oldest emails will start to be permanently deleted. Also we can configure the “litigation hold” per specific accounts and retain all deleted emails.

But we have to think about when the data override that is done by accidentally or maliciously by the users. If we did not back up our data in advance, there will be good chance that we cannot recover once we notice that the calendar or Contact were overridden some time ago.

Now, we have to be aware of the risks we take by not backing up your Office 365 data. But what can we do? Well, there are couple of manual tools we can use to manually backup our data.

Does backing up Office 365 make sense

Office 365 has completely change the email business, and most of the organization using Office365. The subscription-based cloud productivity suite boasts more than 7 million users can use the familiar Office applications on many devices including desktop PCs, laptops, tablets and smartphones. Office 365 is one of the quickest adopted cloud applications in history, but it lacks a reliable enterprise backup system as of now.

What is Microsoft doing to backup data

Microsoft is doing a lot to ensure files and documents are always accessible and backed up. It even prides itself in its 99.9% service up-time with regular backups. In a blog post on its site, Microsoft outlined some techniques it used to ensure data was backed up. It constantly replicates data between data centers and storing data in completely redundant environments with backup and restoring capabilities, such as DAG etc. If something happens to one of Microsoft’s data centers, we most likely retain every single one of our emails!

Why should you have your own backup

While Microsoft does replicate and backup its Office 365 service, it only protects its own interests by making sure any loss on its end can be recovered from. Its backup does not protect us from user errors such as accidental deletion or an employee maliciously deleting files.

In this case all the organizations need a third-party solution to deal with this very prevalent form of data loss.

What options are out there

There are more and more third-party backup applications for Office 365 coming to market; some more reliable than others. IT industry news publication.
In addition, we can store your Office 365 data in the same container as all our other corporate data, providing peace of mind to any IT manager.

Whether our data is in the cloud like Office 365, or on our corporate network, it’s smart to keep a backup in a separate location. Cloud-to-cloud backup solutions are coming to market and leading the front to protect data in the cloud and in the office.

Thank You!

Monday, November 21, 2016

Faulting application name: w3wp.exe Exchange Server 2016 & Windows Server 2016

When today i was trying to deploy Exchange 2016 in Windows Server 2016 got the below error.
The W3WP.exe application constantly crashes and spams the Event Log with crashes every few seconds.
Here is the Event Log:
Faulting application name: w3wp.exe, version: 10.0.14393.0, time stamp: 0x57899b8a
Faulting module name: ntdll.dll, version: 10.0.14393.0, time stamp: 0x578997b2



Solution:

Official from Microsoft:

If you attempt to run Microsoft Exchange 2016 CU3 on Windows Server 2016, you will experience errors in the IIS host process W3WP.exe. There is no workaround at this time. You should postpone deployment of Exchange 2016 CU3 on Windows Server 2016 until a supported fix is available.

https://technet.microsoft.com/en-us/windows-server-docs/get-started/windows-server-2016-ga-release-notes

Monday, November 14, 2016

NetFx3 on Windows Server 2012 R2 - SQL Server 2012

Today, in process to installation of Skype for Business, when deploying back end server SQL Server 2012 on Windows Server 2012 R2, received error "NetFx3, Error Code : -2146498298, Please try enabling Windows feature : NetFx3 from Windows management tools and then run setup again, For more information on how to enable Windows features features"


Workaround

on Windows Server 2012 R2, .NET Framework 3.5 feature is not installed because it already have the .NET framework 4.5 installed as the default platform. If we want to have then we have to install manually on server.


First open the server manager tool of Microsoft Windows Server 2012 R2, click on the Manage and go to Add Roles and Features"


and here .Net Framework 3.5 installed successfully.


once .NET Framework 3.5 installed successfully try on SQl to continue to installation and set will run smoothly.

Tuesday, November 8, 2016

Exchange Server 2010, fixes and updates - October 2016

Office 365 -Managing Mailbox Permissions by using PowerShell

Most of us already managing the Exchange server on-premises, now its time to manage the mailboxes permission into Exchange Online, following are some useful Power Shell command:

Assign Mailbox Permission
Add-MailboxPermission -Identity "ABC" -User "Admin" -AccessRights FullAccess -InheritanceType All

Assign “Send As” Permissions for a Mailbox
Add-RecipientPermission "ABC" -AccessRights SendAs -Trustee "Admin"

Assign “Send As” Permissions for a ALL Mailbox’s (Bulk)
$MBXS = Get-Recipient -RecipientType UsermMilbox ForEach ($MBX in $MBXS) 

Add-RecipientPermission $MBX.name -AccessRights SendAs –Trustee "Admin@tech.com" -Confirm:$False 

Get-RecipientPermission | Where {($_.Trustee -ne 'nt authority\self') -and ($_.Trustee -ne 'Null sid')} }


Assign “Send As” Permissions for recipient for each member in a distribution group
$DL = Get-DistributionGroupMember  
Foreach ($item in $DL) 

Add-RecipientPermission $item.name -AccessRights SendAs
–Trustee "Admin" -Confirm:$False 
}


Assign “Send As” Permissions for each member in a distribution group for a specific recipient
$DL = Get-DistributionGroupMember  
Foreach ($item in $DL) 

Add-RecipientPermission "ABC" -AccessRights SendAs 
–Trustee $item.name -Confirm:$False 
}


Assign “Send on Behalf” Permissions for a Mailbox
Set-Mailbox "ABC"  -GrantSendOnBehalfTo  "Admin"


Assign “Full Access” permissions for all Mailboxes (Bulk)
Get-Mailbox -ResultSize unlimited -Filter {RecipientTypeDetails -eq 'UserMailbox'} | Add-MailboxPermission -User "admin" -AccessRights FullAccess -InheritanceType All


Assign “Full Access” permissions to Distribution Group 
$DL = Get-DistributionGroupMember "DL" | Select-Object -ExpandProperty Name 
ForEach ($Member in $DL ) 
{
Add-MailboxPermission -Identity "ABC"  -User $S -AccessRights FullAccess -InheritanceType All
}


Assign “Full Access” permissions for all Mailboxes and Disable AutoMap
Get-Mailbox -ResultSize unlimited -Filter {RecipientTypeDetails -eq 'UserMailbox'} | Add-Mailboxpermission -User "Admin" -AccessRights FullAccess -InheritanceType All –Automapping $False


Assign “Full Access” permissions for Specific User and Disable AutoMap
Add-MailboxPermission "ABC"  -User "Admin" -AccessRights FullAccess -InheritanceType All –AutoMapping $False


Get “Full Access” Permissions for a Mailbox
Get-MailboxPermission "ABC"


Get “Send As” permission for a Mailbox
Get-RecipientPermission "ABC"


Display “Send On Behalf” Permissions for Mailbox
Get-Mailbox "ABC"


View all “Send As permissions” from your organization
Get-RecipientPermission | where {($_.Trustee -ne 'nt authority\self') -and ($_.Trustee -ne 'Null sid')} | select Identity,Trustee,AccessRights


Display a list of recipient’s that have FULL ACCESS permission on other recipient’s
$a = Get-Mailbox $a |Get-MailboxPermission | Where { ($_.IsInherited -eq $False) -and -not ($_.User -like “NT AUTHORITY\SELF”) -and -not ($_.User -like '*Discovery Management*') } | Select Identity, user, AccessRights


Revoke “Full Access” Permissions
Remove-MailboxPermission  "ABC"  -User "Admin"  -AccessRights FullAccess


Revoke “Send As” Permissions
Remove-RecipientPermission "ABC"  -AccessRights SendAs -Trustee "Admin"

Saturday, November 5, 2016

Update for Lync 2013 (Skype for Business) (KB3127934)

Microsoft has released an update for Microsoft Lync 2013 on November 1, 2016. This update also includes the new Skype for Business client. The version number of this update is 15.0.4875.1001.

This update fixes the following issues:

The update is available for download from the Microsoft Download Center.

32-bit
DownloadDownload the 32-bit Lync update package now.

64-bit
DownloadDownload the 64-bit Lync update package now.


Source: https://support.microsoft.com/en-us/kb/3127934?sd=rss&spid=16924

Dive deep into Microsoft Exchange Server High Availability

High availability has become an essential part of the email services in many organizations around the world, which means that understanding how to deploy and maintain a highly available Exchange Server environment is a critical skill for Exchange Server administrators.

Although Microsoft Exchange Server is a single product it is made up of many different components, such as:

Client access – the protocols that allow mailbox access via Outlook, Outlook Web App (OWA), ActiveSync (mobile devices), and other clients.
Transport – SMTP communications and mail flow.
Mailbox – the databases hosting mailboxes.
Unified Messaging – the telephony integration services.
High availability considerations also vary depending on the version of Exchange Server that is deployed.

Dive deep into Microsoft Exchange Server High Availability


Deploying high availability and site resilience

Hold Exchange Server 2016 on Windows Server 2016 Deployments

Week ago i faced issues on my LAB with Exchange 2016 CU3 on Windows 2016, IIS was getting crashed, i gone through forum etc and came to lot of customers raising the issues about IIS in Exchange Server 2016 CU3 on Windows server 2016.

Finally Microsoft announced there are some issues in IIS (W3WP.exe) process in Exchange 2016 CU3 on Windows server 2016, as per Microsoft "The Exchange team has worked with the Windows team to isolate the source of the problem. An update for Windows Server 2016 will be made available to resolve this issue. Microsoft recommends that customers delay deploying Exchange Server on Windows Server 2016 until this update is made available. For the latest guidance on known issues, please consult the Windows Server release notes on TechNet."


Important Issues in Windows Server 2016

What's New in Windows Server 2016


Friday, November 4, 2016

Design your Exchange infrastructure right

Designing and implementing Microsoft Exchange on premises can be a complex and challenging task. That's why Microsoft offers the Preferred Architecture for simpler, easier and less expensive implementations. Why follow Microsoft's design guidance? Exchange architects, consultants, and support engineers who attend this session will learn about Exchange architecture concepts and design principles, and how to apply them to design and deployment decisions; analyze design challenges; understand "supported" vs. "recommended"; and uncover typical misconceptions and errors. You'll leave the session either ready to whiteboard your Exchange infrastructure, or ready to migrate your on-premises Exchange to Office 365.



Thursday, November 3, 2016

Error looking up local OU, Error Msg: Multiple objects found in AD

Last week, during cross forest mailboxes migration i received the error "Error looking up local OU, Error Msg: Multiple objects found in AD" when running the PrePare-MoveRequest.ps1 script.


After research i got to know that customer having multiple domains in forest.
and when i was specified an OU of "Users" since there is a default Users container in each domain.

When i create new OU such as target users/Source users and specified in prepare move request it run smooth.

So during the cross forest we must have the different OUs name not the default "Users".

Thanks!

Happy Learning.


Tuesday, October 25, 2016

The ACE does not Exist on the Object- Office 365

Yesterday, when i was trying to remove full permission from one of the my online user's mailbox and getting below error "BECAUSE THE ACE DOESN'T EXIST ON THE OBJECT"


Root Cause of the warning is, orphaned SID is pending on the mailbox, which is conflicting with rest all delegate user's permissions.

Solution

Simply we need to remove the SID first, and you have permanently resolved the issue.

Below cmdlet which we can eliminate the things, Get the orphaned SID. Run below cmdlet.

Get-Mailboxpermission -identity abc@domain.com | select user | fl

Run below mentioned command, and remove entry of orphaned SID from User Beta's mailbox.

Remove-Mailboxpermission -identity abc@domain.com -user "SID which we got" -Accessright fullaccess

Once done, we have to give the time for sync to Office 365.

Happy Learning!

Friday, October 21, 2016

Network Assessment Tool-Skype for Business online

We are in cloud era and moving most of technologies into cloud such as Exchange Online, Lync Online aka Skype For Business, Share Point etc. before moving to cloud we have to check some pre-requisite task such as required Network, System Security etc.

In series of assessment tool Microsoft have released a Skype for Business Network Assessment Tool and it is free for public download from here

The Skype for Business Network Assessment Tool provides the ability to perform a simple test of network performance to determine how well the network would perform for a Skype for Business Online call. It’s aimed specifically at testing your connectivity to Skype for Business Online

The tool tests the connection to Microsoft Network Edge by streaming a set of packets to the nearest edge site and back for approximately 20s for a configured number of iterations. The tool reports:

Packet loss
Jitter
Round-trip latency
Reorder packet percentage

Installing and running the tool

First download the tool from here, it will be as zip file you need to unzip the files to directory



We need to use Windows Power Shell the run the tool from any of the computer such as Windows 7 etc.

Before we run this we have to have familiar with the configuration file that sets up the options for the tool to run.

The configuration file is called “NetworkAssessmentTool.exe.config” and is located in the same directory as the other files. You can edit the file if required. The defaults are as shown below:



Now time to run the tool with using the Power Shell command

now you can check the output from here :



The key configuration components are explained in the following table:

Configuration
Description
If Not Specified
Relay.IP
IP address to reach the relay server. MUST be a valid IP address string.
Tool will fail.
Relay.UDPPort
UDP port to reach the relay server for relay allocations. MAY be omitted if the user wishes to test TCP allocations only. If both UDP and TCP are configured, UDP will be preferred if the relay is reachable via UDP.
If UDP and TCP are not specified, tool will fail. Otherwise, allocate on TCP only.
Relay.TCPPort
TCP port to reach the relay server for relay allocations. MAY be omitted if the user wishes to test UDP allocations only.
If UDP and TCP are not specified, tool will fail. Otherwise, allocate on UDP only.
WMAFilePath
Path to valid WMA file to be used as an audio file for the audio call. File MUST exist and MUST be a WMA file.
Tool will fail.
NumIterations
Number of audio calls to make. These will be made serially (no concurrency).
Takes value of 1.
ResultsFilePath
Location to output the results to. This is typically a tsv or csv. The delimiter is specified by the “Delimiter” setting. The first line of the output describes what each column is.
Results will not be output to a file.
Delimiter
For the output file in “ResultsFilePath” (if specified), this is the separator for each column in the output file.
Takes value of .
IntervalInSeconds
Time to wait between consecutive calls.
Takes value of 5.0s.
WMAOutputFilePath
Path to where the audio received will be written.  If file exists it will be overwritten
Tool will fail.

Configuration

Following is the sample for configuration of the tool:

This the concludes a summary of installing and running the network requirements tool for Skype Online, hope it will help you to analyze the Network requirement for Skype for Business.

Happy Learning!

Thursday, October 20, 2016

VoIP Exchange UM service & Microsoft-diagnostics

This is the best diagnostic log when we troubleshoot voice mail issues, diagnostic log shows Ms-diagnostics which is valuable to look first and see what reason and response is with error id.

Which will give us the way to troubleshoot further, Here are the all error id and reason related to Voice mail.


ErrorId
Header
SIP Request, Response
Reason string
15000
ms-diagnostics
Response
User properties not readable.
15001
ms-diagnostics
Response
Unexpected exception sending to UM.
15002
ms-diagnostics
Response
Unable to determine dial plan.
15003
ms-diagnostics
Response
Dial plan is unknown.
15004
ms-diagnostics
Response
Dial plan has no servers.
15005
ms-diagnostics
Response
UM server 302 with wrong contact count.
15006
ms-diagnostics
Response
UM server sent unexpected 302 response.
15007
ms-diagnostics
Response
UM server did not respond to request.
15008
ms-diagnostics
Response
Routing to UM for Subscriber Access.
15009
ms-diagnostics
Response
Routing to UM for Auto-Attendant.
15010
ms-diagnostics
Response
Routing to UM for voice mail deposit.
15011
ms-diagnostics
Response
Attempting PSTN rerouting.
15012
ms-diagnostics
Response
PSTN re-routing is either not enabled, or not fully configured.
15013
ms-diagnostics
Response
No Hosted Voicemail Policy could be found for the user.
15014
ms-diagnostics
Response
Hosted Voicemail Policy assigned to the user is not fully configured. Destination or Organization might be null.
15015
ms-diagnostics
Response
ExUM Routing Application is in an unexpected state.
15016
ms-diagnostics
Response
Phone number is not properly configured for the AA/SA contact object.
15017
ms-diagnostics
Response
Exchange Server did not respond in time.
15018
ms-diagnostics
Response
Client transaction cancelled before final response from Exchange.
15019
ms-diagnostics
Response
Client transaction terminated before final response from Exchange.
15020
ms-diagnostics
Response
Too many 303 redirects.
15021
ms-diagnostics
Response
No contact header in 303 redirect.
15022
ms-diagnostics
Response
Invalid contact header in 303 redirect.
15023
ms-diagnostics
Response
Re-directing request to the destination in 303.
15024
ms-diagnostics
Response
Unexpected non-audio single-part SDP request targeted to voicemail routing.
15025
ms-diagnostics
Response
Unexpected non-audio multi-part SDP request targeted to voicemail routing.
15026
ms-diagnostics
Response
Unexpected non-audio non-SDP request targeted to voicemail routing.
15027
ms-diagnostics
Response
Unexpected dispatch failure.
15028
ms-diagnostics
Response
Target User is not Um Enabled.
15029
ms-diagnostics
Response
No diagnostic information found.
15030
ms-diagnostics
Response
Failed to route to Exchange Server.
15031
ms-diagnostics
Response
Exchange Server returned invalid redirection response.
15032
ms-diagnostics
Response
Re-directing request to the destination in 302.
15033
ms-diagnostics
Response
Failed to route call from public IM network to Exchange Unified Messaging servers.
15034
ms-diagnostics
Response
Failed to route to Exchange Unified Messaging server.