Sumario

Exchange Server 2007 acabo con el limite de 32kb en reglas para un usuario, de manera predeterminada, ahora todo usuario ya trae ese limite y podemos subir este valor hasta 256kb.

Contenido 

Vamos a utilizar el usuario administrator en nuestro ejemplo y vamos a cambiar el limite de reglas para este usuario, siguiend los siguientes pasos:

1. Abrir el Exchange Management Shell
2. Vamos a utilizar el cmdlet Set-Mailbox para modificar la propiedad RulesQuota, de la siguiente manera:
   
   set-mailbox <usuario> -RulesQuota:(tamaño)KB
   
   entonces:
   
   set-mailbox administrator -RulesQuota:256KB
   
3. Para verificar el resultado, usaremos el cmdlet get-mailbox.
   get-mailbox <usuario> |select name, rulesquota
   
   entonces:
   
   get-mailbox administrator |select name, rulesquota
   
   
4. Todo el proceso desarrollado en estos pasos, se muestra en la siguiente figura:
    

Conclusion

En este tutorial, mostramos como aumentar el limite de reglas para un usuario especifico a traves del Exchange Management Shell, con la flexibilidad de que el nos proporciona al poder alterar valores para uno o varios usuarios simultaneamente.

Summary 

Exchange Server 2007, thru its Exchange Management Shell, lets us get mailbox statistics and also lets us get information of a specific mailbox.

More Information

We can review the statistics of any mailbox with the cmdlet GetMailboxStatistics, in the following way:

Get-MailboxStatistics <username> | fl

With this cmdlet we will get lots of interesting information, such as:

• Total size of the deleted items
• Name of the user's database
• Date of last logoff
• Date of last logon
• Last account that logged on to that mailbox
• Number of deleted items
• Total size of the items
• Name of the Storage Group
• Informations about the limit status

In the example below, we use the pipe |fl in order to get the results formatted in a list.

If we want to get even more information, we can use the cmdlet Get-MailboxFolderStatistics:

Get-MailboxFolderStatistics <username>

With the help of this cmdlet we will obtain information for each folder of each mailbox, and within those informations, we will get the following data:

• Number of items on the folder
• Folder Path within the mailbox 
• Size of the Folder
• Number of items in the folders and subfolders
• Date of the oldest and newest size of the folder
• Si es administrada o no

In the example below, we used the pipe |ft for the results to be shown on the table.

Conclusion

In this tutorial, we showed how to how to get statistic information on a mailbox and every folder on it, and we learned how to display output on powershell, on list and table formats.

Summary

We are going to show how to manage Outlook Anywhere, (also known as RPC over HTTP). We are going to show in a few steps how to deploy this feature on Exchange 2007.

More Information 

To add Outlook Anywhere in our Exchange Server 2007 computer, we have several steps to complete, and also some requirements:

