When trying to install a second management server in a SCOM 2016 management group, after entering the OpsDB details, a few moments later the wizard would return to the SQL details screen.
A brief investigation revealed the following error in the installation log file (OpsMgrSetupWizard.txt this is your best friend for troubleshooting SCOM installations):
Info:Error while connecting to management server: The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection. Error: :Couldn’t connect to mgt server stack: : Threw Exception.Type: Microsoft.EnterpriseManagement.Common.ServerDisconnectedException, Exception Error Code: 0x80131500, Exception.Message: The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection.
First confirming that the Data Access service was in fact running on the original management server and that a connection could be made to the SDK.
It turns out that the two servers times were out of sync by more than 5 minutes causing a Keberos time skew. After correcting the server time the second management server installed with no issues.
SQL Server 2008 Replication – here
SQL Server 2012 Replication – here
SQL Server 2014 Replication – here
SQL Server 2014 Replication – here
SQL Server Analysis Services
SQL Server 2008 Analysis Services – here
SQL Server 2012 Analysis Services – here
SQL Server 2014 Analysis Services – here
SQL Server 2016 Analysis Services – here
SQL Server Reporting Services (Native Mode)
SQL Server 2008 Replication(Native Mode) – here
SQL Server 2012 Replication(Native Mode) – here
SQL Server 2014 Replication(Native Mode) – here
SQL Server 2014 Replication(Native Mode) – here
New in this version:
Important Notes About This Release
Please note that we implemented a new alerting rule for SQL Server event #18456 “Login failed” in this release. However, this rule may become rather noisy due to the fact that the target events appear quite frequently in some environments. The rule is enabled by default; thus, if it creates too many alerts in your environment, consider disabling it via the override. The ideal would be to resolve the underlying issues causing the alert but we understand this is not always a priority.
We are introducing a new monitor in this release (see the first bullet below) based on customer feedback. You have now a better solution for monitoring backups of AG databases.
SQL Server 2008-2016
Added new “Availability Database Backup Status” monitor in Availability Group to check the existence and age of the availability database backups (this monitor is disabled by default)
“Database Backup Status” monitor has been changed to return only “Healthy” state for the databases that are Always On replicas, since availability database backups are now watched by the dedicated monitor
Improved performance of DB Space monitoring workflows
Added new “Login failed” alerting rule for SQL Server event #18456
Fixed issue: “Active Alerts” view does not show all alerts
Fixed issue: DB space monitoring scripts fail with “Cannot connect to database” error.
Fixed issue: PowerShell scripts fail with “Cannot process argument because the value of argument ‘obj’ is null” error
Fixed issue: Alert description of “Disk Ready Latency” and “Disk Write Latency” monitors displays the sample count instead of the performance value that was measured
Fixed issue: Different file location info from “sys.master_files” and “sysfiles” causes error when Availability Group secondary database files are in different path
Fixed issue: “DB Transaction Log Free Space Total” rules return wrong data
Introduced minor updates to the display strings
Deprecated “Garbage Collection” monitor and the appropriate performance rule
Resource Pool Discovery is disabled by default for pools not containing databases with Memory-Optimized Tables
“XTP Configuration” monitor now supports different file path types (not only those starting with C:, D:, etc.)
Fixed issue: “Resource Pool State” view shows incorrect set of objects
Fixed issue: Invalid group discovery in SQL Server 2016 Always On
Updated the visualization library
SQL Server Dashboards
Increased the version number to comply with the current version of SQL Server MPs
SQL Server 2008-2016 Replication
Added Distributor name caching to Subscription discovery
Restricted the length of some string class properties
Improved the internal structure of SQL scripts storage
Fixed variable types in SQL scripts
Fixed connectivity issues in SmartConnect module
Introduced minor updates to the display strings
Updated the visualization library
SQL Server 2008-2016 Reporting Services
Reimplemented Instance seed discovery: replaced the managed module with a PowerShell script
Reimplemented Deployment seed discovery: added a retry policy and improved error handling
With the recent deprivation of SHA1 certificates in favour of the more secure SHA2 it’s important to know that SCOM uses SHA1 to manage workloads for cross platform monitoring (Unix / Linux).
Have no fear the MS SCOM team have released an article on how to replace your existsing SHA-1 certificates with the newer SHA256 certificates.
It is important to note that you will need to update your 2012 R2 environments to UR 12 and your 2016 environments to UR2 respectivly in order to use the new SHA256 certificates by default.
Another new management pack is out for Windows Server 2016, the MP for RDS v10.0.5.0 can be found here.
What this MP can do:
Remote Desktop Session Host: Remote Desktop Session Host (RD Session Host) enables a server to host RemoteApp programs or session-based desktops. Users can connect to RD Session Host servers in a session collection to run programs, save files, and use resources on those servers.
Remote Desktop Licensing: Remote Desktop Licensing (RD Licensing) manages the licenses required to connect to a Remote Desktop Session Host server or a virtual desktop. You can use RD Licensing to install, issue, and track the availability of licenses.
Remote Desktop Web Access: Remote Desktop Web Access (RD Web Access) enables users to access RemoteApp and Desktop Connection through the Start menu on a computer that is running Windows 8, Windows 7, or through a web browser. RemoteApp and Desktop Connection provides a customized view of RemoteApp programs and session-based desktops in a session collection, and RemoteApp programs and virtual desktops in a virtual desktop collection.
Remote Desktop Gateway: Remote Desktop Gateway (RD Gateway) enables authorized users to connect to virtual desktops, RemoteApp programs, and session-based desktops on an internal corporate network from any Internet-connected device.
Allows users to reconnect to their existing virtual desktops, RemoteApp programs, and session-based desktops.
Enables you to evenly distribute the load among RD Session Host servers in a session collection or pooled virtual desktops in a pooled virtual desktop collection.
Provides access to virtual desktops in a virtual desktop collection.
Remote Desktop Virtualization Host: Remote Desktop Virtualization Host (RD Virtualization Host) integrates with Hyper-V to deploy pooled or personal virtual desktop collections within your organization by using RemoteApp and Desktop Connection.