User Profile
BryceContento
Copper Contributor
Joined 7 years ago
User Widgets
Recent Discussions
Tenant to Tenant Migration from Existing Hybrid Model
Our company was recently acquired, and the desire is to migrate our tenant into theirs. - we are in a Hybrid deployment (1 remaining OnPrem Exchange server** and using AzureAD Sync) - we are a relatively small shop (~51 accounts w/<400GB total in mailboxes, 200GB in OneDrive, very little in SharePoint) - we create users and mailboxes OnPrem and migrate them to O365 and manage them OnPrem **In preparation and testing for this, I have taken our OnPrem Exchange server out of the mailflow, pointed the MX records to O365, disabled the connectors, etc and mail flows perfectly fine. I also created a test user in our LocalAD and synced that account to O365 (didn't create a mailbox on the local Exchange server), assigned licensing and let it create an ExchangeOnline mailbox and that mail flows fine as well. - they are not hybrid - they are using Azure AD Sync. They create and manage users in their local AD and sync them to O365 (same as we do) - they do not have any OnPrem Exchange, so all of their users mailboxes are created in the cloud automatically as licenses are applied. The question is, what is the best approach? We've looked at some third party utilities for the migration that look good, but the concern with that method is what happens then to my local AD and AzureAD Sync; managing the existing users that were created, synced and then migrated; and my local users authenticating to it, etc? Are we going to be able to fully decommission the last Exchange server and not lose the ability to manage our folks. I need them to authenticate to our Local AD so do I then point AzureAD Sync to the domain in the new tenant? We talked about the possibility of simply creating the users manually in the other tenant, then exporting/importing their data to their new accounts (instead of migrating the account itself) to remove the need to maintain an OnPrem Exchange server if the users weren't created locally then migrated. How then does that affect them authenticating to our local AD since as I understand it, you cant sync from AzureAD back to a local AD. What about the possibility (same as what I wrote in BOLD above) of recreating all of the users in my local AD (with a different UPN), not creating mailboxes locally, syncing them to 0365, assigning licensing and letting the ExchangeOnline mailbox be created automatically (no mailbox migration like we are currently doing). Then we could import their PST to their new mailbox. Now, the users WOULD exist in our localAD and when we migrate that new batch of users to the new tenant, we could point AzureAD Sync to the new tenant and it should sync. AND since they never had a mailbox on our OnPrem Exchange server, there would be no need to maintain it. Appreciate any help on working through this!5.2KViews0likes4CommentsRe: Tenant to Tenant Migration from Existing Hybrid Model
VasilMichev Appreciate the reply. Yes, I was planning on stripping out the hybrid model first. I don't see any continuing need at this point. The EndState: - Company1.com domain moved to Company2's tenant - Company1's users and data are migrated into Company2's tenant and associated with Company1.com - all Company1's mailboxes are in ExO within Company2's tenant - decommission Company1's last OnPremEX - Company1's local AD sync's with Company1.com in AAD in Company2's tenant - Company1's users and local resources continue to authenticate as always (against Company1's local AD) If we simply move our existing domain into Company2's tenant then migrate the users in Company1 (my company) into Company2's tenant (including all of their data) and associate them with my domain there, am I able to continue to use Company1's local AD to manage and maintain users by just pointing AD Sync to the domain within the new tenant? AND will the local AD for Company1 continue to function for local authentication as it currently is?4.8KViews0likes2CommentsRe: Moving Exchange 2010 SP3 from Server 2008R2 to new Server 2019 VM
Ok since I'm going ex2016 on the new 2019 VM with the free hybrid license, do I need to do anything with the existing ex2010 server (latest CU, upgrade to ex2013, etc) before setting up the new server, or is that just wasted effort since it's going away? Thanks again all!3.1KViews0likes1CommentRe: Moving Exchange 2010 SP3 from Server 2008R2 to new Server 2019 VM
oliwer_sundgren thanks very much for the reply. From what I've read, there is no longer a "free hybrid license key" for EX2019 only 2016, correct? That means I'll be setting up EX2016 on the new Server 2019 VM. Am I correct to think that I cannot (or should not) "upgrade" the existing EXC2010 server to 2016 in place? Since it doesn't look like I'll be going to EX2019, does it make sense to even worry about updating the existing EX2010 install at all? Will prepping the AD ad schema for 2016 adversely effect the existing 2010 install?3.1KViews0likes3CommentsMoving Exchange 2010 SP3 from Server 2008R2 to new Server 2019 VM
I know, lots going on in that title, so here we go. We're a small shop of <100 people and a few physical servers (DC the only 2012 server. Everything else still 2008r2). We are getting ready to pull the trigger on a hardware refresh for our entire infrastructure moving almost entirely to virtualized environment. My plan is to first get the new 2019 DC stood up correctly, then tackle the rest. Exchange is one of those pieces. We have EXC 2010 SP3 running on Server 2008r2 in a hybrid environment where on-prem is almost only for management (a couple of local mailboxes for things like network scanner and such that I'm working to move online). All regular user mailboxes are in Exchange Online. My goal is to setup the new EXC server in a Server 2019 VM, then install Exchange (2016? 2019?) and migrate/move mailboxes and settings from the old box to the new VM. Of course, that brings a list of questions: - should I upgrade the current EXC 2010 install to 2013 or 2016 to make that migration/move easier or is that an unnecessary step (because of the current environment config, size, etc)? I know that EX2010 and EX2019 can't live together, so I was leaning toward upgrading first to 2016 then migrating to the new 2019 server. - I thought I read somewhere that if all of my mailboxes were in Exchange Online the EX2016 license has a hybrid model/option that is "free." Is that correct and applicable? Does the same thing apply to ED2019 with only mailboxes online? - I found the Exchange Deployment Wizard, but there is no 2019 option. Is that out there somewhere or even necessary to go from '16-'19? In short, my plan currently looks like this: - upgrade EX2010 to EX2016 (even now before the new hardware arrives) - setup new 2019 DC (and demote old 2012 DC) - install new 2019 Server VM - install EX2019 into new 2019VM - migrate EX2016 setup/data to new EX2019 - remove EX2016 server *somewhere in that process setting up the hybrid settings on the new EX2016 install and eventually the new EX2019 box I assume has to happen or does that migrate well? Thanks all!3.3KViews0likes5CommentsRe: 3rd Party Web Application won't run in Edge Beta
almost got it. I made a couple of changes, and if I manually type the final URL of the web-app instead of letting it route itself through landing pages, etc., it loads. Thanks for the help. I should be able to lock it in from here.1.6KViews0likes1CommentRe: 3rd Party Web Application won't run in Edge Beta
HotCakeX Seem to be making a little progress. I was able to get IE Mode working (tested by setting the XML file to load Yahoo.com in IE Mode). That worked. I then put the URL of the web-app back in to test. Now, when the site starts to load, I do see the IE Mode icon flash briefly, but then it disappears as it moves to loading the .asp page that loads the content. It never progresses beyond the logo screen.1.6KViews0likes2CommentsRe: 3rd Party Web Application won't run in Edge Beta
HotCakeX I used the tool, but it said it couldn't connect to the URL. Could it be because it's not pointing to a full domain name (with a .com extension) as it's running on an internal server? We point IE to http://cas-bst and the site loads. I did modify the XML to include the revisions you suggested. Still no luck. I also changed the site to yahoo.com to see if I could verify at least that site was working, but it also does not appear in IE mode either.1.7KViews0likes4CommentsRe: 3rd Party Web Application won't run in Edge Beta
HotCakeX I did and I can see the policies applied: edge://policy/ I thought I set everything correctly but it still doesn't seem to work. https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#internetexplorerintegrationlevel1 https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#internetexplorerintegrationsitelist\\cas-dc1\NETLOGON\iesites.xml and this inside the XML doc: <site url="http://cas-bst/auroraweb/"> <open-in app="true">IE11</open-in> </site>1.7KViews0likes6Comments3rd Party Web Application won't run in Edge Beta
Having just returned from Ignite, I was excited to learn about the new Edge beta and installed it. We were told that every site would work at least in "internet explorer mode" but one of our 3rd party vendor web-apps does not. It is from BST Global (bstglobal.com/). I runs fine in Internet Explorer but does not load in the new Edge and I don't see any indication that it's trying to run in IE mode (or if that is something I need to force it to do). I'm pretty certain it uses Active X controls. Is there some process I can work through to try and get it to run correctly?1.8KViews0likes10Comments
Recent Blog Articles
No content to show