The issue is that most businesses will setup a cross forest trust whilst doing these mergers for other parts of the migration as they support moving users cross forest ( cough Exchange cough) and as part of the cross forest trust.
Then the simplest method is to sync both forests with the same tenant and move the users from on-prem to Office365. It should be noted if your endgame or nirvana state is to get your users into Skype4B Online or more likely Teams. But that’s not what we are talking about in this article. One notable exception is that you can create a trust between both domains and migrate everyone into a single Office365 tenant. But not merging two companies separate forests each with their own Skype4B topology together. Well Skype4B supports Resource Forests and multiple forests with a Central Forest. Usually they take this opportunity to either rebrand or amalgamate the SMTP/SIP domains making your life quite simple as they are effectively “New users”īut what about when as part of the migration process they decide to create cross forest trusts and do it the “old school” way? The bigger company buys the smaller company and starts migrating users into their domain with tools like Microsoft Identify Manager, Forefront Identity Manager or one of the many Identity management tools available. You know, the kinds that are large enough to need government approval? A lot of them are fairly simple. I’ve been involved in my fair share of acquisitions and mergers larger companies over the years.
0 kommentar(er)
