From the course: Planning and Configuring a Microsoft Messaging Platform

Manage mailboxes - Microsoft Exchange Server Tutorial

From the course: Planning and Configuring a Microsoft Messaging Platform

Start my 1-month free trial

Manage mailboxes

- [Instructor] We're logged into our Exchange 2019 On-premise server, where we will create a new mailbox. So we're under Recipients and Mailboxes. Let's click on the plus and choose User Mailbox. Now if we already have an existing user in active directory that doesn't have a mailbox, we can click on Browse, and it will find one. But in our case, we don't have any, so we're going to choose the New User. And we're going to enter an alias, which is going to be used for our email address. Now we'll put in our user login name, and our password. Now we can also require the password get changed at the next logon, and that adds additional security because we'll never know what password they're using. As the administrator, you're only allowed to reset the password, not actually see the password directly in active directory users and computers. So once you have it set the way you want, you can click Save, and now we see the user. Now if we double click on the user, and click on the edit pencil, we see a lot of information about the user, and the one thing I want to draw attention to, is the email address. It automatically created an email address based on our email policy, and we see it's carrie.lynn, just as the alias said. Now we're going to do the same thing, but we're going to do this using PowerShell. We're going to use the new dash mailbox command. And don't worry about the upper and lowercase. It really doesn't matter except when you're typing passwords. Now we're going to type in the user principle name. And we're going to enter, the techpub.us account instead, followed by an alias, and then we're going to put in the name. This will be the full name and because it has a space in it, I'm going to use quotes. This is going to be followed by the database, and if you have only one database, then you don't need to do this but if you have more than one, you'll want to specify the one that you want to put it in. And then the organizational unit. Now, if you don't want to put in the organizational unit, that's okay, it will just default to the users group. After we've double-checked everything, we can go ahead and hit Enter. Now it wants to know our password, and we see the user's been created. If we minimize that and go back into our Exchange admin center and hit Refresh, we can see that the new user is created. Let me draw you, once again, to the SMTP email properties. We click on email address, even though we specified techpub.us, it actually used the email address policy to switch that to techpub.net. Now, we can add an alias, if we'd like, and it will allow use to do that, there we go, but the default is going to be the joshua@techpub.net, and we set that policy up in a previous video. Now, let's do the same thing but, this time, we're going to do it in Microsoft 365. We're going to start by clicking on Add user under User Management and we'll get a new wizard that pops us. This time we'll put in new user, first name, last name. Looks a little different but we're going to end up with the same thing. It automatically adds the display name, based on your first and last name, and now we're going to put in the user name, and once again, upper, lower case don't matter for the user name, just the password. Here we can Auto generate a password or Let me create a password. I'm going to choose to Let me create a password and I'll enter that here and, once again, we can have the user change their password when they login. I'm going to uncheck that, we don't need to do that, but you might in your organization. Going to also send the password in an email. Next, now, we have to assign a product license. We didn't have to do this with the On-premise Exchange, but we do with our Microsoft 365. So, we already have some licenses available, so we're going to assign a user product license, and we see that the E3 Developer one is available for us. If you don't see one here, you'll have to go to the licensing section and purchase a new license. However, if you don't need to receive email right away with the user, you can click the option to create a user without the product license. It will allow you to create the user, but they won't be able to receive any email until you pay for the license. Next, now, we have the option to set the roles, for this particular user, and we can see that the user is not going to have administrator access. We can also make a change to that and we can allow the person to be a global administrator, help desk service, Et cetera, et cetera. So, there's several different options that we can choose for that. I'm just going to say No administrator access for this user, and click Next. Everything is in place for us to add this new user so we'll go ahead and do that, and now we'll close, and we'll click on Active users, and there we go. We see both of our users here. Now, if we were to go to Show all, and we can get into the Exchange admin center for Microsoft 365, you'll see something interesting. Go to our Recipients, and Mailboxes, and we see the two users plus, of course, the journal user, and that's not something you're going to see in the General admin center, just the Exchange admin center. What's interesting is that I cannot create a user in the Exchange admin center. If I go to mailboxes in the On-premise admin center I see this plus sign, where I can create a user but if I go to the Microsoft 365 admin center, and then I go over to Exchange, the plus sign is not there. You have to go through the admin center the way I did it in order to add that user. There's also a way to link using PowerShell to Microsoft 365 and then you can add the license and the user that way as well. It's a similar procedure to what we did with the On-premise Exchange server with the exception of the command to add the license. Using the graphical user interface, we can create a single mailbox very quickly. However, if we have the need to connect remotely or we need to create many new mailboxes, PowerShell may be the best solution.

Contents