Pass Your Microsoft 365 MS-203 Exam Easy!

Microsoft MS-203 Microsoft 365 Messaging exam dumps vce, practice test questions, study guide & video training course to study and pass quickly and easily. Microsoft MS-203 Microsoft 365 Messaging exam dumps & practice test questions and answers. You need avanset vce exam simulator in order to study the Microsoft 365 MS-203 certification exam dumps & Microsoft 365 MS-203 practice test questions in vce format.

Managing Modern Messaging Infrastructure

4. Implementing iSCSI for Mailbox Database Storage

Open up. Server manager. We're going to go to the Manage menu option, and we're going to click Add Roles and Features. OK? Once we get in there, let me just kind of zoom in on that for you so you can see it a little bit better here. And we're going to click "Next." We're going to get to the screen by clicking Next. That involves roles, and you'll see that we actually already have the File and Storage Services role installed, and we need that role. But we're missing something. If we expand that out, we'll see we have File and Icecuzzy Services, and then what we need to do is scroll down, and we need this guy right here called the Icecuzzy Target Server. Okay? So that is the role that we need to install in order to get all this up and running. Our domain controller is going to be our target. He's the one that's going to actually hold the virtual disc that is going to store all of our mailbox database information. Okay? So we're going to go ahead and click Next, do this, and then we're going to install, and I'll pause the video real quick, and then it'll be done installing. Okay, so as you can see, it's now done. I'm going to go ahead and hit close. We're going to zoom back out here. And now that that is done installing, I'm going to look here on the left side of the screen, and I'm going to click on File and Storage Services. And then you'll see that I have "Scary" also written here on the left side of the screen. So we'll click on IceCuzzy, all right? And once we get into IceCaze, you're going to notice that I do not have any IceCaze virtual discs at the moment. Of course, I need to generate a virtual disc so that the Exchange Server can connect to it and store its mailbox database. Okay? So I'm going to click right here. There's a little hyperlink that tells you to create an IScuzzy virtual disk. Start the new wizard. So we're going to go ahead and click on that, all right? And as you can see, it's going to bring this little wizard up. It's going to go ahead and confirm that I don't already have some existing disk. It's checking to see if any of that is out there. And then once that's done, I'm going to be able to go through the process of creating the disk. All right, here we go. As you can see, it's saying that I've got all this space available on my C drive. If I had another hard drive in here and I wanted to use another hard drive, like a solid state drive or something like that, I could point to it. I'm just going to use the C drive. I've got 82 gigs available, which is plenty for what I'm demonstrating here. but if I had another drive in the computer. I could use it if I wanted to, but I'm going to choose the C drive. I'm going to click Next, and then at that point, it's going to ask me to give this disc a name. Okay? So I'm just going to call this V disc one, which is going to be the disc where this mailbox database is going to be stored. All right, so now we're going to go ahead andclick Next, and then I want to specify how bigI want this disc to be so I can givethis the amount of space that I want. I'm just going to do 60 gigs, we'll leave a little bit of space, and then I can choose to do a fixed disk, a dynamically expanding disk, or a difference in do a fixeNow, a fixed disc is actually a disc where, if I dedicate 60 gigs to this virtual disk, it is going to immediately consume 60 gigs on this hard s virtual dAnd the drive is not going to go past 60 gigabytes or any of that. It's just going to take up exactly 60 gigs right now on this drive. Okay, that is actually the recommended choice of these three options. This is the recommended way to do it. You're going to get the best performance out of your disk. You have dynamically expanding if you have a fixed disk. Now, dynamically expanding makes it so that it tells you that it's going to use 60 gigs, but it's not actually going to consume 60 gigs until it needs them. It basically grows. So the disc will grow. If you are only storing ten gigabytes worth of data, it's only really going to consume ten gigabytes worth of data. Okay, so that's fine. And it would grow. A difference in disc uses what's known as parent disk," and it ends up being that it works kind of like a checkpoint. Differences in discs are for lab testing and things like that. If you had a parent disc and didn't want to make any changes to it, and there was some data on it that you didn't want to change, it would create a child disc and make the changes to the child disk. Okay, this has had the worst performance of all. This is used only in testing environments. In my case, I'm actually going to go with dynamically expanding because I don't really want to consume all that space on my hard drive right now. But in the real world, it's better to go with xpanding beSo I'm going to go ahead and click Next. The next thing is that it's telling me to assign this virtual disc to an existing ISCUZZI target to create a new target for it. I don't have any targets yet. The domain controller, my file server, is going to be my target. So I'm going to click Next to create a new one. It says, "Okay, what do you want to name it?" I'm going to call the name of the target Nycdc One, which is going to be the name of my says, "Okaygoing to click next. Now I've got to specify who the initiator is. Okay. So the initiator is going to be the Exchange Server. So I'm going to click "Add. All right. And at that point, it's going to want me to identify that initiator. So let's zoom back in on that. And you can identify the initiator in various ways if you're using a query initiator computer ID. This is going to be a computer that already identifies itself as scuzzy. But really, the easiest way to do it is just to identify it either by the DNS name or the IP address. I'm going to do it by IP address. So the Exchange Server's IP address is 192 168 00:11.Okay, so we're going to use that. We're going to click. Okay, there's the address. We're going to click next. Now we could, if we wanted to, put in a password, and it would use an encrypted password. In the real world, you should probably set up a username and password for it to authenticate. And that makes it so the Exchange Server has to authenticate with the target when it's communicating. And this is just to make sure there isn't a man in the middle attack or anything like that. But for speed and time purposes, I'm not going to select that right now. I'm going to click Next, and it's going to confirm that I've got everything the way I want it. I'm going to go ahead and click Create, and we'll wait for this to get done. Okay, so as you can see, it's now done, and I'm going to go ahead and hit close. And I now officially have my virtual disc set up and ready to go. All I have to do now is go to my Exchange Server and connect to it. Okay, so we're going to jump over now to the Exchange Server. So as you can see, I'm now on my NYC Exchange Server, which is my Exchange Server. Okay, we got Exchange installed; everything's set up. as you can see. I'm going to come here now to see the server manager. We're going to go to the Tools menu, and you're going to notice that I don't have to install anything to get the IceCuzzy initiator. The Icecazi initiator is already available as a tool on the server when you install it. So I'm going to go ahead and click on that, and it's going to pop a message up on my screen that tells me that the ISCUZZI service is not running on this machine. So I need to go ahead and click Yes, and it's going to go ahead and start that service up on the machine. All right. Now what I've got to do is actually connect from this initiator, the Exchange Server, to the Iscuzzi target, which is going to be the Nycdc One file server. Okay? So we're going to go up here. We're going to put the address, and I could put a DNS name or I could put an address in the address of the target, which is the DC Oneserver, so I'm going to say Quick Connect. And it has detected the target on that NYCDC One server. So it has detected the service. And I'm going to go ahead and click Done, all right? And at that point, I'll click, okay? And guess what? It's now done. It's now connected. So what I'm going to now do is show you that hard drive that I'm connected to. I'm going to hit Tools, and I'm going to go into this tool called Computer Management. All right? So it's going to pop "Computer Management" up on the screen here. And then I'll be able to show you Disk Management as well. All right, here we are. And we have a tool inside computer management called disc management. Okay, so here's disc management, right here. I'm going to click on that. All right? Now take a look. I want you to notice. Let me zoom in on that for ht, here weI've got disc One, which is 60 gigs. This disc is actually running on that other server right now, and I've got to actually bring it in. So I'm going to right-click this. I'm going to say bring it online. And then it says, okay, it's got to be initialized. So it says "not initialized." I'm going to right-click it again. Initialize the disk. I'm going to use GPT, which is the newer format for the master boot code on the disk. It's going to write the signature to the disk. So it's ready. I'm going to click, okay? And as you can see, it's ready. I can now format this disk. I'm going to do a new simple volume and go through this wizard. We're going to do the full 60 gigs. It's going to be assigned the E drive. Keep in mind, when it comes to storage-area networks, you have drive letters like this. But this is also known as a loan. It gets assigned a number called a loan, which is a logical unit number, but it has this drive letter. So I'm going to go ahead and click. Next, it asks me what kind of file system I'm going to use. I'm going to do NTFS, all right? And then I could give the volume a label. I could call it Mailbox. DBMB mailbox database. All right. So we'll perform a quick format, click Finish, and it's now formatting the disk. And we now have our Edshowing set up as an actual partition. Check this out. if I go to the file explorer. Here it is. Here's the E-drive. nothing on it. at the moment, but I can create a folder. If I want a place where I'm going to be storing my date databases, I'll just create a folder called DB. All right? And then I could point Exchange to storage databases here. Okay. which I am going to be showing you. We'll be doing that here. Coming up.

