Microsoft Outlook Voice Access for Exchange Server 2007 by Apptix

Apptix, provider of hosted Microsoft Exchange email, Microsoft SharePoint collaboration services, and hosted VoIP phone service for small and medium businesses (SMBs), has announced the launch of Voice Access for Microsoft Office Outlook 2007.

The new service enables Apptix hosted Exchange Server 2007 customers to remotely access and interact with their email, calendar, contacts, or voicemail using any phone -land line or mobile via touchtone or voice commands.

Also, Apptix customers can easily get access to their Outlook calendars via a mobile phone or landline with this latest announcement. They can use voice prompts to reschedule or alert other participants that a meeting is delayed or that its scheduled time has changed and can also reply to emails by attaching a voicemail message to a distribution list in their Outlook Contact list.

Officials at Apptix said the power of advanced text-to-speech technology together with a hands free device, make it possible to solve many safety and legal concerns while continuing to provide on-the-go business professional with a solution for their needs.

"From email and attached documents to calendar and contact information, Outlook has become a central repository for employees' critical information," said Rick Rumbarger, Vice President of Product for Apptix.

Source: hosted-voip.tmcnet.com

Exchange Server 2007 Service Pack 2 available in Q3 2009

Microsoft Exchange Server 2007 is the industry's leading server for e-mail, calendaring and unified messaging. Exchange Server 2007 is the foundation for a dynamic and holistic unified communications experience, and has been designed to meet the challenges and address the messaging needs of today's businesses. Exchange Server 2007 Service Pack 2 (SP2) enables customers to increase their operational efficiency and it sets the foundation for the transition to Exchange Server 2010, which is expected to be available in the second half of 2009. A public beta of Exchange Server 2010 is available for download at http://www.microsoft.com/exchange/2010.

Customer Benefits

Key new features of Exchange Server 2007 SP2 unveiled today include:

• Enhanced Auditing - New Exchange auditing events and audit log repository enable Exchange administrators to more easily audit the activities occurring on their Exchange servers. It allows the right balance of granularity, performance, and easy access to audited events via a dedicated audit log repository. This simplifies the auditing process and makes review of audited events easier by segregating audited events in a dedicated location.
• Exchange Volume Snapshot Backup Functionality - A new backup plug-in has been added to the product that will enable customers to create Exchange backups when a backup is invoked through the Windows Server 2008 Backup tool. Exchange Server 2007 didn't have this capability on Windows Server 2008 and additional solutions were required to perform this task.
• Dynamic Active Directory Schema Update and Validation - The dynamic AD schema update and validation feature allows for future schema updates to be dynamic deployed as well as proactively preventing conflicts whenever a new property is added to the AD schema. Once this capability is deployed it will enable easier management of future schema updates and will prevent support issues when adding properties that don't exist in the AD schema.
• Public Folder Quota Management - SP2 enables a consistent way to manage quotas by improving the current PowerShell cmdlets to perform quota management tasks.
• Centralized Organizational Settings - SP2 introduces new PowerShell option that enable centralized management of many of the Exchange organization settings.
• Named Properties cmdlets - SP2 enables Exchange administrators to monitor their named property usage per database.
• New User Interface for Managing Diagnostic Logging- SP2 enables Exchange administrators to easily configure and manage diagnostic logging from within the Exchange Management Console.

Source: http://bink.nu/news/exchange-server-2007-service-pack-2-available-in-q3-2009.aspx

Update Rollup 8 for Exchange Server 2007 Service Pack 1

We have released Update Rollup 8 for Exchange Server 2007 Service Pack 1 (KB 968012) to the download center. The release of the rollup via Microsoft Update will happen on May 26.

As in the previous rollups, we have done a mix of product improvements (aka Critical Design Change Requests) and bug fixes. A few key ones which I would like to call out are as follows:

1. KB 969690 - We have fixed the bug introduced in Update Rollup 7 which caused the sender of the Delivery Status Notification (DSN) to be unresolved.
2. Disable kernel mode authentication in Windows Server 2008 for CAS servers - As documented here, it was required to manually take the additional step to configure the CAS servers running Windows Server 2008 to disable kernel mode authentication. Starting this rollup, the installer will configure this for you.
3. X-Header promotion to named properties- Change to the way X-headers are promoted to named properties. More on this in Jason Nelson's blog post Named Properties, X-Headers, and You.
4. KB 961606 - We have fixed a bug where Outlook Web Access (OWA) users may find that the font size of plain text messages is extremely small on third-party Web browsers.

KB 968012 has more details about this release and a complete list of all fixes included in this rollup.

As a follow up to the Exchange Server 2007 Service Pack 2 (SP2) announcement, all fixes in this Update rollup and the previous ones we have released for Exchange Server 2007 will be included with Exchange Server 2007 SP2. We will have a blog post soon which covers:

* When update rollups can be expected for Exchange 2007 SP2.
* Support plans for Exchange 2007 SP1 which will be in support as per the timeline in Microsoft's Service Pack Support Policy.

Source: msexchangeteam.com

New Features in Exchange 2010

Here are the important changes you should know about:

* For starters, note the new orange color to the Exchange logo icon. It's not a technical facet of the new version but good to note, nonetheless.
* In Exchange 2007, clicking Microsoft Exchange at the top gave you Finalize Deployment and End-to-End Scenario tabs. In the Exchange 2010 beta, you get nothing when you click Microsoft Exchange; instead, you have to click Microsoft Exchange On-Premises to see the Finalize Deployment, Post-Installation Tasks, and Community and Feedback tabs. Also note a little option in the Actions pane called Gather Organizational Information; it kicks off a wizard that collects your organization's data for the number of servers, mailboxes, server roles, and licensing summary.
* Clicking the Organization Configuration top branch in Exchange 2007 shows you Exchange administrators and their roles. The Exchange 2010 beta displays three tabs: Federation Trusts, Sharing Relationships, and Sharing Policies. They may seem a bit cryptic if you don't understand the new concept of federation, which amounts to trust of other domains. Clicking the New Federation Trust wizard tells Echange 2010 to create a federation trust with Windows Live to prepare for secure sharing of information with external Exchange organizations. This requires a certificate for federation being deployed on all Exchange servers with client access and hub server role.
* Clicking Mailbox under Organization Configuration offers some new tabs in the Exchange 2010 beta, such as Database Management (which formerly resided under Server Configuration | Mailbox) and Database Availability Group. The Database Availability Group options are exciting to work with because they relate to your High Availability and Disaster Recovery options. Creating a New Database Availability Group launches a wizard that defines a set of servers that provide automatic database-level recovery from database failure. Note that Storage Groups are gone in favor of these new Database Availability Groups (DAGs). Also note some major changes to the High Availability options: specificall, LCR, and SCC are no longer available.
* Clicking Client Access under the Organization Configuration branch shows that ActiveSync policies are still around, and it offers a new set of policies called Outlook Live Mailbox Policies.
* For the most part, the Hub Transport settings look the same. But there are some new transport-policy settings worth looking into. One is If the Sender and Recipient's AD Attribute Are Evaluation. I had a hard time figuring that one out until I actually created the rule and discovered that it lets you change the AD Attribute and the Evaluation. Give it a try, and you will understand.
* The Unified Messaging tabs under Organization are the same. However, after creating a dial plan and going into the properties, I noticed some interesting changes: a check box on the General tab for Allow Voice Mail Preview and another one for Allow Users to Configure Personal Auto Attendants. One of the biggest interface changes I noticed when clicking through was in the UM policy settings on the General tab; new check boxes include Allow Message Waiting Indicator and Allow Play on Phone. There is also a Protected Voice Mail tab to help enforce options that may involve legal requirements for a company (for example, some companies are required to play a message on phone and not through a computer's speakers for confidentiality's sake).
* Moving on to Server Configuration. If you select this branch, you now see Exchange Certificates, which Exchange 2007 did not have. You can create a new certificate, assign services to certificates, or import/export certificates.
* Under Mailbox for Server Configuration, you see Database Copies.
* Client Access under Server Configuration holds the same four tabs as in Exchange 2007 for OWA, POP, and IMAP4, Exchange ActiveSync, and Offline Address Book Distribution.
* Under the Recipient Configuration branch is a new option called Mailbox Migration. In clicking through the properties of a mailbox user, I noticed a few interesting changes. There is a Calendar Settings tab where you can enable the Calendar Attendant and make some quick modificaitons such as Remove Meeting Forward Notifications to the Deleted Items Folder and Remove Old Meeting Requests and Responses without having to create entire policies for them. I didn't see too much else that was different other than a Federated Sharing option for a sharing policy on the Mailbox Settings tab.
* Last but not least, the Toolbox: On the surface, the two versions' interfaces match up perfectly. There are no new tools, it seems. No doubt the Exchange Best Practices Analyzer is newer. I couldn't find, however, some of my options for managing databases and working with Recovery Storage Groups.

Source: infoworld.com

Download Exchange Server 2007 Service Pack 1 Beta

Exchange Server 2007 Service Pack 1 Beta is available for download via TechNet and MSDN. Both the 32-bit and 64-bit versions of Exchange Server 2007 SP1 beta can be accessed through TechNet. At this point in time, MSDN users may be experiencing problems with the x86 version of Exchange Server 2007 SP1 beta.

Microsoft has made the Release Notes for Exchange Server 2007 SP1 since March. The notes will provide comprehensive guidance through the new features that SP1 will bring to the table but also on how to install the service pack, the issues that customers are most likely to face and the adjacent workarounds.

The release of the first beta for Exchange Server 2007 SP1 was announced since back in February by representatives of the Microsoft Exchange Team. It appears that the Redmond Company is right on track with the development of the first service pack. According to Microsoft, Exchange Server 2007 Service Pack 1 will be made available in the second half of 2007.

"As far as hardware requirements are concerned, SP1 will not change the existing Exchange 2007 RTM system requirements. Regarding the operating system, SP1 for Exchange 2007 will require Windows Server 2003 SP2. This will be a hard dependency for installation, so the operating system must be upgraded to Windows Server 2003 SP2 before you upgrade the Exchange 2007 RTM installation to Exchange 2007 SP1, or before installing a fresh build of Exchange 2007 SP1," Ed Banti, Technical Product Manager on the Exchange Server marketing team, revealed.

Source: http://news.softpedia.com/news/Exchange-Server-2007-Service-Pack-1-Beta-Available-for-Download-51698.shtml

Running Exchange Server 2007 in a virtual environment

With the release of Exchange Server 2007 SP1 and Windows Server 2008, Microsoft began supporting Exchange Server 2007 in virtual environments. However, not every scenario is supported, and Microsoft only recommends and supports a virtual environment if specific conditions are met.

First of all, as I implied, only Exchange 2007 SP1 can run virtually. SP1introduced further improvements to Exchange’s I/O footprint, which, I imagine, led to Microsoft’s easing of restrictions on the installation in virtual environments. Second, your Exchange servers must be running under Windows Server 2008; Windows Server 2003-based Exchange servers are out of the question.

Next, your virtual environment needs to be running on Hyper-V or a third-party virtualization provider validated by Microsoft. Validated third-party products include VMware (fortunately!) ESX 3.5 updates 2 and 3 and Citrix Xen Server, among others. Microsoft prefers that you use Hyper-V as your virtualization platform, but it’s nice to see that it isn’t excluding other major players.

One major item of note: If you intend to use unified messaging, that role is not supported in a virtual environment. In fact, it’s not recommended that you use virtualization for any services for which real-time communication is required. I have tested the unified messaging role in a virtual lab and can safely say that this role really needs to run on its own physical server.

There are a number of other items to take into consideration when it comes to running Exchange in a virtual environment. The list below is just a few of the major items. Microsoft provides a complete list of requirements and limitations on TechNet.

* Don’t forget to account for the processing and disk needs of the virtual host, particularly if you’re using Hyper-V. Under Hyper-V, the root machine needs processors assigned to it, and the root machine will consume processing resources and RAM. As you build your virtual hosts and add virtual machines, makes sure that the virtual processor-to-physical core ratio is no greater than 2:1. That is, if you have a four core machine, do not assign more than eight cores worth of processor to the running virtual machines.

* Understand that Exchange’s high-availability features, such as continuous cluster replication, don’t mix well with hypervisor-based clustering, such as Hyper-V’s quick migration or VMware’s VMotion. Microsoft doesn’t support combining these technologies. If you choose to forgo VMotion or quick migration on your root server or virtual host, then Exchange’s clustering capabilities are fully supported in a virtual environment, although you do lose a significant server availability feature. Of course, you can always run clustered mailbox servers on different virtual hosts as a way to mitigate some of this downside. This limitation would only affect the virtual machines hosting the mailbox server role. The servers housing the other roles should not be limited.

* Microsoft does not support making snapshots of full Exchange virtual servers at the virtual host level due to the fact that most hypervisor-based snapshot tools are not application aware. Snapshots could end up creating a mess if used improperly.

* Even when running in a virtual environment, you need to adhere to design recommendations when it comes to building your virtual servers. If, for example, a physical machine would require 16 GB of RAM for a particular Exchange installation, the virtual machine will too.

* Under Hyper-V, VHDs are limited to 2 TB in size. Size your mailbox stores accordingly.

Source: http://blogs.techrepublic.com.com/datacenter/?p=623

Running Exchange Server 2007 in a virtual environment

With the release of Exchange Server 2007 SP1 and Windows Server 2008, Microsoft began supporting Exchange Server 2007 in virtual environments. However, not every scenario is supported, and Microsoft only recommends and supports a virtual environment if specific conditions are met.

First of all, as I implied, only Exchange 2007 SP1 can run virtually. SP1 introduced further improvements to Exchange's I/O footprint, which, I imagine, led to Microsoft's easing of restrictions on the installation in virtual environments. Second, your Exchange servers must be running under Windows Server 2008; Windows Server 2003-based Exchange servers are out of the question.

Next, your virtual environment needs to be running on Hyper-V or a third-party virtualisation provider validated by Microsoft. Validated third-party products include VMware (fortunately!) ESX 3.5 updates 2 and 3, and Citrix Xen Server, among others. Microsoft prefers that you use Hyper-V as your virtualisation platform, but it's nice to see that it isn't excluding other major players.

One major item of note: if you intend to use unified messaging that role is not supported in a virtual environment. In fact, it's not recommended that you use virtualisation for any services for which real-time communication is required. I have tested the unified messaging role in a virtual lab and can safely say that this role really needs to run on its own physical server.

There are a number of other items to take into consideration when it comes to running Exchange in a virtual environment. The list below is just a few of the major items.

• Don't forget to account for the processing and disk needs of the virtual host, particularly if you're using Hyper-V. Under Hyper-V, the root machine needs processors assigned to it, and the root machine will consume processing resources and RAM. As you build your virtual hosts and add virtual machines, make sure that the virtual processor-to-physical core ratio is no greater than 2:1. That is, if you have a four-core machine, do not assign more than eight cores worth of processor to the running virtual machines.
• Understand that Exchange's high-availability features, such as continuous cluster replication, don't mix well with hypervisor-based clustering, such as Hyper-V's quick migration or VMware's VMotion. Microsoft doesn't support combining these technologies. If you choose to forgo VMotion or quick migration on your root server or virtual host, then Exchange's clustering capabilities are fully supported in a virtual environment, although you do lose a significant server availability feature. Of course, you can always run clustered mailbox servers on different virtual hosts as a way to mitigate some of this downside. This limitation would only affect the virtual machines hosting the mailbox server role. The servers housing the other roles should not be limited.
• Microsoft does not support making snapshots of full Exchange virtual servers at the virtual host level due to the fact that most hypervisor-based snapshot tools are not application aware. Snapshots could end up creating a mess if used improperly.
• Even when running in a virtual environment, you need to adhere to design recommendations when it comes to building your virtual servers. If, for example, a physical machine would require 16GB of RAM for a particular Exchange installation, the virtual machine will too.
• Under Hyper-V, VHDs are limited to 2TB in size. Size your mailbox stores accordingly.

These are just some of the most significant limitations and items of note with regard to running Exchange in a virtual environment.

Source: http://www.builderau.com.au/program/windows/soa/Running-Exchange-Server-2007-in-a-virtual-environment/0,339024644,339294994,00.htm

Five dos & Don't for Exchange Server 2007

5 must-dos:-

• Read, read, read. Everything... but especially what is found on the Microsoft Exchange Team blog.
• Look up various MVP sites for Exchange. These folks post information for free regarding their personal experiences. It's a key.
• Nothing beats experience. Work through the how-tos in my book to ensure you have more than head knowledge.
• Try and attend at least one Exchange oriented conference each year. Tech Ed is a good one, TechMentor, Windows Connections, TEC. I speak at most of these and I love attending sessions and learning from other Exchange gurus.
• Teach someone else. You never learn a subject so thoroughly as when you have to teach it to others.

5 don'ts:-

• Don't install the wrong version of Server when working with high availability options. If clustering services are involved, you need the enterprise version of the Server.
• Don't install just an Exchange server. You need to see how the client side will work. Install an OS with Outlook 2003 and 2007 to really make sure you know what is going on in the user world. Don't forget to play with Outlook Web Access too.
• Don't forget to learn how to set up your true incoming and outgoing SMTP connections. Typically in a learning environment you don't worry about that because you aren't working with a live server, but it is a must if you plan on putting a real server out on the Net. DNS records and so forth... it's all important.
• If you're working with Unified Messaging, don't forget to bring in a telephony expert. Most likely, you won't fully understand the configuration for the back end without help.
• Don't think you can rely completely on the GUI. Exchange has a few PowerShell-only configuration options. Get reacquainted with the command-line, my friend. It's not disappearing and any Exchange guru worth his title these days is a command-line lover.

