Alteration in Terminal Server's listening port

It is a well-known fact that TCP port 3389 is used by Terminal Server and Windows 2000 Terminal Services for client connections. Alteration in this port is not recommended by Microsoft. But you can change this port. You have to perform this task carefully, otherwise you will face serious problems.

You have to give more concentration while modifying the registry. If you want to change the default port, then you have to follow these steps:

You start with the task of running Regedt32 and go to this key, HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp. Then you have to find the port number subkey and notice the value of 00000D3D, hex is for 3389. After this, you have to change the port number in Hex and save the new value.

If you want to change the port for a particular connection on the Terminal Server, then follow these steps:

You have to run Regedt32 and go to this key, HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\connection. After this, you have to find the port number subkey and notice the value of 00000D3D, here hex is for 3389. Then you have to change the port number in Hex and save this new value.

After performing this, you have to make alteration in the Port on the Client Side. Follow these steps to perform this:

You have to open Client Connection Manager. Then on the File menu, click on New Connection and then create the new connection. After executing the wizard, you will view a new connection listed there. Then you have to ensure that new connection is highlighted. After this, on the File menu, click Export. Then you have to edit the .cns file using Notepad. You have to make modifications in the server port, Server Port=3389 to Server Port= new port number, that you had specified on Terminal Server. Now import the file back into Client Connection Manager. Then you will be demanded to overwrite the current one. If it has the same name, then overwrite it. In this way, you will receive a client that has the correct port settings to match your Terminal Server settings.

Microsoft SQL Backup

You are aware of the problems like disk failure, system crashes and many more. Due to these problems your important data will get lost. In this situation, you will be the loser. So, to avoid these problems you have to take a backup of your data. Microsoft has developed the Microsoft SQL Server, a widely used database management system. Handy Backup gives a fast and efficient way to backup Microsoft SQL Server database. Nowadays, many businesses whether small or large are using the databases stored on SQL servers. So, it is important to backup the SQL database.

Accuracy and reliability of Microsoft SQL (MSSQL) backup - Handy Backup uses Microsoft API but other backup tools use the ODBC protocol to backup MSSQL database. Handy Backup permits you to backup MSSQL database with all views, indexes, stored procedures and other data. You do not have to interrupt your SQL server services while performing MSSQL backup with Handy Backup. You can take backup of MS SQL Server 2005, MS SQL Server 2000, MS SQL Server 2008 with Handy Backup. Handy Backup can automatically recognize all SQL server databases available on your computer and also display them. It has many options which facilitate you in compressing your MSSQL backup with an integrated ZIP-compressor with 10 levels. You can also schedule the backup for a time period that you desire. You can save MS SQL backup on any storage media. These storage devices can be DVD, external drives and many more. So, it can be deducted that Handy Backup is a perfect tool for MSSQL backup because it allows you to always feel safe about your data.

Windows Server Security 2008 Support Services

This post provides Windows Server 2008 Security Guide. This guide provides instructions and recommendations to help strengthen the security of computers running Windows Server® 2008 that are members of an Active Directory® domain.

In addition to the guidance that the Windows Server 2008 Security Guide prescribes, this Solution Accelerator provides tools, step-by-step procedures, recommendations, and processes that significantly streamline the deployment process. This guide not only provides you with effective security setting guidance. It also provides you with a reproducible method that you can use to apply the guidance to both test and production environments.

The key tool that this Solution Accelerator provides for you is the GPOAccelerator. The tool enables you to run a script that automatically creates all the Group Policy objects (GPOs) you need to apply this security guidance. The Windows Server 2008 Security Guide Settings workbook that accompanies this guide provides another resource that you can use to compare and evaluate the Group Policy settings.

Microsoft engineering teams, consultants, support engineers, partners, and customers have reviewed and approved this prescriptive guidance to make it:
• Proven. Based on field experience.
• Authoritative. Offers the best advice available.
• Accurate. Technically validated and tested.
• Actionable. Provides the steps to success.
• Relevant. Addresses real-world security concerns.

Microsoft has published security guides for Windows Server 2003 and Windows 2000 Server. This guide references significant security enhancements in Windows Server 2008. The guide was developed and tested with computers running Windows Server 2008 joined to a domain that uses Active Directory® Domain Services (AD°DS).

Exchange Server Support for Backups and Single Item Recovery

Naturally after understanding the features included in Exchange 2010, a logical follow up question is "Do I still need backups for single item recovery?" The answer depends on your backup requirements and your capacity planning.

Today many customers minimize the deleted item retention window, yet they maintain long backup retention time periods (from 14 days to several months to years).

Let's consider a customer that currently maintains backups for 90 days and only retains deleted items within Exchange for 5 days. This customer is performing backup restores on a weekly basis to recover deleted items for end users. If the customer moved to Exchange 2010 they could move that process into Exchange by simply increasing their mailboxes capacity for dumpster: This post Contain the exchange server support tips to make backups and single Item Recovery.

• Users send/receive 100 messages per work day and have an average message size of 50KB
• Single Item Recovery is enabled and the deleted retention window is configured to be 90 days
• 10% of items are edited
• Mailbox capacity calculations

o 5 work days * 100 emails = 500 emails / week
o For Purges:
+ 500 emails / week * 13 weeks = 6500 emails / retention period
+ 6500 emails * 50KB ? 318MB
o For Versions:
+ 500 emails / week * 13 weeks = 6500 emails / retention period
+ 6500 emails * .1 = 650 emails
+ 650 emails * 50KB ? 32MB
o Total Space Required per mailbox: 350MB

