Outlook 2003 Service Pack 3 Clients
Issue:
During normal working hours users randomly was unable to access their mailboxes when they launched their Outlook client.

The users were receiving the following Outlook message:

“Unable to open your default e-mail folders. The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.”
It was also reported that some users had issues expanding additional mailboxes. (Delegate Mailboxes )
The following Outlook message appeared.

Or users have issues opening Shared Calendars.

Solution:
http://support.microsoft.com/kb/2299468

With Get-ThrottlingPolicy you can see the value of RCAMaxConcurrency

(Exchange 2010 RTM default value 20) (Exchange 2010 SP1 default value 214748364)

I changed RCAMaxConcurrency to 214748364 and the problem is fixt:

Get-ThrottlingPolicy | set-ThrottlingPolicy -RCAMaxConcurrency 214748364

1. Get a SAN Certificate.

I my case I have the following URL’s registered with the certificate.
webmail.wardvissers.nl
autodiscover.wardvissers.nl
legacy.wardvissers.nl
casarray.wardvissers.local

2. Import the Certificate in to Exchange 2010. 
How to check HERE

3. Create on the Exchange 2010 Server a Client Access Array.
How you must do it I spoke it Configuring Client Access Array. I this case a used casarray.wardvissers.local for the client acces array.

4. Setting the internal & external url’s

Set-ClientAccessServer -Identity ward-ex01 -AutoDiscoverServiceInternalUri https://casarray.wardvissers.local/Autodiscover/Autodiscover.xml

Set-WebServicesVirtualDirectory -Identity “ward-ex01\EWS (Default Web Site)” -InternalUrl https://casarray.wardvissers.local/ews/exchange.asmx -ExternalUrl https:// webmail.wardvissers.nl/ews/exchange.asmx

Set-OABVirtualDirectory -Identity “ward-ex01\oab (Default Web Site)” -InternalUrl http:// casarray.wardvissers.local/oab -ExternalUrl https://webmail.wardvissers.nl/oab

Enable-OutlookAnywhere -Server ward-ex01 -ExternalHostname “webmail.wardvissers.nl” -ClientAuthenticationMethod “Basic”-SSLOffloading:$False

Set-ActiveSyncVirtualDirectory -Identity “ward-ex01\Microsoft-Server-ActiveSync (Default Web Site)” -InternalURL https://casarry.wardvissers.local/Microsoft-Server-Activesync
-ExternalURL https://webmail.wardvissers.nl/Microsoft-Server-Activesync

Set-ECPVirtualDirectory –Identity ward-ex01\ECP (default web site) -InternalURL https://casarry.wardvissers.local/ECP -ExternalURL https://webmail.wardvissers.nl/ECP

5. Configure Exchange 2010 for basic authentication

Set-OwaVirtualDirectory -id ward-ex01\* -BasicAuthentication $true -WindowsAuthentication $true -FormsAuthentication $false

set-WebServicesVirtualDirectory -Identity “ward-ex01\EWS (Default Web Site)” -WindowsAuthentication $true -BasicAuthentication $true

set-EcpVirtualdirectory –Identity ward-ex01\ECP (default web site) -BasicAuthentication $true -WindowsAuthentication $true -FormsAuthentication $false

set-OabVirtualDirectory -Identity “ward-ex01\oab (Default Web Site)” -WindowsAuthentication $true -BasicAuthentication $true

set-ActiveSyncVirtualDirectory -Identity “ward-ex01\Microsoft-Server-ActiveSync (Default Web Site)” -BasicAuthentication $true

6. Import the SAN certificate in to the TMG server.

1. Click Start –> Run –> Type MMC
2. Click File –> add remove Snap-in –> Certificates –> ADD –> Computer account-> Next –> finish-> ok
3. Click Personal –> certificates
4. Right Click certificates –> all task –> import –> next –> select the *.pfx file –> next –> Password –> next –> next –> Finish

7. Publish OWA

1. Publish Exchange Web Client Access

2. Exchange Publishing rule name: OWA 2010

3. Choose Exchange Server 2010 & Outlook Web Access

4. Next ( I have only Single TMG Server)

5. Next

6.Internal Site Name: Client Access Array name. My Case casarray.wardvissers.local

7. Public Name: webmail.wardvissers.nl

8. At this moment I have no Web Listener so we gone create them

9. Weblister Name: HTTPS

10. Next

11. I choise for All Networks (and local host) because the Server has one NIC.

12. Select the Certificate that you just imported.
 

13. Choise for LDAP (Active Directory)

14. SSO Domain name: my case wardvissers.nl (External Domain name)

15. Finish

16. Next

17. Next

18. Next

19. Finish

8. Publish Active Sync

1. Publish Exchange Web Client Access

2. Exchange Publishing rule name: Active Sync 2010

3. Exchange Server 2010 & Exchange ActiveSync

4. Next

5. Next

6. Internal Site name: CasArray name

7. Public Name: I my case webmail.wardvissers.nl

8.Choise the HTTPS web listerner

9. Next

10. Next

11. Finish

Next Time I will publish how to deploy a Legacy Exchange Server 2003 & 2007 with TMG

Today the Exchange Team released Rollup 2 for Exchange Server 2010 Service Pack 1 (KB2425179). This update raises Exchange 2010 version number to 14.1.270.1.

If your upgrading from Exchange 2007 you need to implement this rollup because the bug Exchange 2007 OWA redirect bug with Exchange 2010 sp1 is fixed check: kb2458419

The List with Fixes:

983186 The mailbox alias of a user contains the "?" character unexpectedly after you run the "Enable-Mailbox" cmdlet to create a mailbox for the user in an Exchange Server 2010 environment

2295902 An excepted occurrence is not excluded from a recurring iCalendar message for an Exchange Server 2010 mailbox user

2385017 You cannot edit public folder items even though you are the owner of the items in an Exchange Server 2010 environment

2385194 You cannot connect to an Exchange Server 2010 mailbox by using a MAPI application when a Mailbox server and a Client Access server are installed on different computers

2397171 You cannot reply or forward a large email message on an Exchange Server 2010 mailbox

2403783 An incorrect label is displayed in the date field in a public folder item when you open the item by using OWA in an Exchange Server 2010 environment

2408924 The subject of an item is deleted when you use the "UploadItems" operation together with the "Update" action or the "UpdateOrCreate" action in an Exchange Server 2010 environment

2409597 You cannot open a public folder item when the default public folder database for the mailbox database is unavailable in an Exchange Server 2010 environment

2423776 The Exchange Information Store service crashes frequently during a public folder replication process on an Exchange Server 2010 public folder

2431500 You cannot connect to an Exchange Server 2010 mailbox simultaneously by using Outlook Anywhere from several Windows XP-based computers

2433642 The "FETCH (BODYSTRUCTURE)" command returns a corrupted file name of an email message attachment on an Exchange Server 2010 computer

2452075 You cannot connect to mailboxes in a recovery database on a server after you install Exchange Server 2010 SP1

2458005  The Exchange Mailbox Replication service crashes when you use the "New-MailboxImportRequest" command to import a PST file to an Exchange Server 2010 mailbox

2458419 "A temporary change has occurred that requires you to connect to a different server" error message when Exchange Server 2007 mailbox users try to access their mailboxes by using an Exchange Server 2010 Client Access server

2322161 The replay queue length on passive copies of mailbox databases in Database Availability Group continues to increase in an Exchange Server 2010 environment

982004 Exchange Server 2010 users cannot access the public folder

983492 You cannot view updated content of an Exchange Server 2010 public folder

983549 Exchange Server 2010 removes the sender’s email address from the recipient list in a redirected email message

Download the Hotfix HERE

The List with fixes:
972186 Some functions do not work if you install Security Configuration Wizard on a Windows Server 2008 SP2-based Exchange Server 2007

979046 Attachments are empty when you save them by using OWA after you have applied the update of KB 958881 on an Exchange Server 2007

980038 The Microsoft Exchange System Attendant service crashes intermittently in the Oabgen.dll module on an Exchange Server 2007 server

981602 Event ID: 4999 is frequently generated in a mixed Exchange Server 2007 and Exchange Server 2003 environment

982476 The Imap4.exe process crashes intermittently on an Exchange Server 2007 server

982478 Notes URL links in a plain text message are not clickable when you open this message by using OWA in an Exchange Server 2007 environment

2028675 The MSExchangeFDS.exe process occupies lots of memory if there are thousands of OABs created on an Exchange Server 2007 server

2029086 Some characters of an email message are displayed in an incorrect text size when you access your mailbox by using OWA in Exchange Server 2007

2032216 The Microsoft Exchange Information Store service crashes on an Exchange Server 2007 server when you start it or try to mount certain databases

2121536 Exchange Server 2007 cannot index a message

2201236 The "All Day" field is marked with "No" when you access a meeting request that has a duration time that is more than 24 hours by using a mobile client through ActiveSync in an Exchange Server 2007 environment

2203212 Certain mailboxes cannot be moved from an Exchange Server 2007 server to an Exchange Server 2010 server

2210042 A sub contact folder is still visible after you set the "PR_ATTR_HIDDEN" attribute to "True" in an Exchange Server 2007 environment

2230824 The Microsoft.Exchange.POP3.exe process or the Microsoft.Exchange.Imap4.exe process may crash after you enable protocol logging for POP3 or IMAP4 on an Exchange Server 2007 server

2249814 You receive misleading information when you run the "New-TestCasConnectivityUser.ps1" script on an Exchange Server 2007 server

2263342 "The operation failed" error message in Outlook client when a user sends a recurring meeting request with an email message attachment in an Exchange Server 2007 SP2 environment

