A few hours ago, Microsoft (finally) released Cumulative Update 1 (CU1) for Exchange 2013 RTM. Many of us have been waiting for this update as it was the last prerequisite standing in the way of upgrading to Exchange 2013 when you already had Exchange running prior. I’m pretty sure that over the course of the next few weeks, we will be seeing lots of interesting new information coming out.
For now, we’ll have to settle with Microsoft’s promise to publish the release notes + updated documentation anytime soon. As Bharat Suneja already mentioned, it’s scheduled to be release on the 3rd of April: Where to get it? First things, first. The newer bits are available from the following link: Yes, you’re not dreaming. How is that possible?
A few hours ago, Microsoft (finally) released Cumulative Update 1 (CU1) for Exchange 2013 RTM. Many of us have been waiting for this update as it was the last prerequisite standing in the way of upgrading to Exchange 2013 when you already had Exchange running prior.
Cumulative Updates are quite different from Update Rollups. They are entire new builds of the product that don’t require a prior version to be installed. Hence the size. For more information on this new “update strategy”, have a look. The CU is “huge”.
And I don’t mean that literally (although it’s literally huge as well). Next to a lot of fixes (that should’ve made it in RTM to be honest), will definitely make your life running Exchange 2013 a lot easier. Next to that, there are some things that have changed and have been added. To name a few:. Changes in some High-Availability features. There’s a schema and other AD updates in CU1.
Run Setup.exe /PrepareSchema, /PrepareAD and PrepareDomain (or /PrepareAllDomains) before installing. If you are upgrading from a previous version of Exchange, mind the default OAB. Exchange 2013 will create a new OAB and if you didn’t configure your mailbox database to point to a specific OAB, all your clients might end up downloading the new OAB Could cause some issues if you’ve got a lot of clients or clients connecting of a link with limited bandwidth. Check article for more info!. There’s a limited support for Public Folders in OWA now. Basically, OWA will allow access to “favorite” Public Folders.
However, still no access to the entire tree. You can now configure Groups to manager Groups again. In RTM only a user could be configured to be “manager” of e.g.
A Distribution Group. As the EHLO-blog already mentioned a while back, the has been added.
Mailbox sizes are reported more accurately ( not really a CU1 feature). Why should you care? It’s more accurate, 2.
Mailbox sizes are likely to grow when moving to Exchange 2013 keep an eye on your configured quota’s!. How can I deploy Exchange 2013 RTM CU1? Deploying Exchange 2013 RTM CU1 doesn’t require you to have Exchange 2013 RTM installed. In fact, the download (about 1.3GB in size) contains a full build which you can use to run the install from. How to deploy Exchange 2013 didn’t change over RTM. Preferably using the command line: Setup.exe /mode:install /roles: /IAcceptExchangeServerLicenseTerms If you.are. upgrading, than you should run the following command: Setup.exe /mode:upgrade Note as a CU is a build-to-build upgrade, changes you made to web.config files will be overwritten.
This means that if you had integrated Lync with Exchange prior to the upgrade, you’ll have to make the changes to the web.config file again! What are other saying? As always, many peers from the Exchange community have been busy with providing as much as information that is already available. Make sure to check them out!. (Official Announcement).
Exchange 2013 Cumulative Update 1 Now Available. By. Microsoft today released Cumulative Update 1 (CU1) for Exchange 2013.
The update will allow IT organizations to go forward with on-premises deployments that mix Exchange Server 2013 with earlier Exchange Server versions. It also adds hotfixes since the Exchange 2013 product was released, along with some new features. With the new CU1 in place, Exchange 2013 can coexist with Exchange 2010 Service Pack 3 or Exchange 2007 Service Pack 3 with Update Rollup 10. It also allows Exchange 2013 to work with a mix of those two legacy servers. Organizations trying to get Exchange 2013 working with Exchange 2003 are out of luck as it's not supported at all by Microsoft.
A table showing the possible coexistence scenarios can be found. CU1 reflects Microsoft's new quarterly release cadence that it. IT pros now get full builds of products with these cumulative update releases, so they are going to be a bit fatter. This release, called 'build.029,' is a 1.3 GB download and can be accessed. Install Caveats This first cumulative update for Exchange 2013 comes with lots of caveats before installing it, which are outlined in an and the.
![]()
Organizations that just have an Exchange 2007 environment, but want to add Exchange 2010 at a later time, need to preserve at least one legacy server role if installing Exchange 2013 CU1. 'Once you remove the last server role of a legacy version, you will no longer be able to reintroduce that version into the environment,' the Exchange team warned, in the announcement. The CU1 release comes with schema changes.
Active Directory first needs to be updated to account for the schema changes, as well as role-based access control updates and domain permission changes. The cumulative update will create a new default offline address book (OAB). Clients will look for this new default OAB automatically, which can cause the clients to start full OAB downloads. IT pros can avoid that potential bandwidth hit by changing mailbox database settings to point to the current OAB before installing Exchange 2013, according to Microsoft's announcement. CU1 comes with a big note about the Exchange 2013 architecture. Exchange 2013 is different from earlier releases in that it's architected with just two server roles, a mailbox role and client role.
There's a restriction on uninstalling them if they are both installed on a single machine. Users have to remove both of them at the same time in that case; it's not possible to uninstall them individually, Microsoft warned. Microsoft also offers a note that IT pros could be tripped up by mailbox size quotas. CU1 for Exchange 2013 will increase the size reporting of mailboxes by about 30 percent to 40 percent.
Consequently, the Exchange team suggests that mailbox quotas may need to be increased before performing the update. Supposedly, the increased size isn't actually consumed. It just gets reported as larger. 'Again, this does not mean there will be an increase in the size of the database file on disk; only the attribution of space to each mailbox will increase,' Microsoft's announcement explained. New Functionality CU1 also includes some new functionality, which seems to reflect Microsoft's new release strategy.
Typically, cumulative updates have been described as just including product fixes, not new features, per. In this case, Microsoft added an address book policy routing agent in CU1.
The management functionality was changed back to allowing groups to own other groups, so IT pros no longer need to run a script to make that happen. Public folders can now be accessed through the Outlook Web App. There are lots of high-availability improvements included in CU1. An outline of those improvements can be found in.
Microsoft's announcement also indicated that CU1 for Exchange 2013 will support a management pack for System Center Operations Manager, which will be available at a later date. No clue was provided as to when that might occur. Specifically, management packs for System Center Operations Manager 2007 R2 and System Center Operations Manager 2012 are in the works, according to the announcement. Cancelling the update in process will stall the Exchange transport service, according to Microsoft Exchange MCM and MVP Jeff Guillet. He suggested in that IT pros remember to restart the Exchange transport service in such cases.
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |