کد:
http://articles.techrepublic.com.com/5100-10878_11-6155914.html?tag=rbxccnbtr1
This article is also
available as a TechRepublic download.
The release of new versions of software means learning new tricks. Exchange Server 2007 is no different: When you deploy it, you must learn the new way of doing things at the same time. Here are some of the things you'll have to know how to do.
Adjust mailbox quotas
One common administrative task is the adjustment of mailbox quotas. In case you're not familiar with mailbox quotas, quotas provide a way of limiting the size to which an Exchange Server mailbox can grow.
In Exchange 2007, mailbox quotas can be set at the database level or at the individual mailbox level. To set mailbox quotas at the database level, open the Exchange Management Console and navigate through the console tree to Server Configuration | Mailbox. The upper half of the details pane will then display the Exchange 2007 servers in your organization.
Select the server that contains the database you want to set the quota on, and the lower half of the details pane will display the storage groups and databases contained on the server. Right-click on the database you want to impose a quota on, select Properties, and the management console will display the Mailbox Database Properties sheet.
As you can see in
Figure A, the quotas work very similarly to the way they did in Exchange Server 2003. You can set separate threshold values for issuing a warning, prohibiting messages from being sent, and prohibiting messages from being sent or received. This tab also contains the settings for the retention of deleted items.
Figure A
You can set database-level message quotas through the Links tab on the Mailbox Database Properties sheet. To set quotas on an individual mailbox, navigate to Recipient Configuration | Mailbox. The management console will then display a list of all of the mailboxes found in the Exchange Server organization. Right-click on the mailbox you want to set the quotas for, and select the Properties command from the resulting shortcut menu. You will see the mailbox's properties sheet.
Go to the properties sheet's Mailbox Settings tab and select the Storage Quotas icon and click the Properties button. The management console will now display a Storage Quotas dialog box that contains the exact same settings that you saw in Figure A.
The Exchange Management Shell
You've probably heard that there are two different mechanisms for managing Exchange Server 2007; the Exchange Management Console and the Exchange Management Shell. The Exchange Management Shell is a command line environment that allows you to enter commands manually, or script complex management processes.
The Exchange Management Console is actually built on top of the Exchange Management Shell, and issues Exchange Management Shell commands behind the scenes. Anything that can be done through the Exchange Management Console can also be done through the Exchange Management Shell. The reverse is not always true; there are some tasks that can only be performed through the Exchange Management Shell.
For the purpose of simplicity, I'm using the Exchange Management Console where possible in this article. To give you an idea of how the Exchange Management Shell works, I want to quickly show you how to adjust mailbox quotas using the Exchange Management Shell.
You can launch the Exchange Management Shell by selecting the All Programs | Microsoft Exchange Server 2007 | Exchange Management Shell commands from the start menu. When the show opens, it looks remarkably like a normal command prompt window, as shown in
Figure B.
Figure B
The Exchange Management Shell looks a lot like a normal Command Prompt window. Now suppose that you wanted to implement a quota that prohibited to users from sending messages was their mailbox reached 1 GB in size. To do so, you would enter the following command:
Get-mailbox | set-mailbox –prohibitsendquota 1gb
Once the command executes, you can verify that it has worked by entering the get-mailbox command. Doing so will display a list of all of the mailboxes, along with their quotas.
Monitor system health
Exchange Management Console includes a container called Toolbox, which provides a number of troubleshooting tools. Toolbox contains everything from a queue viewer, to the Best Practices Analyzer, to the Performance Monitor. These tools are all handy, and I highly recommend taking time to see what all is available to you. However, if you want to simply check your system's health, there is no tool that will allow you to quickly do so. Many of the tools will allow you to gain some idea of the system’s health, but you need to know how to interpret the results.
If you truly want to find out how healthy your Exchange Server is, there are some special commands that you can enter into the Exchange Management Shell. The next version of Microsoft Operations Manager will actually monitor system health by using these exact same commands.
Open the Exchange Management Shell and enter the following command:
Test-servicehealth
Upon pressing [Enter], you will see a screen similar to the one that’s shown in
Figure C. Notice that each of these server’s roles are displayed, along with a true or false status that indicates whether or not the required services are running. In this particular case, all of the necessary services are running. Had one of the service is not been running, you could start it from the Exchange Management Shell by entering the NET START command followed by the service name.
Figure C
The Exchange Management Shell indicates whether or not all of the required services are running. Another way in which the Exchange Management Shell can be used to diagnose system health is by allowing you to test MAPI connectivity. To do so, enter the following command:
Test-MAPIConnectivity
Upon doing so, the Exchange Management Shell will display a screen similar to the one that’s shown in
Figure D. As you can see, the Exchange Management Shell indicates that the server was able to communicate with the mailbox database successfully, and had a latency of 8 ms.
Figure D
The Exchange Management Shell can be used to test MAPI connectivity.
Move mailboxes
In larger Exchange Server organizations, it often becomes necessary to move mailboxes from one server to another. Fortunately, moving mailboxes in Exchange 2007 is simple. Begin the process by navigating to Recipient Configuration | Mailbox. When you select the Mailbox container, the console's details pane will display a list of every mailbox in the entire Exchange Server organization.
If you look at
Figure E, you will notice that the Recipient Type Details column lists some mailboxes as being legacy mailboxes, while other mailboxes are listed as being User mailboxes. Anytime you see a mailbox listed as being a user, room, or equipment mailbox, that mailbox is hosted on an Exchange 2007 server. Legacy mailboxes typically reside on Exchange 2003 servers.
Figure E
The Exchange Management Console displays a unified view of every mailbox in your entire Exchange Server organization. Depending upon the size of your organization and the number of mailboxes that need to be moved, having a unified view of all of the mailboxes in the entire organization might not be practical. For example, if you needed to move 10 out of 10,000 mailboxes, then you certainly wouldn't want all 10,000 displayed. Fortunately, the Exchange Management Console allows you to easily create a filtered view that displays only the mailboxes you want to see.
For the purposes of this article, let's assume you wanted to migrate all of the mailboxes off of one of your exchange servers. Let’s create a filtered view that displays only the mailboxes found on that server. You can create filtered views based on many other attributes using the exact same procedure as what I’m about to show you.
Begin by pressing Create Filter. When you do, a series of drop-down lists will appear at the top of the console. These drop-down lists allow you to enter a condition for which you want the list of recipients to be sorted. Since our goal is to migrate all of the mailboxes from a specific server, let’s filter the recipient list so that only recipients with mailboxes on that server are shown.
Select the Server option from the first drop-down list, and leave the second drop-down list set to Equals. Press Browse and you should see a list of all of your organization’s Exchange servers. Choose the server you want to migrate and click OK. Press Apply Filter and the list will be filtered to display only recipients with mailboxes on the selected server.
Now that the list has been filtered, it’s time to move the mailboxes. You can move all of the mailboxes at once, but I recommend moving a couple of mailboxes individually first so that you can make sure that the migration process is working correctly. If you are concerned about the integrity of your user’s mailboxes, you could always create a few sample mailboxes and fill them up with junk mail as a way of testing the migration process before you attempt to migrate live data.
To migrate a mailbox, right-click on the mailbox and select Move Mailbox from the resulting shortcut menu. Exchange will launch the Move Mailbox wizard. The wizard’s initial screen prompts you to select a server, storage group, and database as the destination you want to move the mailbox to.
Press Next and you will see a screen asking you what you want to do if corrupt messages are found within the mailbox. You have the option of either skipping the mailbox or skipping the corrupt messages. If you choose to skip the corrupt messages, then you have the option of specifying the maximum number of messages to skip before the migration is aborted.
Press Next and you will see a screen asking you when you would like for the mailbox to be moved. The default option is to move the mailbox immediately, but you can schedule the move for another time. Scheduling the migration is useful if you are afraid of disrupting user productivity or disrupting the nightly backup.
After setting the migration schedule, press Next and you will see a summary of the migration options you have chosen. As you look over the summary, pay particular attention to the number of mailboxes to be moved. Otherwise, you could be in for a nasty surprise if you accidentally selected the wrong mailboxes. If the summary looks good, press Move to move the mailboxes. When the move completes, press Finish to close the wizard.
Access Outlook Web Access
The last thing that I want to show you is how to use Outlook Web Access (OWA). In case you hadn’t heard, OWA has been completely redesigned in Exchange 2007. For example, OWA now supports autocomplete. This is possible because autocomplete information is now stored in the Active Directory. In addition, spell check has been improved, and flags and categories are now completely supported.
In order to access OWA, one of your servers must be hosting the Client Access role, and you must know the name or the IP address of this server. You can access OWA by opening Internet Explorer and entering the following URL:
https://servername/OWA
Upon connecting to the client access server, a user will be prompted to enter their username and password. The logon screen also gives the user the option of telling OWA whether they are using a public or a private computer. A check box on the screen also gives users the option of using OWA Light. OWA Light is typically used in low bandwidth environments.
The first time that a user logs on to the client access server, they will be prompted to select a language that they want to use, and to verify that the currently selected time zone is correct. Once the user presses OK, they are taken to the main OWA screen, where they should feel right at home