Posts Tagged ‘update’

Hey Folks,

yesterday, the Exchange Team announced that  SP1 for EXCHANGE 2013 was released:

Exchange Server 2013 Service Pack 1 (SP1) is now available for download! Please make sure to read the release notesbefore installing SP1. The final build number for Exchange Server 2013 SP1 is 15.00.0847.032.

SP1 has already been deployed to thousands of production mailboxes in customer environments via the Exchange Server Technology Adoption Program (TAP). In addition to including fixes, SP1 provides enhancements to improve the Exchange 2013 experience. These include enhancements in security and compliance, architecture and administration, and user experiences. These key enhancements are introduced below.

Note: Some of the documentation referenced may not be fully available at the time of publishing of this post.

Security and Compliance

SP1 provides enhancements improving security and compliance capabilities in Exchange Server 2013. This includes improvements in the Data Loss Prevention (DLP) feature and the return of S/MIME encryption for Outlook Web App users.

  • DLP Policy Tips in Outlook Web App – DLP Policy Tips are now enabled for Outlook Web App (OWA) and OWA for Devices. These are the same Policy Tips available in Outlook 2013. DLP Policy Tips appear when a user attempts to send a message containing sensitive data that matches a DLP policy. Learn more about DLP Policy Tips.
  • DLP Document Fingerprinting – DLP policies already allow you to detect sensitive information such as financial or personal data. DLP Document Fingerprinting expands this capability to detect forms used in your organization. For example, you can create a document fingerprint based on your organization’s patent request form to identify when users are sending that form, and then use DLP actions to properly control dissemination of the content. Learn more about DLP Document Fingerprinting.
  • DLP sensitive information types for new regions – SP1 provides an expanded set of standard DLP sensitive information types covering an increased set of regions. SP1 adds region support for Poland, Finland and Taiwan. Learn more about the DLP sensitive information types available.
  • S/MIME support for OWA – SP1 also reintroduces the S/MIME feature in OWA, enabling OWA users to send and receive signed and encrypted email. Signed messages allow the recipient to verify that the message came from the specified sender and contains the only the content from the sender. This capability is supported when using OWA with Internet Explorer 9 or later. Learn more about S/MIME in Exchange 2013.

Architecture & Administration

These improvements help Exchange meet our customer requirements and stay in step with the latest platforms.

  • Windows Server 2012 R2 support – Exchange 2013 SP1 adds Windows Server 2012 R2 as a supported operating system and Active Directory environment for both domain and forest functional levels. For the complete configuration support information refer to the Exchange Server Supportability Matrix. This matrix includes details regarding Windows Server 2012 R2 support information about earlier versions of Exchange.
  • Exchange Admin Center Cmdlet Logging – The Exchange 2010 Management Console includes PowerShell cmdlet logging functionality. Listening to your feedback, we’re happy to announce that this functionality is now included in the Exchange Admin Center (EAC). The logging feature enables you to capture and review the recent (up to 500) commands executed in the EAC user interface while the logging window is open. Logging is invoked from the EAC help menu and continues logging while the logging window remains open.

image

image

  • ADFS for OWA – Also new for Outlook Web App in SP1 is claims-based authentication for organizations using Active Directory Federation Services. Learn more about the scenario.
  • Edge Transport server role – SP1 also reintroduces the Edge Transport server role. If you have deployed Exchange 2013 with a supported legacy Exchange Edge Transport role, you don’t need to upgrade. That configuration is still supported. But we do recommend that future deployments use the Exchange 2013 Edge Transport role. Learn more about Edge Transport in Exchange 2013.
  • New communication method for Exchange and Outlook – SP1 introduces a new communication method for Exchange Server and Microsoft Outlook called MAPI over HTTP(MAPI/HTTP). This communication method simplifies connectivity troubleshooting and improves the user connection experience with resuming from hibernate or switching networks. MAPI/HTTP is disabled by default, allowing you to decide when to enable it for your organization. MAPI/HTTP can be used in place of RPC/HTTP (Outlook Anywhere) for your Outlook 2013 SP1 clients while Outlook 2013 RTM and older clients continue to use RPC/HTTP. Learn more about deploying MAPI/HTTP.
  • DAGs without Cluster Administrative Access PointsWindows Server 2012 R2 introduces failover clusters that can operate without an administrative access point: no IP addresses or IP address resource, no network name resource, and no cluster name object. SP1 enables you to create a DAG without an administrative access point on Windows Server 2012 R2 from EAC or PowerShell. This is an optional DAG configuration for SP1 and requires Windows Server 2012 R2. DAGs with administrative access points continue to be supported. Learn more about creating a DAG without an administrative access point here and here.
  • SSL offloading – SP1 now supports SSL offloading, allowing you to terminate incoming SSL connections in front of your CAS servers and move the SSL workload (encryption & decryption tasks) to a load balancer device. Learn how to configure SSL offloading in Exchange 2013.

User Experience

We know the user experience is crucial to running a great messaging platform. SP1 provides continued enhancements to help your users work smarter.

  • Enhanced text editor for OWA – OWA now uses the same rich text editor as SharePoint, thereby improving the user experience, and enabling several new formatting and composition capabilities that you expect from modern Web application – more pasting options, rich previews to linked content, and the ability to create and modify tables.

image

  • Apps for Office in Compose – Mail apps are now available for use during the creation of new mail messages. This allows developers to build and users to leverage apps that can help them while they are composing mails. The compose apps leverage the Apps for Office platform and can be added via the existing Office store or corporate catalogs. Learn more about Apps for Office.

image

Upgrading to SP1/Deploying SP1

As with all cumulative updates (CUs), SP1 is a full build of Exchange, and the deployment of SP1 is just like the deployment of a cumulative update.

Active Directory Preparation

Prior to or concurrent with upgrading or deploying SP1 onto a server, you must update Active Directory. These are the required actions to perform prior to installing SP1 on a server.

1. Exchange 2013 SP1 includes schema changes. Therefore, you will need to execute the following command to apply the schema changes.

setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

2. Exchange 2013 SP1 includes enterprise Active Directory changes (e.g., RBAC roles have been updated to support new cmdlets and/or properties). Therefore, you will need to execute the following command.

setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms

Server Deployment

Once the above preparatory steps are completed, you can install SP1 on your servers. Of course, as always, if you don’t separately perform the above steps, they will be performed by Setup when you install your first Exchange 2013 SP1 server. If this is your first Exchange 2013 server deployment, you will need to deploy both Client Access Server and Mailbox Server roles in your organization.

If you already deployed Exchange 2013 RTM code and want to upgrade to SP1, you will run the following command from a command line.

setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms

Alternatively you can start the installation through the GUI installer.

Hybrid deployments and EOA

Customers in hybrid deployments where Exchange is deployed on-premises and in the cloud, or who are using Exchange Online Archiving (EOA) with their on-premises Exchange deployment are required to maintain currency on Cumulative Update/Service Pack releases.

Looking Ahead

Our next update for Exchange 2013 will be released as Exchange 2013 Cumulative Update 5. This CU release will continue the Exchange Server 2013 release process.

If you want to learn more about Exchange Server 2013 SP1 and have the opportunity to ask questions to the Exchange team in person, come join us at the Microsoft Exchange Conference.