• Install IIS 6 Resource Kit (http://www.microsoft.com/downloads/details.aspx?FamilyID=56fc92ee-a71a-4c73-b628-ade629c89499&DisplayLang=en)
• The Windows Server 2003 media to install the RPC over HTTP Proxy

The environment for the solution that we are going to show is the following:

We have an Exchange Server 2007 computer with the Client Access, Hub Transport and Mailbox Server roles, and we are going to use a temporary certificate with the help of SelfSSL, a free tool. The best way to do this is by purchasing a certificate, because otherwise we must install a non-trusted certificate in the workstation and that generates additional actions on the client side.

Installing RPC over HTTP Proxy

To install RPC over HTTP Proxy, we must follow these steps:

1. Click on Start, select Control Panel
2. Select Add/Remove Programs
3. Click on the left side on the Add/Remove Windows Components section
4. Select Networking Services and click on Details
5. Select RPC over HTTP Proxy and click on OK in all the windows 

Validating the installation of RPC over HTTP Proxy

To check if the installation was successful, we must go to the IIS Manager and check that the Rpc and RpcWithCert are present, as shown in the picture.

Configuring OutlookAnywhere on our Exchange Server 2007 computer

Ahora vamos a configurar OutlookAnywhere en nuestro servidor Exchange Server 2007, esto se realiza en cada servidor en el nivel de Server Configuration y en la parte de Client Access. Debemos realizar los siguientes pasos: 

1. Open Exchange Management Console
2. Expand Server Configuration
3. Click on Client Access
4. On the Result Panel, select the desired server to configure 
5. On the Work Panel, click on owa (Default Web Site)
6. On the Toolbox Actions, click on Enable Outlook Anywhere

7. On the new window that will be opened, we must type the name that will be used on the Outlook Client, and also will be used for the certificate. We can leave as the authentication the Basic Authentication, because we are going to encrypt all the communications via SSL. Fill out with the public name, and then click Enable to continue.

8. Completion. We will be informed of the cmdlet used for the deployment of Outlook Anywhere on this computer. We must click on Finish.

Creating a certificate with SelfSSL

We must first install IIS 6.0 Resource Kit and then, follow these steps:

1. Click on Start
2. Select Programs
3. Select IIS Resources
4. Click on SelfSSL
5. Click on SelfSSL
6. On the command line prompt, we must type

selfssl /n:cn=mail.contoso.local /v:365

Where: /m:cn=mail.contoso.local is the name that will be used on the certificate and was already defined for Outlook Anywhere
/v:365 is the number of days that the certificate will be valid

1. Select Y and press Enter

8. Now we must test the configuration, so we must go to Start, select Run and type https://mail.contoso.local

9. Security Alert. We will get a window asking for confirmation about the certificate installed, we must click on Yes. Nota: On purchased certificates, this screen will not appear.

Configuring Outlook 2007 to be used with Outlook Anywhere

1. Select Start, go to Control Panel
2. Click on Mail
3. Click on E-mail Accounts
4. On the E-mail tab, click on Microsoft Exchange Server and then click on Change...

6. Click on More settings...
7. Click on Connection
8. Select the Connect to my Exchange mailbox using HTTP checkbox
9. Click on Exchange Proxy Settings...
10. Type the external address on the https:// field, and select the Connect using SSL only and On slow networks, connect using HTTP first, then connect using TCP/IP checkboxes
    Note: To test Outlook Anywhere on a LAN, we must also select On fast networks, connect using HTTP first, then connect using TCP/IP. 
    

11. Now we must open Outlook 2007, and we will see the following screen. We must click on View Certificate.

12. On the new window, we must click on Install Certificate, and we will see a dialog box showing that the import was successful.

13. Now, to check that everything was configured as expected, we must close Outlook 2007 and we must go to Start, then click on Run and type

Outlook /rpcdiag

14. We will see in the following screen the test to check that the connection to the directory and email was done via https, and also confirming that our tutorial was successfully completed.

Conclusion

In this tutorial, we reviewed

• How to configure Outlook Anywhere on Exchange Server 2007 on the Client Access role. As this feature is server-based, enabling it in more computers will add high availability to this feature.
• How to install a temporary certificate on the server
• How to configure the Outlook 2007 e-mail client

Summary

We are going to show how to configure Outlook 2007 to work with the Out Of Office new features that are available on Exchange Server 2007.

The biggest change that we have on the OOF feature on Exchange Server 2007 can be discussed in these points:

• We now have two OOF messages, one for internal users and the other for external users
• Via OWA we can configure these messages with different formats
• We can setup the OOF to be sent on a specific date and time

More Information

To work with OOF in Outlook 2007, we must follow these steps:

1. Open Outlook 2007
2. Click on Tools, then select Out of Office Assistant...
   
   
   
    
3. In the new window, we can enable (or not) OOF in the first two options. For the purposes of our example, we are enabling thru the (Send Out of Office auto-replies) option and also we configure that this will be enabled during a specific day and time.
   
   In the part below, we have to tabs; Inside my organization will be used to configure the messages sent to the internal network and Outside my organization, that is the place where we are going to define the messages that will be sent to the external users.
   
   
   
4. We can also disable this option for an indeterminate time
   
   
   
5. On the Outside My Organization tab, we can also configure if we want to auto-reply to our know contacts or anybody. As this is going to be a reply to an external mailbox, we will type a more formal message.
   
   
6. After configuring Out Of Office (OOF), we can check on the Outlook 2007 interface, on its left corner, that we have the OOF option enabled.
   
   

Conclusion

In this tutorial, we showed how to configure the new OOF features in Outlook 2007 with Exchange Server 2007.

Summary

Exchange Server 2007 introduces new changes on the existing Exchange Organization, and also there are many ways to migrate from our existing environment to Exchange Server 2007. We are going to discuss the most common migration scenarios.

This tutorial is an overview of the steps required at the time of starting the migration process.

More Information 

We are going to review the possible migration scenarios from the following messaging products:

Exchange 5.5

There is no chance to migrate from Exchange Server 5.5 to Exchange Server 2007, it is necessary to migrate all the resources to Exchange Server 2000 or Exchange Server 2003.

Exchange 200x

The Exchange organization must be in native mode. There is no upgrade in place, we must deploy Exchange Server 2007 into our organization and then move the resources to the new servers. There is no problem related to infrastructure, because we can deploy a x64 Exchange Server 2007 into a x86 Exchange Server 200x organization.

Important: During this transition process, it will not be possible to manage Exchange Server 2003 thru the Exchange Management Console of Exchange Server 2007, the Exchange System Manager will have to be used instead.

The steps for this migration can be reviewed in the following steps:

1. Deploy the Edge Transport Server to prepare an external interfaces for the first Hub Transport deployed computers
2. Deploy the Client Access to provide services to our users
3. Deploy the Hub Transport and prepare the connector communication between Exchange 2003 and Exchange 2007, it will appear on the Exchange 200x's Exchange System Manager a random routing group that will let that process to be done. We must enable the Link State in that server for the message routing.
4. Deploy the Mailbox Server.
5. Move resources (mailboxes, public folders and system folders)
6. Remove the legacy Exchange 200x servers that are no longer required
7. Remove the connectors between routing groups and remove the routing groups

Lotus Notes

A migration from Notes will be possible with a new migration tool called Microsoft Transporter.

Other e-mail servers

Sharing SMTP addresses and moving the resources with tools under development at this moment.

Conclusion 

In this tutorial, we learned how to deploy Exchange Server 2007 into an existing infrastructure, which are the high level steps required in this process and what is possible to do inside our environment.

Summary 

Outlook Web Access in Exchange Server 2007 lets us check important Exchange Server 2007 information. Some of them are: additional features that a Exchange Server CAS computer has assigned, if it is using a proxy or redirecting a CAS server, information about the operating system on the server, among other features.

By logging on in Outlook Web Access, we can discover many important features about our deployed Exchange Server 2007 computer.

More Information

Collecting that kind of data is really simple. We must follow these steps.

1. On the upper area, close to the search box, click on Options
2. On Options, select About.
3. On the right frame, we can see the important information, and we can also click on Copy to clipboard to store that information in memory.

Conclusion 

In this tutorial, we learned how to visualize important information of our Exchange Server 2007 computer, such as organization features, etc, everything by using Outlook Web Access.

Summary

Exchange Server 2007, by its Client Access Server (CAS) role, acts as a proxy for Exchange Server 2003 requests. This is important thru the transition period from Exchange 2000 or Exchange 2003 to Exchange Server 2007. Because of Microsoft's best practices, we must deploy a CAS first into our network and remove all the front-end servers of our environment. This tutorial will show an example of how does this work.

More Information

When a CAS server is deployed, this computer has the following virtual directories:

/Exchange and /Public to keep compatibility with legacy versions

/OWA is the new address in OWA 2007

As the CAS is supposed to be the first server to be deployed in the Exchange Organization, and it is going to replace the Front-End servers, it must be in the internal network (as it was not happening with the previous versions)

We are going to see in an example below how a client is going to work when the CAS server is deployed in the network. In our environment, the CAS role is installed in a server named SRV-AD, and the clients will start to access https://srv-ad/exchange for the legacy versions and https://srv-ad/exchange/public for public folder access.

Now, we are accessing the Client Access Server form that will be Exchange Server 2007, but after the user with a mailbox in Exchange 2003 is being authenticated.

The result will be an user authentication with Exchange 2003 and a screen on 2003 format, but we must take a look at the address.

Accessing Public Folders thru the Client Access Server

So now we are going to access the public folders thru the /Public folder of the Client Access Server and we can access as usual to our data even if the interface is Exchange 2003.

Configuring OWA authentication of Exchange Server 2007 legacy versions
By default, the /Exchange folder uses forms authentication, so to do the same that was already for Exchange Server 2003, in other words, we configure that the users on the Authenticated group that access the /exchange folder on the CAS server, the user will have his/her mailbox automatically opened.

To do so, we must do the following:

1. Open Exchange Management Console
2. Expand Server Configuration
3. Click on Client Access
4. Click on the desired server on the Work Panel
5. Click on the Exchange (Default Web Site) folder in the Result Panel
6. On the Toolbox Actions click on Properties
   
   
   
7. We must go to the Authentication tab and click on Use one or more standard authentication methods: and select Integrated Windows authentication, finally click OK.
   
   
8. We will require to do a iisreset /noforce for the changes to take effect.
   
9. After this procedure, we can access http://<cas-server>/exchange and the OWA will be automatically opened.

Conclusion
In this tutorial we learned how the Client Access Server (CAS) computer works with Exchange 2000/2003 and how to configure authentication for a OWA Virtual Server.

Summary

More Information

1. Some features, new for Outlook 2007, cannot be used without Exchange Server 2007
2. Outlook 2007 does not work with Exchange Server 5.5 mailboxes
3. Some features, new for Outlook 2007, are not available in Outlook 2003
4. RPC over HTTP and lists (Safe and Block Lists) are not compatibles
5. Some new Exchange Server 2007 features, are not available in Outlook 2002/XP.
6. Exchange Server 2007 was not tested with Outlook 2000 because of the product lifecycle. It may work, but it is not supported.
7. Exchange Server 2003 was not tested with Outlook 97/8 because of the product lifecycle. It may work, but it is not supported.

Now that we know the Outlook versions that we can deploy with any Exchange Version, we are going to compare the new features of Outlook 2007 compared with Outlook 2003 and OWA (Outlook Web Access) 2007.

Conclusion

Overview

Exchange Server 2007 has a totally different Outlook Web Access (OWA) interface compared to its older versions and has many new features. In this tutorial we are going to compare the end user experience using OWA during the coexistence period of different versions of the product.

More Information