Windows 10 Shows Windows Vista on Windows Server 2008R2 WSUS

請在WSUSDB裡面執行以下的語法，會將所有的Windows 10 Client Machine的OS Description 修改成Windows 10

UPDATE [SUSDB].[dbo].[tbComputerTargetDetail]

SET [OSDescription] = 'Windows 10'

WHERE [OSMajorVersion] = '10'

AND [OSMinorVersion] = '0'

AND [OldProductType] = '1'

AND ([OSDescription] <> 'Windows 10' or [OSDescription] IS NULL) 

Error 2912 (0x80070534) happened when a host was added to VMM.

Cause

=========
The error occurred after the AD service account was renamed, and then the account mismatches with that in VMM registry.

Resolution
==============

1. Login to VMM server machine, and check the below registry:

     HKLM\Software\Microsoft\Microsoft System Center Virtual Machine manager Server\Setup\VMMerviceAccount

Please make note of the value.

2. Compare it with the account in AD side, and make sure they are matching.

Applications that use the Cryptography API cannot validate an X.509 certificate in Windows Server 2003

Cause

========

One such case is Windows Server 2003 and the SHA-2 family of algorithms. Windows Server 2003does not understand SHA-2 family of algorithms.

https://support.microsoft.com/en-us/help/938397/applications-that-use-the-cryptography-api-cannot-validate-an-x.509-certificate-in-windows-server-2003

SCOM Workgroup Monitoring – Disable AD Integration

To disable during setup:
Install the SCOM agent with the following command line: MOMAgent.msi USE_SETTINGS_FROM_AD=0 MANAGEMENT_GROUP=“<Management Group Here>” MANAGEMENT_SERVER_DNS=<FQDN of management server here> /qb

To disable in the registry:
Open registry editor and nagivate to: “SYSTEM\CurrentControlSet\Services\HealthService\Parameters\ConnectorManager“.
Set the EnableADIntegration in the registry to ‘0′
Restart the HealthService (System Center Management)

Installing a server role on a server running a Server Core installation

Dism /online /enable-feature /featurename:Microsoft-Hyper-V
Dism /online /enable-feature /featurename:Microsoft-Hyper-V-Management-Clients /all

http://technet.microsoft.com/en-us/library/ee441260(v=ws.10).aspx

SCOM got a lot Monitoring failed event 4001 Part 2

SYMPTOMDate and Time: 2017/2/16 下午 04:46:07

Log Name: Operations Manager

Source: Health Service Script

Event Number: 4001

Level: 1

Logging Computer:

User: N/A

 Description:

Management Group: CDIBOPS. Script: Main Module: CPUUsagePercentDataSource.ps1 Version: 6.7.15.0 : Error occured during CPU Usage for SQL Instances data source executing. Computer:HDBSERVER1 Reason: Cannot add type. There were compilation errors. Position:325 Offset:29 Detailed error output: Cannot add type. There were compilation errors. -------- (0) : 未指定輸入 (1) : using System; -------- (0) : 找不到原始程式檔 'C:\Windows\TEMP\zsvypltn.0.cs' (1) : using System; 

CAUSE

There are some known errors to the 6.6.4.0 version of the SQL management packs, and one of them does mention “Cannot add type. Compilation errors occured.”
In a thread on the Technet Forums it was suggested that it has to do with rights, but focusing mainly on the SQL instance. What caught our eyes, however, was the fact that the script is using the C:\Windows\TEMP folder instead of its private one. And this seems to be because it is using a few .Net components that do some sort of JIT compilation.
We took a quick look using procmon, filtered on C:\Windows\TEMP\ and yes indeed. The monitoring account used is trying to create and delete its temporary files in that very folder.

work-around

The work-around is simple, but cumbersome. Just make sure that the assigned RunAs account have read/write/delete rights on C:\Windows\TEMP.

SCOM got a lot Monitoring failed event 4001

SYMPTOM

Customer is getting access denied for some registry keys from the sql account:

Detailed error output: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

Requested registry access is not allowed.
 

CAUSE

The SQLMPLowPriv, SQLDefaultAction account didn;t have the right permissions according to the MP guide.

Solution

I managed to find the reg key that needs permission:

SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Modules
 

Please give permissions on this reg key as this is a requirement from SCOM and should have had access to this key.