(Source: http://blogs.technet.com/b/exchange/archive/2014/02/25/exchange-server-2013-service-pack-1-available.aspx )

Cheers,

Chris

The Exchange Team is pleased to announce that in the first half of calendar year 2013 we will be releasing Exchange Server 2010 Service Pack 3 (SP3) to our customers. With SP3, the following new features and capabilities will be included:

Coexistence with Exchange 2013: Customers that want to introduce Exchange Server 2013 into their existing Exchange 2010 infrastructure will need the coexistence changes shipping in SP3.

Support for Windows Server 2012: With Service Pack 3, you will have the ability to install and deploy Exchange Server 2010 on machines running Windows Server 2012.

Customer Requested Fixes: All fixes contained within update rollups released prior to Service Pack 3 will also be contained within SP3. Details of our regular Exchange 2010 release rhythm can be found in Exchange 2010 Servicing.

In order to support these newly added features, there will be a requirement for customers to update their Active Directory schema. We are communicating the required changes ahead of the release date in order to assist our customers with planning their upgrade path ahead of time.

We hope these announcements come as welcome news to you. It is our custom to provide ongoing improvements to features, functionality and security of Exchange Server, based largely on customer feedback, and to provide continual innovation on an already great messaging product. We look forward to receiving your comments and announcing more detailed information as we continue to develop the features that will be included in SP3.

Kevin Allison
General Manager
Exchange Customer Experience

(Source:  EHLO Blog)

Hi Folks,

I just upgraded my Windows 7 installation to Windows 8 Enterprise RTM. The compatibility check failed because of Intel PRO Wireless Utility and Avira AntiVir Pro. After uninstalling the both programs the upgrade started regulary. After some reboots and 1,5 hours installing I logged in first.

Everything looked fine, all apllications started as usual. The desktop and taskbar symbols appeared as before, just the start button was missing. I installed the ClassicShell and got my start button back.

In combination with ClassicShell Windows 8 has nearly the same usability as Windows 7 + the possibilty tu use the new features and the new (formerly known as METRO) interface. So I wish you a happy upgrading and installing 🙂

Cheers,

Chris

On August 13th 2012, the Exchange CXP team released Update Rollup 4 for Exchange Server 2010 SP2 to the Download Center.

This update contains a number of customer reported and internally found issues. See KB 2706690 Description of Update Rollup 4 for Exchange Server 2010 Service Pack 2 for more details.

In particular we would like to specifically call out the following fixes which are included in this release:

Note: Some of the following KB articles may not be available at the time of publishing this post.

  • New updates for August DST – Exchange 2010 – SP2 RU4 – Display name for OWA.
  • 2685001 Retention policies do not work for the Calendar and Tasks folders in an Exchange Server 2010 SP1 environment
  • 2686540 Exchange 2010 Messages are not delivered to Journal Mailbox
  • 2701162 Granting Full Mailbox Access Does Not Allow Full Details of Free/Busy To Be Displayed
  • 2724188 Information loss due to unexpected subject modification while copying a message in Outlook
  • 2743871 Stop Forefront services in RU setup so no manual steps are required
  • 2740358: MS12-058: Vulnerability in Microsoft Exchange Server WebReady document viewing could allow remote code execution: August 14, 2012

(Source: http://blogs.technet.com/b/exchange/archive/2012/08/14/released-update-rollup-4-for-exchange-2010-service-pack-2.aspx)

Cheers,
Chris

Earlier today, the Exchange CXP team released Update Rollup 3 for Exchange Server 2010 SP2 to the Download Center.

This update contains a number of customers reported and internally found issues. See KB2685289 Description of Update Rollup 3 for Exchange Server 2010 Service Pack 2 for more details.

Note: Some of the following KB articles may not be available at the time of publishing this post.

In particular we would like to specifically call out the following fixes which are included in this release:

  • KB2689810 Meeting Requests bodies get rendered in plain text in Outlook when created via Exchange Web Services.
  • KB2674445 Need the function to check ACL consistency during moving mailbox.
  • KB2700705 RpcClientAccess crashes with SocketException when UDP push notification is enabled.
  • KB2705425 Memory Leak in UMWorkerProcess.exe.
  • KB2698976MRM Assistant doesnt process a mailbox with a contact created in other tenants.

(Source: Exchange Team Blog )

Force OAB update

Posted: March 14, 2012 in Exchange 2010
Tags: , , , , , ,

Once you are confronted with forcing an OAB update you have to concern several steps:

Exchange
First step – doing the update

  • get-addresslist | update-addresslist
  • get-globaladdresslist | update-globaladdresslist
  • get-offlineaddressbook | update-offlineaddressbook

Second step – wait a few minutes – push the update through FDS

  • get-clientaccesserver | update-filedistributionservice

Outlook

Perform a full download of the OAB.

Cheers,

Chris

Yesterday I ran into a problem which was often discussed before by my colleagues and me.

I wanted to prepare the AD schema update before installing Exchange 2010. The “setup /pad” and “setup /ps” commands ran without any errors so I started to install Exchange 2010 (SP2).

The Installation itself ran without any errors, too. After rebooting the freshly installed Exchange 2010 server I wanted to opend the EMC and the EMS – and got one of these annoying WinRM management startup failures.

So I did it as recommended by MS and used the articles provided by TechNet and EHLO Team Blog and finally used the Exchange Management Troubleshooter (EMTShooter) without any hint or solution – the EMTShooter only detected an unknown error.

I called my colleague Stephan H.  (A big thank you, Stephan, for the memory of this topic) and he put me on the right track. A virus scanner was installed and activated on the schema master. Several times he had this issue: The schema update seemed to run properly but after installing Exchange 2010 strange errors occured.

The solution was very easy. I deactivated the virus scanner on the schema master and rerun Exchange 2010’s “setup /ps”. After finishing the PrepareSchema I rebooted the Exchange 2010 server and everything worked fine. In this case the AntiVirus software blocked the “evil” remote PowerShell.

Cheers,

Chris