By increasing each mailbox's capacity by a minimum of 350MB, backups are no longer needed for single item recovery. Single item recovery can be maintained and performed within Exchange.

But let's not stop there. What if the requirement is that items must be recoverable for 1 year? Assuming the same assumptions used in the previous example with the exception that deleted item retention is now configured for 365 days, each mailbox needs an additional minimum 1.4GB of space.

Ultimately, if the storage subsystem is planned and designed appropriately and mailbox resiliency features are leveraged, traditional point-in-time backups can be relegated to a disaster recovery mechanism, if they are even needed at all.

How Managed Exchange Can Increase Your Business?

Managed Exchange can help your business by converting Microsoft Outlook from an email communication device into a critical work tool. Get Better access to critical and frequently used information, Book or reserve popular shared company resources and Coordinate your daily schedules through personal calendar tools by Managed Exchange.

Staff can access their email and Outlook work tools (mentioned above) through a number of web-enabled devices such as: Desktop PCs, laptops, PDAs with GPRS, WAP mobile phones with GPRS, Blackberry mobile devices with GPRS. Data is constantly synchronized and updated, so no matter how staffs access their work tools, they always have the most up-to-date information when online. It helps staff be more organized and get more out of their day.

Managed Exchange is ideal for any business whose staffs need to work together using frequently shared information and need to have flexible access to critical work tools such as email, contacts and calendar when they cannot make it into the office.

Service providers Managed Exchange Solution allows smaller businesses to leverage all of the functionality of Microsoft Exchange, without having to cover the associated capital and operating costs associated with running an Exchange Server in-house. Managed Exchange is also suitable for small businesses with limited IT resources because all service providers are able to manage the back-end for you.

Your Managed Exchange service can generally be activated within one business day. For larger, customized configurations, service provider will arrange with you a suitable timeframe for activation of your service. You can get protection from spam, viruses and malware before they reach your network. No software, hardware or user training required.

How To Resolve OST Synchronization Error

In Microsoft Outlook, an offline folder (.ost file) is a locally stored file that is synchronized with your mailbox contents stored on Microsoft Exchange Server. The folders empower you to access them even when the mail delivery or network service is not available. The file converts into a usable .pst file as the synchronization process succeeds. But there can be several synchronization errors, due to which your .ost file might become unusable. In such cases, you might need to restore its contents from a backup stored as a .pst file. If it is not feasible, you should use a third-party tool to Convert OST to PST.

For an instance, you use Microsoft Outlook 2002 or 2003 with an offline folder. You press F9 to synchronize your .ost file with your Exchange Server mailbox, but fail to do so and come across the below error message:

"The file .ost cannot be accessed because it has been configured for use with a different mailbox."

If you close the application and try to perform synchronization again, you receive the same error message.

The Reason:
As the error message suggests, this error is encountered if you are attempting to synchronize the mailbox with an .ost file that is configured to use a different server or e-mail account. This usually occurs if you perform these steps in order:

You synchronize your .ost file with the mailbox 2-You perform some changes in name of either e-mail server or mailbox in your email account profile.

Doing so makes the current .ost file unusable.

Best Possible Solution
Create a new email profile with the desired account settings and restore data using any of the below solution:

1. You can then include the .pst files maintained as a backup of previous .ost file.


2. You can also copy this information to a .pst file from your mailbox after changing the changed email settings back to the original state.


3. If applying the above solutions are not possible, Convert OST to a usable .pst file.

Convert OST to PST are powerful applications that are competent to convert an usable .ost file into a usable .pst file after any type of crash.

Stellar Phoenix Mailbox Exchange Desktop is an effective utility that converts an .ost file into a .pst file. It can Convert OST by maintaining data integrity. Designed to perform safe file conversion, this utility can restore all file objects including emails, notes, journals, tasks and more. It is compatible with Outlook 2003, 2002, 2000, 98 and 97.

Benefits of Small Business Server Exchange 2003

Microsoft small business server 2003 is designed for organizations with up to 50 computers who need high-level reliability and functionality but don't have the economy of scale that allows big corporations to sop up the cost and complexity of licensing best-of-breed enterprise software. SBS 2003 is a cost effective and simple way to form a solid foundation for an information network with enterprise-level security, connectivity, performance, and reliability.

Windows SBS 2003 will be available in standard and premium editions. The standard edition includes Microsoft SBS 2003 and window server 2003. Small business server 2000 included earlier versions of these products. The premium edition adds Microsoft SQL Server 2000 and Microsoft Internet Security and Accelerations Server.

Advantages of Microsoft Small Business Server 2003 include:

• Windows 2003 server management and security tools deduct the cost and enhance the dependability of desktop computers by using centralized user policies, rights and configurations.


• SBS exchange 2003 enhances remote and mobile access by supporting a web client that offers a nearly full implementation of the familiar outlook interface, including calendaring and tools. It means that mobile workers can have complete, secure access to email from any internet-connected computer with a standard web browser.


• Windows SBS server 2003 maximizes server uptime and user availability by incorporating powerful fault tolerance aspects, including disk mirroring, cluster configurations, and distributed file system.


• SBS exchange 2003 uses active directory, providing a greatly simplified administration and security model. It makes exchange server monitoring very easy and also offers complete security. Security enhancements include improved safe and block lists and junk email filtering, public folder permission enhancements and attachment in MOOWA (Microsoft Office Outlook Web Access).


• ISA server features ideal support for protecting IIS servers behind the firewall, which have been the largest areas of hacker exploits for windows 2000 environments.

Microsoft Exchange Server Troubleshooting

The Windows Exchange Server software suite is developed and supported by Microsoft. Microsoft Exchange is used to download, manage and organize email, contact data and calendars on a server network. The Windows-based Exchange server is also often used for mobile data, such as email on a smartphone. Occasionally, errors may be encountered when working within the Exchange framework. Learn how to troubleshoot the Windows Exchange Server network to identify problems and restore your Exchange server's functionality.

You can troubleshoot the exchange server very easily and efficiently with the following given steps;

1. Restart the computer or mobile device with which you are trying to access the Microsoft Exchange server. Occasionally, the issue may be due to software or hardware problems that interrupt the data transfer between the device and the server. These issues can often be easily solved by shutting down the hardware and rebooting the operating system. On a computer, click the "Start" menu and select "Shutdown" or "Restart." On a mobile device, press and hold down the power button or consult the manufacturer's manual.


2. Launch Internet Explorer. Visit the Microsoft Exchange support website. See the Resources section below for a link. Read the list of "Top Issues" published on the top of the web page. This list catalogs all current issues and problems that may be experienced by Exchange users, as well as solutions to the errors. Also, check that all Exchange patches and upgrades have been installed on the server. If you are a businessperson trying to access your company's Exchange server, you typically would not have permission to install upgrades. Contact your company's IT department for assistance in keeping your Exchange products synced with the latest Microsoft Exchange upgrades.


3. Download the official "Microsoft Exchange Troubleshooting Assistant." This program is developed and hosted by Microsoft specifically to pinpoint critical problems on an Exchange server and guide you through fixing the problem. Visit the Microsoft Exchange Troubleshooting Assistant website and click the "Download" button. See the Resources section for a link.


4. Click "Save" in the dialog box that pops up in the Internet Explorer browser. Wait for the download to finish before closing the browser. Depending on the speed of your Internet connection, this may take several minutes.


5. Double-click the "Microsoft Exchange Troubleshooting Assistant" icon on your computer desktop to begin the automated installation process. An installation wizard will appear to guide you through the process. Follow the on-screen prompts to complete the installation.


6. Open the "Microsoft Exchange Troubleshooting Assistant" by clicking the "Start" menu and selecting the program from the pop-up menu. Run the Troubleshooting Assistant and wait for it to generate a report on the status of your Exchange server. The Assistant will scan both the local machine and the server to determine where any potential problems may exist. If it identifies a problem, the assistant will give you a report on how to successfully solve the problem and fix the issue.

If you still unable to resolve the issue, please login at http://www.iyogibusiness.com

Ports used by Exchange Server

For purposes of configuring firewalls or for troubleshooting communications issues, it may be useful to know what TCP/UDP ports Exchange 2000 Server and Exchange 2000 Conferencing Server are using. This article is also true for Exchange Server 2003 installations.

Protocol: LDAP

* Port (TCP/UDP): 389 (TCP)

Description: Lightweight Directory Access Protocol (LDAP), used by Active Directory, Active Directory Connector, and the Microsoft Exchange Server 5.5 directory.

Protocol: LDAP/SSL

* Port (TCP/UDP): 636 (TCP)
* Description: LDAP over Secure Sockets Layer (SSL). When SSL is enabled, LDAP data that is transmitted and received is encrypted.
* To enable SSL, you must install a Computer certificate on the domain controller or Exchange Server 5.5 computer.

Protocol: LDAP

* Port (TCP/UDP): 379 (TCP)
* Description: The Site Replication Service (SRS) uses TCP port 379.

Protocol: LDAP

* Port (TCP/UDP): 390 (TCP)
* Description: While not a standard LDAP port, TCP port 390 is the recommended alternate port to configure the Exchange Server 5.5 LDAP protocol when Exchange Server 5.5 is running on a Microsoft Windows 2000 Active Directory domain controller.

Protocol: LDAP

*Port (TCP/UDP): 3268 (TCP)
* Description: Global catalog. The Windows 2000 Active Directory global catalog (which is really a domain controller "role") listens on TCP port 3268. When you are troubleshooting issues that may be related to a global catalog, connect to port 3268 in LDP.

Protocol: LDAP/SSL

*Port (TCP/UDP): 3269 (TCP)
*Description: Global catalog over SSL. Applications that connect to TCP port 3269 of a global catalog server can transmit and receive SSL encrypted data. To configure a global catalog to support SSL, you must install a Computer certificate on the global catalog.

Protocol: IMAP4

*Port (TCP/UDP): 143 (TCP)
*Description: Internet Message Access Protocol version 4, may be used by "standards-based" clients such as Microsoft Outlook Express or Netscape Communicator to access the e-mail server. IMAP4 runs on top of the Microsoft Internet Information Service (IIS) Admin Service (Inetinfo.exe), and enables client access to the Exchange 2000 information store.

Protocol: IMAP4/SSL

*Port (TCP/UDP): 993 (TCP)
*Description: IMAP4 over SSL uses TCP port 993. Before an Exchange 2000 server supports IMAP4 (or any other protocol) over SSL, you must install a Computer certificate on the Exchange 2000 server.

Protocol: POP3

*Port (TCP/UDP): 110 (TCP)
*Description: Post Office Protocol version 3, enables "standards-based" clients such as Outlook Express or Netscape Communicator to access the e-mail server. As with IMAP4, POP3 runs on top of the IIS Admin Service, and enables client access to the Exchange 2000 information store.

Protocol: POP3/SSL

*Port (TCP/UDP): 995 (TCP)
*Description: POP3 over SSL. To enable POP3 over SSL, you must install a Computer certificate on the Exchange 2000 server.

Protocol: NNTP

