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


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.

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"


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 $ -AccessRights SendAs –Trustee "" -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 $ -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 $ -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.

DownloadDownload the 32-bit Lync update package now.

DownloadDownload the 64-bit Lync update package now.


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".


Happy Learning.