At the same time Microsoft released the Windows 8.1 and Windows Server 2012 R2 bits to TechNet and MSDN subscribers, they also released the Release Notes for Windows Server 2012 R2 on a page on the Microsoft Download Center. On this page you can a document (*.docx format) with the critical issues, that have currently been identified, that might require avoidance or workaround to get Windows Server 2012 R2 installed and running.
Below is the list with the current important issues for Windows Server 2012 R2:
If you create a virtual machine with the minimum supported hardware parameters (1 processor core and 512 MB RAM) and then attempt to install this release on the virtual machine, Setup will fail.
To avoid this, do one of the following:
- Allocate more than 800 MB RAM to the virtual machine you intend to install this release on. Once Setup has completed, you can change the allocation to as little as 512 MB RAM, depending on the actual server configuration.
- Interrupt the boot process of this release on the virtual machine with Shift + F10. In the command prompt that opens, use Diskpart.exe to create and format an installation partition. Run Wpeutil createpagefile /path=C:\pf.sys (assuming the installation partition you created was C:). Close the command prompt and proceed with Setup.
In two screens, the wizard refers to Windows Server 2012; the text should read “Windows Server 2012 and Windows Server 2012 R2.” There is no impact to functionality.
Three issues have been identified with Internet Explorer 11:
- Input Method Editor (IME) input does not accept non-Latin characters with Adobe Flash in Internet Explorer. Only Latin characters can be inserted with an IME. To avoid this, use Internet Explorer for desktop.
- If you visit a website that contains Adobe Flash Player-based content, no PlayTo endpoints are listed in the Devices charm. There is no workaround at this time.
- When you pause Adobe Flash Player-based content in Internet Explorer and switch to Internet Explorer for desktop, the content might not be visible when you return. To avoid this, do not pause content when switching to the desktop. If this has already occurred, try refreshing the web page.
These issues affect both Windows Server 2012 R2 Essentials and other editions of Windows Server 2012 R2 when the Essentials Experience is installed with Server Manager:
- The Windows Server Essentials Experience only works in a single-domain environment that does not include a read-only domain controller. There is no workaround at this time.
- If you install Windows Server Essentials as a virtual machine, and if your server is not connected to the network (or the DHCP service is not available) while running the Configure Windows Server Essentials Wizard, Anywhere Access functionalities (such as Remote Web Access, virtual private networking and DirectAccess) are blocked.
To avoid this, ensure that your server has a network connection when you install Windows Server Essentials as a virtual machine and run the Configure Windows Server Essentials Wizard. If this has already occurred, manually configure the DNS settings.
The client and server must be running the same milestone release for Work Folders to function properly. For example, if the server is running this milestone release of Windows Server 2012 R2, the client must be running the same milestone release of Windows 8.1.