*Port (TCP/UDP): 119 (TCP)
*Description: Network News Transport Protocol, sometimes called Usenet protocol, enables "standards-based" client access to public folders in the information store. As with IMAP4 and POP3, NNTP is dependent on the IIS Admin Service.

Protocol: NNTP/SSL

Port (TCP/UDP): 563 (TCP)

Description: NNTP over SSL. To enable NNTP over SSL, you must install a Computer certificate on the Exchange 2000 Server.

Protocol: HTTP

*Port (TCP/UDP): 80 (TCP)
*Description: Hyper-Text Transfer Protocol is the protocol used primarily by Microsoft Outlook Web Access (OWA), but also enables some administrative actions in Exchange System Manager. HTTP is implemented through the World Wide Web Publishing Service (W3Svc), and runs on top of the IIS Admin Service.

Protocol: HTTP/SSL

*Port (TCP/UDP): 443 (TCP)
*Description: HTTP over SSL. To enable HTTP over SSL, you must install a Computer certificate on the Exchange 2000 server.

Protocol: SMTP

*Port (TCP/UDP): 25 (TCP)
*Description: Simple Mail Transfer Protocol, is the foundation for all e-mail transport in Exchange 2000. The SMTP Service (SMTPSvc) runs on top of the IIS Admin Service. Unlike IMAP4, POP3, NNTP, and HTTP, SMTP in Exchange 2000 does not use a separate port for secure communication (SSL), but rather, employs an "in-band security sub-system" called Transport Layer Security (TLS).

Protocol: SMTP/SSL

*Port (TCP/UDP): 465 (TCP)
*Description: SMTP over SSL. TCP port 465 is reserved by common industry practice for secure SMTP communication using the SSL protocol. However, unlike IMAP4, POP3, NNTP, and HTTP, SMTP in Exchange 2000 does not use a separate port for secure communication (SSL), but rather, employs an "in-band security sub-system" called Transport Layer Security (TLS). To enable TLS to work on Exchange 2000, you must install a Computer certificate on the Exchange 2000 server.

Protocol: SMTP/LSA

*Port (TCP/UDP): 691 (TCP)
*Description: The Microsoft Exchange Routing Engine (also known as RESvc) listens for routing link state information on TCP port 691. Exchange 2000 uses routing link state information to route messages and the routing table is constantly updated. The Link State Algorithm (LSA) propagates outing status information between Exchange 2000 servers. This algorithm is based on the Open Shortest Path First (OSPF) protocol from networking technology, and transfers link state information between routing groups by using the X-LSA-2 command verb over SMTP and by using a Transmission Control Protocol (TCP) connection to port 691 in a routing group.

Protocol: RVP

*Port (TCP/UDP): 80 (TCP)
*Description: RVP is the foundation for Instant Messaging in Exchange 2000. While RVP communication begins with TCP port 80, the server quickly sets up a new connection to the client on an ephemeral TCP port above 1024. Because this port is not known in advance, issues exist when you enable Instant Messaging through a firewall.

Protocol: IRC/IRCX

*Port (TCP/UDP): 6667 (TCP)
*Description: Internet Relay Chat (IRC) is the chat protocol. IRCX is the extended version offered by Microsoft. While TCP port 6667 is the most common port for IRC, TCP port 7000 is also very frequently used.

Protocol: IRC/SSL

*Port (TCP/UDP): 994 (TCP)
*Description: IRC (or Chat) over SSL. IRC or IRCX over SSL is not supported in Exchange 2000.

Full info here

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 2010 Adds New Features to Outlook Mobile

Source: pocketnow.com

Here's a run down of the features: Exchange Server 2010 ActiveSync features

Block/Allow/Quarantine list: You can setup a single list to block/allow mobile devices as needed. You can also quarantine devices such as new untested devices, etc.

Over the Air Update Mode: You can now push new Outlook Mobile updates/new versions to Windows Mobile 6.1 and above. This is really nice since you no longer have to wait for a new Windows Mobile OS version to obtain a new version of Outlook Mobile.

SMS Sync: The ability to send SMS text messages through Exchange and EAS is used to sync SMS message with user’s mobile device.

Benefits of SMS sync:

•User can use OWA, Outlook, and Outlook Mobile to respond
•SMS messages are backed up on the server
•Recipients can respond to messages
•User can switch “screens” while still seeing all their messages

IMAP/POP3 service discovery: You can now autodiscover/autoconfigure the IMAP/POP3 settings from your mobile device by just specifying your email address.

Outlook Mobile features

Conversation View

Reply state: You can now see which emails you have replied to or forwarded.

Conversation actions: You can now ignore threads, move always threads to folders, etc from your mobile device. Ignore thread may become quite a popular feature.

Nickname cache: Very nice that your nicknames follow you now. Especially useful for external recipients you email often.

Voice Card: You no longer have to download the voicemail attached like before (right). You just hit play and hear the VM. The other feature that I really like is the ability to see a transcription of the voice mail in the body of the message. Very useful for meetings, noisy airports, where you can’t play the VM.

Get Free/Busy: It is awesome since you can now at a quick glance from your phone see the Free/busy info vs. breaking out the laptop, etc.

Meeting Workspaces in Microsoft Office SharePoint Server 2007

When planning meetings, Microsoft Exchange Server and Outlook allow organizers to compare attendees' calendars and send out meeting invitations. Exchange 2007 also allows users to reserve conference rooms when sending out meeting invitations. Microsoft Office SharePoint Server 2007 lets you go one step further. MOSS 2007 can augment Outlook's meeting planning capabilities by creating meeting workspaces.

