A “new” feature in the latest cumulative update for WIndows 10 automatically sets the default printer to the last used printer. This setting is turned on by default. This means that every time you use a printer, this printer becomes the default printer for the system.
While this might be a nice feature to have, it can potentially cause a waste of paper and some potentially “difficult” situations when documents are unwittingly printed to the wrong printer. ie, that receipt for the surprise birthday gift, or the 100 page draft document that was supposed to be printed to the paper optimiser print driver.
Fortunately, we can turn off this setting.
- Open up Printers & Scanners. Tip: Click on the Start Menu, and type “Printers & Scanners” in the search box.
- In the Printers & Scanners settings page, turn off the setting “Let Windows manage my default printer“.
The Essentials Server team have released a blog post to highlight which client versions are supported on currently supported Windows Server Essentials and Small Business Server 2011. The blog post can be read here – http://blogs.technet.com/b/sbs/archive/2015/07/23/client-connector-availability-with-windows-home-server-small-business-server-and-windows-server-essentials-for-supported-client-os.aspx
Basically, if you need to connect a Windows 10 client to Windows Server Essentials 2012 R2, which is probably the most common scenario, you will need to perform a manual client connector installation. A fix for the server is scheduled to be released on 17 November 2015.
Another common scenario would be the joining of the client connector for a Windows 10 client to Small Business Server 2011. In this case, 2 lines need to be added to the XML file on the server, which is located at C:\Program Files\Windows Small Business Server\Bin\WebApp\ClientDeployment\packageFiles\supportedOS.xml. Add the following 2 lines.
<OS Architecture="9" RequiredProductType="1" RequiredSuite="" ExcludedSuite="512" SPMinor="" SPMajor="" Build="10240" Minor="0" Major="10" Name="Windows 10, AMD64" id="9"/>
<OS Architecture="0" RequiredProductType="1" RequiredSuite="" ExcludedSuite="512" SPMinor="" SPMajor="" Build="10240" Minor="0" Major="10" Name="Windows 10, x86" id="10"/>
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.ServerState = 2
To Stop the SMTP Virtual Server, type the following:
$SMTP.ServerState = 4
Here is a great article on making an ISO image from the current Windows 10 Preview updates. This is handy when performing a clean install on your PC, as opposed to upgrading.
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
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.
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.
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.
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
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.