Cumulative update 1 for Exchange Server 2013 (KB2816900)

From the Exchange Team.

We know a lot of you have been waiting for this, and so it is with great excitement that we announce that Exchange Server 2013 RTM Cumulative Update 1 (CU1) has been released to the web and is available for immediate download! This is the first release using the new servicing model for Exchange Server 2013. In addition to this article, the Exchange 2013 RTM CU1 release notes are also available.

More information can be found here; as always please read the comments section prior to downloading!!

Server Deployment Updates and Changes (Read First)
Once the preparatory steps are completed, you can then deploy CU1 and start your coexistence journey. If this is your first Exchange 2013 server deployment, you will need to deploy both an Exchange 2013 Client Access Server and an Exchange 2013 Mailbox Server into the organization. As explained in Exchange 2013 Client Access Server Role, CAS 2013 is simply an authentication and proxy/redirection server; all data processing (including the execution of remote PowerShell cmdlets) occurs on the Mailbox server. You can either deploy a multi-role server or each role separately (just remember if you deploy them separately, you cannot manage the Exchange 2013 environment until you install both roles).

If you already deployed Exchange 2013 RTM code and want to upgrade to CU1, you will run setup.exe /m:upgrade from a command line after completing the Active Directory preparatory steps or run through the GUI installer. Deploying future cumulative updates will operate in the same manner.

Notes:
- Unlike previous versions, in Exchange 2013, you cannot uninstall a single role from a multi-role server. For example, if you deploy the CAS and MBX roles on a single machine, you cannot later execute setup to remove the CAS role; you can only uninstall all server roles.

- When you deploy the first Exchange 2013 Mailbox server in an existing Exchange organization, a new default Offline Address Book is created.

- If your environment contains only Exchange 2007, and you upgrade to Exchange 2013, keep in mind you cannot deploy Exchange 2010 in that environment at a later time. If you foresee a need to deploy Exchange 2010 servers into your environment, deploy an Exchange 2010 multi-role server (with all four servers roles) prior to executing Exchange 2013 setup.exe /PrepareAD

- Unlike previous versions, cumulative updates do not use the rollup infrastructure; cumulative updates are actually full builds of the product, meaning that when you want to deploy a new server, you simply use the latest cumulative update build available and do not necessarily need to apply additional Exchange Server updates.

- As you start migrating your mailboxes to Exchange 2013, one thing you may notice is that your mailboxes appear to be larger post move. Our improved space calculations may result in a mailbox’s reported size increasing on average of 30% when the mailbox is moved from a legacy version of Exchange to Exchange 2013.

For example, if a mailbox is reported as 10GB in size on Exchange Server 2010, then when the mailbox is moved to Exchange 2013, it may be reported as 13GB. This does not mean that migrating to Exchange 2013 will increase your capacity footprint by 30% per mailbox; it only means that the statistics are including more data about the space the mailbox consumes.

New Functionality Included in Cumulative Update 1
- Address Book Policy Routing Agent has been included in Exchange 2013 RTM CU1.
- Exchange 2013 RTM CU1 groups can once again be owners of groups for membership management.
- Public Folder Favourites Access through Outlook Web App
- Exchange Admin Center (EAC) has been enhanced and now includes Unified Messaging management.

High Availability and Monitoring Enhancements

- The Best Copy Selection algorithm now honors MaximumActiveDatabases.
- Auto-reseed now supports disks that have Bitlocker encryption.
- Many probes, monitors, and responders have been updated and improved over the RTM release.
- Get-HealthReport cmdlet has been streamlined and its performance has been optimized.
- Exchange 2013 RTM CU1 will support the Exchange Server 2013 Management Pack for System Center Operations Manager (SCOM).

***Scott ^{(beam me up)} Schnoll has posted an update on High Availability Changes in Exchange Server 2013 CU 1

//build/ 2011 Nike Tablet

Interesting read from Build 2011 and the deployment and issues encountered with the Prototype Tablets;

The advance crew also configured the hall so they would be ready to start once Redmond sent down the final bits of the Developer Preview build. The hall was divided into sections, and each section consisted of eight long tables. Four of the tables were arranged in a square, and the other four tables were placed outside the square, one parallel to each side, forming four lanes.

Along the inner tables, there were docking stations, each with power, wired access to a private network, and a USB thumb drive. Along the outer tables, there were desk organizers like this one, ready to hold several devices in a vertical position, and next to the organizer was a power strip with power cables at the ready.

More information can be found here;

Windows Server 2012 AD Recycle Bin GUI

Nice video from Chris Davis outlining the AD Recycle Bin GUI for Windows Server.

Exchange 2013 RTM CU1 Delayed to April 2nd