What is a Meeting Workspace?

A Meeting Workspace serves as a way to prepare for a meeting and a way to report the meeting's outcome once it's done. For example, suppose that you wanted to hold a meeting to discuss your organization's latest press release. You would probably want to make sure that everyone attending the meeting had a copy of the press release. Instead of manually distributing hard copies of the release in the meeting, you could include it in the Meeting Workspace. This way, all meeting attendees have access to the press release ahead of time.

Note: A Meeting Workspace isn't a forum for holding a meeting. The actual meeting will take place in person, over the phone or through an online collaboration forum such as Microsoft LiveMeeting. The Meeting Workspace does not take the place of the meeting's venue.

The anatomy of a Meeting Workspace

What a Meeting Workspace looks like varies, depending on which template is used to create it. Figure 1 shows a basic Meeting Workspace that is made of four elements: Objectives, Agenda, Attendees and a Document library.

Source: searchexchange.techtarget.com

How to setup Exchange on iPhone 2.0 Beta 3

Apple made a couple of changes to the Exchange configuration interface on iPhone 2.0 Beta 3. You can no longer enter a host name. When you begin configuring your Exchange account, you're asked to type in your Email, Username, Password and Description. It looks easy enough right? Wrong. If you're like me, you'll enter your email address, your user name, password and an account description. For example, my email address is vincent@iphonebuzz.com, username is vincent_iphonebuzz.com, and vincent exch for description and changeme for the password. If that's all you did, then you're in for a long wait. Make sure you have the server information handy because you'll need it. For the sake of this example, my email server info is webmail.iphonebuzz.com and DOMAIN is IPHONEBUZZ.



The system is trying to work up some magic to set up your account but based on the information provided, it just doesn't know what to do. You're going to end up one unhappy customer unless you know exactly how to enter the info correctly. Using my previous account information, here's the correct way to enter the information so that your iPhone can understand.



* Email: vincent@iphonebuzz.com should be entered as vincent.webmail.iphonebuzz.com
* Username: DOMAIN\username = IPHONEBUZZ\vincent_iphonebuzz.com
* Password: changeme
* Description: Vincent Exch
As soon as you click NEXT, a second field called Server miraculously appears (see image above). You will NEVER see this field if you INCORRECTLY enter info in the initial four fields. Instead, you will get "Verifying Exchange account information" message with the spinning progress icon and it never connects. Next, enter your Server info. In my case, my server is webmail.iphonebuzz.com. Click SAVE to continue. You should then see the same info in the screenshot below. Click Sync and you're good to go. Make sure to take NOTE that all data in your Contacts and Calendars will be erased when you first synchronize Exchange.

Source: http://www.iphonebuzz.com/how-to-setup-exchange-on-iphone-2-beta-3-152196.php

Google targets Microsoft Exchange Server

Search giant Google has kept its enterprise productivity offering - Google Apps - relatively low key until now. But a new plug-in designed to seduce businesses away from Microsoft Exchange Server as their communications back-end.

The clever bit is Google's acknowledgement that many people are just too used to the Outlook user interface to shift wholesale onto Gmail and its future derivatives. So it has created a plug-in called Google Apps Sync for Microsoft Outlook that lets you use Outlook to connect to Google Apps instead of Exchange Server.

This is an intriguing new twist to the Google, Microsoft battle. Just as Microsoft makes its move on Google's home turf with a new search engine, Google ripostes with an attack at the productivity market currently dominated by Microsoft Office. Fun!

Here's a video clip from Google explaining how it all works:

Full view here: http://channel.hexus.net/content/item.php?item=18815

Is SAN storage supported in Microsoft Exchange Server 2010?

In every Exchange 2010 document, you see direct attached storage (DAS) as the storage medium for Exchange 2010. This is for a number of reasons: The I/O requirements of Exchange 2010 are 10 percent of what they were for Exchange 2003, 30 percent of what they were for Exchange 2007. This means the I/O benefits of a SAN are typically no longer required. The single copy cluster model in Exchange 2007, which required the database to be on shared storage, is no longer supported in Exchange 2010. The only high availability configuration requires every node to have its own copy of the database. DAS is typically much less expensive to purchase than SAN storage.

That's not to say you can't use a SAN for the storage of mailbox data. SANs still have advantages over DAS in terms of Higher disk utilization (when you have dedicated storage on each box a higher percentage is left empty). Central point for backup and generally faster backup/restore technologies. Single point of management.

If you already have a SAN or want to consolidate storage, then you can certainly use a SAN for the storage of Exchange 2010 databases. However, the key item is to make sure you'd don't have any single point of failure. You shouldn't have each Exchange server in a Database Availability Group (DAG) storing its replica of the database on the same SAN, as this makes the SAN a single point of failure.

Look at the messaging for Exchange 2010. Ideally, you should use DAGs with at least three copies of every database. That is a lot more storage and a lot more mail servers, and these servers will all be running enterprise editions of Windows and Exchange, which isn't cheap. The use of DAS over SAN helps offset the cost of additional hardware and licenses.

Many organizations may use the SAN for storage of one copy of the data and then DAS or another SAN for other copies. You can mix DAS and SAN.

Source

Exchange Server 2010 - New Features to Outlook Mobile

If you're tied to a corporate Exchange account, you may want to push for Exchange 2010 when it gets released into the wild by Microsoft. The new features adds some notable enhancements, including threaded email messages, which offers conversation view grouping by sender, similar to GMail and threaded SMS currently available on Windows Mobile 6.1. There is also voicemail transcription if your voicemail is connected to Exchange, which will transcribe your voicemail into true "visual voicemail."

