Exchange 2003 | Blog Bujarra.com

Moving Microsoft Exchange Databases 2003

To help you understand how Exchange databases work, We have two databases in principle, one would be the private DB and the other the public DB, There are two files: priv1.edb and pub1.edb respectively. These files grow as users' mailboxes grow, are by default in: “C:Program FilesExchsrvrMDBDATA“, What I usually do is take them out of the system partition and put them in the data partition which is really the one I'm interested in in case one day I have to format a server. To do this,: “Beginning” > “All Programs” > “Microsoft Exchange” > “System Administrator”

Configuring Limits in Microsoft Exchange 2003,

Message send/receive size limits, including the maximum number of recipients in an email in the To, CC or BCC and storage limits, and so on.

Indexing Microsoft Exchange Databases 2003

In order for our Exchange server to work perfectly, the databases must be tested daily, so that searches from MS Outlook have quick results, and don't take long to open email attachments. To do this, we open the MS Exchange console again, “Beginning” > “All Programs” > “Microsoft Exchange” > “System Administrator”

Setting up MFIs – Smart Message Filter Service – Inteligent Message Filter

Si queremos evitar SPAM/correo basura con un servidor de correo Microsft Exchange 2003 and we don't want to install third-party software, podemos habilitar el IMF para que el correo entrante lo clasifique automáticamente como “Unwanted” or as normal. To do this,:

Configure a Microsoft Exchange server 2003 as a Front-End Server

The interesting thing in an organization is to have secure access from the outside, That's what DMZs are used for, and logically we're not going to put an Exchange server in it with its mailboxes, since users do not need to access from the LAN to the DMZ. What you do is create one or more servers that act as a Front-End in the DMZ that have Exchange, but only for external connections, SMTP and HTTP/HTTPS traffic would enter so that users from the internet can view mail by OWA. In this step, we will create a Front-End server and see how it would be configured. It is assumed that in the LAN we will already have our(s) server(is) with MS Exchange mailboxes accessed from the LAN with MS Outlook-type mail clients.

Setting up a cluster in Microsoft Exchange 2003

This document explains how to create a virtual server with one or more Exchange servers, It is ideal to have the back-end servers always available and in the event that one of them goes down, the virtual server continues to be up depending on another. The steps that should be taken:

Installing additional Microsoft Exchange servers 2003

This procedure explains how to install an additional server in an MS Exchange organization 2003. It's simply the installation procedure.

Installing the first Microsoft Exchange server 2003

This procedure explains how to install it on a Microsoft Windows 2003. The installation of the first server being that of this procedure.

Exchange shutdown problem 2003 in Domain Controller

Este es un procedimiento ‘sencillo’ es para cuando se tiene instalado Microsoft Exchange 2003 en un servidor MS Windows 2003 con función de controlador de dominio. Es un fallo reconocido por Microsoft pero no solucionado (hasta ahora), así que si tenemos eso instalado cada vez que queramos reinciar o apagar el servidor podemos tirarnos fácilmente 30 minutos esperando a que acabe de cerrar todo, para evitar estar ese tiempo, la ‘solución’ es crear un fichero BAT con estas lineas para que pare los servicios y luego ya apagemos o reiniciemos el servidor de forma manual; el problema es que se pega Exchange 2k3 con IIS 6.0. Puedes bajar el BAT de AKI y hacerlo tu a mano con estas lineas como mínimo:

Using ESEUTIL – eseutil.exe on Microsoft Exchange 2003

Microsoft Exchange Command-Line Tool, to perform maintenance on Exchange databases and LOG files. To access it through it, it is done through the MSDOS console and in the PATH: “C:Program FilesExchsrvrBIN”. It must be done in databases that are not in use, and they don't have to belong to the same server.