Monday, January 23, 2017

Undo Send Feature to OWA-Office 365

We are the human and sometime we make the mistake, write the email in anger or after written/send messages we released we need to modify the messages or not to send email. Lot of time this will change our mind — so once we clicked “Send” we’ll see an option to reverse it on your screen for between 5 and 30 seconds, depending on what we’ve indicated in the settings.

As we all know google introduced Undo Send in Gmail March 2009, where users can manually enable on to use. Latter June 2015, Google made the Undo Send feature an official part of the Gmail.

Microsoft derivative another feature from Gmail, Undo Send for email delaying the delivery of messages, we can set 30 seconds the option to stop the sending messages.

You can find the relevant settings under OWA -> Options -> Mail -> Automatic processing -> Undo send.


Undo Send works as of now in OWA for office 365, Undo Send works a delay before OWA transmits an outbound message to the server, during this period, the message stay in the draft folder and can be recalled by clicking the Undo button and when the delay period elapses, OWA sends the message is transmitted to the server.

You can enabled a settings through OWA options and you can decide whether to enable the feature or not, as of now you can set minimum 5 seconds and maximum is 30 seconds delay. Again you can set the time as per your convenience.  One important things if you close browser then this features will not work.

Once you sent email and want to Undo then you can see on your right side on top the option to do Undo.



There is no option to enable Undo Send feature is in on premises Exchange mailboxes and use Power Shell because it is client side OWA features.

Microsoft already have the option to recall message which is in the Outlook desktop client, when we released to recall a message, if the recipients opened and read the messages then it will not worthy, again message recall mostly works on if the everyone mailboxes are in the same organization and uses outlook. If the message reached on mobile clients or transfer via a connector to another system then recall will not work. Recall feature is not available in OWA as of now hope Microsoft will replicate very soon.

Microsoft already replicated Undo Send to Outlook.com & Hotmail.com, you can enable features on your personal emails also.



Thank you!

Happy Learning!











Friday, January 20, 2017

Exchange Server Cross forest Mailbox Move Active Directory error 0x51

Problem

I'm working on project cross forest mailboxes migration it was running very smooth while migrating mailboxes from source to target forest, but suddenly customer asked me to move back some of the mailboxes due to some business critical issues. When  started to move back the mailboxes got the following error

An Active Directory error 0x51 occurred when trying to check the suitability of server 'tech.us.com'. Error: '
Active directory response: The LDAP server is unavailable.'
    + CategoryInfo          : NotSpecified: (0:Int32) [New-MoveRequest], RemoteTransientException
    + FullyQualifiedErrorId : 2946EE38,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest
LDAP connectivity is fine either way.


This is the actual issues here:

Forest A to Forest B- mailboxes migration working fine.
Forest B to Forest A - Getting error

Workaround

\Prepare-MoveRequest.ps1 working fine and it shows all ready for migration mailboxes, when i initiated New-MoveRequest it through the error.

In my scenario customer does not have the Active Directory trust between forest, only we configured DNS and everything fine.

Initially i suspected LDAP communication as error stating, when i checked and telnet the 389 from  Forest A to Forest B and vice versa working as expected.

When i checked the event ID and got the clue with error event ID 6, what is the actual issues which i can not imagine because it is basic requirement for migration and wondering.
After dinging on issues got the root cause that from Forest B to Forest A Global Catalog port tcp/3268 was blocked. Issue with Global Catalog communication from Forest B to Forest A. MailboxReplicationService connection getting failed to connect RemoteGlobalCatalog server.

Telnet getting failed to Forest A Global Catalog servers.

Once i open port in firewall after change  mailbox migration working fine both side.

Now, decided to check everything before taking handover the any projects :)

 You can check the deep dive cross forest migration from here

Thank you!


Thursday, January 12, 2017

Microsoft StaffHub—New App for Deskless Workers- Office 365

Microsoft unveiled the new application called “StaffHub” for office 365, this application for shift workers and management and mainly focus on those who don’t work on desktop computers and have different schedules from week to week, such as hospitality, retail, restaurants, factories or other locales and who typically lack their own office, desk or computer but often do own a smartphone.

Microsoft StaffHub is a cloud-based platform that works across all your devices. It enables staff workers and their managers to manage time, communicate with their teams, and share content.

This mobile app works across device and make easy for managers to create, update and revise their employee schedules and send information, documents, videos to their teams. Team members can view upcoming shifts on their mobile devices, if the any team member want to swap shift with coworkers they can send messages directly to each other or entire team. Employee can access and Interact with this information from StuffHub mobile apps on their iOS and Android devices.

