{"id":1923,"date":"2018-05-03T01:00:00","date_gmt":"2018-05-03T01:00:00","guid":{"rendered":"http:\/\/inswwdev.azurewebsites.net\/au\/insights\/uncategorized\/the-beast-that-is-multi-tenancy\/"},"modified":"2023-02-13T00:44:11","modified_gmt":"2023-02-13T00:44:11","slug":"the-beast-that-is-multi-tenancy","status":"publish","type":"post","link":"https:\/\/www.insentragroup.com\/gb\/insights\/geek-speak\/migrations\/the-beast-that-is-multi-tenancy\/","title":{"rendered":"The Beast That is Multi-Tenancy"},"content":{"rendered":"

Hi guys, yep it\u2019s me again\u2026the pure awesomeness that got you through the cross forest migrations. Just when you thought your cerebrum, you know, the large part of your brain that does all the thinking, had just been taken through its paces with trying to memorise cross forest migrations, along comes me again! This time around, I\u2019ll take you through the implementation of a multi-tenant Exchange organisation because you know, somewhere along the evolution of email and Exchange platforms, someone thought it would be a splendid idea to be able to host more than one organisation on the same platform! (cue the million dollar question of \u201cwhy?\u201d whilst inserting the crying emoji\u201d)<\/p>\n

Easy. Consultants like you and I make the world go around. Our knowledge and expertise of email and Exchange platforms is what helps your finance department send out those all important pay slips so you can finally decide on whether you can splurge on that Tesla you\u2019ve always wanted\u2026unless Elon Musk decides to launch more into space, depleting the Aussie stock of the Model S leaving you with no choice but to purchase a Japanese model electric car whose name we shall not mention. More on electric cars later. Continuing with the topic of the day\u2026multi tenancy and how in the world this ties in with an on-premises Exchange deployment.<\/p>\n

Read on my loyal apprentice.<\/p>\n

I\u2019ve been labelled a mad man for even attempting to deploy a multi-tenant solution but hey, the knowledge built up in my cerebrum needs to be transferred to my fellow Exchange consultants before we get taken over by AI (we\u2019ve all seen I, Robot!)<\/p>\n

So, you purely awesome mad man, tell us how to deploy a multi tenant Exchange platform!<\/p>\n

Here we go!<\/p>\n

One thing to remember is that deploying an Exchange 2013\/2016 multi tenant solution isn\u2019t as difficult as you might think. It\u2019s nothing compared to the days of Exchange 2010. With 2013\/2016, you can actually get things done via the GUI, BUT (and yes, it\u2019s a big BUT), most of the configuration still needs to be done using PowerShell. Oh did you think we were done with PowerShell commands? You\u2019re an Exchange consultant. PowerShell is life!<\/p>\n

If you recall back to my first blog, <\/span>The Mother of All Cross Forest Migrations<\/a>, I provided you with two sets of PowerShell commands containing approx. 4000 cmdlets each. Well, with multi tenant, you\u2019re looking at approx. 4523 cmdlets (in total) so slightly less than cross forest moves but still enough to cause irregular heart beats and loud breathing once you read on and see what the commands are. Don\u2019t worry, I\u2019m here to help!<\/p>\n

ACTIVE DIRECTORY<\/strong><\/h3>\n

There\u2019s two ways you can do this:<\/p>\n