Windows 10 on WSUS Shows as Windows Vista

Please see below comment from Michael regarding Hotfix 3095113 which resolves this issue.

The changes you need to add to the SQL cmd file are:

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)



Delegate Moving User, Group and Computer Accounts Between Organizational Units in Active Directory

http://social.technet.microsoft.com/wiki/contents/articles/20747.delegate-moving-user-group-and-computer-accounts-between-organizational-units-in-active-directory.aspx

Object	Organizational Unit	Permission Tab	Apply to	Permission
User	Source Organizational Unit	Object	This object and all descendant objects	Delete User objects
		Properties	Descendant User objects	Write Distinguished Name
		Properties	Descendant User objects	Write name
		Properties	Descendant User objects	Write Name
	Destination Organizational Unit	Object	This object and all descendant objects	Create User objects
Group	Source Organizational Unit	Object	This object and all descendant objects	Delete Group objects
		Properties	Descendant Group objects	Write Distinguished Name
		Properties	Descendant Group objects	Write name
		Properties	Descendant Group objects	Write Name
	Destination Organizational Unit	Object	This object and all descendant objects	Create Group objects
Computer	Source Organizational Unit	Object	This object and all descendant objects	Delete Computer objects
		Properties	Descendant Computer objects	Write Distinguished Name
		Properties	Descendant Computer objects	Write name
		Properties	Descendant Computer objects	Write Name
	Destination Organizational Unit	Object	This object and all descendant objects	Create Computer objects

RunbookTester.config

To start the Runbook Designer as another user, click Start > All Programs > Microsoft System Center 2012 > Orchestrator, then hold down the SHIFT key and right click on Runbook Designer. Select Run as different user. Enter the account credentials of the other user, and Runbook Designer launches. You can then go to the runbook you want to test and then click Runbook Tester.
Note: Your alternate user must have rights in the Runbook Designer to see the runbook and must be part of the Orchestrator Users group in order to the runbook to load in the Runbook Tester.
You can verify that this account is being used to open and test the runbook by going to the following directory:

C:\Users\<ACCOUNT_NAME>\AppData\Local\Microsoft System Center 2012\Orchestrator

In there you should see an XML file that represents the runbook being edited, and a file named RunbookTester.config that shows that Runbook tester is being opened in that user context.

"Access Denied" in Runbook Designer when connecting to the Orchestrator

To add additional users and/or security groups to be authorized for remote access, launch and activation of the omanagement DCOM Server, follow the instructions below:

1. On the System Center Orchestrator Management Server, launch dcomcnfg to open up the Component Services applet.
2. Expand Component Services, then Computers, then My Computer.
3. Right-click My Computer, then click Properties.
4. Click the COM Security tab.
5. Under Access Permissions, click Edit Limits.
6. Click Add then enter details of the desired local or Active Directory based security group and click OK.
7. Click the new entry and then select the Allow checkbox for each permission then click OK.
8. Under Launch and Activation Permissions, click Edit Limits.
9. Click Add then enter details of the desired local or Active Directory based security group and click OK.
10. Click the new entry and then select the Allow checkbox for each permission then click OK.
11. Click OK to close the My Computer Properties dialog.
12. Expand My Computer, then click DCOM Config.
13. Locate omanagement, then right-click and choose Properties.
14. Click the Security tab.
15. Under Launch and Activation Permissions, click Edit.
16. Click Add then enter details of the desired local or Active Directory based security group and click OK.
17. Click the new entry and then select the Allow checkbox for each permission then click OK.
18. Under Access Permissions, click Edit.
19. Click Add then enter details of the desired local or Active Directory based security group and click OK.
20. Click the new entry and then select the Allow checkbox for each permission then click OK.
21. Click OK to save the changes.
22. Close the Component Services applet.
23. Open a Command Prompt.
24. Type sc stop omanagement and press Enter.
25. Type sc start omanagement and press Enter.

Once the Orchestrator Management Service (omanagement) is restarted, direct users and members of security groups that were added will now be able to successfully connect to the System Center Orchestrator Management Server using the Runbook Designer.

SCOM 2012 - The SDK service still used old database server which was defined in registry.

Symptom

After we upgraded SCOM to 2012R2 and move to a new ops DB server, the console failed to connect to connect to Data Access Service. We found that the Data Access Service was stopped after it's started automatically.

Cause

The SDK service still used old database server which was defined in registry.

Resolution

1. Update the “Reporting”(SCOM DW) settings in registry for the management servers to use the new scom DW server

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Reporting\

2. Update registry value “HKLM\Software\Microsoft\System Center\2010\Common\Database” to use the new server name and database name.

Getting Heartbeat failure Alerts for Unix Agents

Cause

Unix non-Privileged account didn't have the Unix account 

Resolution

1) Verified the configuration and collected the issue related information
2) Found that KB 2585542 is installed on RMS that breaks the WINRM communication 
3) Also found the registry workaround has been followed as per KB 2643584