5. Creating Mailbox Databases

You can go to the name of your server at https://name of your server slash ECP Okay, which, as you can see, I've already done. Alright, so what I want to do now is go, and we're going to go to the area where we can create some databases here on our Exchange on-premises server. Okay. So I'm going to zoom in on this for you so you can see it a little bit better. Okay. And I'm going to click on the server menu option here on the left. And as you can see, you've got your server list here. But what we want to focus on right now is the database. So we're going to click on the database and Exchange Communications with just one mailbox database, which you'll notice has the name "mailbox database" and then a number at the end of that. Okay, so with all Exchange servers, when you install them fresh, you're going to end up with that type of scenario. Okay. The state of the database right now is "mounted," which means that it's active. You're able to use it. It's active. It's only active on this one server right now, though. N y CX one. That means we are not replicating this database with the use of something called a DAG, a database availability group. Okay, so if I want to create a database, all I have to do is click the little plus sign right here, and it's going to pop a box up on my screen, and I can give that database a name. Okay, so maybe my database is going to be for my sales department. So I'm just going to create a database called Sales. Okay. And then I got to specify the server. Of course, at this point I've only got one server set up. So I'm going to be pointing to the NYC ExOne server. I'm going to select NYC ex one click OK to that. And this is where I get to specify my database path. Now the default database path is the C programme files (Microsoft Exchange V 15 mailbox), and it's going to try to store it in that area right there. Okay. But I have set up an Eyescuzzy virtual disk, and that means the Scuzzy virtual disc is stored over on myEd, which is actually stored over on a different server. It's actually on the NYC-DC One server. So if you watched my previous lesson, you saw me set up by Scuzzy, and we're actually going to utilise that E-drive here. Okay. So we're going to say "e colons." Okay. And then this path here is where we want to store the transaction logs. Okay. So I'm just going to put one colon for the transaction logs. Okay. And it's going to ask me if I want to go ahead and mount this database so I can select that selected.And it is going to go ahead and mount that database. I'm going to hit Save. Alright? And it's now going to go through the process of creating that database, and then it's going to mount the database, and then it's also going to ask me if I want to restart the service. Okay, so it's done, and you can see that it says please restart the Microsoft Exchange Information Store service on NYC Ex 1. Okay, so it's telling me that the information store service needs to be restarted. Okay? So we can do that graphically very easily just by opening up Server Manager here. going to tool services. We're going to scroll down and find that particular service that they're wanting me to restart. Okay, so we'll go down here to Microsoft Exchange, and here it is right here, the Information Store. All right. So all I'm going to do is I'm simply just goingto right click that and I'm going to say restart. and that's going to restart this service for me. So as you can see, it's running through that, and this is going to restart the service so that it can associate with that new mailbox database. Okay? Exchange is meant to do this on its own, but it's more for safety than anything else. restarting the information store service. We got our information store restarted. I want to now take a look at the database. So what I'm going to do is open up File Explorer. Here we go. into File Explorer. We're going to browse over to that EDrive. I'm just going to verify the database is there and just take a look at it all together here. So here we are in the folder I created earlier called DB. We're going to click on that, and if you look closely, you can see that all the different files are there. Okay, so we've discussed these files in the past. You have the actual database file; you have the different transaction logs that are available for us. So I'm just going to simply say, "Show me the file extension so I can see all the file extensions." So you can see the database, you can see the reserve files, the JRS files, the checkpoint file here, and your different transaction logs. Okay, so it gives you just kind of a quick glimpse of the actual database itself and where it's located at.So what I want to do now is take a look at the Exchange Management Shell, and we will look at creating databases through the Exchange Management Shell as well. I'm going to go over here now, and we can click Start. We can go to the Microsoft Exchange Server 2019 folder, and we can click on the Exchange Management Shell. Keep in mind, it does take a few seconds to load up. I went ahead and loaded it up for us. So here it is. All right, so I want to show you how you can create a mailbox database using PowerShell using the Exchange Management Shell. So to do this, we're going to use a command called New Mailbox Database. All right? So just hit tab on that and then specify the name of the database. And then we can just call the database whatever we want to call it. I'm going to call this one marketing. Okay, so we're going to name it—we put that in quotation marks. All right, marketing. And then the next thing we've got to do is specify where the EDB file is going to be at.So I'm going to say edbfile path, and we're going to do a colon slash. Now if I wanted to, I could store it in that same folder with the sales database. Or, if I want, I could create a different folder. I'm just going to call it marketing band, and we'll call it marketing EDB. Okay? very original names here. And then I'm going to specify the name of the server that this is going to be on, which obviously is going to be this NYC Exoner. Okay. So there's a dash server switch, and we're going to do NYC ExOne, and we're going to go ahead and hit Enter. Okay, so the database has been created, and you'll notice there it is: it says please restart the Microsoft Exchange Information Store. So it is asking me to restart. I did that earlier for you graphically. Let's do it through PowerShell now. So I'm going to restart the service. And then we're going to do the name of theservice is Ms. Exchange is Keep in mind, guys. You could have typed "Get Service" and it would show you all the services, and that way you could have identified this particular name here, which I'd already done. So at that point I was able to basically just run the command, and as you can see, it's going through the process now. It stopped the service, and it's officially starting the service now. Okay, so it only takes a few seconds, and then at that point you've got your service ready to roll. All right. So here we are, and the database is there. I'm going to type, get mailbox database. going to hit enter. And what is it going to do now? It's going to query Microsoft Exchange and show me the different databases. So as you can see, I have the marketing database listed there. However, right now, if we look at this marketing database in Exchange, let me go back over here into Exchange Admin Center, and we'll just simply refresh the screen here. You're going to notice that the database currently isn't mounted. The marketing database is not mounted. And of course I could mount it graphically if I wanted to, but what's the fun in that, right? Let's do it. Through PowerShell. So I'm going to go now and I'm going to type "mount dash database." So it's "mount database" and the parameter is "identity." And then we're just going to specify the name of the database, which is Marketing. At that point, it's going to go through the process of mounting that marketing database. The database is now mounted. I can jump back in here to the Exchange Management Center, and I can refresh the screen, and you'll notice that it is now officially mounted, the database itself. If we edit the database marketing database here, you'll see that it is on the Edrive. Marketing DB and Marketing EDB are the locations. Okay, so what if I want to move this database to a different place? So what if I want to take it away from this ED and maybe put it on, I don't know, the C drive? Okay, why don't we do that? Let's create a folder on the C drive, and I'll just call that folder marketing. And I'm going to move the marketing database. Now I can't do that graphically. I'm going to do that with PowerShell. Okay? So we've got to jump back over here into the EMS, all right? And we'll type "move database path," okay? Identity. And we're going to specify the name of the database, which is marketing. Okay? And then we're going to specify the EDV file path here that we are going to move the database to. We are going to move the database to Cmarketing Marketing EDV. Okay? And then, in terms of the log, we have to specify that as well. So we're going to say logpath, and it's also going to be the CCOONmarketing folder. So we're going to hit enter, and it's now going to process all of that. It's going to go through the process of moving it.Oh, it's going to actually make me confirm it as well. So it says, Are you sure you want to do this? I'm going to say yes. Do it. Yes to everything, basically. All right. To perform the manoeuvre, the patient must be temporarily dismounted. Are you sure you want to do that? Yes, go ahead and let it temporarily dismount. And now it's officially going to go through that process of moving the database. Okay, so the database has officially been moved, and I should be able to open up File Explorer, go over here to my C drive marketing, and the database should now be safely tucked away inside that folder. And as you can see, the marketing database is now on the C drive. Now my sales database is still over in that database folder on the edge, but the marketing DB folder, as you can see, is now empty on that e-drive. Okay? All right, guys, hopefully that gives you a good understanding now of going through the process of creating databases both graphically through the EAC as well as using the Exchange Management Shell.

6. Configuring Mailbox Databases

As always, we're going to use the server option here for databases. And then here are a couple of databases that we've already got available to us. OK, so I'm going to click on the sales database, and I'm going to click this little edit icon, a little pencil icon here. We're going to edit that. All right? And this is going to allow us to go in. Now we're going to be able to change some of the different options that are available. All right? So we'll go right here under limits, and let's take a look at these different limits that I've got available. So first thing you'll see there is you'llsee an issue, a warning at, okay? So the warning will be issued at 1.9 gigs. So that means that at 1.9 gigs, the user will eventually get a message in their inbox that says, "Hey, you are running out of space." You have got to start freeing up some space or you'renot going to be able to send and receive email. Okay? So we're going to set that warning limit. We're going to set that to three gigs for salespeople. The next thing you'll notice is the prohibited send at, which is set to two gigs. So what's going to happen right now is that when they get to two gigs, it's going to prevent them from being able to send. Well, that's not going to work because our warning level is at three gigs. So why don't we set the prohibitsend at, we'll say, 3.5 gigs, okay? The next option is to prohibit send and receive, and that's set for 2.3. We're going to set that to four gigs. So when we get to four gigs, you can't send or receive. All right? But they are going to keep getting these warning messages until they free up some space in their mailbox. Okay? And then we've got to keep deleted items for a certain amount of time. So essentially, we haven't really gotten into the whole deletion of items yet in exchange, but we have "soft deleted" items where items will get deleted and then they can be permanently deleted after a certain amount of time. So this is telling you to keep these deleted items for 14 days. We're going to change that to 30 days. Okay? So now these items will be retained for 30 days. And keep in mind, we are going to get into some more concepts when it comes to dealing with user-deleted data in some of our further discussions. Because obviously objects getting deleted or items getting deleted from people's mailboxes is kind of a touchy subject, we want to make sure that we have that information backed up somehow. Okay. The next thing you've got is the option to keep deleted items and deleted mailboxes for a certain number of days. Okay? So this is going to happen if you delete somebody's mailbox. Let's say you had an employee who left the company and you decided, okay, we don't need this mailbox anymore. We delete the mailbox. Exchange is going to hold on to that. It's going to basically do a soft delete for 30 days. You'll be able to recover that mailbox. We're going to set that to 60 days. So Exchange is going to hold on to mailboxes in this database for 60 days. Okay? The other option you'll notice is that I can tell you not to permanently delete items until the database is backed up. So essentially, the cool thing about that is that it's going to keep storing your database and your data in the database until that stuff gets backed up and you have actually performed an official backup on the database. All right, now the other thing you'll notice down here towards the bottom is I have a warning message interval right here that will let me set when the warning message is going to go out. You'll notice the warning message is going to go out every midnight, essentially at 12:00 a.m. It's going to happen. It's going to send these warning messages out. If you wanted to, you could customise this further and adjust that schedule a little bit if you wanted. If you want it to happen during other hours, you can alter these little fields here, and it will actually send the warning messages out at another time as well. Okay, so these are some of our limitations; these are some of our limits that we've got on our database right now. We're not getting into offline address books yet or all about the maintenance and journaling and all that stuff just yet, but I wanted to go over these limits with you guys real quick. And I also want to show you that I can save all of this and that I can also tweak all of this using the EMS, using the Exchange Management Shell. Okay? So what I'm going to do now is I'm going to open up EMS, and we're going to look at how we can do this using PowerShell. So I'm going to go into the EMS now, and the first thing I want to do is I just want to see my databases. So I'm going to type "get mailbox database." We're going to hit Enter on that, and it's going to display those same three databases that we saw earlier. Okay? So the one I want to target here is the marketing database. And we're going to change some of the parameters of that marketing database right now. So I'm going to set up mailbox database identity, and it's going to be, of course, marketing. And then we're going to do the deleted items retention parameter, and we're going to set that to 20. And the way that this is going to work is that you'll do 20 dots, and then you're going to do the hours, minutes, seconds, and all that. So you're going to do this right here, and that's going to be the format that it'll have to be in. So 20 periods followed by zero, zero. The next thing I'm going to do is enable circular logging in the parameters. This is kind of a neat parameter. This will enable circular logging with the logging of the database. and you can see that graphically. Now if I want to turn this on, I'm going to have to do a dollar sign true.Okay, now I don't know how familiar you are with dealing with what's called boolean in PowerShell, but that's a true or false statement. You can use a true or false statement in PowerShell at any time. True or false, it will always be a dollar sign. So that's always going to be the way it's going to work. All right. So in this case, I'm turning it on. So now what I'm going to dois I'm going to do dash prohibit. Let's do prohibit send quota. All right. and we'll set that to 2.2 GB. Let's do that. All right. So I've got my parameters in there that I want. I could, of course, specify other parameters. Remember, you can do a dash, and you can cycle through all the different parameters that are available. And of course, as I've told you before, it's a good idea to open up the knowledge base on Microsoft's website for this command. So you can see all the different parameters, and you can also see an example of using the command. You see a couple of examples of using the command. Okay, so as you can see, I've now officially set this up. Now one thing I want to tell you about is that anytime you change parameters like this, it's going to want you to dismount and remount the graphical tool. can do this automatically, but the EMS does not. So I'm actually going to type "dismountdatabase identity" and then the name of the database that I'm dismounting. So we're going to dismantle the marketing database, and it says, "Okay, are you sure you want to do this?" Yes, I am sure I want to do this. And it's going to go through the process now of dismounting the database. And then at that point, we're going to remount the database. So we're going to say "mount database identity marketing" and it's going to now officially remount that database, and I will be able to go ahead and verify that all of that is done. And we'll actually check the various parameters that are currently in that database to ensure that it sets the parameters to what we want them to know that it's mounted. I'm going to minimise EMS, jump back into the EAC Exchange Management Center here, and we're going to go ahead and click on this marketing database, and we'll go ahead and edit the marketing database, and we'll check on the limitations that were set. Okay, so click on the limits here. As you can see, this is all set up. The way I had it, I had set the "keep deleted" items for 20 days, and the other parameter that I had set was the "prohibit sending out." So all that got changed for me exactly the way I wanted the PowerShell command to do it. So hopefully that gives you a good understanding of going into the EAC and modifying some of the different database parameters, as well as using the exchange management shell to modify these parameters. So hopefully that gives you a good starting point. And now that we know how to create databases and do some configurations, we can eventually start moving towards creating recipients and tying those recipients to our databases and all that.

7. Troubleshooting Mailbox Databases

That Microsoft has available to us to assist us in dealing with problems with our mailbox databases. So first off, we have this tool called the Esu Util. OK? The ESE Util is going to be one of your main tools that will help you deal with database-related problems. One of the things that can happen sometimes with databases is what's called a dirty shutdown. Some of your services can get shut down, and the database doesn't get properly mounted. And in a dirty shutdown of a database, it cancause issues with the database getting fragmented and all that. So Microsoft has this tool available to us for checking to see if a database is healthy, if it's clean, or if it's gone through a dirty shutdown. And of course, we can also go through the process of trying to repair any corruptions, as well as do a defragment of the database. Okay, so, as you can see in this slide, we've got a bunch of different switches that are available to us. What we're going to want to do is we're going to want to dismount our database, and we are going to want to run some of these commands in order to check to see if our database has been through a dirty shutdown and if it needs to be defragmented, and we can fix corruption and all that using this command. Okay, so that gives you a little idea. Why don't we jump over now and I'll run a couple of these commands and show you how this is going to work? I'm looking at my databases, and right now my databases say they're mounted. Everything's looking fine. Your database here is active. It's mounted. But what if it's not active? What if it's mounted? It's not active. What if you boot your Exchange server up and you're noticing that it's not able to actually bring this database online? You're getting an error message. All you have to do is look in the event viewer. If I start the right click the start button here,I can open up my Event Viewer and I cango through my logs and look to see what mylogs are saying in regards to Exchange. If Exchange is throwing errors involving my database, okay, so I have application logs I can look at here. I can also load up the operating system logs. And if you expand right here under Application and Services Logs, you can actually look at logs that are specific to Microsoft Exchange. Over here, we've got Microsoft Exchange management. Okay. And I've only got so much memory, so it's lagging on me just a little bit. But if you look, you can check out these logs here for Microsoft Exchange. You can look for errors and things like that that are going on. Of course, I actually do have a couple of errors, but they're not related to my database. Okay. But my point is that you can go through this, and you can look through your exchange logs. You can look through the application log or the system log. You can look for errors and for things pertaining to your database. Okay? Now, as far as also analysing your database and trying to determine what's going on, what I want to do is I want to go into EMS for this. Okay? So we're going to open up the exchange management shell. All right? And I'm just going to clear the screen so we can get a good look at it, and we have the squash. But what I want to do first is to stop the database or dismount the database that I'm going to be looking at. So I'm actually going to say, "Get mailboxdatabase," and that will list out our databases. And I'm going to run the dismount database of identity marketing, and we're going to dismount that marketing database. It says, "Okay, are you sure you want to do it?" Yes, I'm sure. And then, at that point, we are going to run this command here, which is going to be the Escutil. So I'm going to say escutilla. And I'm going to do it, MH. Okay. And this is going to show me the health of the database. So I'm going to do a colon sliding dot EDV. Okay, so it's generating a bunch of information for me here to look at. All right, as you can see, Esetailmh, this is goingto show me the health of the database, and Iwant to just kind of look through this. It's given me some information, and this is what I want to see. Not a dirty shutdown, but a clean shutdown. Okay? Now, of course, if this was a dirty shutdown, I could still go through and run through the defragmenting process and all that if I wanted to try to fix some issues. If the database is fragmented or whatever, I can do this. I can type "Esetails." This is going to be for defragmenting, and we're going to do CCMP marketing. EDB okay. And as you can see, it'sgone through and it's fragmented. It's defragmenting the database. It went really fast because obviously it's not actually fragmented. Okay? So at that point, the only other thing I really need to do is bring my database back up and running. So we'll say "mount database" and we'll do "identity marketing," and that's going to bring our database back up. All right? So that gives you a little bit of information. You definitely should familiarise yourself with these different ESC utility switches you saw in my slide and try them out a little bit. Practice with those a little bit. It's not something commonly we should haveto do a whole lot in exchange. But definitely if your databases, something happens, theyget something like a dirty shutdown occurs. You can clean that up, fix that defragment, and then, don't forget, keep an eye on the event viewer for any errors or anything like that you get so that you know that something's wrong. Of course, if you go into your Exchange Administrative Center and you notice that your database is mounted but it's not active, something is wrong. You try to bring it online; it's not working. You tried rebooting. Maybe your server is not working. At that point, it was probably a dirty shutdown, and you need to be looking into this ESC unit, all right? So hopefully that gives you guys a good idea, understandingof that, just a little bit of the troubleshooting conceptsin dealing with Exchange, and definitely you want to bea little bit familiar with that Escutill. If you're going to take the exam, you need to know what that Escut does. The fragmentation, the dirty shut down, and everything else.

Go to testing centre with ease on our mind when you use Microsoft 365 MS-203 vce exam dumps, practice test questions and answers. Microsoft MS-203 Microsoft 365 Messaging certification practice test questions and answers, study guide, exam dumps and video training course in vce format to help you study with ease. Prepare with confidence and study using Microsoft 365 MS-203 exam dumps & practice test questions and answers vce from ExamCollection.