Team managers can sign in at staffhub.ms, and employees can download the free app on iOS or Android. Each team member and manager using StaffHub needs to have an Office 365 account.

Manager -Easily shift schedules

Manager, who have the access to desktop/Laptop computers, may use the web version of StaffHub to create the staff schedules in the program and employee can only use StaffHub from their mobile phones.

                                                Picture Courtesy from Microsoft


You can add a shift for an employee at any time by clicking a cell and entering the shift details. Also you can copy the entire shift details from previous week if your team members schedule is same, once you schedule you can publish it will automatically pushed the notification/updates to your team member so that you team members will be up-to-date.


Your team members can access their all schedule on mobile app, team members can view summary of their shift with any important notes, also can see the who else are in shift.

                                             Picture Courtesy from Microsoft


In addition to the calendar, there's a separate area for posting documents like employee handbooks, and a messaging platform for quick communication between everyone on the team.

We observed in our daily work sometime schedule conflicts, same can possible on StaffHub, but via StaffHub you can also swap a shift to your co-worker and request always routed via manager approval and update will notify to entire team.

                                                     Picture Courtesy from Microsoft


Microsoft is encouraging companies to centralize all of their workplace communication needs in one place. Microsoft also recognizes that large companies have several different vendors for different tasks, so it plans to let third-party tools have access to StaffHub. It's possible to build custom integrations with Microsoft PowerApps, or for a limited group of beta testers, to take advantage of a built-in integration with the Kronos human resources platform.


Plans & Pricing

The application, immediately available to all Office 365 corporate licensees  with K1, E1, E3 or E5 plans. for pricing & plan you can click here 




More details click here

References : https://blogs.office.com/2017/01/12/microsoft-staffhub-is-here/


Thank you!

Cheers!

Exchange Error-432 4.3.2 STOREDRV.Deliver; recipient thread limit exceeded

Problem

Email stuck up in the Exchange Submission Queue with errors are displayed in Queue Viewer "432 4.3.2 STOREDRV.Deliver; recipient thread limit exceeded"

This issues could be a large volume of emails to Public Folder. In these cases, administrators will see mail queues with the this error.

Some time this issues occur due to throttling/back pressure, but we have to dig dive the issues before going to conclude. Also Exchange 2010 SP1 Exchange Team written post for "Store Driver Fault Isolation Improvements in Exchange 2010 SP1" which gives good understanding the Store drive and related issues and solutions.

Solution

Solution which i executed to create the following two keys to the EdgeTransport.exe.config file (\Program Files\Microsoft\Exchange server\V15\Bin).


For Exchange 2013/2016 these two keys need to be added to the MSExchangedelivery.exe.config file located in the same folder!

After adding the keys, restart both the Microsoft Exchange Transport (MSExchangeTransport) and Microsoft Exchange Mailbox Transport Delivery (MSExchangeDelivery) services.


Thanks!


Friday, January 6, 2017

Released:Exchange Server Role Requirements Calculator v8.4

The Exchange Team released an updated version of the Exchange Server Role Requirements Calculator. This release focuses on bug fixes with the DAG auto-calculation functionality that was introduced in 8.3, as well as, support for ReplayLagMaxDelay.


New Functionality

Added support for ReplayLagMaxDelay
Added support for SafetyNetHoldTime in CreateDAG.ps1


Bug Fixes

Improved the DAG auto-calculation results display to highlight deployment configuration in both datacenters
Fixed an issue that prevented DAG auto-calculation in single site DAG deployments
Fixed a SPECInt2006 validation issue with DAG auto-calculation
Fixed a bug with the DAG auto-calculation with Active/Passive deployments
Fixed conditional formatting issues with the transaction log table
Removed data validation from certain unused cells on the Input tab
Fixed bug in calcNumActiveDBsSF formula

Download Exchange Server Role Requirements Calculator v8.4

You can follow Exchange Team Blog

Cheers!

Thank You!

Wednesday, January 4, 2017

Office 365 Groups with On-Premises Exchange hybrid

Office 365 Groups means sharing information and collaboration across groups and projects teams, even we are using different tools such as distribution groups, buddy list in Lync, groups in Yammer.

Office 365 Groups look like traditional Exchange distribution groups in that we can send a message to a group and have it delivered to all the group members. But the problem with distribution groups is that if you’re not a member of that group, you will not get the message and when you join the distribution group, you don’t have access to previous discussions/message.

Office 365 group is a more email distribution group because when we use a Group, it will store the message/information for any new members, and he can discover all message/information. It is between a distribution group and a public folder. If you want to more accurate comparison is to a combination of the distribution group and a site mailbox or share mailbox because when we look Share Point mixed to deliver the information.

