RAID technology. The total cost of ownership is perfectly justified. Unfortunately, there is no standard method of undeniable measurements, which often causes controversy. A common IBM / Lotus claim is that the cost of the platform is prohibitively high compared to the Lotus platform. However, IBM / Lotus is usually based on a study by the Radicati Group, about which Microsoft made many comments later, and the most recent version yielded results in favor of Microsoft; This new study shows that Exchange 2003 offers a 41% TCO advantage over Lotus Notes / Domino 6 for a number of things, including downtime and training.

Lotus Development Corporation. As mentioned in the section, many customer reviews show the level of product maturity in terms of consistent architecture consolidation and direct consequence in terms of reliability and availability. From a technological point of view, projects of geographical and / or homogeneous consolidation are returned for customers to “put more eggs in fewer baskets”, which places a special emphasis on the concept of architecture “without a single point”. weaknesses (there is no single point of failure). In this regard, Exchange Server 2003 provides encouraging answers: Better cluster support: split failover time in two, switchover strategies for monitored nodes (thanks to the API).

Better SAN Support. In terms of service availability, the Exchange Server 2003 platform brings some very interesting innovations compared to previous versions. In practice, the achievement of a high level of availability of the Exchange Server 2003 solution is the result of achievements at several levels: 1. The effect of minimized downtime on client computers: some inaccessibility can be “absorbed” by the client post. For example, managing the local cache in Outlook allows users to hide most of their response time.

Network delays make failover clusters transparent or even smoothly switch to offline mode for a purely local mode of operation in the event of a complete disruption of the infrastructure infrastructure, which allows users to continue processing (locally) previously received messages. 2. Exchange Server 2003 supports the hardware and software architectures of the “single point of failure”: usually active / passive clusters, possibly a geocluster, SAN and redundancy of critical software and hardware components (for example, DNS, domain controllers, global directories).

In particular, Server 2003 provides encouraging answers: 

  • Better cluster support: Failover time divided by 2, tilt strategies for monitored nodes (thanks to an API called affinity). 
  • Better SAN support.Reducing server downtime by introducing new tools and procedures: quick recovery scenarios, possibly gradual ones — for example, a “tone” scenario — using advanced functions, significantly reduce backup / restore times. These features make it possible to recover messaging scripts in minutes (except in the event of a serious hardware failure requiring the restoration of a new physical server).
  • Provide working groups with appropriate procedures and oversight: Microsoft Operations Manager allows, for example: a. Configure proactive, consistent monitoring of Active Directory, DNS ,, Exchange, and SharePoint performance dynamics. b. Using management packs (there is one for Exchange), MOM allows you to apply control rules that combine the knowledge of Microsoft development teams on various components.

When discussing the security of messaging and collaboration, various areas / specific threats should be considered: – Combating spam. – The fight against viruses. – Confidentiality and data security: digital rights management, message signing and encryption. – Management of security breaches. Being a symbolic actor in the computer world, and especially with respect to hackers.

The fight against viruses. The problem of viruses affects the entire industry. Although Microsoft was especially targeted, especially because the offer is widespread, this problem also affects IBM.

The conclusion that everyone can make is, first of all, the publisher’s “loyalty” to his strategy regarding workstations. In particular, the company’s position on the client workstation is stable for a long period of time: 

– Office, when an advanced client is required, for example, in the context of enhanced performance, mobility, offline mode.

– Access to platform services through a web browser for a thin client approach.