Article ID: 2862551 - View products that this article applies to.
This article lists the issues that are fixed in Update Rollup 3 for Windows Server 2012 Essentials.
Important This update rollup contains server-side fixes. After you apply this update rollup, the client-side package is installed automatically on all client computers. The Update Rollup 3 client-side package is the same as the Update Rollup 1 client-side package (2781268).
For more information about the client-side package, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2781268/ )Client-side package of Update Rollup 1 for Windows Server 2012 Essentials is available
Note This update rollup also applies to versions of Windows Server 2012 Standard that are transitioned from Windows Server 2012 Essentials.
Features and updates that are included in this update
Feature 1The "DNS auto-detect and configure" feature is turned on after Connector is installed on clients. This feature tries to find the server that is running Windows Server 2012 Essentials, and then it uses the server’s address as the client's DNS address. This may temporarily disconnect the Internet connection in some network environments.
Update Rollup 3 introduces some new solutions to skip DNS auto-detect and configuration on the clients. To do this, see the following.
Note These solutions require you to have a solid knowledge of Windows Server Essentials networking configurations. After you apply these solutions, the administrator must manually configure the networks to make sure that the Windows Server Essentials functionalities work correctly.
Feature 2Update Rollup 3 contains new Best Practice Analyzer (BPA) rules. The rules check the known ports that are reserved by Windows Server Essentials.
The following ports are reserved by Windows Server 2012 Essentials.
If any of these ports are being used by applications other than these programs, Windows Server Essentials functionalities may not work correctly. In Update Rollup 3, a new rule is added to the BPA.
Collapse this tableExpand this table
TitlePorts that are unavailable for use by Windows Server Essentials
IssueWindows Server Essentials uses ports 3389, 6602, 8912, 65500, and 65520 for various functionalities. One or more of these ports are currently reserved by other applications.
ImpactWindows Server Essentials uses the following ports: 3389, 6602, 8912, 65500 and 65520.
ResolutionTo resolve this issue, do one of the following:
Update 1This update rollup introduces a new branding name for the Microsoft Azure Backup integration add-in.
Major issues that are resolved by this update
Issue 1Windows Server Essentials Group Policy settings do not work in Windows 8.1.
Issue 2Client Backup stops at the "In progress" status when the destination disk is full.
Issue 3When you run Microsoft Office 365 Windows PowerShell cmdlets by using non-administrator permission, Windows Server Office 365 Integration Service crashes.
Issue 4When you delete users who have a Microsoft Exchange Server 2013 mailbox assigned, the Windows Server On-Premises Exchange Integration Service crashes.
Issue 5Assume that an Office 365 user tries to change their password. If the password cannot synchronize to the Office 365 servers, the user cannot change his or her password.
Issue 6Assume there is a situation in which the password synchronization service is stopped. When password synchronization is tried, the synchronization failure is not reported.
Issue 7Windows Server Password Synchronization Service crashes when the service evaluates password synchronization alerts.
Issue 8After update 2804583 is installed, mailbox management of web APIs does not work.
Issue 9When Windows Server 2012 Essentials is installed on a remotely administered server, an incorrect time zone is used.
Issue 10The Remote Web Access (RWA) File Sharing folder and media page do not work correctly.
Issue 11User State Migration Tool is not updated for the Windows 8.1 client.
Issue 12When the name of a certificate does not match the fully qualified domain name (FQDN), ARRConfig does not provide a clear error message.
How to obtain this update
Windows UpdateThis update is available from Windows Update
PrerequisitesTo apply this update, you must be running Windows Server 2012 Essentials.
Registry informationTo apply this update, you do not have to make any changes to the registry.
Restart requirementYou do not have to restart the computer after you apply this update.
Update replacement informationThis update does not replace a previously released update.
Removal informationTo remove this update, use the Programs and Features item in Control Panel. Additionally, you must separately uninstall the client-side package on all client computers.
Article ID: 2862551 - Last Review: June 20, 2014 - Revision: 4.0