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.
You may or may not know that there is quite a cheap way to archive your backup jobs to tape, without actually having a tape drive.
While I was looking at options to store my backup jobs off-site, I researched a number of things:
- Buying a tape library
- Buying another enterprise NAS (Network Attached Storage)
- Using a JBOD (Just a bunch of disks) system like Microsoft Storage Spaces
All of these are expensive. All of these require some sort of hardware plus additional network and configuration. All of these are a pain in the ass.
Continue reading Veeam to AWS VTL (Virtual Tape Library) – Guide
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.
Recently while trying to import the AWS Virtual Tape gateway, I found the OVF template for VMWare was failing to install.
After getting pretty frustrated, I decided to open the OVA file in 7zip and extract the MF file.
What I found was the file contained a lot of whitespaces.
If you remove this whitespace and add this file back to the OVA archive, the OVA will deploy.
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.
I’ve just recently run in to a problem trying to access ESXi’s CLI from the console using IMM2 (Integrated Management Module). The KVM seems to be intercepting commands incorrectly. This seems to be the case for a number of KVM tools.
The normal command for accessing the CLI once enabled, is to press ALT+F1. This won’t work. You will need to hold down ALT+Space, release Space and press F1 while keeping ALT held down.
ALT+Space release space ALT+F1
I recently lost a host at one of my sites which have a failover policy set of IP Hash. No problem, connect a new host remotely and add it back to the network. Problem is, I cannot access this host from vCenter because of this policy. After posting on Reddit, someone gave me the following command to enter via CLI
You will need to enable the CLI from the console -> troubleshooting options.
esxcli network vswitch standard portgroup policy failover set -p "Management Network" -l iphash
Once this is set, you should now be able to see your host from vCenter.
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=126.96.36.199, 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.