7

I've the same problem in my domain. Someone manually create the o365 mailbox for users who already have an on-premise mailbox I've found this way to fix it: Export office 365 mailbox in PST Remove office 365 user license (this will remove his cloud mailbox) Remove office 365 user from office 365 AD: Remove-MsolUser -UserPrincipalName youruser@...


6

I decided I didn't want to export all the mail from the cloud mailbox using Outlook, remove the Office 365 license (or just the EOL license) from the user, then use Powershell to permanently delete the mailbox, then migrate the on-premise mailbox to the cloud, and then re-import the exported data to the new cloud mailbox. I knew that would work but seemed to ...


4

Please keep noted that running an Exchange Server on a domain controller (it hosts your Active Directory) isn´t really supported. Additional Exchange 2010 is very old and will be end of life in 2020. You also need to adjust the mailflow here, so some emails will still come into your environment and will be send out (during your "migration windows"). So you ...


4

check Exchange 2010 logs why it dismounts. It must have logged something. check the move request log -> EMC -> Recipient Config -> Move request -> right click the move request and check status / or properties there should be a lot of info there. check the system event log -> I think event about dismount should go to Windows log -> application log. check all ...


3

I would start ramping up an additional server (must be joined to your current domain BEFORE you install MS Exchange 2016 on it; keep noted that there is no option to perform an in-place upgrade of MS Exchange, so you need a 2nd server here to move to a higher Exchange server) which will will later one host MS Exchange 2016 and then you need to perform the ...


3

I tried changing the authentication type from Basic to NTLM but that did not make it work. I tried using Exchange Remote instead of Outlook Anywhere and that worked, but you cannot use Exchange Remote for a Cutover Migration. If you are going to do a Cutover Migration you must use Outlook Anywhere. After some research I decided to go with the get rid of ...


3

If you add a second domain controller--which doesn't have to be beefy for two users--then yes, you can retain the existing AD accounts. Depending on the version of SBS08 you have, you might even have a copy of Windows server 2008 that came with it. Conversely... You can just create live accounts for yourusers@example.com and let them use those for login, ...


3

This is possible in general, although quite tricky to get right; here's the only offical documentation I was able to find: https://docs.microsoft.com/en-us/previous-versions/exchange-server/exchange-150/jj873754(v=exchg.150). It refers to Exchange 2013 and it's marked as "no longer updated content", but it should still be valid. Here is another unofficial ...


2

Outlook uses OST files as a local cache of Exchange mailboxes when connected to an Exchange server using MAPI or Outlook Anywhere; it instead uses PST files when connected to POP3/IMAP4 accounts (*). This local cache can also be disabled for Exchange mailboxes, as others have mentioned. You could force Outlook to download all messages to a PST file by ...


2

You need to start from scratch on Office 365 and perform a cutover migration following the detailed step-by-step instructions here. You will need to obtain a valid public SSL certificate and ensure that autodiscover and outlook anywhere (RPC over https) are correctly set up and working. You can test this at http://exrca.com. If you're unable to make this ...


2

Steps to move Exchange 2010 servers to the new AD Site: Open the AD Sites & Services console and select the Subnets folder. Right click the Subnets folder and select New Subnet. Add the individual IP addresses of the Exchange 2010 servers with a /32 prefix. Assign the IP addresses to the RTL AD site. Add the individual IP addresses of the Exchange ...


2

For the PST migration, here are some general steps for your reference: Create Public folder mailbox in EAC (Exchange Admin Center). Create public folder in EAC. Back up the old data in the on-premises public folders using the export feature in the Outlook desktop client. Configure your Office 365 account in Outlook via Exchange mode and add the new created ...


2

The X.500 solution is used when all mailboxes are on to the new platform (whether Office365 or a self hosted). It allows end users to send email to the old addresses and they are delivered. The key bit being that both the sender and the recipient are on the same platform. In your scenario, it isn't going to work. Contacts would be the method you could use, ...


2

I would start ramping up an additional server (must be joined to your current domain BEFORE you install MS Exchange 2016 on it; keep noted that there is no option to perform an in-place upgrade of MS Exchange, so you need a 2nd server here to move to a higher Exchange server) which will will later one host MS Exchange 2016 and then you need to perform the ...


2

Exchange 2007 cannot run on Windows 2016. The latest it will run on is Windows 2008 (NOT R2). Your reason for not upgrading to SP3 isn't really good enough - patching is not an optional task, and certainly not for something as critical as email. You are basically using a product that is eight years old. Therefore you would have problems with modern ...


2

Maybe tell us exactly what you'd like to do. When you say these users would like to "work from anywhere" what do you mean exactly? Why can't they use their email from anywhere now? You don't need to move their email to Office 365 for them to have OneDrive, you just need an Office 365 subscription. You don't have to move anything. As for email, you could ...


1

Looks like each of the affected folders has some items that simply won't sync. I dialed the max replication message size down to 1 KB and tried adding each folder back into replication on the 2010 server and each folder would mostly replicate, so there's something in each folder that is crap. I am not seeing any errors that indicate what is failing. Since ...


1

Run "find" option thru Registry on Exchange Nodes to look 'EXCHSERVER' name or you can look for old DB GUID. You will find old, not existing DBs which were mounted on old/decommissioned 'EXCHSERVER' before but still exists in registry. Backup those registry keys and delete them. Restart MSRepl service and check logs. I resolved issue on that way...


1

It was an issue with DircSync it needed to be re-enabled and the affected mailboxes that said "in cloud" needed deleted in users on 365 then removed using object ID in AAD. once they were removed you use the miisclient.exe from you AAD install to fully import and sync the connectors. Then run a sync with your normal azure AD connect tool This is all in ...


1

With 300 users you can really go either way, technically. It really depends on your end goals. If you want to get rid of Exchange, then you are looking at what is called "cloud-only deployment". I would recommend not configuring Directory Sync in this scenario, it will almost assuredly cause you problems after you remove it later. I would bulk import and ...


1

I only do hybrid. Other methods do not even enter the equation. Things can get in the way, you can find issues, the client can even change their mind! Hybrid allows you to test everything as you go along, introducing things slowly and ensure that the business needs are met. Takes the pressure off!


1

Microsoft provide a method of migrating IMAP accounts to Office365. Effectively you upload a csv file containing the IMAP account information to your office365 account and the office365 servers will then connect to those accounts and pull all the email across. See here for full details Depending on the amount of email you have this process can take ...


1

Thanks Mauro! It worked for me, U had to add -UserPrincipalName to your command and it worked for me! Remove-MsolUser -UserPrincipalName youruser@youroffice365domain -Force Remove-MsolUser -UserPrincipalName youruser@youroffice365domain -RemoveFromRecycleBin -F


1

It isn't clear what you mean by "domain" in your question, as they can have two meanings with regards to Exchange. Have you just changed the email domain, so Exchange 2007 and 2013 can see each other. Alternatively, have you built a completely separate WINDOWS domain/forest and therefore the servers cannot see each other? If the former, then just move ...


1

If you configure the Sync in "Staged" mode (per your title), then no - it won't sync. The purpose of the staging server is kind of like a warm standby in case your primary sync server fails. You can move from staged to production pretty quickly and keep data in sync. If we are in production sync - and users and data is syncing fine but not the initial ...


1

Please have a look on below given informative resources that might helps you to get in more details and lets you to get this job done: Support for Multiple Top Level Domains:- https://community.office365.com/en-us/w/sso/support-for-multiple-top-level-domains Setting up AD FS and Enabling Single Sign-On to Office 365:- blogs.technet.com/b/canitpro/archive/...


1

First - use the legacy method to create a proxy for your Public folders. This will allow your migrated users to access on-prem Public folders thru Outlook Desktop client. ( https://technet.microsoft.com/en-us/library/dn249373%28v=exchg.150%29.aspx ) Migrate all your users to O365. Then you can go back and migrate the public folders. At this point the ...


1

It sounds like you want to migrate completely to O365 and have no on-prem server. B/C you are decommission your AD and Exchange server you wont' have domain accounts that your client machines will be attached to. If this is the case you will not have a matched logon for windows 8.1. To logon with an Azure AD account (Azure AD is used for O365 account ...


1

The answer to your question goes into two parts: Change the domain name: As far as I know, you can change the default domain name of your subscription without the need to add an MX record. so you may need to look again at your setup and insure that you have followed the steps to configure the domain correctly. Step 1: https://support.office.com/en-au/...


1

Check to see if your running Essentials.... If you are running Windows 2012 Server Essentials then Exchange 2013 isn't supported. Likewise if you are running Windows 2012 Server Standard with Essentials Role Added then Exchange 2013 isn't supported. The pre-req check doesn't report Essentials Role as a problem on the install but it isn't supported. If ...


Only top voted, non community-wiki answers of a minimum length are eligible