Category Archives: Fixes

Using Powershell to Start-Stop the SMTP Virtual Server

One of the most popular posts on this blog has been the blog on setting up an Internal SMTP Service for SMBs that need to send server reports and support emailing from Internal devices that have move to cloud based email services.

One of the issues with this service is that is occasionally stops. There does not appear to be any reason why it stops, but it does. Restarting the SMTPSVS service does not restart the service, because it is based on IIS6.

Good news! You can use powershell to script the restart of this service.

Open an Administrative PowerShell window.

To Start the SMTP Virtual Server, type the following:

$SMTP=[adsi]"IIS://localhost/SMTPSVC/1"
$SMTP.ServerState = 2
$SMTP.SetInfo()

To Stop the SMTP Virtual Server, type the following:

$SMTP=[adsi]"IIS://localhost/SMTPSVC/1"
$SMTP.ServerState = 4
$SMTP.SetInfo()

Restore Files and Folders wizard has stopped working on Windows Server 2012R2 Essentials

A hotfix is available for systems broken by the MS15-010 (security update for Windows kernel mode driver: February 10, 2015) update.

When trying to restore files or folders on a client that is connected to the Windows Server 2012 or 2012R2 Essentials server from the dashboard, the following error occurs.

A hotfix for this is now available here – https://support.microsoft.com/en-us/kb/3045682

You can read up more information on this issue here – http://blogs.technet.com/b/sbs/archive/2015/03/13/the-ms15-10-security-update-for-windows-server-2012-r2-essentials-and-the-client-restore-functionality.aspx

How To Fix Domain Trust Issues in Active Directory

A simple reset of the Computer Account in Active Directory Users and Computers might fix the issue where a workstation (or server) reports that “The trust relationship between this workstation and the primary domain failed”.

This is a further possible fix to the issue highlighted in an earlier blog post – http://blog.powerbiz.net.au/fixes/the-trust-relationship-between-this-workstation-and-the-primary-domain-failed/.

More explanation on this fix and why this is a better approach than removing the workstation or server and rejoining it to the domain is detailed here – http://redmondmag.com/articles/2014/04/21/domain-trust-issues.aspx.

How to change the criteria that Outlook 2010 and Outlook 2013 use to archive different item types

When archiving in Outlook, it is often useful to archive by the date of receipt for items. It is not a widely known fact that Outlook archives email messages by the last modified date. This is generally not an issue, unless you were performing some inbox cleaning out and moved an item from 2012 to another folder. At that point, the last modified date becomes the date of when you moved the email. So when you attempt to archive your mailbox, this item does not get archived.

The following KB article explains how you can change this default behaviour in Outlook – http://support.microsoft.com/kb/2553550

According to the KB article, by default, Microsoft Outlook 2010 and Microsoft Outlook 2013 archive different items based on the item type, as follows:

  • Email message: The received date or the last modified date and time, whichever is later.
  • Calendar item: The last modified date and time or the actual date that an appointment, event, or meeting is scheduled for, whichever is later.
  • Task: The completion date or the last modified date and time, whichever is later. Tasks that are not marked as completed are not archived. Tasks that are assigned to other users are archived only if the status is completed.
  • Note: The last modified date and time.
    Journal entry: The date when the journal entry is created or the last modified date and time, whichever is later.
  • Contact: Not archived.

To change this behaviour, you can create or modify the following registry setting.

Outlook 2010 – HKCU\Software\Microsoft\Office\14.0\Outlook\Preferences

Outlook 2013 – HKCU\Software\Microsoft\Office\15.0\Outlook\Preferences

Edit or Create a new DWORD value, ArchiveIgnoreLastModifiedTime, with a value of  1

IMPORTANT: You must restart Outlook after this change has been made.

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.

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.

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.