2276439 (http://support.microsoft.com/kb/2276439/ ) The Microsoft.Exchange.IMAP4.exe process crashes when an IMAP4 client retrieves a meeting request that includes exception attachments in an Exchange Server 2007 environment

2280234 "Your POP3 server has not responded in 60 seconds." error message when a POP3 client connects to an Exchange Server 2007 Client Access server to access an Exchange Server 2003 mailbox

2282570 "550 5.1.3" NDR message when an Exchange Server 2007 user sends an email message to a recipient

2265306 The Exchange Information Store service stops responding when you perform a search operation on an Exchange Server 2007 mailbox in Outlook

2282746 The "Private" sensitivity status of an occurrence of a recurring meeting request is lost when you edit the occurrence in OWA in an Exchange Server 2007 environment

2286782 The response details are still included in the response email message when you set the "EnableResponseDetails" property to "False" in an Exchange Server 2007 environment

2290105 A shared document cannot be open by using OWA after you install Exchange Server 2007 SP3 on an Exchange Server 2007 server

2290159 The POP3 service crashes on an Exchange Server 2007 server

2344372  You cannot move mailboxes to an Exchange Server 2007 server

2362371 You receive a "Success" response when using the Test-Mailflow command on an invalid or nonexistent external email address in an Exchange Server 2007 environment

2384754 "Unable to identify local server row in Replication state table for this FID" error message when you run the Information Store Integrity Checker tool on an Exchange Server 2007 server

2387915 The ESEBack component does not support ETL tracing on an Exchange Server 2007 server

2388057 The Exchange Transport service crashes on Exchange Server 2007 servers in a mixed Exchange Server 2007 and Exchange Server 2010 environment

2394731 An HTML attachment of a shared mailbox cannot be saved when you set the "BypassOwaHTMLAttachmentFiltering" setting to "True" in an Exchange Server 2007 environment

2424499 Exchange Server 2007 does not support to assign a mailbox with the "Send on behalf" permission of a security group in the EMC or in the EMS

2427297 The created time and the modified time of an attachment are incorrect when you save an email message on an Exchange Server 2007 mailbox

2430674 The "Leave message intact" method in a Folder Assistant rule does not work when you post an item by using OWA in an Exchange Server 2007 environment

Download the hotfix HERE

This 300 level hands-on labs online course (including seven hands-on labs) will prepare learners with the knowledge to engage with customers to help them implement best practices for smooth Exchange 2010 upgrades and deployments. These hands-on labs online (HOLOs) are provided at no charge to Microsoft partners, and provide IT Professionals with the essential information they need to setup, deploy, and configure Microsoft Exchange Server 2010.  The course will address gaps in knowledge around topics such as new features, upgrade paths, tools and processes to support upgrade and deployment planning.

Training includes the following curriculum:

Course (Online): Using Exchange 2010 Tools to Plan a Deployment (Part 1)

Course (Online): Using Exchange Tools to Plan a Deployment (Part 2)

Course (Online): Exchange 2010 Setup, Deployment, and Server Role Configuration

Course (Online): Configuring Mail Flow and Outlook Web Access

Course (Online): Moving Mailboxes to Exchange 2010

Course (Online): Moving Other Services to Exchange 2010 (Part 1)

Course (Online): Moving Other Services to Exchange 2010 (Part 2)

Thanks to

Bryan Von Axelson

The property is MSExchDelegateListLink. You can check it with adsiedit.

When you open now Outlook 2010 you can now see that Wardtest is automatilly Added

And additional mailboxes is empty

When you migrating from Exchange 2007 to Exchange 2010 and upgraded the Clients to Outlook 2010
Use dis script to set the MSExchDelegateListLink object automatically. Test I first. It’s your own risk.

$a=get-MailboxPermission * | where {$_.IsInherited –eq $False –and $_.accessrights –eq “FullAccess”}
$a | remove-MailboxPermission –confirm:$false
$a | add-MailboxPermission

Save the scripts to MSExchDelegateListLink.ps1

It works great
Source

In SP1, this redirection is no longer silent.  When your Exchange 2007 user logs in via webmail.wardvissers.nl, they are presented with this screen:

The text reads:

A temporary change has occurred that requires you to connect to a different server.  To connect, click the button below.  For security reasons, you’ll be asked to enter your user name and password again.

Sure enough, when you click Connect, you are redirected to legacy.wardvissers.nl, where you have to re-enter your user information.
Thankfully, the same sort of thing doesn’t seem to happen with Outlook Anywhere or ActiveSync clients.
I checked the LegacyRedirectType value on my 2010 SP1 CAS boxes and they are all still set to Silent.  The issue occurs because the OWA virtual directory value for LegacyRedirectType is being ignored.  This is an extraordinarily unfortunate thing to have been introduced with SP1.   If you have a mixed Exchange 2007/2010 environment, I suggest you wait until the rollup 2 is out before deploying SP1. 

Update 15 December 2010

Update 2 for Exchange 2010 and the fix is there described 2458419 "A temporary change has occurred that requires you to connect to a different server" error message when Exchange Server 2007 mailbox users try to access their mailboxes by using an Exchange Server 2010 Client Access server

You can download the rollup HERE

So What’s New in Exchange SP1:

New Deployment Functionality

During an Exchange 2010 SP1 installation, you can now select a new option to install the required Windows roles and features for each selected Exchange 2010 SP1 server role. For more information, see New Deployment Functionality in Exchange 2010 SP1.

Exchange ActiveSync

In Exchange 2010 SP1, you can manage Exchange ActiveSync devices using the Exchange Control Panel (ECP). Administrators can perform the following tasks:

• Manage the default access level for all mobile phones and devices.
• Set up e-mail alerts when a mobile phone or device is quarantined.
• Personalize the message that users receive when their mobile phone or device is either recognized or quarantined.
• Provide a list of quarantined mobile phones or devices.
• Create and manage Exchange ActiveSync device access rules.
• Allow or block a specific mobile phone or device for a specific user.

For every user, the administrator can perform the following tasks from the user’s property pages:

• List the mobile phones or devices for a specific user.
• Initiate remote wipes on mobile phones or devices.
• Remove old mobile phone or device partnerships.
• Create a rule for all users of a specific mobile phone or device or mobile phone type.
• Allow or block a specific mobile phone or device for the specific user.

SMS Sync

SMS Sync is a new feature in Exchange ActiveSync that works with Windows Mobile 6.1 with the Outlook Mobile Update and with Windows Mobile 6.5. SMS Sync is the ability to synchronize messages between a mobile phone or device and an Exchange 2010 Inbox. When synchronizing a Windows Mobile phone with an Exchange 2010 mailbox, users can choose to synchronize their text messages in addition to their Inbox, Calendar, Contacts, Tasks, and Notes. When synchronizing text messages, users will be able to send and receive text messages from their Inbox. This feature is dependent on the user’s mobile phones or devices supporting this feature

Reset Virtual Directory

In Exchange 2010 SP1, you can use the new Reset Client Access Virtual Directory wizard to reset one or more Client Access server virtual directories. The new wizard makes it easier to reset a Client Access server virtual directory. One reason that you might want to reset a Client Access server virtual directory is to resolve an issue related to a damaged file on a virtual directory. In addition to resetting virtual directories, the wizard creates a log file that includes the settings for each virtual directory that you choose to reset. For more information, see Reset Client Access Virtual Directories.

Exchange Store and Mailbox Database Functionality

The following is a list of new store and mailbox database functionality in Exchange 2010 SP1:

• With the New-MailboxRepairRequest cmdlet, you can detect and repair mailbox and database corruption issues.
• Store limits were increased for administrative access.
• The Database Log Growth Troubleshooter (Troubleshoot-DatabaseSpace.ps1) is a new script that allows you to control excessive log growth of mailbox databases.
• Public Folders client permissions support was added to the Exchange Management Console (EMC).

Mailbox and Recipients Functionality

The following is a list of new mailbox and recipient functionality included in Exchange 2010 SP1:

• Calendar Repair Assistant supports more scenarios than were available in Exchange 2010 RTM.
• Mailbox Assistants are now all throttle-based (changed from time-based in Exchange 2010 RTM).
• Internet calendar publishing allows users in your Exchange organization to share their Outlook calendars with a broad Internet audience.
• Importing and exporting .pst files now uses the Mailbox Replication service and doesn’t require Outlook.
• Hierarchical address book support allows you to create and configure your address lists and offline address books in a hierarchical view.
• Distribution group naming policies allow you to configure string text that will be appended or prepended to a distribution group’s name when it’s created.
• Soft-delete of mailboxes after move completion

High Availability and Site Resilience Functionality

The following is a list of new high availability and site resilience functionality included in Exchange 2010 SP1:

• Continuous replication – block mode
• Active mailbox database redistribution
• Enhanced datacenter activation coordination mode support
• New and enhanced management and monitoring scripts
• Exchange Management Console user interface enhancements
• Improvements in failover performance

Messaging Policy and Compliance Functionality

The following is a list of new messaging policy and compliance functionality included in Exchange 2010 SP1:

• Provision personal archive on a different mailbox database
• Import historical mailbox data to personal archive
• Delegate access to personal archive
• New retention policy user interface
• Support for creating retention policy tags for Calendar and Tasks default folders
• Opt-in personal tags
• Multi-Mailbox Search preview
• Annotations in Multi-Mailbox Search
• Multi-Mailbox Search data de-duplication
• WebReady Document Viewing of IRM-protected messages in Outlook Web App
• IRM in Exchange ActiveSync for protocol-level IRM
• IRM logging
• Mailbox audit logging

Technet Exchange 2010 SP1 info
Release Notes for Exchange Server 2010 SP1
What’s New in Exchange 2010 SP1
Downloads:
Microsoft Exchange Server 2010 Service Pack 1
Microsoft Exchange Server 2010 SP1 Language Pack Bundle
Exchange Server 2010 SP1 UM Language Packs
Exchange Server 2010 SP1 Help

Error:
Failed to communicate with the mailbox database.

MapiExceptionLogonFailed: Unable to make connection to the server. (hr=0×80040111, ec=1010)
Diagnostic context:
    Lid: 37053   Win32Error: 0x6A6
    Lid: 23065   EcDoConnectEx called [length=48]
    Lid: 17913   EcDoConnectEx returned [ec=0x0][length=48][latency=31]
    Lid: 18969   EcDoRpcExt2 called [length=313]
    Lid: 27161   EcDoRpcExt2 returned [ec=0x3F2][length=342][latency=46]
    Lid: 41073   StoreEc: 0x3F2    
    Lid: 48243 
    Lid: 50033   StoreEc: 0x3F2    
    Lid: 1494    —- Remote Context Beg —-
    Lid: 1238    Remote Context Overflow
    Lid: 49213   StoreEc: 0x8004010F
    Lid: 48573 
    Lid: 64957   StoreEc: 0x8004010F
    Lid: 56253 
    Lid: 65085   StoreEc: 0x8004010F
    Lid: 40381 
    Lid: 56765   StoreEc: 0x8004010F
    Lid: 31229   Error: 0×0
    Lid: 19149   Error: 0×0
    Lid: 24509   Error: 0×0
    Lid: 1219    StoreEc: 0x8004010F
    Lid: 3225    StoreEc: 0x8004010F
    Lid: 60049   StoreEc: 0x8004010F
    Lid: 49469 
    Lid: 65341   StoreEc: 0x8004010F
    Lid: 56125 
    Lid: 47933   StoreEc: 0x8004010F
    Lid: 32829 
    Lid: 49213   StoreEc: 0x8004010F
    Lid: 48573 
    Lid: 64957   StoreEc: 0x8004010F
    Lid: 31229   Error: 0×0
    Lid: 19149   Error: 0×0
    Lid: 24509   Error: 0×0
    Lid: 1219    StoreEc: 0x8004010F
    Lid: 24041 
    Lid: 13488   StoreEc: 0x3F2    
    Lid: 28780 
    Lid: 20076   StoreEc: 0x3F2    
    Lid: 57713   StoreEc: 0x3F2    
    Lid: 49009   StoreEc: 0x3F2    
    Lid: 1750    —- Remote Context End —-
    Lid: 52465   StoreEc: 0x3F2    
    Lid: 60065 
    Lid: 33777   StoreEc: 0x3F2    
    Lid: 59805 
    Lid: 52209   StoreEc: 0x3F2    
    Lid: 19778 
    Lid: 27970   StoreEc: 0x3F2    
    Lid: 17730 
    Lid: 25922   StoreEc: 0x3F2    

Exchange Management Shell command attempted:
‘wardvissers.local/wardvissers/wardtest2′ | New-MoveRequest -TargetDatabase ‘MailStore II’

Elapsed Time: 00:00:01

Solution:

I backup the AD with Windows Backup for sure.

Then I suspend and dismounted every mailbox database.

I opened ADSIEDIT.MSC to check the value of HomeMDB and homeMTA:

Go to:
CN=Configuration->CN=Services->CN=Microsoft Exchange->CN=wardvissers->CN=Administrative Groups->CN=Exchange Administrative Group (FYDIBOHF23SPDLT)->CN=Servers->CN=DAGEK10-01->CN=Microsoft System Attendant

The value by my mailbox server looks a bid strange:
HomeMDB: CN=InformationStore,CN=DAGEK10-02,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=wardvissers,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=wardvissers,DC=local

HomeMTA: CN=Microsoft MTA,CN=DAGEK10-01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=wardvissers,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=wardvissers,DC=local

Clear the Value bij HomeMDB & HomeMTA like the picture below.

Important:
Clear the value by every mailbox server if you have a dag cluster

Restarted the Microsoft Exchange System Attendant Service on every mailbox server.

Mounted & Resuming the mailbox database. Now the users could login again in OWA .

Well, let us first list the directories that are used in the Exchange web service:

EWS is used for OOF, Scheduling assistance and free+busy Lookup.
OAB provides offline address book download services for client.
Autodiscover is used to provide users with autodiscover service.
EAS provides ActiveSync services to Windows Mobile based devices.
OWA provides outlook web access for users.
ECP provides Exchange control panel feature for Exchange 2010 users only.

Issues that might be resolved using the troubleshooting steps here:

You cannot set the OOF using outlook client, you receive the server not available error.
You cannot view free/busy information for other users.
You cannot use scheduling assistance, also you might receive not free/busy information data retrieved.
You cannot download Offline Address book errors.
You cannot use autodiscover externally.
Certificate mismatch error in autodiscover, users prompted to trust certificate in outlook 2007/2010.

First let us start by settings the right virtual directory configuration required for Exchange 2010 to work correctly:
Configure External and Internal URLs for OWS, ref: http://technet.microsoft.com/en-us/library/bb310763.aspx

You have to configure the internal URL to be the server name. In case you have multiple cas/hub servers configured in a NLB then can use the nlb cluster name for the internal url. 
External URL will be the URL used by users to access webmail e.g. https://webmail.wardvissers.nl/owa 

Configure the autodiscover internal URL, ref: http://technet.microsoft.com/en-us/library/bb201695.aspx

You will use the powershell cmdlet : Set-ClientAccessServer –Identity <CAS Server Name> -AutoDiscoverServiceInternalUri: <Internal URL>, this FQDN must match the URL included in the certificate. If you have NLB cluster then you put the internal name here like nlbek10.wardvissers.local

If you cannot use autodiscover.wardvissers.nl internally (you have a domain name of domain.local and you must use it), you will get a certificate miss match error, you will have to include the internal name in the SAN certificate if you purchase an external SAN certificate. 

You cannot set autodiscover external URL since outlook will try to access https://autodiscover.wardvissers.nl/autodiscover/autodiscover.xml, this behavior is by design and cannot be changed.

Best Practice: Use SAN Certificates

Depending on how you configure the service names in your Exchange deployment, your Exchange server may require a certificate that can represent multiple domain names. Although a wildcard certificate, such as one for *.wardvissers.nl, can resolve this problem, many customers are uncomfortable with the security implications of maintaining a certificate that can be used for any sub-domain. A more secure alternative is to list each of the required domains as SANs in the certificate. By default, this approach is used when certificate requests are generated by Exchange.

Best Practice: Use the Exchange Certificate Wizard to Request Certificates

There are many services in Exchange that use certificates. A common error when requesting certificates is to make the request without including the correct set of service names. The certificate request wizard in the Exchange Management Console will help you include the correct list of names in the certificate request. The wizard lets you specify which services the certificate has to work with and, based on the services selected, includes the names that you must have in the certificate so that it can be used with those services. Run the certificate wizard when you’ve deployed your initial set of Exchange 2010 servers and determined which host names to use for the different services for your deployment.

Which Names you must include when you use a third party SAN certificate, ref http://technet.microsoft.com/en-us/library/dd351044.aspx:
External:
webmail.wardvissers.nl
autodiscover.wardvissers.nl
legacy.wardvissers.nl (If you migrating from 2003 to 2010)
Internal:
autodiscover.wardvissers.local
legacy.wardvissers.local
nlbek10.wardvissers.local(Internal NLB CAS/HUB Cluster)
casarray.wardvissers.local(I use this address for the casarray. It has the same ip as the nlbek10)

The Management console is there in to flavors x86 and x64.

The Immidio Flex Profiles Advanced Edition.msi that you need later works both fine on x86 and x64 machines.

Start Immidio FlexProfile Kit


Best Practice is that the ini are placed on a domain controller because If one domain controller fails you have no problems with your flex profile kit.

Import the ini files that you will find in the package
I have al ready some ini files (Word 2007, Outlook 2007, Excel 2007) that i used with a older version of flex profile kit.

Create on a File Server an application install folder. I named it Immidio Flex profiles
Copy the Immidio Flex Profiles Advanced Edition.msi to that folder and the following script.

flexprofilesinstall.cmd

REM Voor Immidio FlexProfiles.
IF EXIST "C:\Program Files\Immidio\Flex Profiles\flexengine.exe" GOTO END
msiexec.exe /i "\\ward-dc01\install\Immidio Flexprofiles\Immidio Flex Profiles Advanced Edition.msi" /qb! LICENSEFILE="\\ward-dc01\Install\Immidio Flexprofiles\wardvissers.lic" /l* c:\InstallFlex.log

:END

Create A New GPO on the computers where you want to install Immidio Flexprofile kit. I named Install Immidio Flexprofiles. Asssign the  flexprofilesinstall.cmd als a startup script. Set the maximum wait time on 3600.
 

Afther that i created a new policy for my domain users witch a named Immidio FlexProfiles Users

Add the Immidio Flex Profiles.adm to the new created GPO Immidio FlexProfiles Users
 
I did some settings where to find the ini files and where to save the settings.

Now you have a working roaming profile based on Immidio Flexprofiles. It’s a great tool a im loving it.

It’s works great when you migrate from XP to Windows 7

1. Click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.  
2. Right-click the default Web site, point to New, and then click Virtual Directory.
3. In the Virtual Directory Creation wizard, type IISADMPWD in the Alias box, and then click Next.
    
4. In the Directory box, type c:\windows\system32\inetsrv\iisadmpwd or the location where your hard disk is your default hard disk, and then click Next.
   
5. Verify that only the Read and Run script check boxes are selected, such as the ASP check box, click Next, and then click Finish.
    
6. Verify that the IISADMPWD virtual directory has only basic authentication is set
   
7. If you use Windows 2003/IIS 6.0, verify that the application pool is set to MSExchangeOWAAppPool
    
8. Register the IISpwchg.dll file in the Iisadmpwd directory:
   Click Start, and then click Run.
   In the Open box, type the following, and then press ENTER:
   regsvr32 c:\windows\system32\inetsrv\iisadmpwd\iispwchg.dll
9. Configure the PasswordChangeFlags property in the metabase to make sure that the Password Change functionality is enabled:
   Click Start, and then click Run.
   In the Open box, type cmd, and then press ENTER.
   Locate the C:\Inetpub\Adminscripts directory.
   Type the following command, and then press ENTER:
   cscript.exe adsutil.vbs set w3svc/passwordchangeflags 1

   0: This is the default value. This value indicates that you must use a Secure Sockets Layer (SSL) connection when you change the password.
   1: This value permits password changes on non-secure ports. This value is useful if SSL is not enabled.
   2: This value disables the Password Change functionality.
   4: This value disables the advance notification of password expiration.

10. Do not forget to enable Active Server Pages.
     
    Source http://support.microsoft.com/kb/297121

Windows Server 2008 R2 Support

Exchange Server 2007 SP3 supports all Exchange 2007 roles on the Windows Server 2008 R2 operating system.

Windows 7 Support

Exchange 2007 SP3 supports the installation of the Exchange 2007 management tools on a computer that is running Windows 7. Additionally, Exchange 2007 SP3 provides support for the installation of the Exchange 2007 Management Tools together with the Exchange Server 2010 Management Tools on the same Windows 7-based computer.

Improved Password Reset Functionality

Exchange 2007 SP3 introduces password reset functionality for Internet Information Services (IIS) 7.

To enable the password reset feature

1. Log on to the Exchange server that is running the CAS role by using an account that has local administrator rights.

2. Start Registry Editor, and then locate the following registry subkey:

   HLKM\SYSTEM\CurrentControlSet\Services\MSExchange OWA

3. Create the following DWORD value if it does not already exist:

   Value name: ChangeExpiredPasswordEnabledValue type: REG_DWORDValue data: 1

4. Exit Registry Editor.

 Updated Search Functionality

Exchange 2007 SP3 includes updates to the Exchange Search (MSSearch) component. MSSearch provides support for creating full text indexes for Exchange stores. Exchange 2007 SP3 updates the MSSearch binary files to MSSearch 3.1.

Schema Changes

Exchange 2007 SP3 includes Active Directory schema changes for certain Unified Messaging (UM) mailbox attributes. For more information, see Active Directory Schema Changes (SP3).

Support for Right-to-Left Disclaimer Text

Exchange 2007 SP3 includes support for Right-to-Left text in e-mail message disclaimers in a right-to-left language, such as Arabic. In earlier versions of Exchange, when you use a transport rule to create a disclaimer in a right-to-left language on an Exchange 2007 Hub Transport server, the text appears incorrectly when you view it from Outlook 2007.

Exchange 2007 SP3 adds functionality to the transport rule setting to fully support right-to-left text in disclaimers.

Download here SP3 for Exchange 2007

Office is not activated

Determining Which Activation Method Office is Using – KMS or MAK

Click the start menu and enter cmd /k cscript “%programfiles%\Microsoft Office\Office14\ospp.vbs” /dstatus in the search box.

If running 32 bit Office 2010 on 64 bit Windows, %programfiles% above should be replaced with %programfiles(x86)%.

Not Activated

Checking if a DNS Domain is Configured for KMS Auto-Discovery

To check if a DNS domain is configured for KMS auto-discovery, check that a SRV record exists.

nslookup -type=srv _vlmcs._tcp.wardvissers.nl

If a SRV record exists for the domain, the DNS server will detail the SRV record.

C:\>nslookup -type=srv _vlmcs._tcp

Server:  ward-dc02.wardvissers.local

Address:  192.168.150.6

Non-authoritative answer:

_vlmcs._tcp.wardvissers.local SRV service location:

          priority       = 0

          weight         = 0

          port           = 1688

          svr hostname   = ward-dc2.wardvissers.local

If no SRV record exists for the domain, the DNS server will return an error

Verifying that a Windows Computer can Communicate with the KMS Activation Server

KMS activation requires that the machine to be activated has TCP port 1688 open for outbound communication to the activation server.

Verifying that outbound TCP port 1688 is open to the KMS server

1. Download and install the utility portqry.exe from Microsoft. It is a command line utility from Microsoft that reports the port status of a remote host.
2. From a command prompt, run the command:

portqry.exe -n ward-dc02.wardvissers.local -p tcp -e 1688

The command will return “TCP port 1688 (unknown service): LISTENING” if the computer is able to communicate with the KMS server.

If the command returns “TCP port 1688 (unknown service): FILTERED” then the computer is unable to communicate with the KMS server

Manually Specifying the KMS Activation Server

1. Type cmd in the search bar to locate the command window..
2. At the command prompt, type cd\Program Files\Microsoft Office\Office14.

If running 32 bit Office 2010 on 64 bit Windows, Program Files above should be replaced with Program Files (x86).
Run the command cscript ospp.vbs /sethst:ward-dc02.wardvissers.local to manually specify the KMS activation server.

Run the command cscript ospp.vbs /act to activate Office with the KMS server.

Launch Microsoft Outlook 2010 agein
Click to the File tab. Click Help.

Office is activated

Microsoft Download Center Link is here and direct downloadable exe file link is available below.

File Name: Exchange2010-SP1-Beta-x64.exe
Version: 14.01.0180.002
Date Published: 6/5/2010
Language: English
Download Size: 532.5 MB

You need two or more Exchange 2010 servers (each with two NICs) with the CAS role installed have been deployed, you are ready to start configuring NLB to provide high availability and load balancing.  First, you must allocate a dedicated private IP address and create an associated A record in DNS for the NLB cluster. 

This IP address and name are what clients will connect to and against which the ClientAccessArray will be created.  In this blog post, I will use 192.168.150.95 and casarray.hyper-v.local
To simplify the management of your NLB cluster members, I recommend that you name each NIC’s network connection so that it is easy to understand what function the NIC serves.  For example, as depicted below, I have named the connections “LAN” (used for communication with clients and servers on the network) and “NLB” (used for internal NLB heartbeat).  This process should be repeated on all NLB cluster members.

IP configuration:
Server 1:
LAN:
IP: 192.168.150.90
Subnetmask: 255.255.255.0
Gateway: 192.168.150.254
DNS: 192.168.150.1

Server 2:
LAN:
IP: 192.168.150.91
Subnetmask: 255.255.255.0
Gateway: 192.168.150.254
DNS: 192.168.150.1

Configuring NLB – First Member

On each NLB cluster member, NLB must be installed.  With Windows 2008 R2, this can be completed simply by running the command “ServerManagerCmd -i NLB” via a command prompt.  Once NLB has been installed, launch the Network Load Balancing Manager to continue the configuration process.

To create your new cluster, you can right-click Network Load Balancing Clusters or simply click Cluster, New.  In the New Cluster wizard, enter the name of the first server in the NLB cluster (for example, CHEK10-01) and click Connect.  This will display the available NICs on the server, at which point the NLB NIC should be chosen before clicking Next.

Since this is the first member of the NLB cluster, you can leave the all of the Host Parameters at their default values, as depicted below.  Please note that the Priority value should be configured as 1 for the first member.

Next we must configure the IP address and subnet mask of the NLB cluster, which is the IP address for which we created a DNS A record at the very beginning of this process.  In this example, this would be 192.168.150.95 and 255.255.255.0, respectively.

For the Cluster Parameters, we want to enter the FQDN of the DNS A record we created at the very beginning of this process (casarray.hyper-v.local).  In addition, Unicast should be selected as the desired clustered operation mode.

I lieve the Port Rules how they are and end with Finish

Let the NLB cluster converge with its first member and you should eventually see the cluster report success.

Now you can proceed with adding your second cluster member.

Configuring NLB – Second/Subsequent Member

After the configuration of the NLB cluster itself and the first NLB cluster member has been completed, you are ready to add additional members.  Provided that NLB has been installed, you can simply right-click on your NLB cluster in the Network Load Balancing Manager and click Add Host To Cluster.

Enter the name of the second NLB cluster member, for example CHEK10-02, and click Connect.  Be sure to choose the NLB LAN NIC and click Next.

On the Host Parameters screen, ensure that the Priority is set to 2 (or as appropriate, depending on how many cluster members you have) and click Next.

Confirm that your port rules are accurate and, if they are, click Finish to add your second NLB cluster member.

Let the NLB cluster converge with the new member and, eventually, it should report success.

At this point, you have an NLB cluster with two members!

Next configure CASARRAY.

Solution 1:

1. Close Outlook 2007
2. Start Registry Editor
3. In Windows 7, click Start –> RUN
4. type regedit in de box and then click OK
5. Collapse this imageExpand this image
6. HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\AutoDiscover
7. Click the Edit menu, point to New, and then click String Value.
8. Type RedirectServers, and then press ENTER
9. Right-click RedirectServers, and then click Modify.
10. In the Value data box, type a semicolon delimited list of the HTTPS servers to which AutoDiscover can be redirected without prompting for confirmation from the user, and then click OK.
For example, you want to allow for the following list of servers:
  – https://wardvissers.nl
  – https://wardvissers.local
11.Type the following in the Value data box: wardvissers.local;wardvissers.nl
12. On the File menu, click Exit to exit Registry Editor

Solution 2:
Setting the registry key with group policy preferences.

I highlighted the things with I like from the coming update. It’s a whole list but i thing with this update is Exchange 2010 SP1 the best version ever!!!

A list of al new things in Exchange 2010 SP1:

Archiving:
- Personal Archive to a different mailbox database from their primary mailbox
- You can import historical e-mail data from .PST files, directly into Exchange
- delegate access to a user’s Personal Archive
- SP1 updates the Exchange Management Console with new tools to create Retention Policy Tags
- support access to a user’s Personal Archive with Outlook 2007 Coming with A update

Outlook Web App
- Delete, mark as read, and categorize operations running asynchronously, these actions feel instantaneous to the user
- Attaching a very large file, will not block the rest of the OWA experience
- Sharing calendars to anonymous viewers via the web if you enable this.
- OWA themes back
- Reading pane can be placed on the bottom or the right side

Mobile:
- Support for send-as
- Support for notifying the user if their device has been placed on block or quarantine by their admin
- Full implementation of conversation view
- To sync only unique parts of messages.
- Setting up mobile device to access mail via POP/IMAP/SMTP, information is available in OWA.

New Management UI
- Create/configure Retention Tags + Retention Policies in EMC
- Configure Transport Rules in ECP
- Configure Journal Rules in ECP
- Configure MailTips in ECP
- Provision and configure the Personal Archive in ECP
- Configure Litigation Hold in ECP & EMC
- Configure Allow/Block/Quarantine mobile device policies in ECP
- RBAC role management in ECP
- Configure Database Availability Group (DAG) IP Addresses and Alternate Witness Server in EMC
- Recursive public folder settings management (including permissions) in EMC

Read the whole article at HERE.

Solution:
Go to Organization Configuration in EMC. Right click it in EMC and select Modify Configuration Domain Controller. Point it to your DC hosting the PDC

After that restart the Microsoft Exchange System Attendant services on the mailbox server.

The Microsoft Exchange System Attendant Service does the following thing:

Forwards directory lookups to a global catalog server for legacy Outlook clients, generates e-mail addresses and offline address books, updates free/busy information for legacy clients, and maintains permissions and group memberships for the server. If this service is disabled, any services that explicitly depend on it will fail to start.

Het overzicht wat er allemaal gefixt is:
"451 4.4.0 DNS Query Failed" status message in an Exchange Server 2007 Edge Transport server

Later updates do not match a calendar item that an Exchange Server 2007 user updates by using Exchange ActiveSync on a mobile device

You receive an "0x800423f0" error message when you perform system state backups on the passive node of Windows Server 2008-based Exchange Server 2007 CCR clusters

An external recipient misses the last occurrence of a recurring meeting request or a recurring appointment that is sent from an Exchange Server 2007 user

The Edgetransport.exe process crash when it process meeting requests in Exchange Server 2007

The subject of a confirmation message is garbled for certain languages when a remote device wipe operation is performed in Exchange Server 2007

The sender address of a forwarded meeting request does not include "on behalf of" as expected in an Exchange Server 2003 organization and an Exchange Server 2007 organization mixed environment

A SSL certificate validation error is generated on an Exchange Server 2007 server when you run any test commands after you run the Test-SystemHealth command

A mailbox that was moved from an Exchange Server 2007 server to an Exchange Server 2010 server cannot be accessed by using Outlook

The Microsoft Exchange Information Store service stops responding on an Exchange Server 2007 server

The synchronization and the reconciliation between Microsoft Office Outlook and a BlackBerry mobile device fails when a mailbox is moved around between two Exchange Server 2007

The Microsoft Exchange Information Store service crashes on a Microsoft Exchange Server 2007 server when a user tries to access a specific calendar item

Read items are marked incorrectly as unread items in an Exchange Server 2007 public folder

A delegate cannot save three settings of Resource Settings for an Exchange Server 2007 resource mailbox in OWA

You receive an error message when you use ExBPA to schedule a scan on an Exchange Server 2007 SP2 server

The store.exe process hangs on an Exchange Server 2007 server

Downloaden doe je HIER

De Onderwerpen:

Exchange
- High Availability in Exchange 2007
- Message Hygiene in Exchange Server 200731
- Using Exchange 2007 for Resource Booking
- Controlling Email Messages using Exchange’s Transport Rules
- Exchange 2007 Mailbox Server Clustering
- Top Tips for Exchange Admins
- Exchange Database Technologies
- Message Classifications in Exchange 2007
- Deploying Exchange 2007 on Windows Server 2008
- Exchange Server Log File Replay
- Configuring Exchange Server 2007 to Support Information Rights Management
- Reporting on Mobile Device Activity Using Exchange 2007 ActiveSync Logs
- Online Exchange Backups
- Optimizing Exchange Server 2007
- Exchange: Recovery Storage Groups
- Exchange E-mail Addresses and the Outlook Address Cache
- Upgrading to Exchange Server 2007
- Goodbye Exchange ExMerge, Hello Export-Mailbox
- Determining MS Exchange Disk Performance
- Upgrading to Exchange Server 2007: Part 2
- Message Tracking in Exchange 2007
- Third Party High Availability and Disaster Recovery Tools for Microsoft Exchange Server
- Exchange Server 2010 – The First Public Beta Version
- Emulating the Exchange 2003 RUS for Out-of-Band Mailbox Provisioning in Exchange 2007
- Using Exchange 2007 Transport Rules to Protect the First Entry in the Address Book
- Cluster Continuous Replication Network Design
- Building an Exchange Server 2007 environment
- An Introduction to Messaging Records Management
- Installing Hyper-V and Beyond
- Restricting Outlook Client Versions in Exchange 2007
- Using Twitter and PowerShell to Find Technical Information and Join a Community
- Update: Exchange Server 2010 Release Candidate
- Exchange backups on Windows Server 2008
- Moving to Office Communications Server 2007 R2
- Monitoring and Scheduling Exchange 2007 Database Online Maintenance
- Exchange 2010 High Availability
- Implementing Cluster Replication – Part 1
- The Active Directory Recycle Bin in Windows Server 2008 R2
- Using Group Policy to Restrict the use of PST Files
- Introduction to Exchange Server 2010
- The Ego and the System Administrator
- Implementing Windows Server 2008 File System Quotas
- Implementing Cluster Continuous Replication, Part 2
- Active Directory Management with PowerShell in Windows Server 2008 R2
- Upgrade Exchange 2003 to Exchange 2010
- Customizing the Outlook Address Book

General Articles
- A SysAdmin’s Guide to Change Management
- A SysAdmin’s Guide to Users
- Change Management – What It Is and Why You Need It
- Manage Stress Before it Kills You
- Hiring System Administrators
- Increase Your Value as a Professional in the Technical Industry
- The Art of Dealing with People

Virtualization
- Virtual Exchange Servers
- Virtualizing Exchange: points for discussion
- Build Your Own Virtualized Test Lab
- A Beginner’s Guide to Virtualizing Exchange Server – Part 1
- A Beginner’s Guide to Virtualizing Exchange Server – Part 2
- Windows Server Virtualisation: Hyper-V, an Introduction
- Increasing the Availability of Virtualized Applications and Services
- Microsoft Hyper-V Networking and Configuration – Part 1

Unified Messaging
- An Introduction to Unified Messaging
- Moving to Office Communications Server 2007 R2

PowerShell
- Managing Exchange 2007 Mailbox Quotas with Windows PowerShell
- So You Thought PowerShell Was Only For Exchange 2007

Downloaden klik op het boek

De error zit er als volgt uit:

Oplossing 1:

Op de Exchange 2007 server moet je in de lokale administrators groeps de ad groep Exchange Trusted Subsystem toevoegen. Deze vind je onder Microsoft Exchange Security Groups. 

Om naar buiten geen waarschuwing te krijgen dat het SSL certificaat niet vertrouwd wordt er normaal gesproken gewerkt met commerciële vertrouwd SSL certificaat.

Voor de Exchange 2007 & Exchange 2010 worden de volgende volgende URL’s gebruikt:

webmail.wardvissers.nl (MX records,OWA,IMAP/POP3/SMTP en Exchange ActiveSync – plus het is the reverse DNS record voor je statische IP adres)
autodiscover.wardvissers.nl(Voor Autodiscovery)
legacy.wardvissers.nl (Mocht je van Exchange 2003 vanaf komen)
e2k10.wardvissers.local (De Exchange Server interne naam)
e2k10 (De Exchange server NETBIOS naam).

“webmail.wardvissers.nl” is de eerste naam die verschijnt zodra een gebruiker op dit certificaat klikt. En zorgt er voor dat alles extern connect naar de server zonder support voor SAN/UC certificaten.

(SAN is Subject Alternative Name, UC is Unified Communications –Zijn het zelfde).

Het handige is dat dat je een SAN certificaat aanvraag. Met de eerder genoemde url’s.

Stel je hebt maar een certificaat genaamd webmail.wardvissers.nl dan kun je toch alles gebruiken maar daar is een truk voor nodig.

Vereisten:
- Outlook 2007 SP1
- SRV Record ondersteuning bij uw Externe DNS host. Mocht je dat niet hebben dan kun je twee
dingen doen:
1. Andere Domain aanbieder die wel SRV records ondersteund.
2. San Certificaat.
- Commerciële SSL-certificaat
- Split DNS Setup bijvoorbeeld (.local intern & .nl Extern)

DNS configuratie van Autodiscover

1. Verwijder alle host A records die verwijzen naar autodiscover.domain.local

2. Maak een nieuw Service Location (SRV Record aan). Vul de gegevens in zoals afgebeeld op de plaatjes.

3. Webmail.wardvissers.nl moet verwijzen naar de CAS Exchange 2010 server.

Exchange URL aanpassingen door voeren:

1. Get-ExchangeCertificate (Lijst met alle Exchange Certificaten)

2. Enable-exchangecertificate -services IMAP, POP, IIS, SMTP -Thumbprint 02B3E404EF76A0A839365C7489B59B1D1278EDCD (Certificaat Nummer)

3. Zet de volgende URL’s goed:
Set-ClientAccessServer -Identity e2k10 -AutoDiscoverServiceInternalUri https://webmail.wardvissers.nl/Autodiscover/Autodiscover.xml

Set-WebServicesVirtualDirectory -Identity “e2k10\EWS (Default Web Site)” -InternalUrl https://webmail.wardvissers.nl/ews/exchange.asmx

Set-OABVirtualDirectory -Identity “e2k10\oab (Default Web Site)” -InternalUrl https://webmail.wardvissers.nl/oab

Enable-OutlookAnywhere -Server e2k10 -ExternalHostname “webmail.wardvissers.nl” -ClientAuthenticationMethod “Basic”-SSLOffloading:$False

Set-ActiveSyncVirtualDirectory -Identity “e2k10\Microsoft-Server-ActiveSync (Default Web Site)” -ExternalURL https://webmail.wardvissers.nl/Microsoft-Server-Activesync

Set-ECPVirtualDirectory –Identity e2k10\ECP (default web site) -ExternalURL https://webmail.wardvissers.nl/ECP

4. Nu werkt verwijst intern en extern naar het zelfde adres.

5. Er zijn nog wel twee dingen waar je op moet letten:
- Het kan zijn dat je een voor IE een url moeten toevoegend dat lokaal blijft resolven als je via
een proxy server naar buiten toe gaat.
- Op elke CAS/HUB server moet Exchange URL’s toegepast worden naar het NLB CAS Load
Balacing

A Computer that is running Microsoft Exchange Server 2007 that has the Client Access Server (CAS) role installed becomes slow when a user tries to open a folder that contains many items

An appointment is displayed incorrectly as an all-day event if you use a mobile device to synchronize the calendar in Exchange Server 2007

Exchange Server 2007 users intermittently cannot access an Exchange Server 2003 user’s Free/Busy information in Office Outlook 2007

The Microsoft Exchange Server 2007 log or database experiences abnormal growth

When a user sends e-mail messages to a remote domain, some e-mail messages are queued on an Exchange Server 2007 Hub Transport server or Edge server

A new accepted domain that is added does not work in an Exchange Server 2007 organization

EdgeTransport.exe process crashes intermittently on an Exchange Server 2007 server

You receive an NDR you try to send messages through your Microsoft Exchange Server 2007 account

You cannot log on to your mailbox and you receive an error in an Exchange server 2003 and Exchange Server 2007 coexist environment

Event 2104 and event 2147 are continuously logged in an Exchange Server 2007 Cluster Continuous Replication (CCR) environment

Messages that have duplicate message IDs are deleted when they are archived to an Exchange 2007 mailbox

The free/busy information of an Exchange Server 2007 user is not displayed

You receive the warning "Failed to update recipient" when you run the Update-addresslist cmdlet in Exchange Management Shell on Exchange Server 2007

Windows Server 2008 VSS backup plug-in fails to backup Exchange 2007 Service Pack 2 databases that reside on a volume mount point

De complete lijst met wat er gefixt is vind je HIER en downloaden doe je HIER