How to Change Skype for Business Spell Check Language

If you enable “Check Spelling as I type” (Options/IM) on Skype for Business (Lync) the spell check language is managed by Windows settings. You can quickly change it from the “Input Method” icon near the clock. On the example, I select english check spelling (with italian keyboard). If you are missing languages, add if from “Control Panel (Settings)/Region & Language”


How to Specify Office 2016 trusted locations on a per-application basis by using Group Policy

Depending on which application you want to configure, navigate to one of the following locations in the Group Policy Object Editor tree:

User Configuration/Administrative Templates/Microsoft Office Access 2016/Application Settings/Security/Trust Center/Trusted Locations

User Configuration/Administrative Templates/Microsoft Office Excel 2016/Excel Options/Security/Trust Center/Trusted Locations

User Configuration/Administrative Templates/Microsoft Office PowerPoint 2016/PowerPoint Options/Security/Trust Center/Trusted Locations

User Configuration/Administrative Templates/Microsoft Office Visio 2016/Tools|Options/Security/Trust Center

User Configuration/Administrative Templates/Microsoft Office Word 2016/Word Options/Security/Trust Center/Trusted Locations

In the details pane, double-click a trusted location that has not been configured, such as Trusted Location #1, Trusted Location #2, and so on.

In the Trusted Location Properties dialog box, click Enabled and do the following:

In Path, type the path to the folder that you want to trust.
In Date, type today’s date.
In Description, type a description of the trusted location.
Select the Allow subfolders check box if you want all subfolders within the trusted folder to also be trusted

If you specify a network share as a trusted location, you must enable the Allow Trusted Locations on the network setting.


How to install Office 2016 on Windows Server 2012R2

After installing Office 2016 on Windows Server 2012R2 with RDS services, trying to lunch one of the Office programs (example Excel), I received this error:

The program cant’ start because api-ms-win-crt-runtime-l1-1-0.dll is missing from your computer.  Try reinstalling the program to fix this problem.

To solve the problem you need to install KB2999226 update.

But unfortunately on my server, not only this patch was missing but also some required dependencies (Windows Update show me no updates missing!)
One dependency is KB2919355, that have other dependencies…

Here the patches and the steps to solve the issue. The patches order is important:

  1. KB2919442: is a prerequisite for Windows Server 2012 R2 Update and should be installed before attempting to install KB2919355
  2. KB2919355: there are multiple files available for this download and you need to install it on this order:
    1. clearcompressionflag.exe
    2. KB2919355
    3. KB2932046
    4. KB2959977
    5. KB2937592
    6. KB2938439
    7. KB2934018
  3. KB2999226: This is the required update for solve the CRT dll error.

After that Office 2016 application run without error.


How to find current Exchange Web Services (EWS) Url

If you need the URL of Exchange Web Services (EWS) on your infrastructures, with outlook running, hold CTRL and right-click on Outlook icon on Notification Bar. Select “Test E-mail Autoconfiguration…”. Click on “Test” button. When the test is finished, on “XML” tab you will find something like this:


How to share a VM with Gnome Boxes

By default Gnome Boxes use qemu:///session instead of qemu:///system because make desktop integration easier avoiding permission issues.

But if I what to share the same VM on the same desktop with another user (my wife), “qemu:///session” and “SELinux” can be an issue. On Fedora sVirt and SELinux is enabled by default. This make impossible to run the same VM from different user (not at the same time) due to Dynamic Resource Labeling.

The easiest solution I’ve found was to disable SELinux only for the domain “virt_t”.

First export your VM settings (if you already have a VM):

virsh dumpxml sharedVM > sharedVM.xml

Then move the VM image to a folder that both users can access (and write). In my case:


Set the owner and permission to the new VM folders:

chown root:users /home/Public/VMs

chmod 777 /home/Public/VMs

..and update sharedVM.xml according to the new path.

Import the exported VM on both users. Run this command for both account:

virsh create sharedVM.xml

Set Virt Domain in Permissive mode:

semanage permissive -a virt_t

Now you can start sharedVM with either one of the two users.