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

Difference Between Microsoft Exchange Server Unified Messaging (UM) role & Microsoft Office Communications Server 2007

Exchange 2007 consists of a number of roles, one of which is the UM role. UM requires separate Client Access Licenses and enables the following additional functionality over standard Exchange: Unified store for email, fax, and voice messaging. The Exchange UM role controls the receipt of voicemail, configuration of answer message, fax receipt, and other functions.

Access to a unified store from both a computer and from a phone using voice commands (voice user interface) or numeric key presses (telephone user interface) which collectively are known as Outlook Voice Access. Phone access also includes the ability to search Global Address List, check calendars, accept/reject meetings, and an Auto Attendant is provided to give guidance on feature access.

Essentially, the UM role does exactly what the name suggests. It provides the ability to access your voice messages, fax, and email from a single location via computer or phone. The UM can hook directly into many IP PBX telephone systems that serve a specific business or company. Companies using traditional non-IP PBX systems must install a gateway between the PBX and the UM servers to facilitate communication.

OCS 2007 is a separate product from Exchange, but can integrate heavily with Exchange to give a complete communication solution. OCS 2007 focuses on real-time communication while Exchange is primarily a message store. OCS 2007 provides the following features: Secure and archivable IM for an organizations users with connectivity to public IM services such as Yahoo and Windows Live Messenger through Public IM Connectivity (PIC), which is a separate license. OCS can also federate with other organizations' OCS implementations to allow communication via IM with partner companies without the need to use public IM services.

Presence information showing if a contact is currently online, busy, in a meeting, or so on. This information is visible in many mediums, including Outlook and SharePoint, and can be used to initiate communication through IM, voice, or a meeting scheduling.
File Transfer capabilities.
Peer-to-peer and multiparty conferencing services, including voice and video with web accessibility. Live Meeting client is used to access the services or the web-based interface.

When you combine Exchange 2007, Exchange 2007 UM, and OCS, you have a Unified Communications solution which gives single store access to all your e-mail, fax, and voice messages. You also have a rich interface for real-time communication, whether it be voice, text, video, or meeting-based, with presence information available to help choose the best way to contact people. The traditional divide between your phone system and your computer-based solutions is removed with UC.

For full info visit: http://windowsitpro.com/mobile/pda/Article.cfm?ArticleID=101637&FAQ=1

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

Gaps found in Microsoft Exchange API documentation

Zarafa Chief Executive Brian Joseph--having ported, as he put it, "all the Exchange features to the Linux platform with full MAPI, said there are significant gaps in the Microsoft documentation released to date. Zarafa makes an e-mail server that is compatible with Outlook

Speaking to ZDNet UK at the CeBIT conference, Joseph said Microsoft's start is not promising: "This could definitely make life easier for developers, but we have spotted over 200 undocumented exceptions, including one that allows you to create recurring calendar appointments in Exchange. It was in the documentation for Exchange 2000, but they forgot to document it for Exchange 2003 and Exchange 2007."

Zarafa produces the eponymous e-mail server that runs on Linux and is used by enterprises such as car-rental company Sixt, which recently migrated its entire e-mail server infrastructure to Zarafa. Zarafa uses the MAPI open standard to communicate to e-mail clients such as Outlook. While Microsoft Exchange uses MAPI too, it also uses a large number of proprietary APIs that let the Outlook client perform actions such as creating recurring calendar appointments on the Exchange server.

"I am very positive about unconditional publication of APIs," said Joseph, "but only time will tell if this is justified, given Microsoft's history. I think hundreds of thousands of developers around the world are very interested in full publication with regular updates, but the devil is in the detail; for policy makers, these gaps in the Exchange documentation should put another light on the value of Microsoft's announcement."

Zimbra Vice President John Robb agreed that Microsoft's announcement is a good move, but again expressed reservations. His company produces the Zimbra Collaboration Suite, which also runs on Linux platforms and servers. The Zimbra Collaboration suite runs 11 million mailboxes through the commercial version of its product and many more through the open-source version.

"The MAPI protocol is open anyway, so that doesn't affect us directly," Robb said, "but we are concerned that Microsoft has not announced which APIs have patent conditions, nor what those conditions are. We're anxiously awaiting details."

Source: http://news.cnet.com/Gaps-found-in-Microsoft-Exchange-API-documentation/2100-7344_3-6233802.html?tag=nw.3

How to Creating mail users in Exchange Server 2007

Mail users are actual accounts in your Active Directory, but their email does not reside within your Exchange environment; they use their own messaging system, Hotmail account, etc. This may sound a lot like a contact, but the difference is that a contact is an object that represents someone who neither has a mailbox in your Exchange environment nor an Active Directory account, whereas the mail user still has an Active Directory account.

To create a mail user in the Exchange Management Console, begin by navigating to the Mail User node under Recipient Configuration in the console tree. In the action pane, click the New Mail User link (Figure A) to start the New Mail User Wizard.



Navigate to the Mail User node:-



Beginning the New Mail User Wizard:-

Since you are creating a user within Active Directory, you first need to provide user account information on the User Information page of the wizard, as shown in Figure 3-35. Then, because the user will utilize an outside messaging system, you will need to provide his or her external email address, as shown in Figure 3-36.



Provide account information when creating a new mail user:-



Used For Referrence: http://searchexchange.techtarget.com/generic/0,295582,sid43_gci1333150,00.html

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

How To: Recreate OWA Virtual Directory - Exchange 2007

How To: Recreate OWA Virtual Directory - Exchange 2007. So many times I heard that OWA doesn’t work on Exchange 2007 server. There would be many reason behind it, like permission configuration, missing files, not able to load properly, .net errors etc…

There are different solutions base on various reasons but no one works then you may try by recreating OWA virtual directory which is giving problem.

Check and note the settings of directory in EMC before recreating it, like InternalURL, ExternalURL, Forms-Based Authentication settings ect..

Procedure:

• First step is to identify the directory which is giving the problem.

You can use Get-OwaVirtualDirectory to get the list of virtual directories.

• Now let’s say I have problem while accessing owa directory. Remove it with below command.

Remove-OwaVirtualDirectory “owa (Default Web Site)”

• Now create it again with below command.

New-OwaVirtualDirectory -OwaVersion “Exchange2007″ -Name “owa (Default Web Site)”

Note: if you are recreating other than owa directory which are legacy Exchange directories then you need to use “Exchange2003or2000″ in OWAVersion switch instead of “Exchange2007″

• Now configure the “owa” virtual directory settings like InternalURL, ExternalURL, Forms-Based Authentications etc… & check the OWA by logging with some test users.

Source: exchangeshare.wordpress.com/2008/07/16/how-to-recreate-owa-virtual-directory-exchange-2007