As the title suggests, after updating Windows 10 computers to 1803, users have reported slow RemoteApp sessions.
You can try disabling Remote FX, but user reports suggest this causes further issues.
The easiest fix is to copy mstsc.exe and mstscax.dll from a 1709 build and replace the files on 1803. We have confirmed this works.
This morning we awoke to screams from users not being able to login to our remote desktop servers.
KB4103727 has been released which switches a flag to protect against the CredSSP attack.
The quickest way to fix this to get your users working is to patch your domain controller with the May updates and use group policy to push out a change
You can manually add this to the registry for desktop clients
or via command line
reg add "HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters" /f /v AllowEncryptionOracle /t REG_DWORD /d 2
To fix this problem, the May updates need to be installed on all servers and workstations.
There is an in-the-wild exploit for Microsoft Office. A patch has been released. This exploit has turned up on Virtus Total today.
A remote code execution vulnerability exists in Microsoft Office software when the software fails to properly handle objects in memory. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user. If the current user is logged on with administrative user rights, an attacker could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
Exploitation of the vulnerability requires that a user open a specially crafted file with an affected version of Microsoft Office software. In an email attack scenario, an attacker could exploit the vulnerability by sending the specially crafted file to the user and convincing the user to open the file. In a web-based attack scenario, an attacker could host a website (or leverage a compromised website that accepts or hosts user-provided content) containing a specially crafted file designed to exploit the vulnerability. An attacker would have no way to force users to visit the website. Instead, an attacker would have to convince users to click a link, typically by way of an enticement in an email or instant message, and then convince them to open the specially crafted file.
Microsoft has made a bit of a boo-boo this week. Hopefully, you haven’t auto approved patches this week.
KB4041691 and KB4041676 were pushed as delta updates through WSUS. First published on Twitter, but now there is a Reddit thread on the issue https://www.reddit.com/r/sysadmin/comments/75o0oq/windows_security_updates_broke_30_of_our_machines/
If you run into this issue, you will need to boot into WinRE and use DISM to remove the update.
With all updates from Microsoft lately, I recommend you lab them first. Don’t take the risk.
With Server 2016, we’ve been getting a lot of these errors in the event log
This is caused by a task called Automatic-Device-Join which runs as a scheduled task whenever someone logs into a server (terminal server). This can cause a lot of events on the system.
Disable this task. This is used for Azure AD device joins. No idea why this is enabled by default.
Microsoft has released KB3203467 and KB3191898 which affects Outlook 2010 and 2007 respectively. Both of these patches will cause Outlook search to stop working.
I recommend you block these patches for your June cycle.
This is an annoying issue I’ve been trying to find the answer to for a couple of days.
I get a quick flash on my screen with a black box which looks like a command window. I finally had this happen on a slow enough computer where I could see where it was running from. See below.
To fix this issue, do the following:
- Open task scheduler from the start menu
- Find Microsoft Office under tasks
- Disable OfficeBackgroundTaskHandlerRegistration
A fix from Microsoft on this issue is underway.
We had a problem recent where Veeam 9.5 which was installed on Windows 2012 R2 trying to restore from Exchange 2016 on Server 2016 with ReFS datastores.
It turns out, Server 2012 R2 cannot recognise ReFS 3.1 which is on Server 2016. From the screenshot below, this backup is missing two drives which are ReFS:
When logging in to the Exchange server, you will see the correct drives
To fix this you really only have one option: Install Veeam B&R on Server 2016, or at the bare minimum, the mount points on Server 2016.
Once you have a Server 2016 mount point, you will be able to see the ReFS drives.
We have an old install of Sharepoint 2013 which has the March 2013 PU installed. A bunch of security updates slipped through which patched Sharepoint. You will get the following error:
Method 'Upgrade' in type 'Microsoft.SharePoint.WorkflowServices.WorkflowServiceApplicationProxy' from assembly 'Microsoft.SharePoint.WorkflowServices, Version=188.8.131.52, Culture=neutral, PublicKeyToken=71e9bce111e9429c' does not have an implementation.
This is apparently caused by newer security updates shipping with Sharepoint 2013 SP1 dll files. In order to fix this issue, download and install KB2880963. The install may take some time.
Over the weekend I’ve been installing Microsoft Server 2016 with Exchange 2016 on top. Once my SSL certificates were loaded, I got the following error when accessing OWA
I’ve seen this before on Apache. However, I was amused that this was an issue with Server 2016 since I thought that Microsoft would have disabled the Cipher suites used which cause this error. Apparently not.
A brute-force way to quickly fix this is to disable SPDY. To do this, open up the following registry key
Add the following two dword keys
It should look like the following
You can likely disable your offending cipher suites by following these guidelines.
Update 1: I solved my issue by disabling SHA and MD5 hashes on the Exchange server using IISCrypto. See below: