Cannot access the Mail control panel applet after Office 365 installation

When installing Office 365 Professional Plus on a PC, the wizard automatically connects the email accounts to Office 365 easily. However, if you want to add an additional Microsoft Exchange on-premises account, there may be an issue where the Mail applet in the control panel does not work.

This appears to be cause by incorrect registry settings. Uninstalling Office 2013 and Re installing it appears to solve the problem in most cases. Settings appear to be retained and do not need to be reconfigured.

Hotfix: Resolve Issues in mixed Windows Server 2003 and 2012R2 Domain Controller environments

The issues were documented here - http://blogs.technet.com/b/askds/archive/2014/07/23/it-turns-out-that-weird-things-can-happen-when-you-mix-windows-server-2003-and-windows-server-2012-r2-domain-controllers.aspx

The main issue is that users could not log on to the domain and Kerberos errors (EventID 4) were logged. This could lead to issues, and frustration, especially in migration situations.

The hotfix can be obtained here - http://support.microsoft.com/kb/2989971

Enabling Windows Server 2012 R2 Essentials integration with Microsoft Online Services when there are multiple domain controllers

The latest August 2014 update rollup for Windows Server 2012 R2 has addressed this issue. The integration feature previous only worked when the Essentials server was the only domain controller in the domain, which led to some difficult workarounds in migration scenarios.

The rollup can be downloaded via Windows Update or directly here - http://support.microsoft.com/kb/2975719.

You can read the Microsoft announcement here - http://blogs.technet.com/b/sbs/archive/2014/08/13/announcing-the-availability-of-enabling-windows-server-2012-r2-essentials-integration-of-microsoft-online-services-in-environments-with-multiple-domain-controllers.aspx.

Increase the maximum PST file size for Outlook

I have been working through a bunch of Microsoft Exchange migrations recently. One of the issues that we have seen has to do with the size of the exported PST file. By default, the maximum size of PST files has been limited to 20GB for Outlook 2003 and 2007, and 50GB for Outlook 2010 and 2013.

This limit can be increased or decreased via two registry settings.

  • WarnLargeFileSize – This value sets warning threshold in MB for the maximum size of a PST file. The maximum is 4090445042 (That is about 4PB!)
  • MaxLargeFileSize – This value determines the maximum size in MB that can be written to a PST file. This should be set to about 5% higher than the warning size above. This maximum is 4294967295.

Here are some common values that could be used:

  •  30GB maximum (29GB warning) = 30720 (29696)
  • 75GB (73GB) = 76800 (74752)
  • 100GB (95GB) = 102400 (97280)
  • 150GB (145GB) = 153600 (148480)
  • 200GB (190GB) = 204800 (194560)
  • 500GB (480GB) = 512000 (460800)
  • Are you sure you want such a large PST file after this?

The registry settings are found or created here, depending on the Outlook version.

  • Outlook 2003 HKCU\Software\Microsoft\Office\11.0\Outlook\PST
  • Outlook 2007 HKCU\Software\Microsoft\Office\12.0\Outlook\PST
  • Outlook 2010 HKCU\Software\Microsoft\Office\14.0\Outlook\PST
  • Outlook 2013 HKCU\Software\Microsoft\Office\15.0\Outlook\PST

Hyper-V and the “Windows cannot find the Microsoft software license terms” error

I was building a new Hyper-V server using Windows Server 2012 R2 and ran into this error. The scenario? You set up a new VM using the default settings, and configure the use of Dynamic RAM.

Once the VM is set up, you start this and get to the point of typing in the license key. In the case of the Datacentre edition, with Generation2 VMs, you can use the Automatic Activation Keys as detailed in the Technet article here – http://technet.microsoft.com/en-au/library/dn303421.aspx. And the following error occurs – “We couldn’t verify the product key. Please check your installation media.”

Alternatively, you may get the following message after selecting the operating system – “Windows cannot find the Microsoft Software License Terms. Make sure the installation sources are valid and restart the installation.”

The solution is straightforward. You need to assign at least 576MB RAM as the starting value for the VM to bypass this problem. I usually configure my virtual servers to start with a minimum of 1024MB RAM.

 

 

Archive Outlook items by received or sent date, not by last modified date

While looking through some maintenance tasks, I came across a knowledge base article that solved a long standing issue. In Outlook 2010 and Outlook 2013, it is possible to archive items by their date received or sent instead of by the last modified date.

Microsoft KB2553550 (http://support.microsoft.com/kb/2553550) details the steps.

Outlook 2010

To create the ArchiveIgnoreLastModifiedTime registry value, follow these steps:

  1. Start Regedit.
  2. Locate and then click the following registry subkey:
    HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Preferences
  3. On the Edit menu, point to New, click DWORD Value, type ArchiveIgnoreLastModifiedTime, and then press ENTER.
  4. Right-click ArchiveIgnoreLastModifiedTime, and then click Modify.
  5. In the Value data box, type 1, and then click OK.
  6. Exit Registry Editor.

Outlook 2013

To create the ArchiveIgnoreLastModifiedTime registry value, follow these steps:

  1. Start Regedit.
  2. Locate and then click the following registry subkey:
    HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Preferences
  3. On the Edit menu, point to New, click DWORD Value, type ArchiveIgnoreLastModifiedTime, and then press ENTER.
  4. Right-click ArchiveIgnoreLastModifiedTime, and then click Modify.
  5. In the Value data box, type 1, and then click OK.
  6. Exit Registry Editor.

You must restart Outlook after you add the ArchiveIgnoreLastModifiedTime registry key.

Bonanza collection of Free Microsoft eBooks for IT Pros, End Users, and even teenagers!

Thanks to Eric Ligman, Microsoft Senior Sales Excellence Manager, for sharing this incredible FREE wealth of knowledge. Yes, they are free to download. 300 titles. Here are a few that may be really helpful to various groups of people. Here is the full list - http://blogs.msdn.com/b/mssmallbiz/archive/2014/07/07/largest-collection-of-free-microsoft-ebooks-ever-including-windows-8-1-windows-8-windows-7-office-2013-office-365-office-2010-sharepoint-2013-dynamics-crm-powershell-exchange-server-lync-2013-system-center-azure-cloud-sql.aspx

Or you can grab some of the highlights from here.

IT Professionals in the Small Business

General Microsoft Users

And for Teenagers, and anyone else who needs to be informed about online security and privacy (That’s everyone!) - Own Your Space–Keep Yourself and Your Stuff Safe Online

Enjoy!

Step by Step Windows 2012 R2 Remote Desktop Services

Here is a link to an excellent series of blog posts on how to set up and configure Remote Desktop Services (Terminal Services) in a clear and easy manner.

  1. http://msfreaks.wordpress.com/2013/12/09/windows-2012-r2-remote-desktop-services-part-1/
  2. http://msfreaks.wordpress.com/2013/12/23/windows-2012-r2-remote-desktop-services-part-2/
  3. http://msfreaks.wordpress.com/2013/12/26/windows-2012-r2-remote-desktop-services-part-3/
  4. http://msfreaks.wordpress.com/2014/01/08/step-by-step-windows-2012-r2-remote-desktop-services-part-4/

 

Registry hack enables continued updates for Windows XP

Support for Windows XP ended at the end of April 2014. However, there is still a large base of PCs that are still in use  running Windows XP. This is not good nor safe computing practice, especially if the PC is operating in a business environment and is being used for critical business applications.

ZDNet published an article detailing a simple registry hack (http://www.zdnet.com/registry-hack-enables-continued-updates-for-windows-xp-7000029851/) that will enable Windows XP PCs to emulate a Windows Embedded POSReady 2009 device. These devices are based on Windows XP, and are specifically used in basic terminal applications. The danger is that not all updates will be suitable for mainstream WIndows XP, and some critical ones may be missed. However, if you MUST run Windows XP for a really old legacy application, then there is still a way to obtain some update protection. It is highly advisable that you seek out a way to decommission your Windows XP PCs and replace them as soon as possible.

To enable this hack, add the following Key to the registry - HKLM\SYSTEM\WAP\PosReady

Then create a DWORD called “Installed” with a value of 1.

Alternatively, create a .REG file with the following text and merge it into the registry.

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\WPA\PosReady]
“Installed”=dword:00000001

I will warn again that this should be a “I have no reasonable alternative” move. There are always other options, and the best option is to migrate away from Windows XP.

%d bloggers like this: