Pass Microsoft 365 MS-203 Exam in First Attempt Easily

Managing the Messaging Infrastructure Lifecycle

1. Understanding the Exchange Deployment Process

Things first here. Let's clarify a couple of things. We talk about deployment. Traditionally, what comes to mind is installing Exchange on premise. And that's mainly what I want to focus on right now. But I would like to kind of go back and forth a little bit on Exchange on Prem versus Exchange Online. Of course, this class is really going to focus on both. We're going to sort of jump between the two because, of course, one of the things we have to talk about is getting into the migration world, migrating from on-premises into Exchange Online, and trying to make things work together. So traditionally, when most of us think of Exchange, we think of Exchange on premises. I know that for me, my very first version of Exchange was Exchange 55, and I've worked with Exchange on Prem ever since. As a result, I've had to come up with a new way of thinking about how things have always worked on Prem and how things now work. When we start moving into the cloud with Exchange on Prem, you're just dealing with the local installation of Exchange. It's already installed in your environment. Again, it's sort of the traditional way of doing things. The main benefit of that is we completely control the server, we control the hardware, and we deal with all of that. Of course, you can also see that as a drawback as well, right? We have to maintain the hardware. We have to keep it upgraded, although we do have the ability to customise things more because we control it. But we do have the headaches that go along with that. I know some companies have completely moved to the cloud just because they didn't want the headaches of dealing with the physical servers and having to keep things upgraded and managed. Right. Exchange Online gives us the ability to completely host our email out there in Microsoft's cloud environment, okay? in Microsoft 365 services. And Exchange Online comes with a lot of our subscriptions, and we're going to talk a little bit more about that later. We'll talk about some of the different licences and subscriptions and how you get access to Exchange Online. But you're going to find that a lot of the different subscriptions that are available are part of it. You get Exchange Online as part of the deal. Okay? The other thing is, you don't have to host any Exchange servers in your data centre if you don't want to. If you want to completely go to a cloud-only environment, you can. You can actually host everything out in the cloud if you want. Another option is to do a hybrid deployment in which you host Exchange both on-premises and in the cloud. So, you can kind of mix and match any way you want. You can do what's called a "cutover migration," where you just move everything into the cloud immediately. You can do hybrid migrations where you sort of make the two work together for a period of time and then eventually move out to the cloud. Okay. You've even got the ability to, with Exchange Online, basically maintain everything through Microsoft. Microsoft deals with the updates and upgrades; they deal with all the hardware, and we're just having to maintain our mailboxes and recipients. There's a lot of benefit to that. We'll eventually talk more about those benefits. Okay. But I did want to kind of clarify looking at things from an on-premises perspective versus an Exchange Online perspective. Ultimately, with Exchange Online, obviously, you don't really have to do a deployment. It's already deployed. It's just that you've got to use it at that point. But with Exchange on-prem, we still need to deal with the deployment. So let's talk more about the deployment process of Exchange on Prem. Okay? When you get into this, you really have to think about the reasons for dealing with Exchange on Prem for deployment and then the reasons for dealing with Exchange Online. All right? So first off, if we decide to deal with Exchange Online, we think about things like the total cost of ownership. The total cost of ownership involves a subscription plan. If we deploy Exchange on-premises, we're paying a single price and we're basically paying for a licence agreement with them, so we're not having to pay an ongoing subscription, whereas if we do Exchange Online, it's an ongoing subscription based upon the different licences that are available. And again, eventually I'm going to go over those different licences with you. Okay? We still have the administrative burden of both. If you deal with Exchange on premises and do a deployment there, you still have to administer it, but you don't have to deal with the hardware and all the redundancy of your on premises equipment. Whereas with the cloud, Microsoft is dealing with all the redundancy. So we're shifting all of the risk of things failing and going down to the cloud. Now don't get me wrong, there's still going to be some redundancy in the things that we learned. But for on-premises, we have to manage our own redundancy and our own fault tolerance. Okay? So disaster recovery is a big concern and a big consideration. Whereas Microsoft's SLA, their service level agreement in the cloud, is something they give us as part of the deal when we have Exchange Online, and they guarantee a certain level of uptime. On the other hand, we have to deal with all of that on-site. The other thing is flexibility. They give us a lot of features with ExchangeOnline that we get to control, but there are also some things we don't get to control. If we deal with Exchange on premise, we get complete control over our equipment and the way things are configured. Okay? And then, finally, we have environmental impact. Microsoft looks at things like where and when they build their data centers. They're trying to be as friendly to the environment as possible. Whereas of course, data centres and on Prem, that wouldbe our responsibility to have to deal with that. Of course, at that point, the environmental side of things is being pushed off on Microsoft at that point. If you're using Exchange Online now, what are the requirements for installing Exchange Server 2019? Okay, so first off, you have to have a certain operating system. to install Exchange Server 2019. They require you to have Windows Server 2019. either the data centre edition or standard edition. Okay? They also have server cores. Or you can do the Desktop Experience, which is the graphical version. If you do Server Core, then you're dealing with just a pure command-line environment, and you're putting Exchange on top of that. The great thing about that is that it's using very little resources to make that happen. Desktop experience is going to require more resources. Okay. You're going to see that Exchange Server 2019 is a bit of a memory hog. Now there's other software that's needed as well. You have Net Framework 4.7.2, which Server 2019 will generally come with that. However, let me warn you, if you've got one of the newer cumulative updates for ExchangeSurvey 2019, you're going to need 4.8. You're going to notice that when I install my Exchange 2019, I will be using a newer version. so I will have to have that 4.8 download. Then you've also got the CplusPlus redistributable package. And you must include that as well. Either 2012, 2013, or the Unified Communications API 4.0. So those are going to be some of the required software when I do my demonstration of installing Exchange here. Coming up, you're going to see that I'mgoing to be installing those different software packages. Okay? Now with Exchange 2016, if you decide to go that route, which is Exchange 2016, it's still the most popular version of Exchange. Out there. We have Server 2012 essentially are higher. Standard Data Center Server 2012 has two standard data centers; Server 2016 has one standard data center. And then they don't support Core on Exchange Server 2016. So you can't install it on Core the same way you can on 2019. Okay? As far as the other software that'srequired, it's pretty much the same. The Net Framework 471 C Plus Plus redistributable package for Visual Studio 2012 will be displayed. the Unified Communications API 40. All that is pretty much the same that we saw with Server 2019. Okay, now here is the kicker, right here. Recommended hardware for Exchange servers You'll notice that it specifies that your memory must be Intel 64. They recommend 128 gigs. There are a lot of people that are complaining about this with Microsoft right now, but this is what Microsoft is recommending. And really, the focus is all the components that run in the background if you want Exchange to run smoothly. And if you're going to go through what's known as a hybrid migration, It's going to help you to have that extra memory, okay? Ultimately, to be honest, you can run Exchange for a lot less than that. I'm only going to be running Exchange with four gigs in my virtual machine. You can run it with a lot less, but as you get into the hundreds or thousands of mailboxes and all that, you're definitely going to want to up that memory. But it is kind of amazing to imagine that they recommend 128 gigs for Server 2019, whereas with Server 2016, they're only dealing with eight gigs. The Edge Transport Server, which is a server that goes into your DMZ, is something I'll talk to you more about later. That's 64 gigs. And then for Server 2016, it's just four gigs. and you can see the storage requirements there. You have 30 gigs for Exchange Server, 200 megs on your system drive, 500 megs of message queue, a database, and then refs. They tell you only about mailboxes, databases, and logs. Although I will tell you that Microsoft's Refs Filesystem is supposed to be going away and all the features are going to be part of NTFS, So keep in mind: they say resilient filesystem, but ultimately NTFS, the newer version, is going to be supporting this as well. Okay? So those are your recommended hardware. Now, as far as virtualizing Exchange, as far as, say, server sizing and virtualization, you're going to find that deploying Exchange in a virtual environment works along the same exact lines as it does in a physical environment. You're essentially going to server sizejust like you do physical. If you're going to have an Exchange server running in a virtual environment, you've got to have a lot of memory and high CPU usage. So just playing along the same lines as you do physically, the great thing about virtualization is that it's easier to provide high availability because you can do failover clustering. With HyperV, you've got the ability to use the production capabilities of storage area networks to link all that, too. Now, I will tell you, they don't recommend you use Checkpoint Snapshots In VMware, they call them snapshots. In HyperV, they call them checkpoints. So really, any database product that uses any kind of database in Exchange uses a database. You should not use checkpoints because it can cause a time sync problem when you do that, all right? And the last thing they tell you is, "Don't use dynamic memory with virtualized Exchange, okay?" So in your hypervisor, you have the ability to set a maximum for a minimum of RAM. That's called dynamic memory, and it kind of grows and shrinks. They tell you, "Do not use that in exchange." Use static memory. That basically means setting your maximum limit. And that is what Exchange's memory is. Do not let it jump up and down. It really hurts the performance. So they basically tell you not to use it. All in all, exchange. It's a long, drawn-out process to install, but it's not too difficult. You've just got to make sure you have the required software. You've.

