Server “Online – Performance Counters not started” Windows Server

If you have the following message, Performance counters not started, on the Server Manager on All Servers menu.

The solution is simple:

  1. Right Click on the Server Name
  2. Click on Start Performance Counters

Voilà

Windows 2016 or Windows 10 fail to perform an in-place upgrade

When performing a Windows Server 2012 in-place upgrade to Windows Server 2016, and you get an error pops up saying just that the upgrade has failed, the first thing to do is look at the logs.

Location of the Windows Server 2016 in-place upgrade: C:\$Windows.~BT\Sources\panther\setupact.log

More info regarding log files that are created when you upgrade to a new version of Windows: https://support.microsoft.com/en-us/help/928901/log-files-that-are-created-when-you-upgrade-to-a-new-version-of-window

If you got these two errors below, we have the solution for you.

Error    MOUPG CDlpActionProductKeyValidate::ReportDownlevelInstallChannel(2896): Result = 0x80070490[gle=0x00000002]

Error    MOUPG ProductKey: Failed to report Host OS channel to telemetry.[gle=0x00000002]

The system was not able to mount the WIM file, so what can be preventing this to happen?

A filter driver could be causing this error. To find the filter driver, run this:

fltmc filters


CBFLTFS4 is a CallBackFilter develped by Eldos.


According to Eldos:
Callback File System (CBFS) lets you create virtual file systems and disks that expose and manage remote data as if these data were files on the local disk.

Callback File System is an SDK (software development kit, a component for use in software development) for Windows® platform.

We have it in our remote application host server because we have installed Liquidware Labs’ ProfileUnity.

SOLUTION
We need to temporarily disable this filter driver.

  1. In order to do that we need to change the registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\cbfltfs4
    Value: Start
    Type: REG_DWORD
    To: 4

  2. Restart the machine

You can also run this command line:

Disable
reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\cbfltfs4 /v Start /t REG_DWORD /d 4 /f

Enable Startup automatically (To run after the machine is upgraded)

reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\cbfltfs4 /v Start /t REG_DWORD /d 0 /f

Reference: Charlie Chang Blog

Microsoft Office

Windows Server 2016 KMS error activating Microsoft Office 2013

After migrating the KMS server from a Windows Server 2008 for a new Windows Server 2016, I have run into some issues, and one of the issues was the activation of the Microsoft Office 2013. Let me show you guy how I have fix it.

Workaround

  1. Open the cmd with Admin Rights
  2. Run slmgr.vbs /ato for activating the Windows Server 2016 KMS.
  3. Run Office KMS setup (kms_host.vbs), and insert the Office KMS key
  4. Run “slmgr.vbs /ato 98EBFE73-2084-4C97-932C-C0CD1643BEA7” to activate the Office 2016
  5. Run “slmgr.vbs /ato 2E28138A-847F-42BC-9752-61B03FFF33CD” to activate the Office 2013

Now you need to wait for the KMS to receive more them 5 activation requests to start working. You can always perform the activativation requests through the Volume Activation Management Tool or by runing the following command on the client machine.

  1. Open the cmd with Admin Rights
  2. cd “C:\Program Files (x86)\Microsoft Office\Office13” – For Office 2013 32 bits
  3. Run this command: cscript OSPP.VBS /act

Microsoft Office Installation paths

Office 2010

32 bits: “C:\Program Files (x86)\Microsoft Office\Office14”
64 bits: “C:\Program Files\Microsoft Office\Office14”

Office 2013

32 bits: “C:\Program Files (x86)\Microsoft Office\Office15”
64 bits: “C:\Program Files\Microsoft Office\Office15”

Office 2016

32 bits: “C:\Program Files (x86)\Microsoft Office\Office16”
64 bits: “C:\Program Files\Microsoft Office\Office16”

a-team_A_verylitle.png

Error when try to disable one service “The parameter is incorrect”

To disable the OneSyncSvc_xxxx service, you need to edit the regedit. Please perform a backup of the regedit before doing any change.

When you try to disable the OneSyncSvc through mmc, you will get the following error:

2017-11-03_09h40_49

Services – The parameter is incorrect

If you try to disable through “sc config OneSyncSvc_xxxx start=disabled”, it will also not work and you will get the following error:

[SC] ChangeServiceConfig2 (delayed autostart flag) FAILED 87:

The parameter is incorrect.

Workaround

  1. Open the regedit
  2. Locate the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OneSyncSvc
  3. Change the “Start” REG_DWORD from 2 (Enable) to 4 (Disable)

2017-11-03_09h41_29.png

(mer…)