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.
This procedure explains how to install an additional server in an MS Exchange organization 2003. It's simply the installation procedure.
This procedure explains how to install it on a Microsoft Windows 2003. The installation of the first server being that of this procedure.
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:
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.
This is useful when we are performing a server migration, in the event that we are going to change the IP address DNS servers or the server DNS server, we must change its DNS servers in all positions. The posts may be configured with a dynamic IP address so the change is very simple and we will change it only on the DHCP server. But.. What happens if our posts have a fixed IP address? That we should change the 'Preferred DNS Server'’ and the 'Alternate DNS Server'’ or manually or with the help of a simple script that we can put in the login of the posts through a GPO.
DNS is the service that offers us computer/domain name resolution. Below we will look at the installation and configuration process for Windows 2000 o Windows 2003.
When we set up a net, Or when we migrate one and it has a fixed address, we remember how good it would be to have a DHCP server set up and forget about the issue of going post by post modifying any network data. DHCP is used to save a network administrator work, IPs are configured from the server, a range of IP addresses to be assigned to the positions is established and that's it, We can also include, all the data that interests us apart from the IP, such as, What is the gateway, DNS, WINS and many more. We can assign the duration of the IPs in the clients, by default are 8 days. We can reserve IPs by MAC addresses. And see the list of assigned IP addresses.
One of the new features brought by Microsoft Windows 2003 RC2 is the new console for configuring DFS and configuring replicas that now work perfectly. The most important thing is that you have to have the RC2 version on the servers that are going to have the DFS root. To upgrade to the RC2, just install the CD2 of the distribution, install the new components. And if you want to update the domain to the version 2003 RC2, you have to execute the ADPREP that also comes in CD2 (adprep /forestprep). This document explains the DFS for the Windows version 2000 or 2003 – HERE.
This service is basically for when a company has more than one server and they are file servers. Let's say that a company works all the employees against a server and it goes down, Until the server is lifted, it is impossible for employees to continue working. With DFS it is possible that if the file server goes down they can continue to work against another server. And employees shouldn't be working against the server this way: SERVERFOLDERocumento.eso sino: DOMAINFOLDERAocumento.eso. What this does is it will be working against one server and it will replicate the data against the other server. In the event of a failure of one server, work can continue on the other.
If we want our network to have a domain, The steps to follow are explained in this document. To begin with, we need to be on an MS Windows 2000 or 2003 Server version, steps: