Exchange Server 2013 Cumulative Update 3

Issues that the cumulative update resolves

Cumulative Update 3 for Microsoft Exchange Server 2013 contains the fix for the security issue that is described in Security Bulletin MS13-061 and resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

• 2865161 "Errors: Failed exporting item id: from source id" when you try to copy search results in an Exchange Server 2013 environment

• 2866064 Can't load OWA Premium by using Internet Explorer 11 in an Exchange Server environment

• 2871980 Child domains are not displayed for selection when you create a mailbox by using EAC in an Exchange Server 2013 environment

• 2874216 Security issue that is described in Security Bulletin MS13-061 is resolved by an Exchange Server update

• 2878160 "The Active Directory user wasn't found" error when you create or update an In-Place eDiscovery search in an Exchange Server 2013 environment

• 2882608 Exchange Server 2013 does not share the inproxy.dll file

• 2886115 Retention policies are not applied to Exchange Server 2013 mailboxes when user accounts are on different domains

• 2888274 WebClientReadFormQueryString string and WebClientEditFormQueryString string return incorrect URLs in an Exchange Server 2013 environment

• 2888315 Event 2112 or 2180 is logged when you try to back up a database in an Exchange Server 2013 environment

• 2888612 Retention policy does not work after you run a cmdlet in an Exchange Server 2013 environment

• 2889786 Sign-in format for Outlook Web App on mobile devices is not adjusted according to the Set-OwaVirtualDerictory cmdlet in an Exchange Server 2013 environment

• 2890650 Items in the Drafts folder are not stamped with the retention policy tag in an Exchange Server 2010 or 2013 environment

• 2895487 "Copy Search Results" option does not work in an Exchange server 2013 environment

• 2895500 DBCS characters appear garbled when you run some PowerShell scripts in EMS in an Exchange Server 2013 environment

• 2895678 "Nombre de usuario\dominio" is displayed unexpectedly on the Spanish version of the OWA and EAC logon pages in an Exchange Server 2013 environment

• 2902929 You cannot forward an external meeting request in an Exchange Server 2013 environment

• 2902929 You cannot forward an external meeting request in an Exchange Server 2013 environment

• 2902933 "Generate incident report" does not display the "Bcc" field in an Exchange Server 2013 environment

• 2902934 Korean language localization issue in Exchange 2013 OWA user interface

• 2902936 You cannot change SMTP addresses for distribution groups by using EAC in an Exchange Server 2013 environment

• 2902938 You cannot preview Office documents in shared folders by using Outlook Web App in an Exchange Server 2013 environment

• 2902939 EMS connection error when you separately install an Exchange Server 2013 Mailbox server and a Client Access server

• 2883203 Exchange Server 2013 restarts frequently after Cumulative Update 2 is installed

• 2890814 No redirection to the Outlook Web App URL for Exchange Online users in an Exchange hybrid deployment

More information can be found here; download CU3 here. As always please read comments section here prior to install.

Update Rollup 3 For Exchange 2010 Service Pack 3

Update Rollup 3 for Exchange Server 2010 SP3 contains the fix for the security issue that is described in Security Bulletin MS13-061 and resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

• 2715761 "550 5.6.0" NDR when you send a yearly recurring meeting request in an Exchange Server 2010 environment

• 2839533 RPC Client Access service freezes in an Exchange Server 2010 environment

• 2840454 "The rules on this computer do not match the rules on Microsoft Exchange" error when you manage rules by using Outlook 2013 in an Exchange Server 2010 environment

• 2866064 Can't load OWA Premium by using Internet Explorer 11 in an Exchange Server environment

• 2874070 Public folders are exposed although the user does not have rights to see the parent folders in an Exchange Server 2010 SP3 environment

• 2878175 Client Access server crashes when you use Outlook with a Riverbed WAN optimizer in an Exchange Server 2010 environment

• 2879320 Retention action setting is not updated in FAI items by running the Set-RetentionPolicyTag cmdlet in an Exchange Server 2010 environment

• 2879736 Office 365 users cannot retrieve an on-premises user’s free/busy data in an Exchange Server 2010-based hybrid deployment

• 2880153 RPC Client Access Service crashes if Outlook is in online mode in an Exchange Server 2010 environment

• 2880290 RPC Client Access service crashes when you use Outlook in ANSI online mode in an Exchange Server 2010 environment

• 2882467 RPC Client Access service stops if Outlook is in online mode in an Exchange Server 2010 environment

• 2882677 BlackBerry device is not redirected in an Exchange Server 2010 environment

• 2886469 EAS client receives status code 8 during synchronization in an on-premises Exchange Server 2010 environment

• 2886567 "Objects added to a BindingSource's list must all be of the same type" error message when you add an additional domain name in Exchange Server 2010 SP3

• 2887574 RPC Client Access service freezes when your mailbox reaches the quota limit in an Exchange Server 2010 environment

• 2888406 Mailbox Replication service crashes when you try to move mailboxes in an Exchange Server 2010 environment

• 2888906 Events 1000, 4999, and 9775 are logged when Store.exe crashes on an Exchange Server 2010 SP3 Mailbox server

• 2888911 W3wp.exe crashes when you decline a meeting request by using Outlook Web App or an EWS application in an Exchange Server 2010 environment

• 2890650 Items in the Drafts folder are not stamped with the retention policy tag in an Exchange Server 2010 or 2013 environment

• 2891194 Exchange ActiveSync devices are marked as "Blocked" in EMS and EMC when the devices are synchronizing with the Exchange Server 2010 server

• 2892337 Outlook client freezes when you try to sort email folders by columns in an Exchange Server 2010 environment

• 2893437 Delegate can read your AD RMS protected messages by using Outlook Web App in an Exchange Server 2010 environment

• 2896304 Background image is displayed incorrectly in an email message when a disclaimer rule is enabled in an Exchange Server 2010 environment

• 2899146 You cannot drag email messages to other folders by using Outlook Web App in an Exchange Server 2010 environment

More information can be found here; download RU3 here. As always please read comments section here prior to install.

Exchange 2010 Certificate change; don’t forget Lync!

If your Exchange 2010 certificate expires you will find that the OWA Lync integration will stop working as Lync is using the expired certificate.

This is relativity easy to fix from any CAS Server.

Open Exchange Powershell on a CAS Server and type the following to get the new certificate thumbprint (check the certificate expiry date to be 100%)

This is my old certificate thumbprint it will be 40 characters long (mine is trimmed)

You can verify the old thumb print by running the following command.

With your new thumbprint use the following command

get-owavirtualdirectory | set-owavirtualdirectory -InstantMessagingCertificateThumbprint newthumbprintgoeshere

Run the following command to verify that the thumbprint has changed. (I have two CAS Servers hence two settings.)

If your happy that the new thumbprint match's then reset IIS at a time that suits.

Getting Started with Xbox One

Kinect for XBOX One

Settings up cables for XBOX One

XBOX One Guide

More information on getting started with XBOX One can be found here;

Free ebook: Microsoft System Center: Troubleshooting Configuration Manager

The third title in this series, Microsoft System Center: Troubleshooting Configuration Manager (ISBN 9780735683020) by Rushi Faldu, Manoj Kumar Pal, Andre Della Monica, Kaushal Pandey, and the System Center series editor Mitch Tulloch, is now available.

• Troubleshooting common Configuration Manager tasks such as software distribution, software updates, and deployment.
• Understanding how the various components of Configuration Manager on both the server and client side work together when such tasks are performed.
• Dealing with the enormous number of log files that are generated on both the server and client side of Configuration Manager.

Download ebook here; more information can be found here.

Free ebook: Introducing Windows Server 2012 R2 Technical Overview

This book is intended to provide you with an overview of the new features and enhancements introduced in Windows Server 2012 R2. The intended audience for this book is IT pros who deploy, manage, and maintain Windows Server workloads in data center, private cloud, and hosting provider environments.

More information can be found here; download here.

Performance Tuning Guidelines for Windows Server 2012 R2

When you run a server system in your organization, you might have business needs that are not met by using the default settings. For example, you might need the lowest possible energy consumption, or the lowest possible latency, or the maximum possible throughput on your server. This topic provides a set of guidelines that you can use to tune the server settings in Windows Server 2012 R2 and obtain incremental performance or energy efficiency gains, especially when the nature of the workload varies little over time.

This topic is split into the following sections:

• Performance Tuning for Server Hardware
• Performance Tuning for Subsystems
• Performance Tuning for Server Roles
• Performance Tuning for Workloads
• Additional Resources for Performance Tuning Guidelines