Looks like someone is superstitious…

From the Exchange Team Blog…..

Exchange 2013 RTM Cumulative Update 1 (CU1)  was to be delivered by the end of this quarter (March 2013).  Unfortunately, we are not going to meet that goal. We know that many of you will be disappointed as a result of this statement. We understand your pain, however, the decision to delay is due to an issue we found in our final test pass coupled with feedback from members within our Technology Adoption Program community.

Specifically, we found an issue with Exchange 2010 coexistence. The issue actually had an easy workaround, but we made a decision; instead of burdening you with a configuration change on all of your Exchange 2010 Client Access servers, we decided to take a code change in Exchange 2013 and solve the problem so that you will not have to make any additional configuration changes. Given that the goal of CU1 is to enable coexistence with legacy versions of Exchange, we felt this was the right decision; after all, we want to ensure that your upgrade to Exchange 2013 and your coexistence period goes as smooth as possible.

We regret the impact that this delay has on our customers, and as always, we continue to identify ways to better serve your needs through our regular servicing releases. The release date for Exchange 2013 RTM CU1 is currently planned for April 2^nd. We will let you know if that date changes, as well as, post an announcement when the download is live.

As always please read the comments section.

Exchange 2013 Coexistence with Exchange 2010 (ignite Video)

Ignite Webcasts are online sessions led by Microsoft Office 365 Product Managers, Engineers and Support staff.

The Ignite webcast series addresses Office 365 technical subjects and scenarios and is beneficial to anyone who wants to increase their knowledge of the Office 365 suite. View the Ignite Site for more information about Ignite programs and webcasts.

You can view past Ignite Webcast sessions and materials here and be sure to see upcoming Ignite Webcasts on the Ignite Events Page.

 

Windows Server 2012 / 2008R2 with iSCSI error 80 or 83 VPD

If you encounter the following error when testing a Windows Server Cluster Disk;

Two disks have been found on node node1 that cannot be distinguished from one another. The disks involved have disk signature afac8423, SCSI page 83h VPD descriptor 60060160FB602D00E8C82BA2978CE211, SCSI page 80h VPD Serial Number CKM00112500835. Please verify the storage configuration. You must either mask (unpresent, detach) one of these LUNs at this node, or, run validation and specify a disk list that includes only one of these disks, for example by using the Test-Cluster cmdlet in Windows PowerShell.

The error probably relates to your MPIO configuration;

When you install MPIO you must configure it for iSCSI (if you are using iSCSI); so under Discover Multi-Paths tick “Add support for iSCSI devices” click Add and you will be prompted to Reboot.

After the Reboot you should now see the following iSCSI setting under MPIO devices.

Retest your cluster and hopefully the error will now be gone!

Exchange Server 2013 High Availability and Site Resilience

This session focuses on the improvements in the areas of high availability, site resilience in Exchange Server 2013.

TechEd Australia 2012
Speakers: Scott ^{(beam me up)} Schnoll.

Find AutoReseed documentation here;

Lync 2013 Available for Windows Phone and iOS

Lync 2013 Client now available for Windows Phone and iOS; new features added are:

VoIP & Video
Now you can make and receive VoIP & video calls from all Lync 2013 Mobile apps.

Desktop & Application Share Viewing (iPad only)
Improving on the ability to view PowerPoint in meetings with Lync 2010 Mobile iPad 1.5.

For more information go here; Microsoft Lync 2013 for iPhone & Microsoft Lync 2013 for iPad

Windows Cluster and Hyper-V hotfixes

Windows Server 2008 R2 Cluster and Hyper-V Hotfixes.
http://blogs.technet.com/b/askcore/archive/2013/02/15/looking-for-windows-server-2008-r2-cluster-and-hyper-v-hotfixes.aspx

Hyper-V: Updates for Windows Server 2012
http://social.technet.microsoft.com/wiki/contents/articles/15576.hyper-v-update-list-for-windows-server-2012.aspx

Failover Cluster Hotfixes for Windows Server 2012
http://social.technet.microsoft.com/wiki/contents/articles/15577.list-of-failover-cluster-hotfixes-for-windows-server-2012.aspx

Exchange Server 2013 Deployment Assistant

The Exchange Deployment Assistant is a web-based tool that helps you deploy Exchange 2013 on-premises organization, configure a hybrid deployment between your on-premises organization and Office 365, or migrate to Office 365.

It will ask few simple questions about your requirements and based on your answers, provides you a customized checklist with instructions to deploy and configure Exchange 2013.

Just a pity it’s missing the hook into Exchange 2010/2007 … but … it’s coming soon.

More information can be found here; Exchange 2013 Deployment Assistant can be found here.