Awesome Script This script checks various configuration items on the server to make sure they match the recommendations published in the “Exchange 2013 Sizing and Configuration Recommendations” guidance on TechNet. It also reports on OS, system, and hardware information. It can be ran remotely, against a single server or a group of servers. It takes some of the most common configuration causes of Exchange 2013 performance cases that we encounter in support and allows you to rule them out quickly without having to check each server or read through the entire TechNet guidance.
This script needs to be executed from the Exchange 2013 Management Shell.
Here is a current list of items the script reports on:
Operation System version Exchange Build Physical/Virtual Machine Server Manufacturer and Model (physical hardware only) VM host processor/memory configuration recommendations Exchange server roles Pagefile Size Power Settings .NET Framework version Network card name and speed Network card driver date and version (Windows 2012 and Windows 2012 R2 only) RSS enabled (Windows 2012 and Windows 2012 R2 only) Physical Memory amount Processor Model Number of processors, cores, and core speed Hyper-threading enabled/disabled Processor speed being throttled Current list of active/passive databases and mailboxes (optional)
There is a known issue which causes some PCs updated with the Windows 8.1 Update (KB 2919355) to stop scanning against Windows Server Update Services 3.0 Service Pack 2 (WSUS 3.0 SP2 or WSUS 3.2) servers which are configured to use SSL and have not enabled TLS 1.2.
The problem is specific to the following scenario when all of the following are true
Client PC has installed Windows 8.1 Update KB 2919355
Windows 8.1 with Windows 8.1 Update KB 2919355 attempts to scan against WSUS 3.2 running on any affected platform:
Windows Server 2003 SP2, or
Windows Server 2003 R2 SP2, or
Windows Server 2008 SP2, or
Windows Server 2008 R2 SP1
HTTPS and Secure Sockets Layer (SSL) are enabled on the WSUS server
TLS 1.2 is not enabled on the server
Only users who have enabled HTTPS and have not enabled TLS 1.2 on their WSUS 3.2 servers and who are also using these WSUS 3.2 servers to manage PCs running the Windows 8.1 Update KB 2919355 are affected by this issue. Please note, while we do recommend the use of HTTPS on WSUS servers, HTTPS and TLS 1.2 are not enabled by default.
If you are using WSUS 3.2 on Windows Server 2008 R2, you may perform either of the following steps to restore the scan functionality if you have deployed the Windows 8.1 Update KB2919355.
Enable TLS 1.2 (follow the instructions under More Information > SCHANNEL\Protocols subkey), or
Disable HTTPS on WSUS
If you are using WSUS 3.2 on an operating system other than Windows Server 2008 R2, you may perform the following step to restore the scan functionality.
Disable HTTPS on WSUS
When Microsoft releases an update that resolves the issue, you may re-enable HTTPS on WSUS.
Microsoft plans to issue an update as soon as possible that will correct the issue and restore the proper behavior for Windows 8.1 Update KB 2919355 scanning against all supported WSUS configurations. Until that time, we are delaying the distribution of the Windows 8.1 Update KB 2919355 to WSUS servers.
You may still obtain the Windows 8.1 Update (KB 2919355) from the Windows Update Catalog or MSDN. However, we recommend that you suspend deployment of this update in your organization until we release the update that resolves this issue. You may also find the workarounds discussed in this article to be useful for testing this Windows 8.1 Update for your organization. Thank you for your patience during this time.
You still run adksetup.exe to install or download the updated ADK, but you do see that the new ADK is slightly bigger than the previous kit. The Patches folder content also have a higher version number. The October 18, 2013 release of Windows 8.1 ADK had a folder named 8.100.26020, but the April 2, 2014 release of Windows 8.1 ADK have 8.100.26629.
New features in ADK 8.1 are the WIMBoot option, updates to dism, updates to WinRE and a new WinPE version (5.1). There are also fixes for USMT.
Important Change: DISM: Does not support Windows Vista or Windows Server 2008 images.