Publishing Exchange 2010 Services using ISA 2006 works fine. Just select Exchange 2007 as Exchange Version and publish OWA, PushMail and Outlook Anywhere.
The only problem is the new ECP. You have to add a directory manually in the ISA Publishing Rule:
Here is a list of new features, provided by Exchange 2010:
Microsoft Exchange Server 2010 brings a new and rich set of technologies, features, and services to the Exchange Server product line. This topic includes a list of the new features and functionality that are included in Exchange 2010. The list isn’t comprehensive, but it provides important information to use when you’re planning, deploying, and administering your Exchange 2010 organization. This topic also includes information about some of the limitations of this release and features from Exchange Server 2007 that have been removed.
New Rights-Protected E-Mail Functionality with Active Directory RMS
The following is a list of new rights-protected e-mail functionality with Active Directory Rights Management Services (AD RMS) that has been included in Exchange 2010:
Transport rules to apply AD RMS protection to messages based on conditions.
Persistent protection of attachments in rights-protected messages.
Support for AD RMS templates.
An Internet confidential AD RMS template for protection over the Internet.
AD RMS protection for Unified Messaging voice mail messages
Vom Exchange Server 2007 Nachfolger “Exchange Server 2010″ ist die erste Public Beta erschienen. Folgende Neuerungen bietet Exchange Server 2010:
New Rights-Protected E-Mail Functionality with Active Directory RMS
The following is a list of new rights-protected e-mail functionality with Active Directory Rights Management Services (AD RMS) that has been included in Exchange 2010:
Transport rules to apply AD RMS protection to messages based on conditions.
Persistent protection of attachments in rights-protected messages.
Support for AD RMS templates.
An Internet confidential AD RMS template for protection over the Internet.
AD RMS protection for Unified Messaging voice mail messages.
New Transport and Routing Functionality
The following is a list of new transport and routing functionality that has been included in Exchange 2010:
Cross-premises mail routingAn organization can choose to outsource some of their mailboxes to a hosted solution while maintaining their on-premises deployment. For example, a university can choose to host the mailboxes for all faculty and staff in their on-premises deployment and use a hosted solution for student mailboxes. Exchange 2010 allows routing of messages between the on-premises and hosted mailboxes.
Enhanced disclaimers Exchange 2010 lets you add disclaimers that can include hyperlinks, images, and HTML-formatted text. You can also insert Active Directory attributes that are substituted for the sender’s attributes when a disclaimer rule is triggered.
Transport rules integration with AD RMS Exchange 2010 gives you the ability to create rules that require AD RMS protection based on keywords or patterns.
Moderated Transport Exchange 2010 provides an approval workflow for sending messages to recipients. When you configure a recipient for moderation, all messages sent to that recipient must go through an approval process.
Shadow redundancy Messages that are submitted to an Exchange 2010 Hub Transport server are stored in the transport database until the next hop reports successful delivery of the message. If the next hop doesn’t report successful delivery and it fails, the message is resubmitted for delivery.
Transport dumpster truncation based on log copy status When messages that are in the dumpster are replicated to all mailbox databases, they’re removed from the dumpster.
Latency SLA management Exchange 2010 Transport lets you measure service levels delivered relative to your service level agreement (SLA) goals. Exchange 2010 gives you the ability to measure latencies for each hop, as well as end-to-end latency.
Transport database improvements Performance improvements in the Transport database result in reduced database I/O per second (IOPS) per message, which increases message throughput.
New Permissions Functionality
In Exchange 2010, Role Based Access Control (RBAC) has replaced the permissions model that was used in Exchange 2007. RBAC lets you define extremely broad or extremely precise roles and assignments based on the roles of your administrators and users, and the tasks they perform. Access to the cmdlets and parameters required to perform a task is granted by assigning the related RBAC management role to a user or universal security group. If you want to grant an administrator or user the ability to perform tasks in Exchange 2010, you must either add the administrator or user to a universal security group that already has been assigned a specific RBAC role, or you must assign the role directly to the administrator or user.
New High Availability Functionality
Exchange 2010 integrates high availability into the core architecture of Microsoft Exchange to enable customers of all sizes and in all segments to economically deploy a messaging continuity service in their organization.
Exchange 2010 combines the key availability and resilience features of cluster continuous replication (CCR) and standby continuous replication (SCR) into a single high availability solution that handles both on-site data replication and off-site data replication. Mailbox servers can be defined as part of a Database Availability Group to provide automatic recovery at the individual mailbox database level instead of at the server level. Each mailbox database can have up to 16 copies.
The following features in Exchange 2007 and Exchange 2007 Service Pack 1 (SP1) no longer exist in Exchange 2010:
Local continuous replication (LCR)
Single copy clusters (SCC)
New Messaging Policy and Compliance Features
Exchange 2010 compliance features make retention independent of users’ mailbox management and filing habits, and these features ensure retention policies are applied continuously. The following is a list of new messaging and compliance features that have been included in Exchange 2010:
New interface for applying retention policies
Auto tagging for retention policies
Mailbox search features for cross-mailbox search with Advanced Query Syntax (AQS) support
New transport rules predicates and actions
New Outlook Web Access Features
The following is a list of new features in Outlook Web Access in Exchange 2010:
Favorites in the Navigation Pane
Search folders
Message filtering
The ability to set categories in the message list
Options in the Web management interface for Outlook Web Access
A side-by-side view for calendars
Multi-client language support
The ability to attach messages to messages
Expanded right-click capabilities
Integration with Office Communicator, including presence, chat, and a contact list
Conversation view
The ability to send and receive text (SMS) messages from Outlook Web Access
Outlook Web Access mailbox policies
New Unified Messaging Features
The following is a list of new Unified Messaging features that have been included in Exchange 2010:
Personal auto attendants (call answering rules)
Additional language support including in Outlook Voice Access and Voice Mail Preview
Enhancements to name lookup from caller ID
Voice Mail Preview
Messaging Waiting Indicator
Missed call and voice mail notifications using text messaging (SMS)
Protected Voice Mail
Built-in Unified Messaging administrative roles
Web Management Interface
The following is a list of the features available in the new Web management interface for Exchange 2010:
Text messaging (SMS) integration
Voice messaging integration
Mailbox Search
Distribution list creation and management
Moderation and approval for distribution list submission
New Exchange Core Store Functionality
The following is a list of core store functionality that is included or has been changed in Exchange 2010:
Storage groups are deprecated.
Mailbox databases are no longer connected to the server object.
Extensible Storage Engine (ESE) has many improvements for high availability, performance, and database mobility.
The Store schema has been flattened.
New Administration Functionality in the Exchange Management Console
The core EMC refers to new functionality that affects how you use the Exchange Management Console, not how you use specific features. The following is a list of the new core Exchange Management Console (EMC) features that have been included in Exchange 2010:
Customer Experience Improvement Program (CEIP)
Organizational Health
Community and Resources
Command logging
Property dialog command exposure
New Administration Functionality in the Exchange Management Shell
The following is a list of features available in the new Exchange Management Shell:
Remote administration With the new Shell, you can connect to remote Exchange 2010 servers across the network with only Windows PowerShell V2 CTP3 and Windows Remote Management 2.0 CTP installed.
Administrator audit logging Actions that result in the modification of Exchange organization configuration and other object properties in the Exchange Management Console, the Web management interface, and the Shell can now be logged for later review. For more information, see Overview of Administrator Audit Logging.
HP ML350 G5 with Microsoft Small Business Server 2003 installed.
After 400 days uptime, we had to install several patches from Windowsupdate.com, several reboots was necessary. The System was stable after installing the updates.
A day after that, the System was freezed in the morning. I resettet the Server using ILO2 and tried to boot it again. But it hangs 15 Minutes at “Applying computer settings”. I resettet the machine again and tried “Last known good configuration”. Same issue. Again reset.
Know i booted the machine in safe mode and disabled several Services, such Exchange Services and Backup Exec services. Reboot – it works, Server is up.
Now, i tried to manually start the Exchange Information Store – Server freeze, reset.
I tried to make a eseutil /k to check the Database – freeze.
After searching a bit, i found the information, that there is an issue with the RAID Driver for the e200 Smart Array Controller. I updated the Smart Array Controller to the latest Version, rebooted the machine again. – Worked.
I started Exchange Services manually – Worked.
If you have the same issue, try to update the e200 Array Drivers, it should be fixed after that.
Exchange 2007 MailBox / Hub / CAS Server sind im LAN
Exchange 2007 Edge Server ist in der DMZ
Der Exchange MailBox… Server meldet, das der Edge Server nicht lizenziert sei und nach XX Tagen nicht mehr funktionsfähig sei. Um das Problem zu beheben, muss via Exchange Shell der folgende Command abgesetzt werden:
Nach einer Implementation von Exchange 2007 erhielten einige User Mails mit entfernten Attachements.
Zuerst dachte ich, GFI MailSecurity würde dies ausführen, was aber nicht der Fall ist. Es handelt sich um den Exchange eigenen “Attachement Filtering Agent”.
Dieser kann mit folgendem Console Command deaktiviert werden:
Bei Distribution Groups in Exchange 2007 muss man by Default “authenticated” sein, um Mails zu senden. Mails von anderen Mailservern haben es also schwer, anzukommen.
Um das zu beheben öffnet man die Properties der Distribution Group, wechselt zum “Mail Flow Settings” Tab, öffnet die “Mail Delivery Restrictions” Properties. Dort muss das Flag “Require that all senders are authenticated” entfernt werden.
Groups/Your administrative group/Servers/Server name/Information Store
3. Right-click Information Store, and then click Properties.
4. Under the list of Attributes, scroll down and select
msExchESEParamCacheSizeMax.
5. Click the Edit button, then type the number of 8 kilobyte (KB) pages
that you want to set the maximum cache size to.
For example to set the cache at 5GB which would allow the system with 8GB of memory to keep 1GB of memory for various processes and 2GB for the kernel. A 5GB cache equates to 5242880 (5120 * 1024).
Note The msExchESEParamCacheSizeMax parameter controls the ESE buffer size.
Its value is expressed as a page count, and must be set to an exact
multiple of 8192 for maximum efficiency. If this value is not met, the
cache size is rounded up to the next 32-MB boundary when virtual memory is
allocated. If this value is incorrectly set, memory may be wasted.
6. Quit ADSI Edit, and then restart the Microsoft Exchange Information
Store service.
Soeben im Web gefunden und definitiv ein Download Wert – der Exchange 2007 Autodiscover Song.
Text:
>>Autodiscover
>>There is no other
>>Way to decide
>>Where your mailbox is stored
>>Autodiscover
>>Your sister and brother
>>Exchange Admin and mother
>>Will be proud if you do
You may be tempted to wing it
Use a hardcoded link submit it
But performance will suffer
When you’re left to your druthers
Should have Autodiscovered
Then all would be well
>>Chorus
Call it once for each mailbox of interest
Pair the link and mailbox for each request
If you encounter errors
Refresh once again
For more information search M-S-D-N for
>>Chorus
Exchange won’t exist in a bubble
If you think that it will you’re in trouble
Add a site, one or two
And your perf will be through
Unless you step up and decide that your app will just…
>>Chorus
Autodiscover,
Autodiscover,
Just AutoDiscover for me.
It’s just plain XML
Das bekannte Problem. Wer mit dem Internet Explorer auf das OWA zugreift und eine E-Mail schreiben möchte, muss zuerst ein ActiveX installieren. Funktioniert das nicht oder wird das ActiveX nicht installiert, funktioniert das schlichtweg nicht mehr.
Dafür gibt es einen Patch von Microsoft für den Exchange Server:
When you access Microsoft Outlook Web Access by using Microsoft Internet Explorer 6 or a later version of Internet Explorer, you experience one of the following symptoms.
Symptom 1
On a computer that is running Microsoft Windows Vista, you cannot perform any editing tasks that you typically expect to perform. For example, you cannot perform the following tasks:
•
Compose a new e-mail message
•
Reply to an e-mail message
•
Create a new contact, task, note, journal entry, or appointment
•
Change any configuration in the Outlook Web Access options folder
Additionally, you may receive an error message when you try to perform these tasks.
Symptom 2
On a computer on which you have installed update 912945, you must first click one time in the compose frame in Outlook Web Access before you edit text. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
912945 (http://support.microsoft.com/kb/912945/) Internet Explorer ActiveX update
Symptom 3 On a computer on which you have installed security update 912812 that is described in security bulletin MS06-013, you must first click one time in the compose frame in Outlook Web Access to activate the edit control.
CAUSE
Symptom 1
This behavior occurs because Windows Vista no longer includes support for the ActiveX control that is used for HTML editing in Outlook Web Access.
Symptom 2
Update 912945 requires that you click one time in an ActiveX control to enable the control in Internet Explorer 6.
Symptom 3
Security update 912812 requires that you click one time in an ActiveX control to enable the control in Internet Explorer 6.
RESOLUTION
This Microsoft Exchange Server hotfix resolves the three issues that are mentioned in the “Symptoms” section. This hotfix enables a new editor for Internet Explorer. The new editor uses an Internet Explorer “iframe” instead of an ActiveX control. After you apply hotfix 911829, you are not required to first click in the compose frame in Outlook Web Access before you edit text.
Harold Wong eine bietet seinen Webcast “Exchange in the Depth – Master concepts and optimize your server environment” zum kostenlosen Download an. Insgesamt sind es 24 Files, welche 24 Stunden Material beinhalten.
Scenario: Exchange 2003 SP2 auf Windows Server 2003 mit SP2. Der Exchange Server ist ein BackEnd Server, muss aber gleichzeitig Active Sync zur Verfügung stellen. Ein Front-End Server kommt in dieser Konstelation nicht in Frage.
Beim Sync mit einem Mobile Device werden keine Nachrichten heruntergeladen und es erscheint die folgende Fehlermeldung:
The mailbox server [] does not allow “Negotiate” authentication to its [exchange] virtual directory.
Dieser Fehler tritt auf, wenn Form Based Authentication und SSL auf dem Exchange Server aktiviert ist
Die Lösung für dieses Problem ist wie folgt:
Form Based Authentication ausschalten:
1.
Open Exchange Manager.
2.
Expand Administrative Groups, expand the first administrative group, and then expand Servers.
3.
Expand the server container for the Exchange Server 2003 server that you will be configuring, expand Protocols, and then expand HTTP.
4.
Under the HTTP container, right-click the Exchange Virtual Server container, and then click Properties.
5.
Click the Settings tab, clear the Enable Forms Based Authentication check box, and then click OK.
6.
Close Exchange Manager.
7.
Click Start, click Run, type IISRESET/NOFORCE, and then press ENTER to restart Internet Information Services (IIS).
Neues Virtual Directory erstellen:
1.
Start Internet Information Services (IIS) Manager.
2.
Locate the Exchange virtual directory. The default location is as follows:
Web Sites\Default Web Site\Exchange
3.
Right-click the Exchange virtual directory, click All Tasks, and then click Save Configuration to a File.
4.
In the File name box, type a name. For example, type ExchangeVDir. Click OK.
5.
Right-click the root of this Web site. Typically, this is Default Web Site. Click New, and then click Virtual Directory (from file).
6.
In the Import Configuration dialog box, click Browse, locate the file that you created in step 4, click Open, and then click Read File.
7.
Under Select a configuration to import , click Exchange, and then click OK.
A dialog box will appear that states that the “virtual directory already exists.”
8.
In the Alias box, type a name for the new virtual directory that you want Exchange ActiveSync and Outlook Mobile Access to use. For example, type exchange-oma. Click OK.
9.
Right-click the new virtual directory. In this example, click exchange-oma. Click Properties.
10.
Click the Directory Security tab.
11.
Under Authentication and access control, click Edit.
12.
Make sure that only the following authentication methods are enabled, and then click OK:
•
Integrated Windows authentication
•
Basic authentication
13.
On the Directory Security tab, under IP address and domain name restrictions, click Edit.
14.
Click the option for Denied access, click Add, click Single computer and type the IP address of the server that you are configuring, and then click OK.
15.
Under Secure communications, click Edit. Make sure that Require secure channel (SSL) is not enabled, and then click OK.
16.
Click OK, and then close the IIS Manager.
17.
Click Start, click Run, type regedit, and then click OK.
Right-click Parameters, click to New, and then click String Value.
20.
Type ExchangeVDir, and then press ENTER. Right-click ExchangeVDir, and then click Modify.
NoteExchangeVDir is case-sensitive. If you do not type ExchangeVDir exactly as it appears in this article, ActiveSync does not find the key when it locates the exchange-oma folder.
21.
In the Value data box, type the name of the new virtual directory that you created in step 8. For example, type /exchange-oma. Click OK.
22.
Quit Registry Editor.
23.
Restart the IIS Admin service. To do this, follow these steps:
a.
Click Start, click Run, type services.msc, and then click OK.
b.
In the list of services, right-click IIS Admin service, and then click Restart.
Form Based Authentication wieder aktivieren.
Nun sollte der Sync mit Active Sync funktionieren.
Nach der Installation von Exchange 2007 ist der Server standardmässig nicht für den Versand / Empfang von Mails konfiguriert. Wie dies konfiguriert wird, erklärt dieser Artikel.
In meiner Testumgebung verwende ich die Domain “the-admin.net”. Für die Domain “the-admin.net” ist der MX Record auf die IP meiner Firewall konfiguriert. In diesem Test
In Outlook 2007 gibt es im Zusammenhang mit Exchange 2007 ein geniales neues Feature, Autodiscover.
Alle Informationen die Outlook braucht, um einen Exchange Account einzurichten, sind im Active Directory hinterlegt. Dazu gehört z.B. der Exchange Server Name.
Beim starten von Outlook wird eine Verbindung zum Active Directory aufgebaut, wo die ganzen Informationen ausgelesen werden, um einen Exchange Account einzurichten:
In diesem Artikel wird erklärt, wie Exchange 2007 SP1 auf Windows Server 2008 RTM installiert wird.
Bei dieser Installation handelt es sich um eine Installation in einer Testumgebung, d.h. nicht alle Einstellungen sind für den Einsatz in produktiven Umgebungen zu übernehmen!
Falls GFI MailEssentials (Version 12 in diesem Fall) und Exchange 2003 auf dem gleichen Server installiert werden, sind im Exchange Message Tracking Center folgende Einträge in der Message History zu finden:
SMTP: Started Message Submission to Advanced Queue
SMTP: Advanced Queue Failed to Deliver Message
Auf den jeweiligen Modulen war als Action “Move to subfolder of user’s mailbox” gewählt.
Nach einem Telefonat mit GFI stellte sich heraus, dass dies kein Fehler ist, sondern “normal”. weiterlesen… »
New Rights-Protected E-Mail Functionality with Active Directory RMS
)
