O G
asked on
Strange Exchange 2010 issues
Dear Exchange experts,
I am having a very strange Exchange issue. Here is a little background information. On Sunday We needed to restore an older database from our backups. After successful restore i opened the database with a third party Quest software. I had to installed Outlook (MAPI) for the software to run. We restore emails that we needed to.
On Monday several users complained that on Sunday they were getting prompted for password while working from home and Outlook would not accept password, but OWA did. When in the office, Outlook works fine.
On Tuesday i arrive to the office and i get an error message while launching Outlook saying that my mailbox was moved and i had an option use temporary mailbox or offline version. The only way to fix this was to delete the profile. Which i did.
Throughout the day i sent bunch of emails and never got responses to. Towards the end of the evening i confirmed with one user that my email from an hour ago didn't go through, when i resent it, it went through right away.
I get home, open my outlook and all mail in inbox is missing except Brand new bounce back emails from the entire day. I log into my OWA and all of my mail is there, but the bounce back emails are not. Below is an example of two bounce back emails. Any suggestions how to start troubleshooting this issue?
We are using Exchange 2010, not 365.
From: Microsoft Outlook
Sent: Tuesday, March 13, 2018 9:33 AM
To: User1
Subject: Undeliverable: RE: Sick Today
Your message couldn't be delivered to multiple recipients.
The recipients weren't found at the destination domains.
user1 Office 365 Recipients
Action Required Recipients
Unknown To address
Couldn't deliver to the following recipients:
user2@domain2.com, user3@domain1.com, User4@domain2.com
How to Fix It
The address may be misspelled or may not exist. Try one or more of the following:
• Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose Send Again from the Report ribbon. In Outlook on the web, select this NDR, then select the link "To send this message again, click here." Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don't select it. After typing the complete address, click Send.
• Contact the recipient (by phone, for example) to check that the address exists and is correct.
• The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly.
• Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article: Fix email delivery issues for error code 5.1.10 in Office 365, and then send the message again. Retype the entire recipient address before selectingSend.
If the problem continues, forward this message to your email admin. If you're an email admin, refer to the More Info for Email Adminssection below.
Was this helpful? Send feedback to Microsoft.
__________________________
More Info for Email Admins
Status code: 550 5.1.10
This error occurs because the sender sent a message to an email address hosted by Office 365 but the address is incorrect or doesn't exist at the destination domain. The error is reported by the recipient domain's email server, but most often it must be fixed by the person who sent the message. If the steps in the How to Fix It section above don't fix the problem, and you're the email admin for the recipient, try one or more of the following:
The email address exists and is correct - Confirm that the recipient address exists, is correct, and is accepting messages.
Synchronize your directories - If you have a hybrid environment and are using directory synchronization make sure the recipient's email address is synced correctly in both Office 365 and in your on-premises directory.
Errant forwarding rule - Check for forwarding rules that aren't behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature.
Recipient has a valid license - Make sure the recipient has an Office 365 license assigned to them. The recipient's email admin can use the Office 365 admin center to assign a license (Users > Active Users > select the recipient > Assigned License > Edit).
Mail flow settings and MX records are not correct - Misconfigured mail flow or MX record settings can cause this error. Check your Office 365 mail flow settings to make sure your domain and any mail flow connectors are set up correctly. Also, work with your domain registrar to make sure the MX records for your domain are configured correctly.
For more information and additional tips to fix this issue, see Fix email delivery issues for error code 5.1.10 in Office 365.
Original Message Details
Created Date: 3/13/2018 1:33:00 PM
Sender Address: user1@domain1.com
Recipient Address: user2@domain2.com, user3@domain1.com, . . .
Subject: RE: Sick Today
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotF
DSN generated by: BLUPR17MB0020.namprd17.pro
Message Hops
HOP TIME (UTC) FROM TO WITH RELAY TIME
1 3/13/2018
1:33:00 PM BLUPR17MB0452.namprd17.pro
BLUPR17MB0452.namprd17.pro
mapi *
2 3/13/2018
1:33:02 PM BLUPR17MB0452.namprd17.pro
BLUPR17MB0020.namprd17.pro
Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_
Original Message Headers
Authentication-Results: domain2.com; dkim=none (message not signed)
header.d=none;domain2.com;
header.from=domain1.com;
Received: from BLUPR17MB0452.namprd17.pro
BLUPR17MB0020.namprd17.pro
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_
15.20.548.13; Tue, 13 Mar 2018 13:33:02 +0000
Received: from BLUPR17MB0452.namprd17.pro
([fe80::4b8:a916:6a8d:a1c6
([fe80::4b8:a916:6a8d:a1c6
13:33:00 +0000
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding:
From: Oleg Gudym <user1@domain1.com>
To: Andy Michalski <user2@domain2.com>
CC: Marcelo Motta <User3@domain1.com>, Andrea Zeman
<user3@domain1.com>, "Albina, Ballali" <User4@domain2.com>
Subject: RE: Sick Today
Thread-Topic: Sick Today
Thread-Index: AdO6z2ytoQGFhNKsRDWMz/7Af6
Date: Tue, 13 Mar 2018 13:33:00 +0000
Message-ID: <BLUPR17MB0452F604E17852A7
References: <A929E6263B1A654D8B9403EAA
In-Reply-To: <A929E6263B1A654D8B9403EAA
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator: <BLUPR17MB0452F604E17852A7
MIME-Version: 1.0
X-Originating-IP: [50.193.154.113]
X-MS-PublicTrafficType: Email
X-Microsoft-Exchange-Diagn
X-MS-Exchange-Antispam-SRF
X-Forefront-Antispam-Repor
SFV:SKI;SCL:-1;SFV:SKI;SFS
Return-Path: user1@domain1.com
X-MS-Office365-Filtering-C
X-Microsoft-Antispam:
UriScan:;BCL:0;PCL:0;RULEI
X-Microsoft-Exchange-Diagn
1;BLUPR17MB0020;3:9PDA1dlY
X-MS-TrafficTypeDiagnostic
X-Exchange-Antispam-Report
X-Exchange-Antispam-Report
BCL:0;PCL:0;RULEID:(910152
X-Microsoft-Exchange-Diagn
1;BLUPR17MB0020;4:ZM46gBFf
X-Microsoft-Antispam-Messa
cnPkLzAX6I2EmTSKHnfaojRsHH
X-Microsoft-Exchange-Diagn
1;BLUPR17MB0020;5:2ymu6BhB
SpamDiagnosticOutput: 1:0
X-MS-Exchange-CrossTenant-
(UTC)
X-MS-Exchange-CrossTenant-
X-MS-Exchange-CrossTenant-
X-MS-Exchange-CrossTenant-
X-MS-Exchange-Transport-Cr
--------------------------
From: Microsoft Outlook
Sent: Monday, March 12, 2018 3:57 PM
To: User1
Subject: Undeliverable:
Your message to user2@domain2.com couldn't be delivered.
user2 wasn't found at domain2.com.
user1 Office 365 user2
Action Required Recipient
Unknown To address
How to Fix It
The address may be misspelled or may not exist. Try one or more of the following:
• Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose Send Again from the Report ribbon. In Outlook on the web, select this NDR, then select the link "To send this message again, click here." Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don't select it. After typing the complete address, click Send.
• Contact the recipient (by phone, for example) to check that the address exists and is correct.
• The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly.
• Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article: Fix email delivery issues for error code 5.1.10 in Office 365, and then send the message again. Retype the entire recipient address before selectingSend.
If the problem continues, forward this message to your email admin. If you're an email admin, refer to the More Info for Email Adminssection below.
Was this helpful? Send feedback to Microsoft.
__________________________
More Info for Email Admins
Status code: 550 5.1.10
This error occurs because the sender sent a message to an email address hosted by Office 365 but the address is incorrect or doesn't exist at the destination domain. The error is reported by the recipient domain's email server, but most often it must be fixed by the person who sent the message. If the steps in the How to Fix It section above don't fix the problem, and you're the email admin for the recipient, try one or more of the following:
The email address exists and is correct - Confirm that the recipient address exists, is correct, and is accepting messages.
Synchronize your directories - If you have a hybrid environment and are using directory synchronization make sure the recipient's email address is synced correctly in both Office 365 and in your on-premises directory.
Errant forwarding rule - Check for forwarding rules that aren't behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature.
Recipient has a valid license - Make sure the recipient has an Office 365 license assigned to them. The recipient's email admin can use the Office 365 admin center to assign a license (Users > Active Users > select the recipient > Assigned License > Edit).
Mail flow settings and MX records are not correct - Misconfigured mail flow or MX record settings can cause this error. Check your Office 365 mail flow settings to make sure your domain and any mail flow connectors are set up correctly. Also, work with your domain registrar to make sure the MX records for your domain are configured correctly.
For more information and additional tips to fix this issue, see Fix email delivery issues for error code 5.1.10 in Office 365.
Original Message Details
Created Date: 3/12/2018 7:57:01 PM
Sender Address: user1@domain1.com
Recipient Address: user2@domain2.com
Subject: MirrorCast in the conference room
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotF
DSN generated by: BLUPR17MB0434.namprd17.pro
Message Hops
HOP TIME (UTC) FROM TO WITH RELAY TIME
1 3/12/2018
7:57:02 PM BLUPR17MB0452.namprd17.pro
BLUPR17MB0452.namprd17.pro
mapi 1 sec
2 3/12/2018
7:57:02 PM BLUPR17MB0452.namprd17.pro
BLUPR17MB0434.namprd17.pro
Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_
Original Message Headers
Authentication-Results: domain1.com; dkim=none (message not signed)
header.d=none;domain1.com;
header.from=domain1.com;
Received: from BLUPR17MB0452.namprd17.pro
BLUPR17MB0434.namprd17.pro
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_
15.20.567.14; Mon, 12 Mar 2018 19:57:02 +0000
Received: from BLUPR17MB0452.namprd17.pro
([fe80::4cc4:75f5:93d0:256
([fe80::4cc4:75f5:93d0:256
2018 19:57:02 +0000
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding:
From: Oleg Gudym <user1@domain1.com>
To: Nate Carpenter <user3@domain1.com>, Adam Norris
<user4@domain1.com>
CC: Andy Michalski <user2@domain2.com>, Marcelo Motta
<User3@domain1.com>
Subject: MirrorCast in the conference room
Thread-Topic: MirrorCast in the conference room
Thread-Index: AdO6O18iDIiHzuv4QMWajyKvCi
Date: Mon, 12 Mar 2018 19:57:01 +0000
Message-ID: <BLUPR17MB045228556BF4306A
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: <BLUPR17MB045228556BF4306A
MIME-Version: 1.0
X-Originating-IP: [50.193.154.113]
X-MS-PublicTrafficType: Email
X-Microsoft-Exchange-Diagn
X-MS-Exchange-Antispam-SRF
Return-Path: user1@domain1.com
X-MS-Office365-Filtering-C
X-Microsoft-Antispam:
UriScan:;BCL:0;PCL:0;RULEI
X-Microsoft-Exchange-Diagn
1;BLUPR17MB0434;3:nDvznln2
X-MS-TrafficTypeDiagnostic
X-Exchange-Antispam-Report
UriScan:(28532068793085)(2
X-Exchange-Antispam-Report
BCL:0;PCL:0;RULEID:(102415
X-Microsoft-Exchange-Diagn
1;BLUPR17MB0434;4:0lp4a5On
X-Forefront-Antispam-Repor
SFV:SKI;SFS:;DIR:INB;SFP:;
X-Microsoft-Antispam-Messa
cHiIEjdXoNBRXlp03lJtMC87VY
X-Microsoft-Exchange-Diagn
1;BLUPR17MB0434;6:XodiOqYJ
SpamDiagnosticOutput: 1:0
X-Microsoft-Exchange-Diagn
1;BLUPR17MB0434;7:pyUVApNC
X-MS-Exchange-CrossTenant-
(UTC)
X-MS-Exchange-CrossTenant-
X-MS-Exchange-CrossTenant-
X-MS-Exchange-CrossTenant-
X-MS-Exchange-Transport-Cr
I am having a very strange Exchange issue. Here is a little background information. On Sunday We needed to restore an older database from our backups. After successful restore i opened the database with a third party Quest software. I had to installed Outlook (MAPI) for the software to run. We restore emails that we needed to.
On Monday several users complained that on Sunday they were getting prompted for password while working from home and Outlook would not accept password, but OWA did. When in the office, Outlook works fine.
On Tuesday i arrive to the office and i get an error message while launching Outlook saying that my mailbox was moved and i had an option use temporary mailbox or offline version. The only way to fix this was to delete the profile. Which i did.
Throughout the day i sent bunch of emails and never got responses to. Towards the end of the evening i confirmed with one user that my email from an hour ago didn't go through, when i resent it, it went through right away.
I get home, open my outlook and all mail in inbox is missing except Brand new bounce back emails from the entire day. I log into my OWA and all of my mail is there, but the bounce back emails are not. Below is an example of two bounce back emails. Any suggestions how to start troubleshooting this issue?
We are using Exchange 2010, not 365.
From: Microsoft Outlook
Sent: Tuesday, March 13, 2018 9:33 AM
To: User1
Subject: Undeliverable: RE: Sick Today
Your message couldn't be delivered to multiple recipients.
The recipients weren't found at the destination domains.
user1 Office 365 Recipients
Action Required Recipients
Unknown To address
Couldn't deliver to the following recipients:
user2@domain2.com, user3@domain1.com, User4@domain2.com
How to Fix It
The address may be misspelled or may not exist. Try one or more of the following:
• Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose Send Again from the Report ribbon. In Outlook on the web, select this NDR, then select the link "To send this message again, click here." Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don't select it. After typing the complete address, click Send.
• Contact the recipient (by phone, for example) to check that the address exists and is correct.
• The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly.
• Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article: Fix email delivery issues for error code 5.1.10 in Office 365, and then send the message again. Retype the entire recipient address before selectingSend.
If the problem continues, forward this message to your email admin. If you're an email admin, refer to the More Info for Email Adminssection below.
Was this helpful? Send feedback to Microsoft.
__________________________
More Info for Email Admins
Status code: 550 5.1.10
This error occurs because the sender sent a message to an email address hosted by Office 365 but the address is incorrect or doesn't exist at the destination domain. The error is reported by the recipient domain's email server, but most often it must be fixed by the person who sent the message. If the steps in the How to Fix It section above don't fix the problem, and you're the email admin for the recipient, try one or more of the following:
The email address exists and is correct - Confirm that the recipient address exists, is correct, and is accepting messages.
Synchronize your directories - If you have a hybrid environment and are using directory synchronization make sure the recipient's email address is synced correctly in both Office 365 and in your on-premises directory.
Errant forwarding rule - Check for forwarding rules that aren't behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature.
Recipient has a valid license - Make sure the recipient has an Office 365 license assigned to them. The recipient's email admin can use the Office 365 admin center to assign a license (Users > Active Users > select the recipient > Assigned License > Edit).
Mail flow settings and MX records are not correct - Misconfigured mail flow or MX record settings can cause this error. Check your Office 365 mail flow settings to make sure your domain and any mail flow connectors are set up correctly. Also, work with your domain registrar to make sure the MX records for your domain are configured correctly.
For more information and additional tips to fix this issue, see Fix email delivery issues for error code 5.1.10 in Office 365.
Original Message Details
Created Date: 3/13/2018 1:33:00 PM
Sender Address: user1@domain1.com
Recipient Address: user2@domain2.com, user3@domain1.com, . . .
Subject: RE: Sick Today
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotF
DSN generated by: BLUPR17MB0020.namprd17.pro
Message Hops
HOP TIME (UTC) FROM TO WITH RELAY TIME
1 3/13/2018
1:33:00 PM BLUPR17MB0452.namprd17.pro
BLUPR17MB0452.namprd17.pro
mapi *
2 3/13/2018
1:33:02 PM BLUPR17MB0452.namprd17.pro
BLUPR17MB0020.namprd17.pro
Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_
Original Message Headers
Authentication-Results: domain2.com; dkim=none (message not signed)
header.d=none;domain2.com;
header.from=domain1.com;
Received: from BLUPR17MB0452.namprd17.pro
BLUPR17MB0020.namprd17.pro
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_
15.20.548.13; Tue, 13 Mar 2018 13:33:02 +0000
Received: from BLUPR17MB0452.namprd17.pro
([fe80::4b8:a916:6a8d:a1c6
([fe80::4b8:a916:6a8d:a1c6
13:33:00 +0000
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding:
From: Oleg Gudym <user1@domain1.com>
To: Andy Michalski <user2@domain2.com>
CC: Marcelo Motta <User3@domain1.com>, Andrea Zeman
<user3@domain1.com>, "Albina, Ballali" <User4@domain2.com>
Subject: RE: Sick Today
Thread-Topic: Sick Today
Thread-Index: AdO6z2ytoQGFhNKsRDWMz/7Af6
Date: Tue, 13 Mar 2018 13:33:00 +0000
Message-ID: <BLUPR17MB0452F604E17852A7
References: <A929E6263B1A654D8B9403EAA
In-Reply-To: <A929E6263B1A654D8B9403EAA
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator: <BLUPR17MB0452F604E17852A7
MIME-Version: 1.0
X-Originating-IP: [50.193.154.113]
X-MS-PublicTrafficType: Email
X-Microsoft-Exchange-Diagn
X-MS-Exchange-Antispam-SRF
X-Forefront-Antispam-Repor
SFV:SKI;SCL:-1;SFV:SKI;SFS
Return-Path: user1@domain1.com
X-MS-Office365-Filtering-C
X-Microsoft-Antispam:
UriScan:;BCL:0;PCL:0;RULEI
X-Microsoft-Exchange-Diagn
1;BLUPR17MB0020;3:9PDA1dlY
X-MS-TrafficTypeDiagnostic
X-Exchange-Antispam-Report
X-Exchange-Antispam-Report
BCL:0;PCL:0;RULEID:(910152
X-Microsoft-Exchange-Diagn
1;BLUPR17MB0020;4:ZM46gBFf
X-Microsoft-Antispam-Messa
cnPkLzAX6I2EmTSKHnfaojRsHH
X-Microsoft-Exchange-Diagn
1;BLUPR17MB0020;5:2ymu6BhB
SpamDiagnosticOutput: 1:0
X-MS-Exchange-CrossTenant-
(UTC)
X-MS-Exchange-CrossTenant-
X-MS-Exchange-CrossTenant-
X-MS-Exchange-CrossTenant-
X-MS-Exchange-Transport-Cr
--------------------------
From: Microsoft Outlook
Sent: Monday, March 12, 2018 3:57 PM
To: User1
Subject: Undeliverable:
Your message to user2@domain2.com couldn't be delivered.
user2 wasn't found at domain2.com.
user1 Office 365 user2
Action Required Recipient
Unknown To address
How to Fix It
The address may be misspelled or may not exist. Try one or more of the following:
• Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose Send Again from the Report ribbon. In Outlook on the web, select this NDR, then select the link "To send this message again, click here." Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don't select it. After typing the complete address, click Send.
• Contact the recipient (by phone, for example) to check that the address exists and is correct.
• The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly.
• Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article: Fix email delivery issues for error code 5.1.10 in Office 365, and then send the message again. Retype the entire recipient address before selectingSend.
If the problem continues, forward this message to your email admin. If you're an email admin, refer to the More Info for Email Adminssection below.
Was this helpful? Send feedback to Microsoft.
__________________________
More Info for Email Admins
Status code: 550 5.1.10
This error occurs because the sender sent a message to an email address hosted by Office 365 but the address is incorrect or doesn't exist at the destination domain. The error is reported by the recipient domain's email server, but most often it must be fixed by the person who sent the message. If the steps in the How to Fix It section above don't fix the problem, and you're the email admin for the recipient, try one or more of the following:
The email address exists and is correct - Confirm that the recipient address exists, is correct, and is accepting messages.
Synchronize your directories - If you have a hybrid environment and are using directory synchronization make sure the recipient's email address is synced correctly in both Office 365 and in your on-premises directory.
Errant forwarding rule - Check for forwarding rules that aren't behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature.
Recipient has a valid license - Make sure the recipient has an Office 365 license assigned to them. The recipient's email admin can use the Office 365 admin center to assign a license (Users > Active Users > select the recipient > Assigned License > Edit).
Mail flow settings and MX records are not correct - Misconfigured mail flow or MX record settings can cause this error. Check your Office 365 mail flow settings to make sure your domain and any mail flow connectors are set up correctly. Also, work with your domain registrar to make sure the MX records for your domain are configured correctly.
For more information and additional tips to fix this issue, see Fix email delivery issues for error code 5.1.10 in Office 365.
Original Message Details
Created Date: 3/12/2018 7:57:01 PM
Sender Address: user1@domain1.com
Recipient Address: user2@domain2.com
Subject: MirrorCast in the conference room
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotF
DSN generated by: BLUPR17MB0434.namprd17.pro
Message Hops
HOP TIME (UTC) FROM TO WITH RELAY TIME
1 3/12/2018
7:57:02 PM BLUPR17MB0452.namprd17.pro
BLUPR17MB0452.namprd17.pro
mapi 1 sec
2 3/12/2018
7:57:02 PM BLUPR17MB0452.namprd17.pro
BLUPR17MB0434.namprd17.pro
Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_
Original Message Headers
Authentication-Results: domain1.com; dkim=none (message not signed)
header.d=none;domain1.com;
header.from=domain1.com;
Received: from BLUPR17MB0452.namprd17.pro
BLUPR17MB0434.namprd17.pro
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_
15.20.567.14; Mon, 12 Mar 2018 19:57:02 +0000
Received: from BLUPR17MB0452.namprd17.pro
([fe80::4cc4:75f5:93d0:256
([fe80::4cc4:75f5:93d0:256
2018 19:57:02 +0000
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding:
From: Oleg Gudym <user1@domain1.com>
To: Nate Carpenter <user3@domain1.com>, Adam Norris
<user4@domain1.com>
CC: Andy Michalski <user2@domain2.com>, Marcelo Motta
<User3@domain1.com>
Subject: MirrorCast in the conference room
Thread-Topic: MirrorCast in the conference room
Thread-Index: AdO6O18iDIiHzuv4QMWajyKvCi
Date: Mon, 12 Mar 2018 19:57:01 +0000
Message-ID: <BLUPR17MB045228556BF4306A
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: <BLUPR17MB045228556BF4306A
MIME-Version: 1.0
X-Originating-IP: [50.193.154.113]
X-MS-PublicTrafficType: Email
X-Microsoft-Exchange-Diagn
X-MS-Exchange-Antispam-SRF
Return-Path: user1@domain1.com
X-MS-Office365-Filtering-C
X-Microsoft-Antispam:
UriScan:;BCL:0;PCL:0;RULEI
X-Microsoft-Exchange-Diagn
1;BLUPR17MB0434;3:nDvznln2
X-MS-TrafficTypeDiagnostic
X-Exchange-Antispam-Report
UriScan:(28532068793085)(2
X-Exchange-Antispam-Report
BCL:0;PCL:0;RULEID:(102415
X-Microsoft-Exchange-Diagn
1;BLUPR17MB0434;4:0lp4a5On
X-Forefront-Antispam-Repor
SFV:SKI;SFS:;DIR:INB;SFP:;
X-Microsoft-Antispam-Messa
cHiIEjdXoNBRXlp03lJtMC87VY
X-Microsoft-Exchange-Diagn
1;BLUPR17MB0434;6:XodiOqYJ
SpamDiagnosticOutput: 1:0
X-Microsoft-Exchange-Diagn
1;BLUPR17MB0434;7:pyUVApNC
X-MS-Exchange-CrossTenant-
(UTC)
X-MS-Exchange-CrossTenant-
X-MS-Exchange-CrossTenant-
X-MS-Exchange-CrossTenant-
X-MS-Exchange-Transport-Cr
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It did not mount the database on the Exchange. I also know that Rapid Recovery didn't mess with Exchange because i worked at Dell on backup and recovery team and we used this software to Exchange restores. Basically what it does just opens unmounted database and you're able to drill down to a single mailbox and restore a PST.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
@Alen - Suggesting Exchange server is broken without more details is a bit extreme. Exchange server working fine without any issues.
What ended up happening is this client has Office 365 Business premium subscription. Office 365 Business plan comes with Online Exchange. My AD and Office 365 password was the same. For some reason Outlook connected to Office 365 Exchange instead of our in house Exchange server. I opened a support ticket with MS, they are still trying to figure out why this happened. Same issue happened to another user in our organization, right after his AD password expired and he changed it to whatever his Office 365 password was. Has anyone experienced this issue before?
What ended up happening is this client has Office 365 Business premium subscription. Office 365 Business plan comes with Online Exchange. My AD and Office 365 password was the same. For some reason Outlook connected to Office 365 Exchange instead of our in house Exchange server. I opened a support ticket with MS, they are still trying to figure out why this happened. Same issue happened to another user in our organization, right after his AD password expired and he changed it to whatever his Office 365 password was. Has anyone experienced this issue before?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Options for resolving given.
ASKER
Yes, but the restore was not through exchange server. Restore was through a third part application to a completely different volume on the server. So basically i restored a database from 2015, opened it with a third party app and restored a single mailbox to a PST file. I did try ti create a new recovery database and point it to the restored DB, but received an error and didn't move forward. What do you think?