Here's a run down of the features:

Exchange Server 2010 ActiveSync features

Block/Allow/Quarantine list: You can setup a single list to block/allow mobile devices as needed. You can also quarantine devices such as new untested devices, etc.

Over the Air Update Mode: You can now push new Outlook Mobile updates/new versions to Windows Mobile 6.1 and above. This is really nice since you no longer have to wait for a new Windows Mobile OS version to obtain a new version of Outlook Mobile.

SMS Sync: The ability to send SMS text messages through Exchange and EAS is used to sync SMS message with user’s mobile device.

Benefits of SMS sync:

•User can use OWA, Outlook, and Outlook Mobile to respond
•SMS messages are backed up on the server
•Recipients can respond to messages
•User can switch “screens” while still seeing all their messages

IMAP/POP3 service discovery: You can now autodiscover/autoconfigure the IMAP/POP3 settings from your mobile device by just specifying your email address.

Outlook Mobile features

Conversation View

Reply state: You can now see which emails you have replied to or forwarded.

Conversation actions: You can now ignore threads, move always threads to folders, etc from your mobile device. Ignore thread may become quite a popular feature.

Nickname cache: Very nice that your nicknames follow you now. Especially useful for external recipients you email often.

Voice Card: You no longer have to download the voicemail attached like before (right). You just hit play and hear the VM. The other feature that I really like is the ability to see a transcription of the voice mail in the body of the message. Very useful for meetings, noisy airports, where you can’t play the VM.

Get Free/Busy: It is awesome since you can now at a quick glance from your phone see the Free/busy info vs. breaking out the laptop, etc.

Source: http://pocketnow.com/index.php?a=portal_detail&t=news&id=7500

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

MailTips in Outlook 2010 and Exchange 2010

The next iteration of Microsoft's email client and messaging and collaboration server under the Office 2010 brand umbrella will bring to the table a new feature dubbed MailTips. Designed to deliver information to end users about the recipients of their messages even before they start writing the emails, MailTips is set up to increase workflow, and avoid common faux pas scenarios. According to Microsoft, MailTips will be available to users of Office 2010, Outlook Web Access and Exchange 2010. The Redmond company underlined that the feature would not be tweaked to offer backward compatibility, and as such legacy Outlook/OWA releases would not be supported.

“Have you ever sent a really well thought out, important email, only to find out (through an automatic response) that the recipient is on vacation for two weeks? For most of us, this means either waiting two weeks for a response or emailing an alternate contact. For the recipient, it means dealing with tons of messages when returning from vacation,” revealed E.J. Dyksen, from the Exchange Transport team. “This scenario is one of the many reasons we developed MailTips in Exchange Server 2010. MailTips are there to give you information about your message and its recipients before you hit the send button.”

MailTip is of course capable of displaying automatic replies for recipients to emails, but the feature delivers additional functionality. In this regard, Dyksen informed that MailTips would alert the users if a message was about to be sent to a large audience, or of situations in which the Reply All options would confirm to other users that certain messages were indeed received. At the same time, MailTips is designed to alert the user on emails that are going to people outside a particular organization, if the recipient's inbox is full, if the message itself is oversized, but also on invalid or restricted email addresses.

Source:news.softpedia.com/news/MailTips-in-Outlook-2010-and-Exchange-2010-110554.shtml

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

Exchange Server 2010 Beta Tips

On April 15, Microsoft released a public beta of Exchange Server 2010, formerly code-named Exchange 14. I've had the opportunity to spend a lot of time working with the new version of Exchange since before the public beta, and I thought I'd share a few tips and tricks that might be useful to you.

First of all, don't even think of installing the beta in production. It's not supported or licensed for production use, and there's no guarantee that you'll be able to upgrade from this beta to later betas (if any) or to the release version. Nino Bilic on the Exchange team blog also has something to say about this point.

Second, keep in mind the prerequisites you'll need to download and install before you install the Exchange 2010 beta. I had hoped that Exchange 2010 would automate installation (or at least downloading) of the prerequisite updates it requires, but it doesn't. Microsoft's Scott Schnoll posted a step-by-step installation guide on his blog that you can use as a guide. There are two sets of prerequisites: Windows features that you must have installed, such as the Windows RPC over HTTP proxy server for the Client Access server role; and patches or updates to existing features, including Microsoft .NET Framework 3.5 and the latest version of the Windows Remote Management (WinRM) management service.

Third: Exchange 2010 requires PowerShell 2.0, which supports remote management. When you use the Exchange Management Shell link on the Windows Start menu, you're actually getting a remote PowerShell session on the same machine. In some cases, remote PowerShell sessions don't start properly. If that happens, look in the Start menu again and you'll see an Exchange Management Shell (Local PowerShell) link. Use it instead, and you'll be in good shape.

Exchange Server 2010 beta by Microsoft

Source: windowsitpro

Kaspersky Security for MS Exchange Server 2003 5.5

Kaspersky Security for Microsoft Exchange Server 2003 protects users of corporate mail systems against viruses, spyware and spam, and can be centrally administered. Kaspersky Security for Microsoft Exchange Server 2003 provides anti virus scanning of incoming and outgoing messages and mail stored on the server, as well as messages in shared folders.

It also helps mail system users to block unwanted mail using intelligent spam recognition technologies in addition to technologies provided by Microsoft. Advanced technologies for protection against viruses and spam. In addition to its proven anti virus technologies that ensure traditionally high detection rates of malicious programs, the product makes use of the Spam Test technology to detect unwanted mail.

