October 2, 2007 at 9:24 AM
The Microsoft Exchange Server 2007 Exchange Management Shell Help file helps you use cmdlets in the Exchange Management Shell to perform day-to-day administration of Exchange 2007. You can view help in the Exchange Management Shell by using the Get-Help cmdlet. This Help file applies to the Microsoft Exchange Server 2007 Service Pack 1 (SP1) version of Exchange Server 2007.
Source: Microsoft Exchange Server 2007 Service Pack 1 Shell Help
September 4, 2007 at 12:55 PM
The Exchange Calendar Update Tool enables administrators to update multiple user mailboxes and adjust calendars and meetings for daylight savings times.
Before you run the Exchange Calendar Update tool, refer to Microsoft Knowledge Base article 941018, "How to address daylight saving time by using the Exchange Calendar Update Tool," for complete information about potential effects on your IT environment and user base.
After you install the DST updates for Microsoft Windows, all old appointments that occur during the DST change periods will be incorrectly displayed as occurring one hour later. This is true for both recurring and single-instance appointments. These appointments must be updated so that they will be displayed correctly in Outlook, in Outlook Web Access, and in CDO-based applications. Outlook provides a tool that is named the Time Zone Data Update Tool for Microsoft Office Outlook . This tool enables users to update their own calendars.
The Exchange Calendar Update Tool ("the Exchange tool") helps you avoid the challenges difficulties that are faced by administrators in deploying the Outlook tool widely to all users and to make sure that each user runs the Outlook tool correctly.
Download Microsoft Exchange Calendar Update Configuration Tool v2.0
September 3, 2007 at 1:42 PM
Exres.dll is Resource DLL of Exchange Server. It acts like "proxy" in communication between Windows Cluster Services and Exchange Services. Windows Cluster service communicates trough Resource Monitor to Exres.dll, and Exres.dll communicates with the Exchange services. This .dll is responsible for reporting failures in the cluster and bringing resources onnline/offline.
September 1, 2007 at 12:28 AM
If you are brave enough you probably already tried Exchange Server 2007 Service Pack 1 Beta 2. ;-)
So if you want to install Forefront Security for Exchange don`t use RTM version of Forefront Security for Exchange. Microsoft provided special version for Exchange Server 2007 with Service Pack 1 Beta 2.
Forefront Security for Exchange Server SP1 Beta 2 integrates multiple scan engines from industry-leading security firms into a comprehensive, layered solution, helping protect your Microsoft Exchange Server messaging environments from viruses, worms, spam, and inappropriate content.
This new release provides support for Exchange Server 2007 SP1 and Windows Server 2008, as well as content filtering and manageability enhancements. These enhancements include:
- Seamless support for organizations running IPv6.
- Improved content filtering with installable keyword lists that can be used to eliminate email containing profanity in eleven supported languages.
- Improved integration with Microsoft System Center Operations Manager through new management packs (available in Q4 2007) that allow administrators to proactively monitor the state of their Exchange 2007 protection.
- Increased flexibility for scanning or blocking high compression zip files and RAR archives.
Note: Forefront Security for Exchange users who are running Exchange 2007 RTM and wish to upgrade to Exchange 2007 SP1 must first upgrade to Forefront Security for Exchange SP1.
You can download it here.
August 24, 2007 at 10:46 AM
Update Rollup 4 for Exchange Server 2007 resolves issues that were found in Exchange Server 2007 since the software was released. This update rollup is highly recommended for all Exchange Server 2007 customers.
For a list of changes included in this update rollup see KB940006.
This is a cumulative update rollup and replaces the following:
August 22, 2007 at 6:36 PM
Microsoft finally published Release Notes for Microsoft Exchange Server 2007 SP1 Beta 2. You may have noticed that they were "published" earlier but the they were Beta 1. A must read before implementation! Do NOT install it in production environment since it is not supported.
Some of the important things from release notes:
- You must prepare Active Directory as a prerequirements to introduce Exchange Server 2007 SP1 Beta 2 into environment.
- You can either perform a clean install or upgrade RTM version or SP1 Beta 1 to SP1 Beta 2.
- You can NOT uninstall Exchange Server 2007 SP1 Beta 2. The only way to remove it is to uninstall Exchange 2007 from server and then reinstall RTM version of Exchange Server 2007.
- You can not use existing version of Forefront Security for Exchange. You must install Microsoft Forefront Security for Exchange Server 2007 with Service Pack 1 Beta 2 version.
- Remote Streaming backups are disabled by default in SP1!
- There are also some known issues with specific tasks in SP1, see Release Notes for details.
- In SP1 new High Availability Scenarios are introduced.
- You can only install Exchange Server 2007 SP1 Beta 2 on Windows Server 2008. There are also some issues with specific server roles. In my case with Mailbox Role.
I will post more details about installing Exchange Server 2007 SP1 Beta 2 on Windows Server 2008 later.
February 15, 2007 at 6:22 PM
Jim McBee writes:
"I came across this on Josh Maher's blog. Danilo Bordini of Microsoft Brasil has posted some early plans for Exchange 2007 Service Pack 1. Keep in mind that these are "plans" and may not reflect reality. The availability is "sometime after Longhorn" releases. So, don't hold your breath. Here are some high-points, at least based on what I could read and get translated from Portuguese."S/MIME controls for Outlook Web Access
Personal distribution lists via OWA
Outlook Web Access monthly calendar view
Custom fields visible in the OWA address book
Rules wizard for OWA
Move-Mailbox cmdlet will import/export from a PST file!
Bulk mailbox operations (I'm assuming this means creation)
Public folder management from GUI
POP3/IMAP4 configuration management from GUI
Support for Longhorn server
Standby continuous replication (SCR)
Log shipping on private networks
Information Rights Management (WRMS integration was pulled from E2K7 right before RTM)
Improvements in geographic CCR clusters
Improved VOIP security
September 22, 2006 at 9:56 AM
I`m really busy lately. I have some projects involving Microsoft Exchange Server 2007 Beta 2 (Rapid Deployment Program). But I will talk about that some other time... What I can say for now is that Exchange 2007 really ROCKS (or FYDIBOHF23SPDLT if we take the name from New Exchange Admin Group [H])!
It`s not a new thing but a lot of people never saw it on Windows (but they are familiar with it from Unix or Novell).
So what is Access-based Enumeration?
Windows Server 2003 Access-based Enumeration makes visible only those files or folders that the user has the rights to access. When Access-based Enumeration is enabled, Windows will not display files or folders that the user does not have the rights to access. This download provides a GUI and a CLI that enables this feature.
You can download it from here: Windows Server 2003 Access-based Enumeration
July 3, 2006 at 1:15 PM
Microsoft released beta version of Exchange 2007 documentation.
[This topic is pre-release documentation and is subject to change in future releases. Its current status is: Content Complete. Blank topics are included as placeholders.]
Welcome to Microsoft Exchange Server 2007! Exchange 2007 provides a reliable messaging system with built-in protection against spam and viruses, which provides people throughout your organization with anywhere access to e-mail, voicemail, calendars, and contacts from a wide variety of devices.
The technical documentation for Exchange 2007 consists of the following categories:
• Getting Started
• Planning and Architecture
• Security and Protection
• Technical Reference
Documentation is available here.
April 14, 2006 at 10:09 AM
Exchange 12 uses Active Directory sites as a basis for choosing which servers to communicate with directly. What that means? When running native Exchange 12 organization no additional routing configuration is required. It automatically routes with minimal hops (shortest path between the source and destination). Each Active Directory site is considered a hop.
If no Bridgehead servers whithin site are available due to temporary network outages, mail will be queued at the point of failure. To avoid this kind of failures deploy multiple Exchange 12 Bridgehead servers whitin site. In this configuration mailflow between the Bridgehead and Mailbox servers is automatically load balanced by default. If one Bridhead server is unavailable (due failure or maintance) failover to other Bridgehead servers is automatic by default.