Source: http://www.itworld.com/unified-communications/62208/five-must-dos-exchange-server-2007-and-5-donts?page=0%2C1

Microsoft plans critical patches for IE, Exchange

Microsoft Corp. today said it will deliver four security updates on Tuesday, two of them pegged "critical," and will finally issue a patch for SQL Server that it's been working on since last April.

The four updates detailed in the advance notice published today will quash bugs in Internet Explorer 7 (IE7); its Exchange mail server software; the Visio application that's part of the Office lineup; and SQL Server. The IE and Exchange vulnerabilities will be labeled critical, the company's highest threat ranking, while the SQL Server and Visio bugs will be marked as "important," one step lower.

That bug is notable for several reasons. When Micosoft confirmed the vulnerability in a Dec. 22 advisory, it noted that exploit code had been published. Several days later, the company admitted that it first received a report on the bug from Bernhard Mueller of SEC Consult Security, a Vienna-based security consulting company, in April 2008.

"Three of these are all equally important, at least with the information we have today," Storms said about the IE, Exchange and SQL Server patches. "It all depends on an enterprise's infrastructure."

Companies are always sensitive to Exchange fixes, Storms continued, so the critical fix set for Exchange Server 2007, 2003 and 2000 will be parsed carefully. "Messaging is so important to the enterprise," Storms said, "that they'll want to spend a little extra time making sure the patch works." One plus, he said, is a "Does not require restart" note by Microsoft in today's bulletin.

"That could mean it's not necessarily a giant hole, or that we're just going to get lucky," said Storms. Because they won't have to restart their Exchange servers, IT administrators should be able to deploy the patch more quickly, he said.

"The IE vulnerability has to be something unique to IE7," wagered Storms. According to Microsoft, the critical vulnerability affects only that version of the browser, not IE6 or IE5.01, the latter edition specific to Windows 2000, and the oldest browser that the company still supports with security updates. Storms hesitated to guess what IE7-only issue might be patched. "It could be any number of things," he said. "Could be scripting or the antiphishing filter."

Microsoft's advance notice reported that the IE7 bug will be rated critical for both Windows XP and Windows Vista, but only "moderate" on Server 2003 and Server 2008.

Microsoft will release February's four updates at approximately 1 p.m. EST Tuesday.

Source: http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9127438

Microsoft Exchange Server and PowerShell: Debate Continues

When Microsoft Exchange Server 2007 was released a little over two years ago, one of the biggest drawbacks in the minds of many admins was its reliance on Windows PowerShell. In fact, some of our readers were quite vocal and angry over this situation. The release of Exchange 2007 SP1 added more functionality to the GUI, Exchange Management Console (EMC), but certain tasks can still only be performed through Exchange Management Shell (EMS).

Last week, KC Lemson posted the first public information about Exchange 14 on the Microsoft Exchange Team Blog and invited people to reply with what features they're most interested in hearing about in the new version. I suppose it should be no surprise that at least part of the reader dialog that followed centered on this issue of PowerShell.

A commenter named Thomas wrote:

"I applaud the efforts to make more management tasks doable via the GUI instead of just in powershell. Exchange 2007 RTM was severely lacking in that respect with even common tasks like Send On Behalf permissions requiring long power shell commands. In small/medium organization's IT depts. we need to be Jack of All Trades (and masters of none) since 2 or 3 man IT depts. don't have the manpower to specialize in Exchange Management and memorize the long powershell commands."

Taking up the other side of the argument, Hal Rottenberg said:

"If you value your time, then you should be learning PowerShell, regardless of whether you work with Exchange or not. As they say, if you repeat it, script it."

I for one am a big fan of automation. I use Word 2007 just about constantly, and while I like the Ribbon interface, I still use macros with keyboard shortcuts for any functions I use frequently. Yes, it takes a few extra minutes to set those things up, but the benefits in the long run are worth it. Likewise, it seems like scripting common Exchange tasks with PowerShell would be well worth the time investment.

With the release of Exchange 14 looming, and its expected continued use of PowerShell through EMS, I'm wondering how Exchange Server admins are feeling about their management options now. I'd love to hear your stories: If you prefer to work through the GUI, what ways have you discovered to work around limitations in Exchange 2007? Or maybe you were resistant at first but have come to embrace the control EMS gives you. If you're using Exchange Server 2007, you can't avoid PowerShell

