Disables NETBIOS communication outside of local subnet

Implement workarounds from https://support.microsoft.com/en-us/kb/3165191

After you install this security update, the following changes are applied:

•NETBIOS communication outside of the local subnet is hardened. Therefore, by default, some features that depend on NETBIOS (such as SMB over NETBIOS) will not work outside the local subnet. To change this new default behavior, create the following registry entry:

SUBKEY: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters
Value Name: AllowNBToInternet
Type: Dword
Value: 1
Default value of the flag: 0

• By default, WPAD resolution for auto proxy detection will not use NETBIOS. Therefore, if proxy detection depends on NETBIOS alone for WPAD resolution, it may fail. We recommend that you use the DHCP option or DNS for WPAD resolution instead of NETBIOS. To change this new default behavior, create the following registry entry.

Note This registry entry only applies for Windows 8.1 and earlier versions of Windows.
SUBKEY: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp
Value Name: AllowOnlyDNSQueryForWPAD
Type: DWORD
Value: 0
Default value of the flag: 1

•The default behavior of PAC file download is changed so that the client's domain credentials are not automatically sent in response to an NTLM or Negotiate Authentication challenge when WinHTTP requests the PAC file. This occurs regardless of the value of the fAutoLogonIfChallenged flag that is specified in WINHTTP_AUTOPROXY_OPTIONS. To change this new default behavior, create the following registry entry:

Note This registry entry only applies for Windows 8.1 and earlier versions of Windows. SUBKEY: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet
Settings\WinHttp
Value Name: AutoProxyAutoLogonIfChallenged
Type: DWORD
Value: 1
Default value of the flag: 0

Few objects are not available while running reports

Cause

This default limit of 500 objects is by design 

Resolution

-Create a registry key to manually set the maximum object limit in the Add Object Wizard. 

On the computer that's hosting the Operations Manager console, close all running instances 
of the console.
Start Registry Editor. Make sure that you're using the same user account that's used to 
run the console. 
Locate and then click the following registry subkey: 

HKEY_CURRENT_USER\Software\Microsoft\Microsoft Operations Manager\3.0\Console
Create a new DWORD value key, and save it as MaximumSearchItemLimit. Assign a value to this key that reflects the maximum number of objects that you want to display. For example, use a value of 1000 if you want to limit the maximum number of objects to 1000 instead of to the default limit of 500.

Location: HKEY_CURRENT_USER\Software\Microsoft\Microsoft Operations Manager\3.0\Console
Name: MaximumSearchItemLimit
Type: REG_DWORD
Value: 0 to 65535

Exit Registry Editor.
Reopened console 

LocalAccountTokenFilterPolicy

To disable UAC remote restrictions, follow these steps: 
1. Click Start, click Run, type regedit, and then press ENTER. 
2. Locate and then click the following registry subkey: 
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
3. If the LocalAccountTokenFilterPolicy registry entry does not exist, follow these steps: 
a. On the Edit menu, point to New, and then click DWORD Value. 
b. Type LocalAccountTokenFilterPolicy, and then press ENTER. 
4. Right-click LocalAccountTokenFilterPolicy, and then click Modify.
5. In the Value data box, type 1, and then click OK. 
6. Exit Registry Editor.

Update Scan errors of 0x8007000e

Analysis

=======

11:37:43:574+0800 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8007000e AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x8007000e.

2016-05-10 11:37:48:582 912 870 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8

2016-05-10 11:37:48:582 912 870 Report WER Report sent: 7.6.7600.320 0x8007000e 00000000-0000-0000-0000-000000000000 Scan 101 Managed

Solution

========

Please consider to upgrade all clients` agent to the latest first. [Windows7/2008R2 KB3138612] [Windows 8.1/2012R2 KB3138615]

Move or Delete a WSUS 4 Windows Internal Database (WID) on Windows Server

For Windows 2012 you will need the following updated information:

1. WSUS for Windows 2012 is up to version 4. If you read a blog post about 3 something you know (now?) the info is wrong.
2. The WSUS 4 WID database is in the following location: C:\Windows\WID\Data\SUSDB.mdf. Delete or move this database at the file level is not an option, you have to use the SQL Management Studio.
3. Install SQL Server Management Studio 2012 Express (Download SQLManagementStudio_x64_ENU.exe).
4. Once installed run SQL Management Studio 2012 with Run As Administrator.
5. Make the connection with Server Name: \\.\pipe\Microsoft##WID\tsql\query
6. Now you can use most posts to delete or move the WSUS database.

SCOM 2012 SP1,More than 5 asynchronous responses generates Event ID 21410

On the RMS use RegEdit to navigate to

HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Modules

Under this key create a new subkey called Global

Under the new Global subkey create another subkey called Command Executer Under the Command Executer subkey

create a new DWORD value AsyncProcessLimit

For the value of AsyncProcessLimit you can set a minimum of 0x00000001 (Strongly not recommended)

and a maximum of 0x00000064 (100)

(again definitely not recommended).

So, if you wanted to increase the number of async command notifications from 5 to 10 the key would look like:

HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Modules\Global\Command Executer\AsyncProcessLimit

REG_DWORD:0x0000000a

Error when trying to install DPM2012R2 with SQL 2014 database

Cause
Not supported

Resolution
Install DPM 2012 R2 on SQL 2012
Install UR6 and then upgrade SQL to 2014