Skip to main content

Exchange 2007 SP1 Rollup 5 released

Rollup 5 for Exchange 2007 SP1 fixes plenty of issues:

  • 925371 (http://support.microsoft.com/kb/925371/ ) Domino users cannot find meeting request attachments that are sent from Exchange 2007 users

  • 939037 (http://support.microsoft.com/kb/939037/ ) By default, managed content settings apply to the root folder and all subfolders in an Exchange 2007 environment

  • 949722 (http://support.microsoft.com/kb/949722/ ) Event ID 800 does not include the user name of users who ran the Get-MessageTrackingLog command in an Exchange 2007 environment

  • 949893 (http://support.microsoft.com/kb/949893/ ) You cannot create a new mailbox or enable a mailbox in an Exchange Server 2007 environment on February 29, 2008

  • 949895 (http://support.microsoft.com/kb/949895/ ) Exchange Management Shell crashes (stops responding), and Event ID 1000 is logged when you perform a cross-forest migration from Exchange Server 2003 to Exchange Server 2007 S949895

  • 949901 (http://support.microsoft.com/kb/949901/ ) Exchange 2007 users cannot send e-mail messages to a mail-enabled public folder in a mixed Exchange 2003 and Exchange 2007 environment

  • 949968 (http://support.microsoft.com/kb/949968/ ) Unified Messaging does not handle the diversion header correctly in Exchange Server 2007 Service Pack 1

  • 950272 (http://support.microsoft.com/kb/950272/ ) The formatting of a plain text message is incorrect when you print the plain text message by using Outlook Web Access in an Exchange Server 2007 environment

  • 951267 (http://support.microsoft.com/kb/951267/ ) An exception occurs in Exchange Management Console when you preview AddressList in an Exchange Server 2007 environment

  • 951273 (http://support.microsoft.com/kb/951273/ ) The received date and the received time of IMAP messages are changed to the time of migration after you migrate mailboxes to an Exchange 2007 Service Pack 1-based server

  • 951505 (http://support.microsoft.com/kb/951505/ ) You may receive an error message when you run the Update-SafeList cmdlet in an Exchange 2003 and Exchange 2007 mixed environment

  • 951564 (http://support.microsoft.com/kb/951564/ ) Exchange 2007 Service Pack 1 Update Rollup 5 supports the addition of new items to context menus in Outlook Web Access 2007

  • 951710 (http://support.microsoft.com/kb/951710/ ) You receive error messages or warnings when you change an Active Directory schema so that the Company property supports more than 64 characters

  • 952097 (http://support.microsoft.com/kb/952097/ ) Event ID 12800 is logged on an Exchange 2007-based server: "Message processing failed because there is not enough available memory (8007000E-82000387)"

  • 952583 (http://support.microsoft.com/kb/952583/ ) Japanese DBCS characters are corrupt when you reply to a message or forward a message in an Exchange Server 2007 Service Pack 1 environment

  • 953619 (http://support.microsoft.com/kb/953619/ ) A public folder conflict message cannot be delivered, and event error 1016 is logged, when the public folder name contains DBCS characters in an Exchange Server 2007 Service Pack 1 environment

  • 953787 (http://support.microsoft.com/kb/953787/ ) You receive an error message when you try to move Exchange 2000 mailboxes or Exchange 2003 mailboxes from one forest to an Exchange 2007 server that is located in another forest by using the Move-Mailbox command

  • 953840 (http://support.microsoft.com/kb/953840/ ) Event ID 5000 occurs, and the IMAP4 service may crash, on a server that is running Exchange Server 2007 with Service Pack 1 when you use a third-party application to migrate POP3 and IMAP4 users

  • 954036 (http://support.microsoft.com/kb/954036/ ) Hidden folders or files are listed when you view a UNC file server by using OWA in an Exchange 2007 environment

  • 954195 (http://support.microsoft.com/kb/954195/ ) The task originator is not notified of task changes and task progress in an Exchange Server 2007 environment

  • 954197 (http://support.microsoft.com/kb/954197/ ) Exchange 2007 CAS cannot copy the OAB from the OAB share on Windows Server 2008-based Exchange 2007 CCR clusters

  • 954270 (http://support.microsoft.com/kb/954270/ ) Message class changes during conversion when a digitally signed Message Disposition Notification is received by a server that is running Exchange Server 2007 Service Pack 1

  • 954451 (http://support.microsoft.com/kb/954451/ ) An appointment item cannot be opened by a CDOEX-based application if the item is saved by Exchange Web Service together with the Culture property in Exchange Server 2007

  • 954684 (http://support.microsoft.com/kb/954684/ ) You cannot use an Outlook 2007 client to display or download an attachment when you access a message that includes an inline attachment from Exchange Server 2007

  • 954810 (http://support.microsoft.com/kb/954810/ ) An Exchange 2007 room mailbox stops processing requests after the resource booking assistant receives a delegated meeting request from an Exchange 2003 user

  • 954887 (http://support.microsoft.com/kb/954887/ ) You cannot add a Mail User or a Mail Contact to the Safe Senders list in Exchange 2007 by using OWA Client

  • 955001 (http://support.microsoft.com/kb/955001/ ) Error message when you use the IMAP protocol to send a SEARCH command that has the CHARSET argument on an Exchange 2007 server: "BAD Command Argument Error"

  • 955196 (http://support.microsoft.com/kb/955196/ ) Log files are not copied to the target server in a standby continuous replication environment in Exchange Server 2007

  • 955429 (http://support.microsoft.com/kb/955429/ ) A VSS backup application causes the Information Store service to crash repeatedly on an Exchange 2007 Service Pack 1-based server

  • 955460 (http://support.microsoft.com/kb/955460/ ) The start time and the end time of a meeting request are incorrect when a delegate uses Exchange Web Service to send the request in an Exchange 2007 environment

  • 955480 (http://support.microsoft.com/kb/955480/ ) Meeting requests from external senders are displayed as Busy instead of Tentative in an Exchange 2007 environment

  • 955599 (http://support.microsoft.com/kb/955599/ ) Event ID 10 messages fill up the Application log on an Exchange 2007 CAS server if an Exchange Server 2003 mailbox owner makes an Exchange Web Service call

  • 955619 (http://support.microsoft.com/kb/955619/ ) A user cannot access the mailbox by using a POP client or an IMAP client through Client Access Server in an Exchange 2007 environment

  • 955741 (http://support.microsoft.com/kb/955741/ ) A message stays in the Outbox, and the message is resent until it is deleted manually on Windows Mobile 6.1-based devices in an Exchange 2007 Service Pack 1 CAS proxying scenario

  • 955946 (http://support.microsoft.com/kb/955946/ ) A sender receives an NDR from the Exchange 2007 server when the sender submits a private message by using an SMTP server

  • 955989 (http://support.microsoft.com/kb/955989/ ) The SPN registration of a cluster fails, and Error event IDs 1119 and 1034 are logged in an Exchange Server 2007 Service Pack 1 environment

  • 956199 (http://support.microsoft.com/kb/956199/ ) The last character of a user’s Chinese display name is truncated in the Offline Address Book on an Exchange 2007 server

  • 956319 (http://support.microsoft.com/kb/956319/ ) The W3wp.exe process may crash on an Exchange 2007 CAS server after you use Entourage to send a message that is larger than 48 KB

  • 956573 (http://support.microsoft.com/kb/956573/ ) Event ID 1032 is not logged in the Application log when users send e-mail messages while they are logged on to Outlook Web Access as another user in Exchange 2007

  • 956582 (http://support.microsoft.com/kb/956582/ ) Exchange Server 2007 Update Rollup 3 does not update the Outlook Web Access Logon.aspx file after you modify the file

  • 956613 (http://support.microsoft.com/kb/956613/ ) The W3wp.exe process intermittently stops responding and Event ID 1000 is logged in Exchange Server 2007 Service Pack 1

  • 956709 (http://support.microsoft.com/kb/956709/ ) Some recurring meetings may be missing when you view the meetings using Outlook Web Access in Exchange Server 2007

  • 957002 (http://support.microsoft.com/kb/957002/ ) The Edgetransport.exe process may crash intermittently on a server that is running Exchange Server 2007 Service Pack 1

  • 957137 (http://support.microsoft.com/kb/957137/ ) The reseed process is unsuccessful on the CCR passive node after you restore one full backup and two or more differential backups to the CCR active node

  • 957813 (http://support.microsoft.com/kb/957813/ ) A Non-Delivery Report is generated when you try to send a high priority message that is larger than 250 KB in an Exchange Server 2007 Service Pack 1 environment

  • 957978 (http://support.microsoft.com/kb/957978/ ) The OAB generation is unsuccessful and Event IDs 9328 and 9373 are logged in the Application log in a Windows Server 2008-based Exchange 2007 Single-Copy cluster environment

  • 958855 (http://support.microsoft.com/kb/958855/ ) The Edge Transport service crashes repeatedly, and an event error 1000 is logged repeatedly on a server that is running Exchange Server 2007 Service Pack 1

  • 958856 (http://support.microsoft.com/kb/958856/ ) Event ID: 7012 occurs when you search message tracking logs on an Exchange Server 2007-based server

    •  

    Related article:

    http://support.microsoft.com/?kbid=953467

    Comments

    Post a Comment

    Popular posts from this blog

    Netscaler vs Exchange 2019 "time out during ssl handshake stage

    If you are using Citrix Netscaler as load balancer in front of Exchange 2019 server you must know this: Microsoft Exchange 2019 is secured by default and allows only TLS 1.2. Therefore default schannel settings are as follows (using IISCrypto tool from Nartac Software): While Citrix Netscaler offers following Cipher Suites: TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_RSA_WITH_DES_CBC_SHA TLS_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 TLS_DHE_DSS_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA TLS_DHE_RSA_WITH_DES_CBC_SHA TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT1024_WITH_RC2_CBC_56_MD5 TLS_DH_anon_WITH_DES_CBC_SHA TLS_DH_anon_WITH_AES_128_CBC_SHA TLS_DH_anon_WITH_AES_256_CBC_SHA TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA Now, you will fi
    1 comment
    Read more

    Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}]

     If you got this error checking the mail flow for a distribution group, it means the distribution group is closed and only internal senders can send e-mail to this group. When outside user sends e-mail to this group you get  Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}] Set Delivery for this group to internal and external users and your problem will be solved. 
    Read more

    Ports that need to be open on Firewall for Edge Transport servers

    Ports that need to be open on firewall for Edge Server subscription with Hub Server to function properly: For Inbound traffic: SMTP - TCP port 25 (from Internet) SMTP - TCP port 25 (from Edge server to Hub server on internal network) For Outbound traffic: SMTP - TCP/UDP port 25 (from Edge to Internet) SMTP - TCP/UDP port 25 (from Hub to Edge server) LDAP for EdgeSync - TCP port 50389 (from Hub to Edge server) Secure LDAP for EdgeSync - TCP port 50636 (from Hub to Edge server) Since Edge server needs to communicate with Hub server it is important that it can resolve Hub transport servers by FQDN and Hub transport servers must be able to resolve Edge servers by its FQDNs. To accomplish this you need to either open 53 (DNS) port and configure internal network adapter to use internal DNS but as a security precaution I would suggest to enter DNS records for Edge servers on local DNS manually and to fill hosts file on Edge servers with FQDNs for Hub transport servers.
    2 comments
    Read more