2. Understanding Active Directory with Exchange On-Premise

I want to spend some time now talking about the requirements that are going to be needed for Active Directory. Now, the first order of business is to ensure that we have a fundamental understanding of what Active Directory is and how Exchange will use Active Directory. So I want to start out by drawing a little something for you. And the concept here involves the fact that we could have a bunch of computers in our environment. And let's say that this little symbol that I'm making here is going to represent 10 computers in our environment, okay? So this little symbol right here is going to represent 1,000 computers. Now, that being the case, when it comes to your computer, by default, in the Windows world, computers start out in something called a work group. And a work group is a peer-to-peer network. That means that pretty much every computer is on its own to manage those computers. We'd have to sit down at each individual computer and make changes in order to actually implement anything in our environment. That's a lot of work. So Microsoft created this concept of domains. And the kind of domain that we use today is called an Active Directory domain. An Active Directory domain is represented by a triangle. So if you ever see in the Microsoft world that they draw out a triangle, you're going to know that is the symbol of a domain, okay? Now, in a Microsoft domain, it is sort of like the security boundary of these machines. And it's going to let us control these machines. And we have a type of server that's going to manage our domain. and these are called domain controllers. Or you can say DC. It's also known as an AD DS server in an Active Directory domain services server. Now, on our domain controllers, we have a database. This little cylinder-looking thing that I'm making here is going to represent a database, all right? and that database is called Active Directory. All right? So I'm just going to put an ad in here, all right? Active Directory. By the way, lots of times people ask me, they'll say, "Why do you draw this out?" Why don't you just have it pre-drawn on the screen? Because to me, it's a lot more effective to draw this out and explain it than just to have a bunch of stuff on the screen. It can get a little overwhelming. So I like to draw this out and explain it at the same time. My domain controller, though, is going to help me manage the domain. So here's the thing. The key to a domain is centralization. If you were to ask me, "Why is the domain important?" I would say for centralization purposes because domains allow me to control all of my resources. my client computers, my servers, all the different servers in my environment—file servers, Exchange Server, SharePoint Server, SQL Server, you name it. Okay? Now it's also important to have more than one domain controller. You don't want to just have one domain controller, generally speaking. You should have multiples depending on the amount of load you have. So I'm actually going to put a couple of domain controllers up on the screen here. Another thing that's interesting about domain controllers is how they replicate. So whatever you do to one will be replicated in the other. Okay? So, for example, if I were to create an email account, there was going to be a mailbox recipient. In exchange, let's say I draw this little smiley face guy and move him over here. This little smiley-face guy is going to represent a user. Our user account will eventually receive a mailbox—a little jacked up smile—but that's fine. That user account is going to replicate from one domain controller to the other. So you're going to notice that, essentially, he's going to show up over here. Active Directory is going to replicate that over to that other domain controller. All right? So that also means, though, that this user could log on to any one of these machines if we've given them access. Now there's another key element in Active Directory, and this key element is also going to play a very big role in Microsoft Exchange. Our domain must have a name, and the name must be a DNS-based name. My domain in my lab, which I'm demonstrating everything in, is called Examlabpractice.com. That's the name of my domain. All right? I have to have a DNS server that's going to manage that namespace. So this server here is going to be my DNS server. This DNS server is going to have a database, except in DNS, we call the databases zone databases. Another name for a DNS database is sometimes referred to as a namespace database. So zone databases and namespace databases are the same thing. All right, I'm going to put a red border around this name, and I'm going to illustrate that this database is actually named after that. Okay? So there we go. We have the DNS database there that is actually named examlabpractice.com. All right? And then of course, we've got file servers in our environment. Let's make a file server. Let's say this is our file server, and we can have other types of servers in our environment, including Exchange, which of course I am going to bring into the picture here. Okay? So what ends up happening though, is all of thesedevices are going to register in DNS who they are. They're going to register their names, their IP addresses, all of that stuff. And then this is how everybody's going to find each other. So now when my clients boot up and they want to authenticate with these domain controllers, they can query DNS and say, "Hey, DNS, do you know who the domain controllers are for my domain?" DNS can reply back, and the client will know who they are, and then the client can go up and authenticate. If one of these domain controllers goes down, you have a backup. This is one of the reasons why you want to have more than one domain controller. Another reason you want to have more than one domain controller is for performance, okay? Because if you have a big environment, you don't want just one domain controller. You want lots of domain controllers so that they can handle the amount of load that you're putting in your environment. Okay? Of course, the other thing that's got to happen is if we're dealing with Exchange, we're going to want to set up an Exchange server. Now, we can go full-blown Exchange online, but for now, I want to explain the concept of using Exchange on premises. Now, before we can install Exchange on-premises, you're going to notice that you're going to be running a command called Setuppreparead. That command is going to prepare your Active Directory for you to install Exchange. And you'll see me demonstratethis as I install Exchange. Coming up, I'm going to run this command, and I'm going to allow it to prepare Active Directory before I actually get Exchange installed. But then once I'm ready, I've got my Exchange server here, all right? And I'm going to call this exchange server Ex One. In my lab environment, it'll actually be called NYC Ex One. We'll just say, "example. For sure. This is going to be my Exchange Server, okay? Now, Exchange servers can have different roles. The main role of an Exchange server now is called "mailbox" mailbox role. A mailbox role is going to contain a mailbox database, and that mailbox database is going to contain all of your recipient's email accounts. So you'll actually have a mailbox database. So here we go again: another little cylinder symbol. And that mailbox database is going to contain your mailbox information and your recipient information. In the older versions of Exchange, there used to be all sorts of roles. You had the mailbox role; you had the client access role; you had the hub transport role; you had the edge role. Now there are really only two main roles: the mailbox role and then the edge role, which I'm about to show you, okay? So to get into that, I'm just going to add the Internet into the picture here. This little cloud that I'm creating here is going to represent the Internet, all right? And we'll just kind of clean it up a little bit, all right? And the Internet connection is coming into my network here, and I'm going to have a firewall in there, too, that's going to be shielding our network. We don't want our network completely exposed, right? So we're just going to make a little firewall, and we've got to have ports open and all that stuff in order to let things flow in. But here's the issue. It's actually fine and dandy for you to send emails here. And then this goes out, talks to the Internet, delivers your email—that's not a problem. The problem we've got is: what happens when email servers out here on the internet want to send email to me, okay? So there's some other email server out there that's wanting to send email to my internal environment. And do I want that email server talking directly to my internal email server? That's where things get a little dangerous, right? So email servers have a protocol, the SMTP (simple mail transfer protocol), and they're going to communicate with each other using that protocol. It's a bit of a security risk to allow this email server just to communicate directly with mine. So here's what Microsoft says. Microsoft says you should set up what is called an Edge Server, which is the other role in Exchange. So they're basically telling you that you should set up another server out here, outside your firewall. and that's going to be called your Edge Transport. edge transport server Okay? So I'm just going to put the word "Edge" here. Actually, I'll put that inside the server, all right? And so this is an EdgeExchange server as well, all right? The other thing is that you don't want to expose that port edge transport server completely. So Microsoft says you should actually have another firewall as well. You should put this other firewall here. And then what you do is you call this "your internal firewall," all right? And this is called your external firewall, all right? And then the network between the two firewalls is called a DMZ. A DMZ is a perimeter network. Okay. and that perimeter network. Now what I'm going to do is I'm going to open up ports coming in that allow servers on the outside to communicate with this Edge Transport server, and then the Edge Transport server can deliver email to this guy, okay? The great thing about the Edge Transport Server is that if somebody were to hack the Edge Transport Server, he really doesn't know anything. So hackers are not going to be able to steal people's email or any of that. So this is a great way to help secure our environment, okay? And these are going to be some of the requirements that we're going to have. So as far as setting up Exchange on-premises, this is a pretty common design. We got our Exchange internally, we got our Edge Transport Server, we set up a DMZ, and we're now allowing mail to flow outside and allowing mail to flow inside. And we'll go over some of the rules, ports, and other details later in the course. But this gives you a little bit of a visualisation of things going out and things coming in. The two main roles, the mailbox server role and the edge transport role here, are going to be your two main roles, and you're not going to have the edge transport role on the inside. It's going to be on the outside. And that DMZ. Okay, so this gives you a look at things on premise. In this next little video, I'm going to talk about throwing exchange online into the mix and how that's going to work. It's.

