Squan_JRP

Thank you for these resources, I'll work through the last article you linked to.

Thanks, we were a couple builds behind so we'll give that a try and see what happens.

We have an on-premises Exchange server (2019) which relays messages from on-premises clients (scanners, servers, etc.) and most of our user mailboxesare in Exchange Online. Over the past few days, some (but not all) messages relayed from them on-premises server to exchange online get delayed for up to nearly 2 hours. You can tell from the timestamps in the headers of the messages. As an example, this morning, I ran the Get-Queue command on my on-premises server. This showed 32 messages in the queue to my exchange online domain (myorg.mail.onmicrosoft.com). Some of the messages had been delayed over an hour. When I ran Get-Queue -Identity "8137" nearly all the messages showed as being in "ready" status. [html][/html] Nothing in queue was being delivered. I then ran Retry-Queue -Identity "8137" and within about a minute all the messages were delivered. As I noted, this has happened a few days in a row now and not sure why. I've rebooted the server and it still persists, sometimes. Can anyone suggest next steps to investigate why this is happening?

Hmm, okay, this was actually the 4th attempt I made to migrate it. This was the first time it even got this far.

We are running exchange 2013 in hybrid but still have some on-prem mailboxes. Recently added a new exchange 2019 server into the environment to migrate everything to so we can eliminate the 2013 server. Got it set up and tried migrating the first mailbox. It was a large mailbox of about 50GB. About 20 hours into the move, I got a confirmation email saying "The migration process failed to complete because it has encountered errors. You can fix these errors, and try to complete the migration again. Or you can complete the migration and select the option to ignore any errors associated with the migration." However, despite getting this, I could still see that the migration was still going using Get-MigrationUserStatistics command in the management shell. After about 3 days, I see from the same log that the migration is complete (see log entries below), but in the ECP it is still saying status as "Completed with errors" and saying "Failed mailboxes: 1" In the log entries from the management shell I can see things like "Copying messages is complete" and "Mailbox store finalization is complete" and "Mailbox contents verification complete." There is an option to complete the migration batch, but I am just nervous since it still says there were errors. Is it safe to complete the batch now or are there other things I should be checking first to make sure this is successful? Here's an except of the end of the log using Get-MigrationUserStatistics: 12/29/2019 4:18:49 AM [EXCHANGE19] Stage: CopyingMessages. Percent complete: 94. 12/29/2019 4:18:49 AM [EXCHANGE19] Copy progress: 796696/797488 messages, 50.56 GB (54,286,927,922 bytes)/50.6 GB (54,332,554,316 bytes), 10/62 folders completed. 12/29/2019 4:23:34 AM [EXCHANGE19] Copying messages is complete. Copying rules and security descriptors. 12/29/2019 4:23:49 AM [EXCHANGE19] Initial seeding completed, 797488 items copied, total size 50.6 GB (54,332,540,906 bytes). 12/29/2019 4:23:50 AM [EXCHANGE19] Stage: CopyingMessages. Percent complete: 95. 12/29/2019 4:23:50 AM [EXCHANGE19] Copy progress: 797488/797488 messages, 50.6 GB (54,332,540,906 bytes)/50.6 GB (54,332,540,906 bytes), 54/62 folders completed. 12/29/2019 4:23:50 AM [EXCHANGE19] Folder hierarchy changes reported in source '814f5c95-21e6-4b83-a3a1-5873d4bd1dbe (Primary)': 0 changed folders, 0 deleted folders. 12/29/2019 4:23:50 AM [EXCHANGE19] Total content changes applied to mailbox '814f5c95-21e6-4b83-a3a1-5873d4bd1dbe (Primary)': New 0, Changed 0, Deleted 0, Read 0, Unread 0, ItemUpdates 0, Skipped 0, Total 0. 12/29/2019 4:23:50 AM [EXCHANGE19] Incremental Sync '814f5c95-21e6-4b83-a3a1-5873d4bd1dbe (Primary)' completed: 0 hierarchy updates, 0 content changes. 12/29/2019 4:23:51 AM [EXCHANGE19] Stage: IncrementalSync. Percent complete: 95. 12/29/2019 4:23:51 AM [EXCHANGE19] Final sync has started. 12/29/2019 4:23:51 AM [EXCHANGE19] Folder hierarchy changes reported in source '814f5c95-21e6-4b83-a3a1-5873d4bd1dbe (Primary)': 0 changed folders, 0 deleted folders. 12/29/2019 4:23:51 AM [EXCHANGE19] Total content changes applied to mailbox '814f5c95-21e6-4b83-a3a1-5873d4bd1dbe (Primary)': New 0, Changed 0, Deleted 0, Read 0, Unread 0, ItemUpdates 0, Skipped 0, Total 0. 12/29/2019 4:23:52 AM [EXCHANGE19] Incremental Sync '814f5c95-21e6-4b83-a3a1-5873d4bd1dbe (Primary)' completed: 0 hierarchy updates, 0 content changes. 12/29/2019 4:23:52 AM [EXCHANGE19] Source mailbox information: Regular Items: 797463, 50.6 GB (54,332,541,763 bytes) Regular Deleted Items: 0, 0 B (0 bytes) FAI Items: 26, 30.52 KB (31,253 bytes) FAI Deleted Items: 0, 0 B (0 bytes) 12/29/2019 4:23:52 AM [EXCHANGE19] Stage: FinalIncrementalSync. Percent complete: 95. 12/29/2019 4:23:52 AM [EXCHANGE19] Copying per user read/unread data. 12/29/2019 4:23:52 AM [EXCHANGE19] Per user read/unread data copied successfully. 12/29/2019 4:23:53 AM [EXCHANGE19] Mailbox store finalization is complete. 12/29/2019 4:23:53 AM [EXCHANGE19] SessionStatistics updated. 12/29/2019 4:23:53 AM [EXCHANGE19] Verifying mailbox contents... 12/29/2019 4:30:06 AM [EXCHANGE19] Mailbox contents verification complete: 15 folders have been examined, 39 empty folders have been skipped, 797488 items, 50.6 GB (54,332,540,906 bytes). 12/29/2019 4:30:09 AM [EXCHANGE19] Mailbox 'ONPREMMailbox1' was loaded from domain controller 'DC1.domain.local'. 12/29/2019 4:30:09 AM [EXCHANGE19] Target mailbox information: Regular Items: 797463, 52.09 GB (55,926,039,968 bytes) Regular Deleted Items: 0, 0 B (0 bytes) FAI Items: 26, 34.44 KB (35,269 bytes) FAI Deleted Items: 0, 0 B (0 bytes) 12/29/2019 4:30:34 AM [EXCHANGE19] PrimarySize: 55926039968, ArchiveSize: 0, DumpsterSize: 0, ArchiveDumpsterSize: 0 12/29/2019 4:30:34 AM [EXCHANGE19] PrimaryQuota: 59055800320, ArchiveQuota: 53687091200, DumpsterQuota: 32212254720, ArchiveDumpsterQuota: 32212254720 12/29/2019 4:30:34 AM [EXCHANGE19] Mailbox was updated using domain controller 'DC1.domain.local'. 12/29/2019 4:30:40 AM [EXCHANGE19] Mailbox 'ONPREMMailbox1' was updated on domain controller 'DC1.domain.local'. 12/29/2019 4:30:40 AM [EXCHANGE19] Stage: FinalIncrementalSync. Percent complete: 95. 12/29/2019 4:30:41 AM [EXCHANGE19] Move has completed and final cleanup has started. 12/29/2019 4:30:41 AM [EXCHANGE19] The Directory Cache on the source mailbox '814f5c95-21e6-4b83-a3a1-5873d4bd1dbe (Primary)' was successfully populated after the move. 12/29/2019 4:30:44 AM [EXCHANGE19] Source mailbox '814f5c95-21e6-4b83-a3a1-5873d4bd1dbe (Primary)' was successfully cleaned up after the move. 12/29/2019 4:30:45 AM [EXCHANGE19] Target mailbox information: Regular Items: 797463, 52.09 GB (55,926,039,968 bytes) Regular Deleted Items: 0, 0 B (0 bytes) FAI Items: 26, 34.44 KB (35,269 bytes) FAI Deleted Items: 0, 0 B (0 bytes) 12/29/2019 4:30:45 AM [EXCHANGE19] Target mailbox '814f5c95-21e6-4b83-a3a1-5873d4bd1dbe (Primary)' was successfully reset after the move. 12/29/2019 4:30:46 AM [EXCHANGE19] Request is complete.

At the beginning of year year I have to create mailboxes for any new students in a particular OU. In the past I have accomplished this by using powershell like : Get-User -OrganizationalUnit "domain.local/SchoolA/Users/Students/09" | Enable-Mailbox The problem with this is, when users in that OU already have a mailbox it creates a problem and doesn't just error out on those users. It seems to create incorrect aliases for the new users and the existing users go back to being "User" mailboxes instead of being O365 mailboxes (we're running in a hybrid environment). Is there a clean way with powershell to enable-mailbox on a whole OU but skip any accounts that already have a mailbox? Any help would be appreciated.

We seem to have Azure AD device join on Windows 10 working. It will automatically register the device with Azure AD and will automatically sign the user in to Office 365 using Edge or IE browsers. Is there any support for this auto-login in other browsers (i.e. Chrome)?

I don't see this in the Azure custom settings. Where do you specify the default domain?

OK, based on how that redirected I was able to construct this and it worked. https://login.microsoftonline.com/login.srf?wa=wsignin1.0&whr=[domain] Is there any way, though, to not require the user to enter their whole email address (with domain) on that page since it is already specified in the URL and you are already on the custom sign-in page?

How do you structure the URL for an azure AD custom logon page? For example, when I go to login.microsoftonline.com and enter my email address, it redirects to my customized logon page with my company's logo, etc. but the URL doesn't actually change in the browser. How can I point users directly to my custom logon page?

This is helpful for understanding the differences in identity types, but I'm still stuck in transitioning away from ADFS to Azure AD with our existing infrastructure.

We have been using O365 with ADFS for two years now. To simplify things, we'd like to move our authentication to Azure AD to rely less on the on-prem infrastructure. We've already started syncing with Azure AD connect and things seem to be working fine. My question is how do we "tell" O365 to use Azure AD login instead of ADFS for a particular domain/user?

[h=1]This was the issue. Applied the commands in the article and it began working right away. Important notice about certificate expiration if you have an Exchange 2013 hybrid deployment with Office 365:[/h]https://support.microsoft.com/en-us/kb/3145044

This is the error that comes back.

There are transport rules, but nothing that should affect this. In any event, all the transport rules would return their own error, not this generic one.