In: Categories » Computers and technology » Servers » What`s Missing in Exchange Server 2007 That Was in Previous Versions
|
In Exchange 2007, the concept of the recovery storage group has been removed. Exchange 2003 introduced the recovery storage group as a way to restore an Exchange database to an Exchange server that wasn’t the original server that the database was created or was running on. With Exchange 2007, Microsoft has added a whole new series of technologies. The new technologies do a better job of replicating Exchange databases and making Exchange recoverable both from a local database crash and from a server or entire site failure. Also relative to Exchange databases, the STM database has been removed, so Exchange is now back to just the EDB database as it was in Exchange 2000 and prior versions. Rather than completely removing the STM database, Microsoft incorporated the streaming data technology into the new EDB database, so instead of having two databases for each mailbox and trying to reconcile the storage of information within those two databases, the combined mailbox database is now the standard. From an administration standpoint, the concept of administrative groups and routing groups has been completely removed. Administrative groups were introduced with Exchange 2000 as a method of grouping together users to identify who would manage and administer groups of mailboxes. Administrative groups were brought forward from Exchange 5.5 where administration was done based on sites connected by site connectors. In Exchange 2007, administration is now completely consolidated into an enterprise view of users and mailboxes. The administration of the users and mailboxes is handled as delegated rights of administrators, not by a group of users and servers. So, rather than grouping together servers and users into special containers, an administrator is merely assigned rights to manage specific users, mailboxes, servers, or preexisting containers. As noted in the preceding paragraph, routing groups have also been removed. Rather than having to group servers by routing groups, Exchange 2007 has done away with separate routing groups within Exchange. Instead, the Active Directory Sites and Services now uses its configuration to determine organizational sites and the routing of message communications to those sites. With the release of Exchange 2007, Microsoft has noted that public folders are being deemphasized, which basically means they are still there in Exchange 2007, but will be completely going away in a future version of Exchange. What you will find is when you install Exchange 2007 from scratch, public folders are not created at all. You need to manually add public folders to a Mailbox server and extend public folder access from the server system. During a migration, if the organization has public folders, they will continue to operate in Exchange 2007. Public folders, however, have not been improved in Exchange 2007. Their support is there, but no changes were made in the way public folders work or the features and functions of public folders. Microsoft has created excellent hooks between Exchange 2007 and SharePoint 2007 that allow a user to click on what used to be a folder for public folders, but instead a SharePoint share is rendered in the user’s Outlook or OWA screen. You can do pretty much everything you were able to do with public folders with SharePoint 2007—and then some. Several things have drastically changed in Exchange 2007, such as a completely new Exchange administration tool, a new Exchange server scripting language, and the removal of front-end and bridgehead servers with new server roles that will be covered in the next handful of sections.
|
legal disclaimer
1) Our website is not responsible for the information contained by this article as well for any and all copyright infringements by authors and writers. E-articles is a free information resource. If you suspect this article for any copyright infringements, please read the Terms of service and contact us to investigate the problem.
2) The E-articles directory team is not responsible for inaccuracies, falsehoods, or any other types of misinformation this tutorial may contain and will not be liable for any loss or damage suffered by a user through the user's reliance on the information gained here. Please read the Terms of service
Useful tools and features
If you like this article (tutorial), please link to it from your web page using the information above. Linking to this page, this is the only way to help us improve our service, the same time providing your visitors with a way to improve their online experience.
related articles
Previous versions of Exchange essentially forced many organizations into deploying servers in sites with greater than a dozen or so users. With the concept of site consolidation in Exchange Server 2007, however, smaller numbers of Exchange servers can service clients in multiple locations, even if they are separated by slow WAN links. For small and medium-sized organizations, this essentially means that one or two servers should suffice for the needs of the organization, with few exceptions. Larger organizations require a larger numbe...
2. Configuring Exchange Server 2007 for Maximum Performance and Reliability
After decisions have been made about AD design, Exchange server placement, and client access, optimization of the Exchange server itself helps ensure efficiency, reliability, and security for the messaging platform. Designing an Optimal Operating System Configuration for Exchange As previously mentioned, Exchange Server 2007 only operates on the Windows Server 2003 operating system, and is scheduled to be able to run on the next version of the Windows Server operating system, currently referred to as Windows L...
3. Managing Identity Information Between LDAP Directories and Exchange Server 2007
LDAP directories are commonplace today and can be found in many business environments. UNIX applications in particular make wide use of the LDAP standard for directories. Along with this proliferation of LDAP directory structures comes a need to synchronize the information contained within them to an Exchange 2007 environment. The Enterprise version of MIIS 2003 contains MAs that support synchronization to LDAP directories. Consequently, a good understanding of LDAP concepts is required before syncing between the environments. ...
4. Understanding DNS Requirements for Exchange Server 2007
In Active Directory, all client logons and lookups are directed to local domain controllers and GC servers through references to the SRV records in DNS. Each configuration has its DNS and resource requirements. Exchange relies on other servers for client authentication and uses DNS to find those servers. In an Active Directory domain controller configuration, on the other hand, the Exchange server also participates in the authentication process for Active Directory. Using DNS in Exchange Server 2007 As has bee...
One of the greatest advantages of Exchange Server 2007 is its emphasis on security. Along with Windows Server 2003, Exchange Server 2007 was developed during and after the Microsoft Trustworthy Computing initiative, which effectively put a greater emphasis on security over new features in the products. In Exchange Server 2007, this means that the OS and the application were designed with services “Secure by Default.” With Secure by Default, all nonessential functionality in Exchange must be turned on if needed. Thi...
6. Improvements in Exchange Server 2007 Relative to Security and Compliance
One of the improvement goals Microsoft has had with all of their products over the past few years has been to constantly improve the security in the products. More recently with all of the regulatory compliance laws and policies being implemented, Microsoft has focused a lot of security enhancements to address privacy, information archiving, and compliance support. The release of Exchange 2007 was no different—Microsoft added in several new enhancements in the areas of security and compliance support. One of the addition...
7. Designing Exchange Infrastructure
After Active Directory and the physical OS has been chosen and deployed, the Exchange infrastructure can be set up and optimized for the specific needs of the organization. With these needs in mind, you can do several things to optimize an Exchange 2007 setup, as detailed in the following sections. Determining the Exchange Version When installing Exchange, the choice of Exchange version needs to be made. As with Windows Server 2003, there are two versions of Exchange, Standard and Enterprise. The Standard Edit...
8. Synchronizing Exchange Server 2007 with Novell eDirectory
Novell eDirectory and Novell Directory Service (NDS) environments are relatively commonplace in business environments, and there is often a need to integrate them into deployed Exchange infrastructures. Several tools exist that can make this a reality, including the MIIS 2003 tools discussed. In addition, tools in the Microsoft-supplied Services for NetWare can be used to synchronize directory information between the two directory systems. NOTE Exchange 2000 Server and Exchange Server 2003 included a GroupWise ...
9. Integrating Client Access into Exchange Server 2007 Design
Although the Exchange server is a powerful systems component, it is only half the equation for an email platform. The client systems comprise the other half, and are a necessary ingredient that should be carefully determined in advance. Outlining Client Access Methods Great effort has been put into optimizing and streamlining the client access approaches available in Exchange 2007. Not only have traditional approaches such as the Outlook client been enhanced, but support for nontraditional access with POP3 and...
10. Domain Name System and Its Role in Exchange Server 2007
For computer systems to communicate with each other, whether you are talking about a local area network (LAN), a wide area network (WAN), or the Internet, they must have the ability to identify one another using some type of name resolution. Several strategies have been developed over the years, but the most reliable one to date (and the current industry standard) is the use of a DNS. Accurate name resolution is critical in a mail environment as well. For a message to reach its destination, it might pass through several syste...