Source: http://windowsitpro.com/article/articleid/101326/microsoft-exchange-server-and-powershell-the-debate-continues.html

Entourage to Exchange Web Services (EWS) Open to Public

Microsoft Tuesday launched a public beta for software that ties Mac users more closely to Exchange mail servers, making good on a promise the company announced earlier this month.

A beta of the Entourage to Exchange Web Services (EWS) client software is now open to the public, said Mike Tedesco, a senior product manager for the company's Mac development group. Previously, the beta had been tested by a handful of corporations running Exchange server and Office 2008 for Mac.

EWS allows the Exchange server itself do most of the heavy lifting, as opposed to WebDAV, which left the bulk of the work up to the client. This results in as much as a 2x speed increase. Also, the improved compatibility means that tasks, notes, and categories are now synced with the server, names can be resolved from the Global Address List over standard HTTP connections (no more VPN!), and improved Autodiscover keeps account settings synced with your Exchange server.

With the beta, Microsoft is moving away from the WebDAV protocol it's used for the last five years to connect Entourage, the e-mail client included in the Mac version of Office, to Exchange, the popular enterprise mail server software. Rather than rely on Web DAV, the beta supports Exchange's native connectivity protocol through an API, putting Entourage on a more equal footing with Microsoft's Windows-based Outlook e-mailer when it comes to synchronizing with Exchange.

Apple licensed Microsoft's ActiveSync technology last March to give iPhone users a way to grab business e-mail from Exchange servers.

The beta also adds some new functionality to Entourage, said Tedesco, including synchronizing tasks, notes and categories in the e-mail program with Exchange.

Users interested in trying the beta of Entourage to Exchange Web Services can apply on the Microsoft Connect site, said Tedesco, but must be running Office 2008 for Mac as well as Exchange Server 2007 with Service Pack 1 with Update Rollup 4, or later.

Source: http://www.techworld.com.au/article/273747/microsoft_unveils_mac--exchange_sync_beta

Virtualization of Microsoft Exchange Server

Microsoft Exchange Server is a product which is used for making the purpose of emailing faster. This software is designed to make the work more efficient. Since nowadays the e-mail pays a vital role in the business dealings, so many companies are going for the Microsoft Exchange Server which has made their work much easier and faster. Microsoft Exchange Server not only has increased the reliability but also provides the feature if adding servers for other applications and hence its utilization makes the workload much easier.

The main advantage of the Microsoft Exchange Server is that it is used for providing security enhancement to many software packages.

Harmful threats like viruses spam and hackers can be neutralized by the use of this server.

Hence it is much more reliable and provides the confidence to the customers and employees that their email system is well protected and full potential utilization of their system can be done with the help of this server.

• Going for the virtualization of Microsoft Exchange Server: -

i. This server provides a cost effective technique and hence providing a simpler business environment. The use and costs of e-mails can be managed and hence the complexities which are increasing day by day can be controlled by the use of M.E. server.

ii. Besides the helpful features like flexibility, increase availability, reduction in cost, disaster recovery simplifications, your hardware products can be tested and provided with a valid virtual solution. This is the technique used in the virtualization of this server.

iii. These services are provided by the two leading software companies - Microsoft Exchange Server 2007 and VMware (leading data storage enterprise).

• Advantages of virtualization of Microsoft Exchange Server: -

It helps in increasing the reliability of the email system and also improves the disaster tolerant system by providing efficient infrastructure.

i. By encapsulating the Exchange Servers into virtual machines, it helps in simplifying the recovery of data for the improvement in the Exchange infrastructure.

ii. The VMware Infrastructure plays an important role in protecting the servers. So it is even more powerful technique with virtual machine.

It helps in improving the performance by the information exchange.

i. With the introduction of 'New 64-bit architecture' in Microsoft Exchange Server 2007, the performance of the system has improved as much more RAM usage can be done with the better coordination with VMware virtual machine.

ii. Hence better access to the disk can be done and more memory can be used.

Source: http://ezinearticles.com/?Virtualizing-of-Microsoft-Exchange-Server&id=1156138

Protect Data with Exchange Server 2007

Lucid8 delivers next-generation automated disaster prevention, optimization, protection, and recovery solutions for Microsoft® Exchange. Today, Lucid8 has over six-thousand product implementations to customers worldwide ranging from SMEs to Fortune 100 companies worldwide whose businesses depend on Microsoft Exchange 5.5, 2000, 2003, and 2007.

Fear of loss compels us to protect ourselves, our cars, our homes, our families and our friends. Our concerns for potential loss encourage us to take precautions to help mitigate risks. This is why most of us exercise, take our cars into the shop when they make unexplained noises or motions, and buy insurance policies in case of other catastrophic losses. I seriously hope that no one’s life is in danger from his or her messaging system, but I am fairly certain that most companies would be wounded should a catastrophic problem occur within the Exchange environment.

Exchange Server 2007 is as self-healing as Exchange has ever been, but without a healthy hardware platform, drivers, Active Directory, DNS, network, and regular policy management, it can go belly-up faster than you can say cardiac arrest. To make matters even worse, many Exchange administrators are not current with the latest CPR techniques nor have they been practicing preventive maintenance on their Exchange databases in order to minimize unplanned downtime. In this white paper, you will learn the bare and necessary facts you should know to proactively maintain your Exchange Server 2007 environment.

In order to download the Protecting Your Data with Exchange Server 2007 whitepaper, please fill out the form below: You will find form here:

http://windowsitpro.com/Whitepapers/Index.cfm?fuseaction=ShowWP&WPID=393a7bec-e173-483c-b887-95b1cf858e28&code=winflink

Microsoft Exchange Server 2007 Service Pack 1 Security features

Microsoft announced Exchange Server 2007 Service Pack 1 and opened a technology preview for the software. Exchange Server 2007 SP1 features enhancements such as support for Windows Server 2008, enhanced integration with Microsoft Office Communications Server 2007, and improved mobile device management and advanced security technology.

Among other new features of Exchange Server 2007 SP1, these are security related ones:



Additional Exchange ActiveSync policies

New Exchange ActiveSync policies in SP1 build on Exchange Server 2007's robust security and management features with new policies for synchronization, authentication and encryption. For businesses with more advanced data protection needs, Exchange Server 2007 SP1 offers device, network and application controls. These new features allow network administrators to help manage and secure Exchange ActiveSync-enabled mobile devices.

Enhanced security

Microsoft also unveiled Forefront Security for Exchange Server SP1, which integrates with Exchange Server 2007 SP1 to provide an extra layer of security for even greater protection and control. Forefront Security for Exchange Server includes multiple scan engines from industry-leading security firms integrated in a single solution to help protect against viruses, worms and spam. The new service pack for Forefront Security for Exchange Server features improvements in content filtering and manageability as well as support for Windows Server 2008.

Source: net-security.org/secworld.php?id=5423

Rollup 5 for Exchange Server 2007 SP1

This is a heads up that Rollup 5 for Exchange Server 2007 SP1 is in the final stages of getting released and should be out in a couple of days. The next step for the Exchange team will be to release the Update Rollup onto the Download Center and then publish it to Microsoft Update. Microsoft Update publishing will happen 2-3 weeks after the Download Center publishing, due to internal policies and processes. We will let you know when this happens.

Regarding the overall patching experience, we have addressed the issue of Exchange 2007 managed services might time out during certificate revocation checks. While we will have a full list of issues fixed when the Rollup releases, some of major issues are:

• CDCR: Need an option to apply ELC policy to only the root instead of applying it recursively to root and all subfolders
• CDCR: Add generatePublisherEvidence enabled="false" to Exchange Services Config Files
• SCR does not copy logs in a disjoint namespace scenario
• SCR cannot be enabled when DNS suffixes differ on source/target in disjoint namespace scenarios
• Exchange 2007 CAS cannot copy the OAB from the OAB share on Windows Server 2008-based Exchange 2007 CCR clusters
• Messages get stuck in outbox on Windows Mobile 6.1 devices When using CAS proxy
• CDCR: MSI patching doesn't update logon.aspx if the file is modified by customer

Source:bink.nu/news/update-rollup-5-for-exchange-server-2007-sp1-is-almost-out-the-door.aspx

Why does the user name get rejected when some users log in to Exchange Server 2007 via POP3?

Question:- Why does the user name get rejected when some users log in to Exchange Server 2007 via POP3?

Answer:- We're all familiar with the user principal name (UPN); it includes a user's log-on name, the @ symbol, followed by the domain name. Errors can occur when users have a UPN that exceeds 40 characters, which is the default limit for POP3 set by the MaxCommandSize setting. You can resolve this issue in one of two ways. The first method just increases the value of MaxCommandSize, this way:

• Start the Exchange Management Shell.
• Type Get-POPSettings to view current settings. You'll notice the default value is 40.
• To increase the value to 50 (the upper limit is 1,024 bytes), type Set-POPSettings -MaxCommandSize 50
• Restart POP3 for the changes to take effect.

2. The second method increases the value of MSExchPopImapCommandSize via the Adsiedit.msc snap-in. It's a bit more complicated...

Via:mcpmag.com

Difference between MS Exchange Server 2003 and MS Exchange Server 2007

Exchange Server 2003(v6.5)(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 who cannot afford the downtime and expense that comes with a complete migration.One of the new features in Exchange Server 2003 is enhanced disaster recovery which allows administrators to bring the server online quicker. This is done by allowing the server to send and receive mail while the message stores are being recovered from backup.

Exchange Server 2007 was released in late 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, voice mail integration, better search and support for Web services, better filtering options, and a new Outlook Web Access interface. Exchange 2007 also dropped support for Exchange 5.50 migrations, routing groups, admin groups, Outlook Mobile Access, X.400, and some API interfaces, amongst other features.

Key improvements of MCSE 2003. 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
• Improved IT Experience: 64-bit performance & scalability, command-line shell & simplified GUI, improved deployment, role separation, simplified routing
• Exchange Management Shell: a new command-line shell and scripting language for system administration (based on Windows PowerShell). Shell users can perform every task that can be performed in the Exchange Server graphical user interface plus additional tasks, and can program often-used or complex tasks into scripts that can be saved, shared, and re-used. The Exchange Management Shell has over 375 unique commands to manage features of Microsoft Exchange Server 2007.
• Unified Messaging” that lets users receive voice mail, e-mail, and faxes in their mailboxes, and lets them access their mailboxes from cell phones and other wireless devices. Voice commands can be given to control and listen to e-mail over the phone (and also send some basic messages, like “I’ll be late”)
• Removed the database maximum size limit. Database size is now limited by hardware capability and the window for backups and maintenance.
• Increased the maximum number of storage groups and mail databases per server, to 5 each for Standard Edition (from 1 each in Exchange Server 2003 Standard), and to 50 each for Enterprise

Source:/blog.test4actual.com/?p=407

Exchange Server 2007 SP1 review

When it released Exchange Server 2007 at the beginning of last year, Microsoft admitted to dropping a number of the expected features in order to meet its deadline. Some of these were new to the 2007 product, but others were already available in Exchange Server 2003, causing more than a little concern among customers looking to upgrade. It comes as no surprise, therefore, to find many of these features reinstated in Service Pack 1 (SP1) in a clear attempt to finally deliver the product that Microsoft originally promised.

Along with the usual performance enhancements and bug fixes, one of the new features is, naturally, support for Windows Server 2008, with SP1 required if you want to host Exchange Server 2007 on that platform. Otherwise you’ll need Windows Server 2003 with the SP2 update applied to run Exchange Server 2007 SP1. As before, the latest implementation is designed for 64-environments, although it can be deployed on 32-bit servers for unsupported testing and evaluation purposes.



Exchange Server 2007 SP1 fills in a lot of those gaps. For example, POP3/IMAP4 server settings can now be configured from the Exchange Management Console (EMC) just as before. Public folders can, similarly, be managed from the EMC again, along with user Send As permissions. With the original release, these options all had to be configured via the Exchange Management Shell (EMS), requiring programming skills that are not normally available in smaller companies. The Move Mailbox tool has also been enhanced in this release to allow import and export to personal folders.

The Outlook Web Access (OWA) Premium client in Exchange Server 2007 SP1 is yet another component to benefit from the return of lost functionality. This includes the ability to manage personal distribution lists from a browser, create and maintain custom rules, recover deleted items and select a monthly calendar view — all of which were dropped when Exchange 2007 was first launched. Support for S/MIME is similarly reinstated, but only when using IE 7.0; the list of attachments that can be converted to HTML in a message (WebReady Document Viewing) is also extended to include more of the Office 2007 formats. However, there are still document components that can’t be viewed this way.



Conclusion

The Exchange Server 2007 SP1 update can be downloaded free of charge. At 840MB it’s not small, but it can be used to install a fresh copy of Exchange as well as upgrade existing code. We found it straightforward to apply and would recommend anyone already on the new platform or installing Exchange for the first time to get hold of it. Upgrading from an earlier version of Exchange, however, can be problematic, and the support forums are full of customers who have experienced problems.

Careful planning and testing is, therefore, advisable even with this new and improved implementation. It's also still very much an enterprise solution, and there's no news yet about a small-business version of Exchange Server 2007.

Source:zdnet.co.uk/