Exchange server
Many companies use Microsoft Exchange to give their employees messaging, calendaring, contact and task management, discussion and groups, document-centered workflow services. In a typical setting, each employee has an Exchange account, and access to this account requires a network connection to the Exchange server. If employees work at their desks or other workstations, they usually have this type of connectivity to the corporate intranet; but if they re traveling or at home, they might not.
The system proposed describe the global/universal database containing the information about the registered user's personal, financial, medical, family and almost every information about the user in multiple meta tag languages, duly verified by the users country authorities(citizen registration authorities)and protected by the users login name and password. In our proposed system this database will be used to register the user to other websites which need to register only the verified and genuine users i.e. no bots or fake users. This method will completely remove the fake ids, auto bots users, frauds and various other internet threats to the sites which are child sites.
Microsoft Exchange Server 2003 (v6.5, code name Titanium) debuted on September 28, 2003. Exchange Server 2003 can be run on Windows 2000 server. Like Windows Server 2003, Exchange Server 2003 has many compatibility modes to allow users to slowly migrate to the new system. This is useful in large companies with distributed Exchange Server environments who cannot afford the downtime and expense that comes with a complete migration.
The June 2, 2003, release of Exchange Server 2003 made the migration from pre-2000 versions of Exchange significantly easier, and many users of Exchange Server 5.5 waited for the release of Exchange Server 2003 to upgrade. The upgrade process also required upgrading a company's servers to Windows 2000. Some customers opted to stay on a combination of Exchange Server 5.5 and Windows NT 4.0 both of which are no longer supported by Microsoft.
One of the new features in Exchange Server 2003 is enhanced disaster recovery which allows administrators to bring the server online more quickly. This is done by allowing the server to send and receive mail while the message stores are being recovered from backup. Some features previously available in the Microsoft Mobile Information Server 2001/2002 products have been added to the core Exchange Server product, like Outlook Mobile Access and server-side Exchange ActiveSync, while the Mobile Information Server product itself has been dropped. Better anti-virus and anti-spam protection have also been added, both by providing built-in APIs that facilitate filtering software and built-in support for the basic methods of originating IP address, SPF ("Sender
ID"), and DNSBL filtering which were standard on other open source and *nix-based mail servers. Also new is the ability to drop inbound e-mail before being fully processed, thus preventing delays in the message routing system. There are also improved message and mailbox management tools, which allow administrators to execute common chores more quickly. Others, such as Instant Messaging and Exchange Conferencing Server have been extracted completely in order to form separate products. Microsoft now appears to be positioning a combination of Microsoft Office, Microsoft Office Live Communications Server, Live Meeting and Share point as its collaboration software of choice. Exchange Server is now to be simply e-mail and calendaring.
Exchange Server 2003 added several basic filtering methods to Exchange Server. They are not sophisticated enough to eliminate spam, but they can protect against DoS and mailbox flooding attacks. Exchange Server 2000 supported the ability to block a sender's address, or e-mail domain by adding '*@domain.com', which is still supported in Exchange Server 2003. Added filtering methods in Exchange Server 2003 are:
1.1 Connection filtering
Messages are blocked from DNS RBL lists or from manually specified IP addresses/ranges
1.2 Recipient filtering
Messages blocked when sent to manually specified recipients on the server (for intranet-only addresses) or to any recipients not on the server (stopping spammers from guessing addresses)
1.3 Sender ID filtering
Sender ID, a form of Sender Policy Framework (SPF)
1.5 Editions
Exchange Server 2003 is available in two versions, Standard Edition and Enterprise Edition. Standard Edition supports up to two storage groups (with one of the storage groups, called the recovery storage group, being reserved for database recovery operations) and a maximum of 2 databases per storage group. Each database is limited to a maximum size of 16GB. Beginning with the release of Service Pack 2, Standard Edition allows a maximum database size of 75 GB, but only supports 18 GB by default; larger sized databases have to be updated-in with a registry change. Enterprise Edition allows an 16 TB maximum database size, and supports up to 4 storage groups with 5 databases per storage group for a total of 20 databases per server.
Exchange Server 2003 is included with both Microsoft Small Business Server 2003 Standard and Premium editions and is 32-bit only, and will not install on the various 64-bit versions of Windows Server 2003.
Planning the migration from Microsoft's internal "legacy XENIX-based messaging system" to Exchange Server environment began in April 1993, and by January 1995 some 500 users were running on Exchange Server Beta 1. By April 1996 32,000 users were migrated to that environment.
2.5 Exchange Server 2003
Exchange Server 2003 (v6.5, code name Titanium) debuted on September 28, 2003.
Table 2.5:The Evolution of Exchange Server Deployment at Microsoft
Exchange 4.0 | Exchange 5.0 | Exchange 5.5 | Exchange 2000 | Exchange 2003 | |
Mailboxes per Server | 305 | 305 | 1,024 | 3,000 | 4,000 |
Mailbox Size/User | 50 MB | 50 MB | 50 MB | 100 MB | 200 MB |
Restore Time per Database | 12 hours | 12 Hours | 8 Hours | 1 Hour | 25 minutes |
Total number of Mailboxes | 32,000 | 40,000 | 50,000 | 71,000 | 85,000 |
Exchange Server 2003 (currently at Service Pack 2) can be run on Windows 2000 Server (only if Service Pack 4 is first installed) and 32-bit Windows Server 2003, although some new features only work with the latter. Like Windows Server 2003, Exchange Server 2003 has many compatibility modes to allow users to slowly migrate to the new system. This is useful in large companies with distributed Exchange Server environments.
2.7 Exchange Server 2007
Exchange Server 2007 was released on November 30, 2006, to business customers as part of Microsoft's roll-out wave of new products. It includes new clustering options, 64-bit support for greater scalability. The principal enhancements, as outlined by Microsoft, are
- Protection: anti-spam, antivirus, compliance, clustering with data replication, improved security and encryption
- Improved Information Worker Access: improved calendaring, unified messaging, improved mobility, improved web access
2.8 Exchange Server 2010
Microsoft Exchange 2010 | |
Server Client | |
Microsoft announced the Exchange 2010 to be available from the second period of 2009, and it was released to manufacturing (RTM'ed) on October 9, 2009. Exchange Server 2010 was officially launched on November 9, 2009;] a month after hitting RTM. A 120 day trial is also downloadable from Microsoft at Microsoft
Comments