3. Understanding Exchange On-Premise with Exchange Online

Okay? So now that we've got an understanding of the foundation of Active Directory and how Microsoft Exchange is going to interact with Active Directory and how you've got to prepare Active Directory for Exchange on-premises, what I'd like to talk about now is throwing the cloud into the mix. Okay? So Microsoft has over the years been buildingdifferent data centres all over the world indifferent regions and they are now offering whatis known as their cloud services. So I'm just going to represent that with this cloud symbol here. And we will connect this to the Internet with all of their various data centres and everything. And there are some different names for their cloud. Okay? So first off, Microsoft's main cloud technology is called Azure. Azure is what is known as Microsoft's IaaS cloud. IaaS stands for infrastructure as a service. What that means is they've got all this hardware in their data center, okay? tonnes of server blades, CPU, memory, storage, network bandwidth with fibre optics, all that They've got lots of redundancy set up for you—whether it's power or air conditioning, everything is already done, and they are hosting the equipment, and they will allow us as tenants to store things on their Azure services on their Cloud. Okay? So we can actually set up virtual machines if we want them there. We can store virtual machines, and we can have virtual load balancing equipment out there. They've got the ability to do database instances out there in their cloud, which is essentially all of this virtual stuff. We can have virtual networks, and we can actually have our firewall here tap into their VNet, allowing us to access virtual networks, virtual machines, and everything else about the cloud. I can actually host-exchange the on-premises version. If I wanted, Exchange could be hosted in a virtual machine in the cloud. Okay? But that's what Infrastructure as a Service is. You pay a fee based upon how muchusage you're using for all their equipment. So they have a mathematical formula that calculates things based on the CPU, memory, storage network, and all that. Now the other part of their cloud is known as Microsoft 365, which for the longest time they were calling Office 365, but it confused a lot of people. People would hear that word "Office 365" and think, "Okay, well, this is just purely the Office applications, right?" and so it just confused a lot of people. So they actually changed the name from Office365 to Microsoft 365 because there's a lot more to this than just Office. Okay? Now what is that? Microsoft 365, on the other hand, is a Microsoft PaaS cloud service and a SaaS cloud service. Now what is that? PaaS means platform as a service. Okay. SaaS is software as a service. You're going to see that those two are very closely related. So when you get into that, they're actually offering Office 365, which is a management platform for Office that gives us access to all the software as a service apps. and this will also include something called Office Online as well. Okay? We also understand that this is what we really care about: Online Exchange, okay? We have SharePoint online. All right? We get Skype for Business, which is now becoming teams, as well as their new collaboration software. We get something called Entune, which is Microsoft's MDMAM solution. Okay? And you get One Drive for Business, which is acloud storage, one drive for I'm just going to sayone drive for B, one drive for business. Actually, there are so many thingsyou get with the Microsoft cloud. I don't have enough room in my drawing here to put it all. But what we really care about is this exchange online. Now, another piece of this puzzle that I'd like to add and that I've left off here that I want to show you is a directory service that plays a role in managing all this. I'm going to kind of put it toward the top here, and it's called Azure Ad. Azure Active Directory. Now, I don't know about you guys, but when I first heard about Azure Active Directory, I thought, "Oh, well, what they're doing is basically just going to probably host virtual machine domain controllers out in the cloud." And actually, that's not true. See, on premise, Active Directory, which is referred to as "Adds Active Directory Domain Services," uses technologies that, well, they're pretty old nowadays. It was cutting-edge 20 years ago. But for example, it uses a security protocol called Kerberos for authentication. It employs the LDAP query language and the lightweight Directory Access Protocol query protocol. Again, those were cutting-edge at one point, but they're considered old technologies. Now, see, the problem is that when you get out on the cloud and you're dealing with everything that's just purely Internet-based, you really need to be using the web-based standards that all the different web servers and web browser companies are all using. And so there are all these things we call the WS standards. So what Microsoft did was rebuild a whole new directory service using Web standards. And this is what Azure AD is. Azure Ad has objects that you can store—your user accounts, your recipients, your mailbox recipients—all of which can be tied to this Azure Ad. Okay? And Exchange Online is going to use Azure AD as its main method of dealing with its recipients and its objects. Okay? But of course, this does create a slight problem. Yes. I can just use Exchange Online if I want. I could just use Exchange on premise. But what if I want all of that to work together? What if I want to make it all work together? Okay? I need to tie these things together. So what you'll end up doing if you would like to synchronise and make this all work together is, in Exchange, you can do what is called a cutover migration. Cutover migration simply means I'm just going to move every one of these objects out to Exchange Online. And then, at that point, we are going to just get rid of Exchange on premise. That's called a cutover migration. But I may not want to do that because maybe I'm in a big environment and we're not ready to go just full-blown into the cloud yet. Maybe we would like to support something called "hybrid." What you can do is you can set up a server. You can set up a server called Azure AD Connect, okay? It's called an Azure AD Connectserver because, see, here's the problem. Active Directory on premise does not speak the same language as Azure AD does. They actually speak different languages, okay? On Prem. We're talking Kerberos and LDAP. However, Azure AD understands all web service languages, including Open ID and OAuth. Open authorization and authentication So we need to speak both languages. So we can set up a server called an Azure Ad Connect Server on premise. Now, could you use an existing server? Yes, you could use a domain controller if you wanted to, or even the file server, but Microsoft recommends that it's a separate server. By doing this, this is going to build a trust relationship with your domain, and it's going to build a trust relationship with Azure AD. And at that point, we can do syncing. We can actually synchronize. You've got a capability called Sync Directory Sync, and you can choose what's going to synchronise out there. Now, once you've done this, there is a tool you can run in Exchange called the Configuration Wizard. So I can actually run this thing called the Hybrid Configuration Wizard on my Exchange Server. Okay? I can run this tool on my Exchange Server. I'll be showing you where that's at in one of my later discussions. Okay? I can run that right here on my Exchange Server, and it will talk to the Azure Ad Connect. It will talk to Azure AD, and it will talk to Exchange Online. And I can synchronise objects if I want. And here's the other beautiful thing. I get to choose what's going to synchronize. If I don't want all of my mailboxes to go out there to Exchange Online and synchronize, I don't have to. I had control over that. Okay? If you want, you can control mail flow rules, and we're going to have a lesson on mail flow rules, and you can decide how you want mail to flow. If I want these clients to use the on-premises Exchange server and have it flow out to the Internet from there, and when people go, they go through the edge and it delivers email, you can do that. Then you could have some of your clients only communicate with Exchange Online. You could even configure it so that only clients from outside the organisation use Exchange Online. I'm going to go ahead and tell you, and I'm going to talk more about this later. Microsoft is going to recommend that you set your mail rules up.If you do a hybrid deployment with Exchange, you set your mail flow rules up so that all mail has to flow through Exchange Online. Even if you're sending mail through here, you should have this server forward everything to ExchangeOnline, including any mail that comes in. So if it's coming in from another email server, they're saying it should go through Exchange Online before it ever makes it to the Edge Server. Why is that? Microsoft has two incredibly powerful products with Exchange Online. You have something called EOP, which is exchange online protection. And you have something called advanced threat protection). Exchange Online Protection has got all these filter rules that can protect your email. ATK is awesome. It allows you to make safe attachments and safe links. It'll scan every link and every attachment against all the different malware detections and other things that they've found on their security team. Microsoft has something like over 3000 people worldwide that are monitoring for different new threats, and all that goes into this database. So, according to Microsoft, any mail going out should go through Exchange Online. But definitely, any mail flowing in should flow through Exchange Online first and then go into your Exchange environment. Okay? And we're going to learn how to do that when we get into the mail flow rules a little bit later. That's all about mail flow, but hopefully this little lesson here has given you guys a good foundation now of how we can make Exchange on Prem and Exchange Online work together. This gives you, in a nutshell, a lesson on how we can make all of this stuff work together and how there are a lot of benefits to this. Okay. setting up an Azure ad. Connect Server. This is going to set up your hybrid environment between your on-prem Active Directory and Azure AD. And then after you've done that, you can do the hybrid configuration wizard in Exchange, which is going to link your on-premises Exchange to Exchange Online. And then finally, you can configure your mailflow rules so that mail can flow out to Exchange Online and back in. and there are a lot of benefits to that. Okay, so hopefully this clears things up. This gives you somewhat of a visual representation of that sort of high-level overview. And, of course, as we move through this course, we're going to get down to the nitty gritty and all this stuff.