More information can be found here;

Windows Azure Poster

More information can be found here; download here.

IE 11 now available

More information can be found here;

Download x32 x64 Windows 2008 R2.

Operating system
Windows 7 32-bit with Service Pack 1 (SP1) or higher
Windows 7 64-bit with Service Pack 1 (SP1) or higher
Windows Server 2008 R2 with Service Pack 1 (SP1) 64-bit

Note
You must have Service Pack 1 (or higher) to install Internet Explorer 10 and Internet Explorer 11 for Windows 7.

KMS : Windows Server 2012 and 8.1 (How To)

What is KMS?
KMS stands for Key Management Service (or server); KMS activates computers on a local network, eliminating the need for individual computers to connect to Microsoft and the need for manually entering product keys.

Microsoft offers two types of Windows (and Office) products keys;
- KMS Keys (used to activate volume license media VLK)
- MAK Keys (Multiple Activation Key usually activates over internet / phone)

KMS is not for every environment as the following pre-req’s should be noted:
- Activations are only valid for 180 days, to remain activated, KMS client computers must renew their activation by connecting to the KMS host at least once every 180 days.
- By default, KMS client computers attempt to renew their activation every seven days. If KMS activation fails , the client will retry every two hours. After a client computer’s activation is renewed, the activation validity interval begins again.
- KMS has a threshold before it starts activating; clients such as Office / Windows 7/8/8.1 is ≥ 25 with Servers ≥ 5.

Installing KMS Windows Server 2008 R2.
No software required just a Windows 2008 R2 Server or a Windows 7 Client.
- Login to the Volume License Website and make a note of your KMS B or C key.
- From your intended KMS; open an elevated command prompt and type;

slmgr /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

- Replace x’ with your KMS Key and allow Firewall exception for Key Management Service
- Activate the Key by typing in the command window;

slmgr /ato

- Publish the KMS into DNS as this is how the clients find the KMS by typing;

slmgr /sdns

- Verify that the DNS entry is created

- Reboot the KMS Server for the changes to take effect.
- Make sure that your clients / servers are installed using the VLK media as they will included the proper client side KMS Key.  Please note that this Client Key is not the same as your KMS Key that you used above; this Client side Key is a generic Microsoft Key that can be found here;

Windows 8.1 Professional	GCRJD-8NW9H-F2CDX-CCM8D-9D6T9
Windows 8.1 Professional N	HMCNV-VVBFX-7HMBH-CTY9B-B4FXY
Windows 8.1 Enterprise	MHF9N-XY6XB-WVXMC-BTDCT-MKKG7
Windows 8.1 Enterprise N	TT4HM-HN7YT-62K67-RGRQJ-JFFXW
Windows Server 2012 R2 Server Standard	D2N9P-3P6X9-2R39C-7RTCD-MDVJX
Windows Server 2012 R2 Datacentre	W3GGN-FT8W3-Y4M27-J84CP-Q3VJ9
Windows Server 2012 R2 Essentials	KNC87-3J2TX-XB4WP-VCPJV-M4FWM

- If you meet the criteria above your clients and servers should now automatically activate.
- Either check the System information or type the following from your client;

slmgr /dli
(current license information)

slmgr /dlv
(current license information verbose)

All slmgr commands can be found here.

Note – an update is required for Windows 7 and Windows 2008 R2 Servers to activate Windows 8.1 and Windows Server 2012 R2; more information can be found here.

 

Installing KMS Windows Server 2012 R2.

Add the Volume Activation Service using Server Manager.

Configure using the Volume Activation Tools

Add your KMS B or C Key from the Volume License web site.
*Active Directory-Based Activation (ADBA) is a new feature for Windows 8, which enables enterprises to activate computers through a connection to their domain.

Configure the KMS Options and Commit the changes.

Tools;
Volume Activation Management Tool (VAMT)

SCVMM 2012 R2 and the removal of P2V

I’m not sure if you are aware but VMM 2012 R2 has removed the P2V capability!  Seemingly an alternative product is in the pipeline; I’m guessing an updated version of Microsoft Virtual Machine Converter?

The VMM group have suggested the following method but standing up another instance of VMM 2012 SP1 is crazy.

More information can be found here; plus read the comments.