Office 365 Groups is feature that enable to communicate, schedule meetings and collaborate on documents more easily. All information share/sent email with in a Group, file will stored in the groups OneDrive for business or SharePoint libraries.

If you have the Hybrid deployment between your on-premises Exchange organization and Office 365, you can also create the Groups in Office 365and it will available to On-premises users. It is very new feature in Office 365, here are the process how we can enable Office 365 Groups to On-premises users.

Prerequisites
Before we start for enabling the Office 365 Groups to on-premises, we have check the prerequisites, following are the list:
  • Premium licenses for Azure Active Directory on your tenant which will help to enable the groups write back feature in Azure Active Directory Connect (AAD).
  • Well functioned hybrid deployment between Exchange on-premises and Office 365.
  • Least CU1 or new releases for Exchange 2016, and CU11 or newer releases of Exchange 2013.
  • Configured Azure Active Directory Connect for single sign-on, which will allow users to click on view group files link in group email messages.

Enable Group write back in AAD Connect

We have to enable the group write back in Azure Active Directory Connect, following are the steps:

  • Open Azure AD connect wizard-Select Customize synchronization option->Next.

  • On the Connect your Directory page, give the Office 365 global administrator credentials--> Next.
  • On the Optional features page, we have to verify that the options we have configured are still selected. The most commonly-selected option are Exchange hybrid and Password hash synchronization.
  • Select Group write back-->Next.
  • On the Write Back page, select a location in AD to store objects that are synchronized from Office 365 to your on-premises organization and click next.
  • Now Ready to configure page-->Install.
  • When wizard is complete, click Exit on the Configuration complete page.


Configure a group domain

The default accepted domain in the organization is chosen as the domain for the primary SMTP address of Office 365 group when it created, this is called a group domain, here we have to setup a new sub-domain that will be used as the group domain, following are the steps:
  • Add the group domain as an accepted domain in the on-premises Exchange org with below PowerShell command
New-AcceptedDomain -Name groups.tech.com -DomainName groups.tech.com -DomainType InternalRelay
  • Add the new group domain to Office 365 Org.
  • Create the two DNS record with DNS provider
DNS Record Name- Group.tech.com
DNS record type- MX
DNS record value-group-tech.com.mail.protection.outlook.com

DNS Record Name- autodiscover.groups.tech.com
DNS record type-CNAME
DNS record value- autodiscover.outlook.com
  • Add the group domain to the hybrid send connector, which is created by the Hybrid Configuration wizards 
Set-SendConnector -Identity "Outbound to Office 365" -AddressSpaces "tech.mail.onmicrosoft.com","groups.tech.com"


Create the Office 365 Groups

We have multiple option to create the Office 365 Groups, here we will create the Groups via Outlook /OWA, steps are :

1. From your outlook from left hand side on bottom select Group right click and
    select New Group

  From OWA click on New and Select Group


2. Give the name of the Group and select the privacy 
                   From Outlook:
                 From OWA
3. Now time to add the user in Group
                       

4. Now we can check from Office 365 admin portal newly created Office 365  
    Groups, Select Group->Select Office 365 Groups from view (otherwise    
    you will see all the groups) then you can see all the Office 365 Groups in list.

5. Now you can view the created Groups details from outlook & OWA.

6. Once you add the user in Office 365 Groups user will get the automatic 
    Welcome email.




Test using an on-premises mailbox
  • Add an on-premises & Office 365 mailbox to an Office 365 group.
  • Log into the Office 365 mailbox using Outlook on the web.
  • Send a message to the group using the Office 365 mailbox & on-premises mailboxes.
  • Open the on-premises/Office 365 mailbox and verify the message received.
  • In the same mailbox, compose a reply to the message and send it to the group.
  • Verify that the message can be viewed by all of the members of the group.

Test using a mailbox moved to Office 365
  • Move a mailbox from your on-premises Exchange organization to Office 365.
  • Add the mailbox to an Office 365 group.
  • In a new browser session, log into the mailbox that was moved to Office 365.
  • In Outlook on the web, verify that the group is listed in the left navigation bar.
  • Post a message to the group.
  • Verify that the message can be viewed by all of the members of the group.

Known Issues 

Group don’t appear for mailboxes moved to Office365
        Remove the mailbox from any groups and re-add it to each group.

New groups don't appear in the on-premises Exchange GAL
        Update-Recipient “GroupName”

Groups don't receive messages from on-premises user
        Wait for next AAD Connect synchronization.

On-premises users can't use links included in group message footers
       Users should contact an group administrator.

Mail sent to a group's secondary SMTP address fails to be delivered
      Configure only one SMTP address on each group.


Find Ownerless Office 365 Groups

As we know every Group have the owner which is managing as per business required, but some time we find some of the group does not have the owner it is not good if a group doesn’t have any owners. Group members will still able to access all the group resources/messages but problem is that when some group administration in needed for any modification then we have to find someone who can work. We can find out ownerless Office 365 Groups with help of Exchange Godfather "Tony Redmond's" articles, where we can find the script to pull out the ownerless Office 365 Groups.

Using PowerShell to Locate Ownerless Office 365 Groups



Reference: 
https://blogs.office.com/2016/06/13/whats-new-in-office-365-groups-administration-june-2016-update/

Happy Learning!

Thanks!

Tuesday, January 3, 2017

RoutingMasterDN is pointing to an old server- Exchange 2013

I came the following errors in the Application Event Log in Exchange 2013 server:

Log Name:      Application
Source:        MSExchange ADAccess
Date:          12/16/2016 11:14:02 AM
Event ID:      2937
Task Category: Validation
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xxxxxxxxxxx
Description:
Process edgetransport.exe (Transport) (PID=32144). Object [CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=xxxxxx,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=xxxxx,DC=xxxxx]. Property [RoutingMasterDN] is set to value [xxxxxxxx
DEL:67729122-b25b-4d4c-b5b0-75ad9e9dacd4], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible.


Solution:

1. Open ADSIEdit and navigate to CN=Servers,CN=Exchange Administrative         Group (FYDIBOHF23SPDLT),CN=Administrative Groups,
    CN=domain,CN=MicrosoftExchange,CN=Services,CN=Configuration,  
    DC=domain,DC=com.

2. Right-click the Edge Transport server and copy the distinguishedName value.
3. Navigate to CN=Exchange Routing Group   
    (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange   
    Administrative Group (FYDIBOHF23SPDLT),CN=Administrative    
    Groups,CN=domain,CN=Microsoft
    Exchange,CN=Services,CN=Configuration,DC=domain,DC=com and open  
    properties paste the copied DN value to the msExchangeRoutingMasterDN 
    attribute.

In this issue, this attribute was pointing to an old Exchange 2010 server that had already been decommissioned. Once I corrected this, and restarted the Transport services, the issues resolved.


Happy Learning!

Thank You!


Monday, January 2, 2017

Remove Default Database-Exchange 2016

When we install Exchange server 2016, a default mailbox database is created automatically in default Exchange installation location and name is automatically created which doesn’t meet any naming convention. We have options to get the mailbox database as per our standard. First, we can rename the database which is simple to open the properties of database in EAC and edit the name but it won’t rename the .edb database file. To change the .edb file name, dismount the database and move the database new location,after that mount the database. we have another option to delete the default mailbox database and create a new one.

Here are the steps to delete the default mailbox database in Exchange 2016.

First view the default mailbox database location type following cmdlet

Get-MailboxDatabase -Identity "Mailbox Database 2095368010" | fl *filepath*

In order to delete the default mailbox database, first move all the mailboxes from default mailbox database to new mailbox database.

Create a new mailbox database. Then, move all user mailboxes to new database. Type following cmdlet to move all mailboxes from default mailbox database to DB1.

Get-Mailbox -Database "Mailbox Database 2095368010" | New-MoveRequest -TargetDatabase DB1

To view the arbitration mailboxes with following cmdlet:

Get-Mailbox -Database "Mailbox Database 2095368010"  -Arbitration

Now move the arbitration mailboxes with following cmdlet

Get-Mailbox -Database "Mailbox Database 2095368010" -Arbitration | New-MoveRequest -TargetDatabase "DB1"

You can view the move request

Get-MoveRequest

Now view the monitoring mailboxes with following cmdlet

Get-Mailbox -Database "Mailbox Database 2095368010" -Monitoring

Move monitoring mailboxes to newly created database

Get-Mailbox -Database "Mailbox Database 2095368010" -Monitoring | New-MoveRequest -TargetDatabase DB1

Now view the AuditLog mailboxes

Get-Mailbox -Database "Mailbox Database 2095368010" -AuditLog

Move the AuditLog mailboxes to new database

Get-Mailbox -Database "Mailbox Database 2095368010" -AuditLog | -TargetDatabase DB1

Once all mailboxes move to new Database than delete the default mailbox database:

Go to EAC-->Database-->Select default mailboxe database than click on Delete, click the Yes on confirmation page, then you will get a warning message which will says, you have to delete the database file from location.

Cheers!

Happy Learning.