Two-tier spam filtering. The product filters unsolicited mail in conjunction with Microsoft Exchange 2003 / Outlook 2003, guaranteeing high recognition of spam.

Source: zdnet.de

Save With an Online Exchange Server

Get through lean times by watching your business expenses like a dieter tracking calories. Is the cost of your ISP bandwidth and IT support worth hosting your own Exchange Server? Many businesses can save money with an offsite, hosted Exchange Server.

Self-hosting, up-front fees sting the hardest. Let's first figure you'd buy Small Business Server Standard for about $1,000 and a middle-weight server for about $1,500. That'd get you support for five users at an initial cost of about $2,500. Additional user licenses run $77 each. So for a business of about 20, you'd pay more than $3,500 to get started, and you'd likely pay more for help from an IT consultant.

A hosted Exchange Server eliminates these initial costs and ongoing IT maintenance fees. In this situation, hardware, software, and user licenses are billed monthly. Depending on the host and service, expect to pay about $10 a month per user.

Based on this rough 20-person business example, you'd be even with the up-front, $3,500 cost of self-hosting after about 18 months. But that still doesn't factor in your specific, ongoing ISP and IT bills, which could double this figure. And you'll eventually have to pay for hardware and software upgrades, too.

A hosted Exchange Server makes even more sense when you further scrutinize employee needs. Does everyone need the full features of an Exchange account, or can some employees get by with a simpler POP setup?

Source: pcworld.com

Exchange Server 2010 beta by Microsoft

Microsoft has unveiled the public beta of Exchange Server 2010, with the final release slated for year's end.

Among the new features, Exchange Server 2010 will allow users to opt-out of group email threads they're not interested in, and offer a voice-to-text transcription feature allowing voice messages to be stored in the inbox.

Elsewhere, Microsoft's making a big noise over privacy and Exchange Server 2010 will now offer MailTips - a series of configurable warnings that will alert users before they send out mail to large groups, people with their out-of-office switched on and those not on "trusted" organisation lists.

It will also feature to three Gmail innovations: Mail Googles which requires the user to complete a difficult sum before sending an email; Undo Send, which holds the email for ten seconds in case the user immediately regrets pressing the send button and wants to stop it going out. Outlook will also now present mail in threads, a feature pioneered by Gmail.

From: pcpro

How to install the Microsoft Exchange Server Clustered Mailbox Role during Microsoft IIS error? How can I install it??

Answer:

First, make sure you've installed the required prerequisites: ISAPI Extensions Basic Authentication Windows Authentication IIS 6 Management Compatibility

The common cause for this error if you meet the prerequisites is that your .NET installation is incomplete or corrupt. When you attempt to install the Clustered Mailbox Role, you'll get the following error. An error occurred while creating the IIS virtual directory 'IIS://savdalex01.savilltech.net/W3SVC/1/ROOT/Exchange' on 'savdalex01'. Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

The solution is to reinstall .NET 3.0, even though it may show as installed.

Source: Windowsitpro

Exchange Tool Tests Remote Connections

Microsoft announced an online service for IT pros that enables them to test incoming e-mail traffic to Microsoft Exchange Server.

The tool, called Exchange Server Remote Connectivity Analyzer, was announced last week as a beta version. However, it's apparently been available as a test version since late last year.

The Microsoft Exchange team on Wednesday pointed to the availability of the beta version. The team's blog includes a video that demonstrates how the tool works, which can be accessed here.

The remote analyzer tool helps IT administrators assess server setup problems, particularly when e-mail clients located outside an organization's firewall are having problems trying to connect. While Exchange Server comes with its own test tools, those tools can only test traffic within an organization's firewall.

The Exchange Server Remote Connectivity Analyzer will test incoming e-mail traffic by simulating three client types, including Windows Mobile clients using Exchange ActiveSync, Outlook clients using Outlook Anywhere and clients that use SMTP.

You can run the tests for Windows Mobile and Outlook with autodiscovery turned either on or off.

The beta still has some usability limitations, and it requires certificates for some tests to work, according to the Exchange team blog. The team plans make those improvements in a future version, along with adding new tests for Exchange Web Services, IMAP, Outlook Web Access and POP.

The Exchange Server Remote Connectivity Analyzer tool, nicknamed "ExRCA," can be accessed for free online here.

Source: http://entmag.com/news/article.aspx?editorialsid=10734

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

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

Microsoft Exchange 14: Will it be a jackpot, Some Rumors?

First of all, it appears that Microsoft is making a sincere effort to make Exchange 14 more accessible to a wider user audience. Microsoft has indicated that Outlook Web Access (OWA), arguably the best Web mail product on the planet, will fully support Firefox and Safari. Until now, Microsoft has made the premium OWA experience available only to users running Internet Explorer, while users of other browsers faced limitations in the OWA Light experience.

Microsoft will also introduce Gmail-like conversation threads into OWA, helping users tame their inboxes. Finally, the new OWA will sport instant messaging capabilities with users able to see presence information for and send instant messages to other users in the organization — all from within the new Web client.

A user on the Microsoft Exchange Team Blog has also repeated a rumor that Exchange 14’s high-availability features will remove the need to use Microsoft Clustering Services. If this is true and is implemented correctly, a great level of complexity could potentially be removed from highly available configurations.

Here are some other items I’ve run across that are rumored to be included in Exchange 14:-

• User-created distribution lists.
• Users can manage some of their own information that is presented in the Global Address List.
• Public folders. I list that here because there were questions as to whether Microsoft would jettison this legacy from the product. From most indications, public folders will remain fully supported in Exchange 14. However, an astute reader on the Exchange Team Blog did notice in the new OWA some reference to SharePoint where the Public Folder link belongs, so we’ll have to wait and see what happens.
• The next version will be named Microsoft Exchange Server 2010.

I have only listed what seems reasonably true given the information that is out there. Some people are expecting that Exchange Server 14 will move away from the Jet database to a SQL backend. Personally, I doubt this will happen, but it is another rumor out there.

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

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

Next version of Outlook Web Access to actually support popular browsers

Microsoft announced on Thursday that the next version of the Exchange server, Exchange 14, will have a few useful new features including, finally, full support for browsers other than Internet Explorer.

A Microsoft demo video shows full Web access to the Exchange e-mail server from Firefox running on Vista, and Safari on OS X. The Web access product is now called Outlook Live. University users of Microsoft's free hosted e-mail service (Exchange Labs) will get the beta of the service shortly. It appears that corporate users, who know of Web access to Exchange servers as Outlook Web Access, will get it when their companies upgrade to the Exchange 14 platform. Exchange 14 is expected either late in 2009 or in 2010.

Outlook Live will also give users a threaded conversation view, useful for tracking e-mails that get more than a few replies. And the online app will integrate IM (as Gmail does), although it will likely only connect to users of Microsoft instant messaging servers.

Since corporations are generally very conservative in their upgrade plans for electronic mail platforms, business users (like my CNET co-workers) should not expect access to Exchange 14 until, at the earliest, several months after the release of the product. Until then, users who want full-featured access from a Web browser to their Exchange e-mail servers are advised to keep a copy of Internet Explorer handy on their desktop.

Source:http://news.cnet.com/8301-17939_109-10163423-2.html

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

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

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

Implementing and Configuring Blacklist Support in Exchange Server 2003

Spam filtering software based on keywords, etc. is only one brick in the wall guarding against Spam; another one is to implement black- or block-list support within your messaging and collaboration environment. With the new release of Exchange, Microsoft implemented the functionality to filter every incoming email whether the sender is on a blacklist or not. Within this article you will learn how blacklists work and how you can configure support with Exchange Server 2003.

But Spam filtering software based on keywords, etc. is only one brick in the wall guarding against Spam; another one is to implement black- or block-list support within your messaging and collaboration environment. With the new release of Exchange, Microsoft implemented the functionality to filter every incoming email whether the sender is on a blacklist or not.

Learn how blacklists work and how you can configure Exchange Server 2003.

What are blacklists and how do they work?

f you perform a search with an internet search engine you will find lots of blacklist providers throughout the world. This means, the first thing you have to do is consider what blacklist provider you want to use. Nobody can say this or that blacklist provider is the best, you should make your own experiences but if you have a look at the recommendations of the IT press and testing results published in these magazines one of the following blacklist providers may be a good choice.

* relays.ordb.org
* relays.visi.com
* bl.spamcop.net
* blackholes.wirehub.net
* list.dsbl.org

If you have a look at one of these blacklist provider’s websites you will find an explanation on how blacklists work.

Each blacklist server is a special kind of service that can be compared with DNS services. If the SMTP-domain is on the blacklist it reports return status codes back to the checking messaging system providing special IP addresses.

Here is a list of the codes and what they mean:

127.0.0.2 è Open relay

127.0.0.3 è Dialup spam source

127.0.0.4 è Confirmed spam source

127.0.0.5 è Smarthosts

127.0.0.6 è Spamware software developer or spamvertized site (spamsites.org)

127.0.0.7 è Listserver that automates opts users in without confirmation

127.0.0.8 è Insecure formail.cgi script

127.0.0.9 è Open proxy server

By default, Exchange Server 2003 blocks all mails with one of these codes, but you can also configure the behavior as you want.

Configuring blacklist support with Exchange 2003

In Exchange Server 2003 you can find the feature for blacklist support within the global settings of your organization.



As seen above, you can implement multi-blacklist provider rules and put them in your own sequence. Exchange Server 2003 then checks every configured blacklist before it reroutes the email.

If you choose the button “Add” the following window opens:



In the field “Display Name” you should put in a brief description of the rule, in the second field you have to put in the DNS suffix of the blacklist provider itself. And by default, every return status code means a blocking of that email. If you are having trouble with your blacklist provider, just disable the rule by choosing the appropriate button.

If you want to configure a customized return status code behavior, make your choice and the following window will open and will provide your customized configuration.



“Match Filter Rule to any return code” is the default setting and provides a blocking of every email that has a return status code. If you choose “Match Filter Rule to the Following Mask”, you can implement your own status code mask, provided by the blacklist company. If you need to implement customized return status codes, you have to choose the third radio button and then add your codes as shown below:



No rule without exceptions … Therefore you have a way to put in your exceptions by choosing the appropriate button. If you want to configure global IP accept and/or deny lists, this is possible, too. Just choose the “Accept” or “Deny” button.

The next step is now to check if everything runs. If it does not, in general the reason is not your Exchange Server 2003; check your DNS- and firewall settings. The Event log may be your friend, too.

But which servers in your messaging environment should have blacklist blocking enabled? Well, that is quite easy to say: that ones that receive email directly from the internet or via a smart- or relay host within your DMZ. It should be a server that reroutes every incoming email in your organization, and if there is more than one “front-end” server in your environment, you should configure all of them. In addition, don’t forget to check the filtering directory, if there are mails from companies that are on blacklists by accident. In general their entries will be deleted within 24 hours, but within that time window your users do not receive any email from that company.

Source:http://www.msexchange.org/tutorials/Blacklist_Support_Exchange_2003.html