4. Performing the Exchange On-Premise Deployment

Search engine. The search engine just searched for the offline.net 4.8 installer. So we search for that. You can download it right here. So it's an offline file. You download it, and you can install it. That way, you don't have to stream it. You can download it and put it on as many servers as you want. Okay, so that's where you're going to get that. Then there's the C plus, plus redistributive, redistributable. All right. And that will be just a search away, and you can download the most recent version of it. 20-12, 20-13 will be fine. All right, this is where you're going to get that. And then the last thing is unified communication. So we'll say "unified communication." 40. Download. Search that, and you'll find that pretty easily as well. So you can find all three of these very quickly and very easily. I've gone ahead and downloaded those, and I put them in this little folder right here. And I went ahead and installed these as well, because they do take some time, particularly the.net framework. It can take 1520 minutes to install. So you just run these one at a time, and they'll get installed. The.net framework will cause your server to reboot. So you just reboot after it's done. And then, at that point, you had all the required software that's needed to get Exchange installed. Exchange the DVD in here, which is really just an ISO. Exchange 2019 ISO I'm going to right-click my Start button. I'm going to go run I'm going to type CMD, and I'm now on a command prompt. So let me zoom into that for you so you can see it better. And I'm going to run the following command. We're going to go to the D drive. And this is where the setup executable is, right here. So you can see if I type "Dirstar.exe," the setup executable is listed right here on the D drive. So I'm going to run set up, which I accept Exchange Server licence terms. And of course, we need to make sure we've spelled that correctly. And there we go. All right, so the next part is, "I'm going to say organisation name," and my organisation name is Exam Lab m going to say. So I'm going to hit Enter, and this is going to take a good, solid few minutes to run. So I'm going to go ahead and pause this video and let it run through, and we'll catch it when it's done. Okay, so our Active Directory preparation is done. As you can see, it took a few minutes to run through. It tells you here that Exchange has gone through and prepared Active Directory. It went through the process, finished 100%, and then was completed down here at the bottom. OK, so the next thing I'm going to be doing is actually triggering the Exchange installation. So I'm going to jump over to my Ex One service, Nycx One. And I've actually got the Exchange DVD in the drive here, which is actually, again, just an ISO. And we've got the executable set up, and we're going to run this executable right here. So I'm just going to double click on that, and it's going to trigger the setup programme to go ahead and run and pop up on my screen. Okay, so the first thing that Exchange is going to ask me is if it's okay to check for updates. Now in the real world, I would normally say, "Yeah, go ahead and check for updates." But considering this is a lab environment and I'm going to try to get it to go as quickly as I can, I'm going to tell it to not check for updates. So I'm going to say: don't check for updates right now. Okay, we're going to go down here now and click Next, and it's now going to start copying some files down, and I'll go ahead and just pause the video and let it fast forward. Okay, so it's done copying the files, and here it is on the introduction screen, which is giving you some information about Exchange. I'm going to go ahead now and click Next and accept the licence agreement. Click Next again, and at that point it's going to ask me if I'd like to just accept all of the defaults. If you look closely, you'll notice that it basically just installs the automatic check online for solutions. If it runs into any problems, it's going to do some default things there and essentially report to Microsoft to help improve future updates and Exchange. I'm going to say do not use these recommended settings because I am going to sort of customise things a little bit. So I'm going to go ahead and click Next on that. At this point, it's going to ask me which roles I want to go over, and we're going to definitely go through the Mailbox role and the EdgeTransport role and talk about all of that. There are really only two roles in Exchange nowadays—the mailbox role and the edge transport role. Okay. The Mailbox role is going to be the main role that you're going to have in Exchange. On Prem. The Edge role is actually something that goes into your demilitarised zone. And of course, the management tools are the tools that are going to help me manage Exchange. Believe it or not, those are kind of helpful to be able to actually get in there and change things. And if you choose the Mailbox role, you have to install the management tools. The other thing is, it's going to ask you if you want to go ahead and install the different features that are needed for Exchange. I'm going to say yes to that. You could put those on there separately. Or if you wanted some of the features to be managed by third-party software, you could do that instead, but I'm going to say automatically install the Windows and several roles and features that are required for Exchange. Okay, so now I'm going to click Next. It's going to ask me where I'm going to install Exchange. I'm just going to take the default location, which is going to be the programme files. Microsoft Exchange Server V 15 folder tells you there quired disc space and how much is available. I'm going to click next to that, and it's asking if I would like to disable malware scanning. So malware scanning is generally a good thing. It's going to use Windows Defender malware scanning. Of course, if you wanted to use a third party, you could disable that and use a third party. I am going to disable it just because I want this to actually install a little faster. But in the real world, I would definitely want malware protection on there. And you can always enable this later, by the way. So even if you choose to turn it off right now, it's not a problem. You can always go back and add it later. So I'm going to click Next, and then at that point, it is ready to look at the prerequisites and check the prerequisites. Okay, so we'll let it go through. I'll pause the video. We'll come back after this is ready to go. Okay, the readiness check all went through successfully. says all the prerequisites are 100% ready to go. So now I'm just going to pull the trigger and click Install. All right, so this is another process. It's going to take a while, depending on how much memory you've got in Exchange. You better be ready to wait. This is going to take anywhere from 45 minutes to an hour, depending upon how much memory and processing power your servers have. So, of course, I'm going to let this run through, pause the video, and let this run through, and we'll continue on and check everything once it's done. Okay, so Exchange is now officially installed. As you can see, I've got a message here saying setup is complete. Congratulations! It was done successfully. And it is telling me that to complete the installation, I've got to reboot the computer. So I'm going to click Finish, all right? And then at that point, we can restart the server. So I'm just going to right-click and tell it to restart. Now, while the server is restarting, I'm going to jump over to my domain controller and just confirm that things are set up properly on the domain controller. So here we are. We are back over here on NYCD One. Now we're going to go to Server Manager. We're going to click tools active Directory users and Computers. We'll bring that up, and we're just going to verify there are a couple of Exchange-related pieces of content that are going to show up there for my Active Directory users and computers. Okay, so Active Directory users and computers are up here. Now, you'll notice that I've got a Managed Service Accounts area here and a Microsoft Exchange security group. And here are the different security groups that Exchange has created; we'll be talking more about groups and roles and all that later. But this tells you that Active Directory now has the stuff that it needs. And Exchange is now officially configured for me. And I can also go here to view and click Advanced Features. I can expand all this out. And you're also going to notice that there is a folder here called Microsoft Exchange System Object, where some of the other Exchange components that we'll be discussing throughout this course are added. So this has given you a good look at the fact that Exchange has been officially set up. Exchange has been officially installed, and Active Directory is aware of it. Okay, so now my Exchange Server should be up and running. So I'm going to go ahead and jump over to the NYC, and we can verify the Exchange installation by going to the C drive. Let me zoom in on that for you. C drive programme files. And then you should be able to essentially see that you have Exchange setup logs. You have the actual Exchange installation showing up. And another thing we can do is to check our virtual directory settings. So I'll show you that as well. All right, so here we are. And I can go right here into the Microsoft folder. And the Microsoft folder is where your Exchange folder is at.So Exchange Server, and essentially your Exchange setup files, your Exchange installation files, are listed as V 15. And here are the different folders. All right, so exchange is definitely present. The other thing I can do is, going to Server Manager, I can go to Tools and open up Internet Information Services. Click on that. and this is Internet Information Services right here. We'll take a deeper look at it. The web service is as well. and the web service plays a big role in Exchange. So I'm just going to expand that out, expand sites, and then set the default website. And you'll also see the Exchange back end. And then you'll see these different virtual directories, which are the web pages that the different Exchange services are going to utilise when somebody is using Outlook on the Web or somebody is using the Exchange Admin Center. So these are also present. We'll cover virtual directories in greater detail throughout the course. So clearly, you guys can see Exchange has been officially set up on the server. It definitely took some time, but it's now up and running. And we'll be able to look at Exchangeon Prem in our next few lessons.

5. Using the Exchange Administration Center

directly and then put in the URL for your server with an ECP on the end of that. All right. So if I go here and I type, I'm goingto put in the name of my server, which isgoing to be I'm going to put Httpsnyc one. ECP. All right. And that is going to actually hit the virtual directory on the IIS web server that's going to let me get into the EAC. So I'm going to go ahead and hit enter on that, and it's going to begin loading up the EAC log on. All right, so zooming out You can see that there are administrators of my domain name and then the account I want to log on to. Okay, so I'm just going to go ahead and enter the password here. All right. We'll click to sign in, and it's going to go ahead and sign in for me. All right. Okay, so now the EAC is up on the screen. I'd like to sort of go over what the outline of this console is. So this is the first time you've ever seen it. This area right here on the left side is called the feature pane. The feature pane is going to allow you to basically navigate to the main sections of Exchange. now appear at the top. They call these tabs, but you can also call them menu options. All right. However, tabs is the common name for them. You also have the toolbar, which has these options that will allow you to modify, edit, and create new objects, among other things. Down here, this is called the list view. So as you navigate and you click on things, you will have a list view of the things that you can work with in Exchange. Over here you have the detail pane. So as you navigate and are working with things on the right side of the screen, you have the details pane as you click on users, such as the administrator here. Being the only recipient that I've got, the details of that administrator user account are over here on the right side of the screen. So those are your main areas in Exchange. Okay, let's take a look at some of these options over here. So if I click on "obviously," I'll get Mon Recipients right out of the gate. This is going to let me work with my recipients—all the things that can receive email and all that. We'll have a lesson coming up on that. I've also got permissions. All right. And it is in permissions that you will work with roles. So one of the things that we'll also be talking about is how, in exchange, we use what's called RBAC role-based access control. And this is where you're going to hand out rights. You're going to give out permissions when administering Exchange, controlling what people can and cannot do. You have compliance management. Compliance management, as you can see here, allows you to do a bunch of things involving the compliance of your environment, such as performing in-place holds, e-discovery for evidence collection, and auditing. You can work with data loss prevention, retention policies, and tags that get into how long people can keep their emails. And then there are journal rules, where we get into journaling. That's all stuff we'll eventually be talking more about. We've also got the organisation options here. All right, so this is where we get into creating something called a Federated Trust. We can share information; we can even do add-ins, which is really cool. This makes it so that when people utilise Outlook and some of the features that they get there, we can add additional features to their Outlook. You can see some of the default ones here. You've got protection, which is where malware filtering is going to control mail flow. This is where you get into the inbound and outbound rules that govern the flow of mail in and out of your organization. Whether it is Exchange on-premises or Exchange in the cloud, You're going to be working with these things called connectors and different policies. You're going to specify what DNS domain names you're going to be working with. That's where you get accepted domains. This is all stuff we're going to go over. You have a mobile option here. So this is where you get into mobile device access, and you can configure mobile device policies. This controls something called Active Sync and how mobile devices can interact in Exchange. We've also got public folders, which is a place where we can actually share files. Though I will say this, Microsoft is sort of trying to get us away from public folders. I'll talk more about that a little later. But this is traditionally a place where we can create folders and share those folders in people's Outlook, and they can get in there and share files and all that if they want servers. This is where we're going to specify all of the different Exchange servers in our environment. In this case, I currently have one Exchange server called NYC Exexone. All right, so that's my Exchange server, and I could set up databases. We can work with these things called Database Availability Groups) where we have a database that supports redundancy between two different Exchange servers or more. your virtual directories. You're going to work with certificates here. So a lot there you can do. Finally, there is the hybrid. All right, so we're going to be talking about migration, getting into the migration process of migrating from our Exchange on-premises world into the cloud. And as you might have heard me say previously, you really have a lot of control there. I can move everything into the cloud if I want to use Exchange Online, or I can take my time. I can have a hybrid deployment, and I can use that hybrid deployment for as long as I want. Okay, so that hopefully gives you guys sort of a quick rundown of the Exchange Administrative Center. We're going to be here a lot. We're going to be playing around with the on-premises version of the Exchange Administrative Center, and we're also going to be looking at the cloud version of this as well. and you'll see that they're very similar. There are a few differences, but all in all, the great thing is that once you learn how to use one EAC, you're already going to have a good understanding of how to use the other, whether it be the on-premises version or whether it be in the cloud. Okay, so we'll get into the Cloud aspect of this a little later.

Hide