Table of contents
TOC
Collapse the table of content
Expand the table of content

Release Notes for System Center 2016

CFreemanwa|Last Updated: 4/18/2017
|
11 Contributors

Applies To: System Center 2016

The following set of notes lists known issues and steps to mitigate the issue. These notes only apply to System Center 2016.

System Center 2016 - Data Protection Manager Release Notes

The following release notes apply to System Center 2016 - Data Protection Manager.

Silent Installation of System Center DPM with SQL Server 2008

Description: You cannot silently install DPM 2016 RTM on SQL Server 2008.

Workaround: Deploy DPM 2016 RTM on a version of SQL Server higher than 2008, or use the DPM 2016 Setup UI.

Remove-DPMDiskStorage commandlet may delete volumes with active or inactive backups

Description: When you try to remove volumes from DPM using Remove-DPMDiskStorage commandlet, if the volume has datasources being backed up actively or inactively, it can be removed too.

Workaround: Ensure that the volumes do not have datasources being actively or inactively protected before using the commandlet to remove them.

DPM 2016 on Windows Server 2016 slowing down and hanging due to high memory consumption

Description: Memory consumption on the DPM Server increases continuously, reaching about 90%, leading to the DPM server slowing down.

Workaround: The issue was found to lie in the underlying layers. The issue is fixed with KB4013429 and SC 2016 DPM UR2.

Hyper-V VMs are protected twice on VM upgrade

Description: If you upgrade your Hyper-V VM from Windows Server 2012 R2 to Windows Server 2016 to enable Resilient Change Tracking (RCT), a new VM representing the upgraded VM may appear in the Create Protection Group Wizard. The 2016 version of the VM may appear in addition to the 2012 R2 version of the VM.

Workaround: For the VMs that have not been upgraded, stop protection with Retain Data. After upgrading the VM, create a new protection group, Then, refresh the data sources and protect the VMs. This protects the VMs using Resilient Change Tracking (RCT).

Agent installation fails on Windows Server 2008, Windows Server 2008 R2

Description: If you are trying to protect Windows Server 2008, or Windows Server 2008 R2, agent installation may fail.

Workaround: Upgrade the Windows Management Framework (WMF) on the production server to 4.0. Download the WMF from https://www.microsoft.com/en-in/download/details.aspx?id=40855. Install WMF and then install the agent.

Restoring a previous version of an upgraded Hyper-V VM causes future recovery points to fail.

Description: If you upgrade a protected 2012 R2 Hyper-V VM to the 2016 version, then stop protecting the VM (but retain data), and then re-enable protection, if you then recover a 2012 R2 copy at the original location, further backups may fail.

Workaround: After recovery change the VM Version to 2016 followed by a Consistency Check.

Bare Metal Recovery protection failures

Description: If you configure Bare Metal Recovery (BMR) protection, the BMR protection job may fail with the message that the replica size is not sufficiently large.

Workaround: Change the default replica size for BMR datasources using the following registry key: Registry Path : HKLM\Software\Microsoft\Microsoft Data Protection Manager\Configuration ReplicaSizeInGBForSystemProtectionWithBMR (DWORD)

Re-protecting DPM DB after Upgrade to DPM 2016

Description: When you upgrade from System Center DPM 2012 R2 to System Center Data Protection Manager 2016, the DPM database name can change in some scenarios.

Workaround: If you are protecting DPM DB, please ensure that you enable protection for new DPM DB. Protection for the old DPM DB can be removed once DPM upgrade is validated.

Hyper-V RCT - recover as files for D-T backup fails

Description: Recovery of Hyper-V RCT VMs as files created directly on tape (D-T) fails. D-D-T backups will not exhibit this issue.

Workaround: Do Alternate Location Recovery as a VM, and then transfer those files to the desired location.

Recovery Points not being pruned, leading to an accumulation of Recovery Points

Description: DPM prunes the recovery points older than the retention range. During this process, for the recovery points getting pruned, DPM calculates the storage they consumed, which may take some time. The storage calculation hence delays pruning, which may lead to storage pressures.

Workaround: DPM can be configured to not calculate the size of the recovery points getting pruned. As a result of this, the pruning script can run fast and prune all the recovery points older than the retention range, relieving any storage pressures. Hence, the Storage consumed per data-source will not be updated once DPM is configured to not calculate the size while pruning. The storage consumption per volume will continue to reflect the correct values. The size calculation can be turned back on when needed by running a PowerShell script. To suppress size calculations and do complete size calculations again, you can use the following script:

Location: Program Files\Microsoft System Center 2016\DPM\DPM\bin\Manage-DPMDSStorageSizeUpdate.ps1

Script: Manage-DPMDSStorageSizeUpdate.ps1 -ManageStorageInfo [StopSizeAutoUpdate | StartSizeAutoUpdate | GetSizeAutoUpdateStatus | UpdateSizeInfo ] [-UpdateSizeForDS ] [-UpdatedDSSizeReport ] [-FailedDSSizeUpdateFile ]

  1. ManageStorageInfo: Specifies the kind of operation needed.

    StopSizeAutoUpdate: Stops the size calculations completely. Both UI and Powershell will not report sizes.

    StartSizeAutoUpdate: Resumes the size calculations. Immediately after enabling size calculations, please use “UpdateSizeInfo” (in the following options) to recalculate sizes for all the datasources, until which sizes reported in PowerShell and UI may not be correct.

    GetSizeAutoUpdateStatus: Tells whether size calculations are enabled or disabled.

    UpdateSizeInfo: This triggers the calculation of sizes and reports the size consumed by a datasource. This can be a long running operation, so please use it only when needed for scenarios as billing. Note that during this time, backups may fail with vhd mount errors.

  2. UpdateSizeForDS: Path to a text file with a list of Datasource IDs for which size needs to be calculated, with a datasourceID on each line. When not passed, size calculation is triggered for all the datasources. This may be used after using “UpdateSizeInfo” in “ManageStorageInfo”. To get the Datasource IDs of specific datasources, please use “Get-DPMProtectionGroup | Get-DPMDatasource | Format-table -Property Computer,name,ObjectType,Id”.

  3. UpdatedDSSizeReport: Path to a file which will store the updated sizes of the datasources when the script is run. When not passed sizes.csv file is created in the execution directory. This should be used after using “UpdateSizeInfo” in “ManageStorageInfo”.

  4. FailedDSSizeUpdateFile: Path to a file to store the Datasource IDs for the datasources for which the storage consumption couldn’t be calculated. This may happen due to reasons as ongoing backups. When not passed failedDS.txt file is created in the execution directory. This file can be given as input to “UpdateSizeForDS” to update the sizes of all the datasources. This should be used after using “UpdateSizeInfo” in “ManageStorageInfo”.

System Center 2016 - Operations Manager Release Notes

The following release notes apply to System Center 2016 - Operations Manager.

SharePoint integration with Operations Manager has to be recreated

Description: While using SharePoint to view Operations Manager data, the existing Web Console Dashboard URLs provided will not work and these Web parts have to be recreated with the steps below.

Workaround: Perform the following steps to setup SharePoint to view Operations manager data:

  1. Create a new page on SharePoint in which you want to display the Dashboard.
  2. Open the page and click edit and insert a new Web Part.
  3. In Web Part, under categories select “Media and Content” and under that select “Page Viewer” and click add.
  4. Edit the Web Part and select Web Page and enter the URL of the Operations Manager Web console dashboard.
  5. Append “&disabletree=true” at the end of the dashboard URL for disabling the tree view getting displayed on the SharePoint page
  6. Configure the appearance, layout, and Advance attribute of the SharePoint page.

Web Console might not work due to IIS becoming corrupt

Description: Web Console might throw an error “Could not load type ‘System.ServiceModel.Activation.HttpModule”.

Workaround: Add “HTTP Activation” to the role services of the OS. Then, on Server 2012 – run the following in an elevated command prompt: “C:\Windows\Microsoft.NET\Framework64\v4.0.30319>aspnet_regiis.exe -r”.

Anomalies in handling tables and bullets in Knowledge Articles

Description: If tables are inserted in a knowledge article, when re-editing the knowledge article the borders are not applied to the table. Similarly, if bullets are added in the knowledge article it gets converted to numeric bullets while re-editing. And, if there is a single bullet in the article then the article doesn’t get saved in the MP and the console throws error.

Workaround: None.

MSI based installation does not work for Nano agent

Description: MSI based installation is not supported for Nano agent. The agent can be installed from Discovery Wizard\PowerShell installer scripts.

Workaround: None.

Issues with uninstalling an update for Nano agent

Description: Uninstalling an update to Nano agent is not possible.

Workaround Only option is to uninstall the Nano agent, then install the RTM version + desired update.

Issues with updates of Nano agent

Description: Updates to Nano agent will not be pushed from Windows Update. To update Nano agent you Will need to either download the available update and install using the PowerShell update scripts; or trigger a repair from an updated Management server.

Workaround: None.

Unable to override the path or folder for Nano agent installation

Description: Nano agent is always installed to the following path: ‘%SystemDrive%\Program Files\Microsoft Monitoring Agent’; the agent installation folder cannot be overridden.

Workaround: None.

Inconsistencies in push install experience of Nano agent

Description: The Discover Wizard status dialog closes but agent stays in pending state in console for some time until the installation fails or completes successfully. Installation may fail, and you will need to refer to the setup log file for further information to troubleshoot.

Workaround: None.

Inconsistencies in push uninstall experience of Nano agent

Description: When performing a Push uninstall from the Operations console, the status dialog (which shows progress status) shows the uninstall completed successfully, but the agent uninstall is still being performed. Uninstall may fail and refer to the setup log file for further information to troubleshoot.

Workaround: None.

ACS is not working for Nano agent

Description: ACS is not working for Nano agent, in some cases. There are issues in certain scenarios.

Workaround: None.

Client-side monitoring (CSM) alerts might stop flowing from the System Center Operations Manager management server

Description: The update sequence of System Center Operation Manager management server may cause an issue with the client-side monitoring alerts collection from the management server. System Center Operations Manager agents are not affected. Likelihood of occurrence: Medium.

Workaround: Restart the "Microsoft Monitoring Agent" service on System Center Operations Manager management server.

After updating System Center Operations Manager server or agent, Application performance monitoring (APM) events, client-side monitoring (CSM) events, and APM alerts might stop flowing from the monitored hosts

Description: The update sequence of System Center Operations Manager agent may cause an issue with the following:

• Client-side monitoring (CSM) events and alerts collected on the host.

• Application Performance Monitoring (APM) events and alerts collected on the host. System Center Operations Manager management server is not affected.

Workaround: Restart the "Microsoft Monitoring Agent" service on the System Center Operations Manager agent-managed computer that is experiencing the issue.

Application performance monitoring (APM) for Windows services is not supported in System Center - Operations Manager on computers where Application Insights Status Monitor is installed.

Description: Application performance monitoring (APM) workflow fails to process monitoring configuration for .NET Windows services on the computer if Application Insights Status Monitor and the System Center - Operations Manager agent are both installed.

Workaround: Uninstall Application Insights Status Monitor.

Namespace values for performance tracking will be ignored

Description: Setting the Namespace value for performance tracking when tracking a custom namespace in .NET Applications Performance Monitoring (APM) will be ignored.

Workaround: Set both the exception tracking and performance tracking settings to include the same custom namespaces.

Using sudo elevation with Solaris operating systems requires a configuration change if sudo executable is not in an expected path

Description: If you want to use sudo elevation on a computer running Solaris, and the sudo executable is not in the expected path, you will need to create a link to the correct path. Operations Manager will look for the sudo executable in the path /opt/sfw/bin, and then in the path /usr/bin. If sudo is not installed in one of these paths, a link is required.

Workaround: The UNIX and Linux agent installation script creates the symbolic link /etc/opt/Microsoft/scx/conf/sudodir to the folder expected to contain sudo. The agent uses this symbolic link to access sudo. The installation script automatically creates the symbolic link, so no action is needed for standard UNIX and Linux configurations. However if sudo is installed in a non-standard location, you should change the symbolic link to point to the folder where sudo is installed. If you change the symbolic link, its value is maintained for uninstall, re-installation, and upgrade operations with the agent.

Operations Manager Console will stop responding if you attempt to resolve a dependency while importing a management pack

Description: When you click Import Management Packs from the Administration workspace of the Operations Manager Operations console, the console will display the Resolve button if the Management Pack is dependent on another Management Pack. If you click Resolve you will see the Dependency Warning. If you click the Resolve button in the Dependency Warning dialog, the Operations console will stop responding.

Workaround: Install the Update for System Center 2016 - Operations Manager. See the Knowledge Base article 3117586 for specific instructions.

Telemetry data may be erroneously sent when the "Usage and Connectivity Data" setting is set to "False"

Description:If two operators have Operations Manager consoles open and one sets the Usage and Connectivity Data setting to "Do not send data" data may continue to flow to Microsoft until the second user closes and reopens their instance of the Operations manager console.

Workaround: Restart all Operations Manager console sessions after making changes to the Usage and Connectivity setting.

Description:When a new component such as a management server or gateway server are added to an existing Operations Manager environment, usage information about the setup process is sent to Microsoft even though the Usage and Connectivity Data setting is set to "Do not send data". After the component is added, no further usage data will be sent to Microsoft from the component.

Workaround: None

Namespace values for performance tracking will be ignored

Description: Setting the Namespace value for performance tracking when tracking a custom namespace in .NET Applications Performance Monitoring (APM) will be ignored.

Workaround: Set both the exception tracking and performance tracking settings to include the same custom namespaces.

Operations Manager web console is not compatible with Microsoft Edge web browser

Description: When you open the Operations Manager web console from the Windows 10 Start Menu the console will open in the Microsoft Edge web browser. This will result in an error.

Work around: Open the Operations Manager web console with Internet Explorer. Internet Explorer is available from Windows Accessories sub-menu.

Launching the Operations Manager Web Console may result in a blank screen

Description: When you first open the Operations Manager web console you may encounter a blank screen.

Work around: To resolve the issue:

  1. Click on "Configure" button.
  2. When prompted to Run or Save SilverlightClientConfiguration.exe, click Save.
  3. Run SilverlightClientConfiguration.exe.
  4. Open the file properties of exe (right-click) and open the Digital Signatures tab.
  5. Select the certificate with Digest Algorithm as sha256 and click on Details.
  6. In the Digital Signature Details dialog box, Click on View Certificate.
  7. In the dialog box which appears next, click on Install Certificate.
  8. In the Certificate Import Wizard, Set store location as - Local Machine. Click Next.
  9. Select the option - "Place all certificates in the following store" Browse to Trusted Publishers.
  10. Click Next and then Finish.
  11. Refresh the Browser

System Center 2016 - Orchestrator and Service Management Automation Release Notes

The following release notes apply to System Center 2016 - Orchestrator and Service Management Automation .

Sending telemetry data for SMA and SPF to Microsoft can only be turned off via PowerShell

Description: The default telemetry data setting is to send data to Microsoft. Since Service Management Automation and Service Provider Foundation do not provide a user interface, you can only change this setting for Service Management Automation or Service Provider Foundation with a PowerShell cmdlet.

Work around: See Knowledge Base article 3096505 for detailed instructions on how to stop sending telemetry data to Microsoft for Service Management Automation or Service Provider Foundation.

Orchestrator Web Console is not compatible with the Microsoft Edge web browser

Description: You cannot open the Orchestrator web console with the Microsoft Edge web browser.

Work around: Open the Orchestrator web console with Internet Explorer.

Orchestrator - Runbook Designer's About Page shows the version as System Center 2016 Technical Preview

Description: In the Runbook Designer when you click on Help -> About, the version is shown as System Center 2016 Technical Preview.

Work around: You can validate that you have latest version using the version number. If you have the RTM version, the build numbers are as follows:

  • Runbook Designer - 7.3.149.0
  • Management Server - 7.3.149.0

When you apply Update Rollup 1 (GA update), the build numbers are as follows:

  • Runbook Designer - 7.3.149.0
  • Management Server - 7.3.164.0

System Center 2016 - Service Manager Release Notes

The following release notes apply to System Center 2016 - Service Manager.

SQL Server 2014 Cardinality Estimation might affect the performance of Service Manager 2016

Description: If your Service Manager database is running on SQL Server 2014 with the cardinality estimator set to the SQL Server 2014 version you may experience slow performance.

Workaround: Switch the Cardinality Estimator (CE) for the SQL Server to use the SQL Server 2012 version. See the following article for more information on changing the Cardinality Estimator: New functionality in SQL Server 2014 - Part 2 - New Cardinality Estimation.

Microsoft Visual C++ 2012 Redistributable is a pre-requisite for installing Service Manager 2016 Authoring Tool

Description: Microsoft Visual C++ 2012 redistributable should be installed before deploying Service Manager 2016 Authoring Tool.

Workaround: None

Create Exchange Connector wizard might crash

Description: Creating a new Exchange Connector via Service Manager 2016 console throws an exception if the admin clicks on the "Test Connection" button in the "Server Connection" pane of "Create Exchange Connector" wizard.

Workaround: Download and install the Microsoft.SystemCenter.ExchangeConnector.dll.exe from here.

Browsing domain in AD connector wizard raises error

Description: Error is raised on clicking “Browse” while choosing Domain or OU in AD connector wizard of Service Manager 2016 console.

Workaround: Install Microsoft Visual C++ 2012 Redistributable on the affected machine.

Creating a new Software type configuration item throws the error - "The form could not be submitted for the following reasons: Property Is Virtual Application must be set"

Description: The property “Is Virtual Application" in create Software configuration item form is mandatory, but the asterix (*) symbol is not shown for this property. Hence on clicking "Ok" or "Apply" button without setting this field throws an error and makes the form unusable.

Workaround: Reopen the create Software configuration item form, and fill all the details including the field "Is Virtual Application", before clicking on "Ok" or "Apply" button.

Manual steps to configure remote SQL Server 2014 Reporting Services

Description: During deployment of the Service Manager data warehouse management server, you can specify the server to which Microsoft SQL Server Reporting Services (SSRS) will be deployed. During setup, the computer that is hosting the data warehouse management server is selected by default. If you specify a different computer to host SSRS, you are prompted to follow a procedure in the Deployment Guide to prepare the server. However, if you use SQL Server 2014, you should instead use the following information to prepare the remote computer to host SSRS.

  • Copy Microsoft.EnterpriseManagement.Reporting.Code.dll from the Service Manager installation media to the computer that is hosting SSRS.

  • Add a code segment to the rssrvpolicy configuration file on the computer that is hosting SSRS.

  • Add an Extension tag to the existing Data segment in the rsreportserver configuration file on the same computer.

If you used the default instance of SQL Server, use Windows Explorer to drag Microsoft.EnterpriseManagement.Reporting.Code.dll (which is located in the Prerequisites folder on your Service Manager installation media) to the folder \Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportServer\Bin on the computer that is hosting SSRS. If you did not use the default instance of SQL Server, the path of the required folder is \Program Files\Microsoft SQL Server\MSRS12.\Reporting Services\ReportServer\Bin. In the following procedure, the default instance name is used.

To copy the Microsoft.EnterpriseManagement.Reporting.Code.dll file

  1. On the computer that will host the remote SSRS, open an instance of Windows Explorer.

  2. For SQL Server 2014, locate the folder \Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportServer\Bin.

  3. Start a second instance of Windows Explorer, locate the drive that contains the Service Manager installation media, and then open the Prerequisites folder.

  4. In the Prerequisites folder, click Microsoft.EnterpriseManagement.Reporting.Code.dll, and drag it to the folder that you located previously.

To add a code segment to the rssrvpolicy.config file

  1. On the computer that will be hosting SSRS, locate the file rssrvpolicy.config in the following folder:

    • For SQL Server 20014, locate \Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportServer.
  2. Using an XML editor of your choice (such as Notepad), open the rssrvpolicy.config file.

  3. Scroll through the rssrvpolicy.config file and locate th code segments. The following code shows an example of a segment.

    
       class="UnionCodeGroup"
       version="1"
       PermissionSetName="FullTrust">
       <IMembershipCondition
          class="UrlMembershipCondition"
          version="1"
          Url="$CodeGen$/*"
       />
    
  4. Add the following segment in its entirety in the same section as the other segments.

    
       class="UnionCodeGroup"
       version="1"
       PermissionSetName="FullTrust"
       Name="Microsoft System Center Service Manager Reporting Code Assembly"
       Description="Grants the SCSM Reporting Code assembly full trust permission.">
       <IMembershipCondition
          class="StrongNameMembershipCondition"
          version="1"
          PublicKeyBlob="0024000004800000940000000602000000240000525341310004000001000100B5FC90E7027F67871E773A8FDE8938C81DD402BA65B9201D60593E96C492651E889CC13F1415EBB53FAC1131AE0BD333C5EE6021672D9718EA31A8AEBD0DA0072F25D87DBA6FC90FFD598ED4DA35E44C398C454307E8E33B8426143DAEC9F596836F97C8F74750E5975C64E2189F45DEF46B2A2B1247ADC3652BF5C308055DA9"
    />
    
  5. Save the changes and close the XML editor.

To add an Extension tag to the Data segment in the rsreportserver.conf file
  1. On the computer hosting SSRS, locate the file rsreportserver.config in the following folder:

    • For SQL Server 2014, locate \Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportServer.
  2. Using an XML editor of your choice (such as Notepad), open the rsreportserver.config file.

  3. Scroll through the rsreportserver.config file and locate the code segment. There is only one code segment in this file.

  4. Add the following Extension tag to the code segment where all the other Extension tags are:

    <Extension Name="SCDWMultiMartDataProcessor" Type="Microsoft.EnterpriseManagement.Reporting.MultiMartConnection, Microsoft.EnterpriseManagement.Reporting.Code" />
    
  5. Save the changes and close the XML editor.

Service Manager console installed on a VMM Server causes VMM connector failure

Description: If the Service Manager console is installed on the same server as VMM, then you cannot use that Service Manager console to create a VMM connector to that VMM server.

Workaround: None, however you can use a different Service Manager console to create the VMM connector.

Data Warehouse Setup Might Fail if the Database or Log Path Includes a Single Quotation Mark Character

Description: During Setup, if you specify a database or log path that includes a single quotation mark character ('), Setup might fail.

Workaround: None. The path that you specify cannot include a single quotation mark character.

Setup Might Fail if the Service Manager Authoring Tool Has Been Installed

Description: Setup might fail if you have previously installed any version of the Service Manager Authoring Tool.

Workaround: Remove the Service Manager Authoring Tool, and then retry Setup.

Setup Does Not Install the Report Viewer Language Pack

Description: Setup includes a prerequisite checker that checks for and - if necessary, installs - the Microsoft Report Viewer. However, Setup does not install the Report Viewer Language Pack, which makes the Microsoft Report Viewer compatible with Windows operating systems that are configured to use languages other than English.

Workaround: If your system is configured to use a language other than English, you should manually install the Report Viewer Language Pack for that language.

Service Manager Setup Fails if a SQL Server Instance Contains a $ Character

Description: If you attempt to install Service Manager using a named Structured Query Language (SQL) instance that contains a dollar sign ($) character, Setup fails.

Workaround: Use a SQL instance that does not contain the $ character in its name.

Orchestrator Connector Account Password Cannot Contain $ Characters

Description: If the Orchestrator connector account password contains a $ character, the sync job completes, however runbooks are not updated in the Service Manager database.

Workaround: If your Orchestrator connector account password contains a $ character, change the password to one that does not include the $ character.

Information Linked from Setup Might Not Display Localized Content

Description: Information that is linked from Setup to the Setup log and to technical documentation might not display localized content. Setup logs in Service Manager are available in English only. Technical documentation is available in a variety of localized languages. Where available, localized technical documentation is displayed on TechNet; however, not all languages are available.

Workaround: None.

Errors Might Occur When You Modify or Delete Service Request Template Items

Description: When you create a service request using a request offering template and you modify or delete activities that are contained in the template, various errors might occur that prevent you from saving the service request.

Workaround: When you create service requests, avoid modifying or deleting activities that are contained in a request offering template. If necessary, you can create a new request offering template with only the activities that are necessary and configured properly for your intended use.

Configuring the Reporting Server Might Take a Long Time

Description: When you install the data warehouse, validation of the default web server URL might take as long as 25 seconds to complete.

Workaround: None.

Double-Byte Characters Are Sent Incorrectly to Search Provider

Description: When you perform a knowledge search and you type double-byte characters in the Search Provider box, they are not sent correctly to the search website. Instead, erroneous characters are sent.

Workaround: None.

Sorting Knowledge Articles by Date Does Not Work

Description: When you try to sort knowledge articles by date, sorting does not work.

Workaround: None.

Do not change Active Directory group expansion selection after upgrade until the connector has run at least one time.

Description: When upgrading from System Center 2012 R2 - Service Manager to System Center 2016 - Service Manager, do not change the AD group expansion selection value in any AD connector (if it is OFF, let it remain OFF, if it is ON, let it remain ON), until the connector has run at least one time after the upgrade.

Workaround: None.

System Center 2016 - Virtual Machine Manager Release Notes

The following release notes apply to System Center 2016 - Virtual Machine Manager.

Upgrading a cluster's functional level does not refresh the platform information for a File Server

Description: If you upgrade the functional level for a cluster that includes a file server the new platform information will not be automatically updated in the VMM database.

Workaround: After upgrading the cluster's functional level, refresh the storage provider for the File Server. This will refresh the platform information.

Trying to patch a Storage Spaces Direct cluster with VMM will fail

Description: Patching of a Storage Spaces Direct cluster (either hyper-converged or disaggregated) using VMM is not supported and trying to do it using VMM may cause data loss .

Workaround: The recommendation is to patch the Storage Spaces Direct clusters outside of VMM using Cluster Aware Updating (CAU) functionality provided by Windows Server .

Cluster Rolling Upgrade (CRU) of a Windows Server 2012 R2 host cluster to Windows Server 2016 Nano Server-based host cluster will fail

Description: When you try to upgrade the nodes of a Windows Server 2012 R2 cluster to Windows Server 2016 - Nano Server-based hosts using Cluster Rolling Upgrade functionality in VMM, the upgrade will fail with the below error:

*Error (20406) VMM could not enumerate instances of class MSFT_StorageNodeToDisk on the server . Failed with error MI RESULT 7 The requested operation is not supported.

Recommended Action Ensure the provider is running, and then try the operation again*

Note that rolling upgrade from Windows Server 2012 R2 to Windows Server 2016 Full Server works fine. This issue is specific to Nano.

Workaround: Manually upgrade the Windows Server 2012 R2 host cluster to Nano outside of VMM.

Adding a cluster via the VMM Administrative console may result in an error

Description: When you add a cluster as a resource in the VMM Administrative console you may receive an error stating "There were no computers discovered based on your inputs".

Workaround: Select OK, close the error dialog box, and retry adding the cluster.

Promoting a VM on local storage might fail

Description: You create a VM on local storage, start it, and create checkpoints. If you then try to migrate and promote to VM to highly available in a cluster, migration might fail.

Workaround: Before you run the migration, delete the running checkpoint, and stop the VM.

Migrating a VM from CSV storage to LUN storage might fail

Description: You create a highly available VM using CSV storage. Then you add a LUN as available storage on the cluster, and migrate the VM from CSV to the LUN. If the VM and LUN storage are on the same node, the migration will succeed. If they're not, migration will fail.

Workaround: If the VM isn't on the cluster node on which the LUN storage is registered, move it there. Then migrate the VM to the LUN storage.

Shielding a VM may result in an error

Description: If you shield an existing non-shielded VM or if you create a shielded VM from a non-shielded template, the job might fail with the error: Error (1730) The selected action could not be completed because the virtual machine is not in a state in which the action is valid.

The failure happens at the last step of the job in which the VM is shutdown after the shielding is completed, the VM gets shielded properly and is usable.

Workaround: Repair the VM with ignore option.

VMM does not immediately reflect changes to security properties

Description: Changing the secure boot properties of a Gen 2 VM or disabling/enabling vTPM for a shielded VM, outside of VMM, does not immediately reflect in VMM.

Workaround: Manually refresh the VM in VMM to ensure the changes done outside of VMM are reflected.

Storing a VM in VMM Library fails if you change the default port for BITS(443) while configuring the VMM Server

Description: Storing a VM in VMM Library will fail with the error below if you change the default port for BITS (443) while configuring the VMM Server. Error (2940) VMM is unable to complete the requested file transfer. The connection to the HTTP Server <name> could not be established.

Workaround: Manually add the new port number to the Windows Firewall exceptions list of the Nano host using the below command: netsh advfirewall firewall add rule name="VMM" dir=in action=allow localport= protocol=TCP

VMM does not support creation of VM Templates from a Nano Server-based VM.

Description: When you try to create a VM template from a Nano Server-based VM, you will receive the below error: *Error (2903) VMM could not locate the specified file/folder '' on the '' server. This file/folder might be required as part of another object. The system cannot find the file specified (0x80070002)

Recommended Action Ensure that you have specified a valid path parameter, and that all necessary files/folders are present. Try the operation again.*

Workaround: Create a VM template from scratch using a Nano Server VHD.

VMM requires manual steps to be performed to add a Nano Server-based host in an Untrusted domain to VMM

Description: When you try to add a Nano Server-based host in an untrusted domain to VMM, it fails.

Workaround: Execute the below steps on the Nano Server-based host and then try to add it as an Untrsuted host to VMM:

  1. Enable WINRM over Https on Nano Server-based host:

    New-Item -Path WSMan:\LocalHost\Listener -Transport HTTPS -Address * -CertificateThumbPrint $cert.Thumbprint –Force

  2. Create Firewall exception on Nano Server-based host to allow WINRM over https:

    New-NetFirewallRule -DisplayName 'Windows Remote Management (HTTPS-In)' -Name 'Windows Remote Management (HTTPS-In)' -Profile Any -LocalPort 5986 -Protocol TCP

VMM does not support addition of Nano Server-based Perimeter hosts

Description: When you try to add a Nano Server-based Perimeter host to VMM using the "Add Resource" Wizard, addition of the perimeter host will fail.

Workaround: Execute the below steps on the host and instead of adding the host as a Perimeter host, add it as a host in an Untrusted domain (Second option in the Add Hyper-V Hosts & Clusters wizard)

  1. Enable WINRM over Https on Nano Server-based host:

    New-Item -Path WSMan:\LocalHost\Listener -Transport HTTPS -Address * -CertificateThumbPrint $cert.Thumbprint –Force

  2. Create Firewall exception on Nano Server-based host to allow WINRM over https:

    New-NetFirewallRule -DisplayName 'Windows Remote Management (HTTPS-In)' -Name 'Windows Remote Management (HTTPS-In)' -Profile Any -LocalPort 5986 -Protocol TCP

Description: When selecting Roles & Features for a Service Template, the Guest OS Profile (i.e. Windows Server 2016) doesn't differentiate between Core, Nano Server and Desktop. Selecting Roles/Features that do not apply to Core/Nano Server-based Guest OS, will result in failure during deployment.

Workaround: There is no workaround, do not include these roles & features in your service template.

Servicing a service post an upgrade from VMM 2012 R2 to VMM 2016 will not update the VMM guest agents

Description: When you upgrade your VMM environment from 2012 R2 to 2016 with existing service deployments and then service those services, VMM 2016 guest agents will not get updated on the VMs that were part of the service deployment. There is no functionality impact due to this.

Workaround: Manually install the VMM 2016 guest agent.

Attempt to join a Nano Server-based VM to a domain while deploying the VM will fail, the VM will get deployed but will not join the domain

Description: While deploying a Nano Server VM, if you try to join the VM to a domain by specifying the domain join information on the OS Configuration page of the VM deployment Wizard, VMM will deploy the VM but will not join it to the specified domain.

Workaround: After the VM is deployed, manually join the VM to the domain. For more details on how to do this, see the 'Joining Nano Server to a domain' section in the Getting Started with Nano Server guide.

VMM throws an error when you start a VM configured for Start Ordering

Description: Windows Server 2016 has a new functionality called VM Start Ordering which can be used to define the order in which dependent VMs will get started. This functionality is not exposed through VMM today. However, if you have configured VM start ordering outside of VMM, VMM does honor the order in which the VMs will start. It however throws the below false positive error which should be ignored *Error (12711) VMM cannot complete the WMI operation on the server because of an error: [MSCluster_ResourceGroup.Name=] The group or resource is not in the correct state to perform the requested operation. The group or resource is not in the correct state to perform the requested operation (0x139F)

Recommended Action Resolve the issue and then try the operation again.*

Workaround: Ignore the error as the VMs will start in the correct order.

Bare metal deployment of hosts may fail after VMM in an HAVMM setup is upgraded from VMM 2012 R2 to VMM 2016

Description: In a Highly Available (HA) VMM environment, after a VMM upgrade, VMM may incorrectly update the Windows Deployment Services (WDS) registry key, HKLM\SYSTEM\CCS\SERVICES\WDSSERVER\PROVIDER\WDSPXE\PROVIDES\VMMOSDPROVIDER, to 'HOST/VIRT-VMM-1' instead of 'SCVMM/VIRT-VMM-1'. This will lead to failure of bare metal deployment of hosts & clusters.

Workaround: Manually change the registry entry for HKLM\SYSTEM\CCS\SERVICES\WDSSERVER\PROVIDER\WDSPXE\PROVIDES\VMMOSDPROVIDER to 'SCVMM/VIRT-VMM-1' and then try bare metal deployment of hosts & clusters.

Cluster Rolling Upgrade in VMM does not live migrate VMs that are not Highly Available

Description: When you try to do a rolling upgrade of your Windows Server 2012 R2 cluster to Windows Server 2016 using VMM, it does not live migrate the virtual machines which are not high-available and moves them to saved state.

Workaround: Before kicking off cluster rolling upgrade, either make all the VMs in the cluster highly available or manually live migrate the non highly available VMs to nodes which are not getting upgraded as part of Cluster Rolling Upgrade

Trying to import a Console add-in as a non-administrator to VMM will fail

Description: If you are not an administrator and you try to import a console add-in to VMM, the console will crash. This is because the console add-in is stored at location “C:\Program Files\” which only administrators have access to.

Workaround: Store the console add-in at a location where the user has write access, for example “C:\user<username>\”, and then try importing the add-in.

Microsoft System Center 2012 displayed in Start Menu

Description: After you have installed UR2 or a later patch and if your environment had UR1 at any point of time, you will see Microsoft System Center 2012 displayed in Start Menu. This is only a UI issue and has no functional impact.

Workaround: You need to delete the "Microsoft System Center 2012" folder under "Program Menu" folder so that, "Microsoft System Center 2016" entry becomes visible.

SSAS integration broken with Virtual Machine Manager and Operations Manager 2016 Update Roll up 1

Description: If you are using VMM and OM 2016 Update Roll up 1, you will not be able to configure SSAS for SQL Server.

Workaround: Please download latest VMM Management Packs from download center. The updated MPs will also be available with Update Roll up 2.

Dynamic IP not supported for NC managed Logical Networks

Description: Although possible through VMM, Dynamic IP configuration for VMs connected to Network Controller managed Logical Networks is not supported by network Controller.

Workaround: You should configure static IP for such VMs

SET switch deployed OOB shows up an ‘Internal’ in VMM

Description: Once you deploy an SET switch out of band from VMM and later on-board the switch into VMM. VMM UI shows the switch type as ‘Internal’. This, however, doesn’t impact the functionality of the switch.

Workaround: None

Host agent status after upgrade

Description: When SCVMM updates the host agent, it generates a new certificate for the host. Because of this certificate update, NC server certificate and Host certificate don't match.

Workaround: This can be remediated by repairing the Host from the host status page

LACP teamed switch non-functional after upgrade

Description: LACP team configured in a Logical Switch gets into non-functional state after upgrade to RTM.

Workaround: you can either redeploy the Switch or remove and re-add a member pNIC of the team

Backend NIC connectivity for SLB MUX

Description: Backend NIC connectivity of SLB MUX may get impacted after VM migration.

Workaround: Users can opt for scale in/scale out of the SLB MUX VM as a workaround.

Publishing SLBM VIP after upgrade

Description: Customers after upgrading from TP5 to RTM will hit this issue if they have published VIP pools in TP5.

Workaround: After upgrade to RTM they need to publish the VIP pools again after upgrading to RTM

.CNG based CA cert not supported

Description: If you are using CA provided certificates, you will not be able to use .CNG certificates for VMM based SDN deployment.

Workaround: use other formats for CA based certs

vNIC connected to Network Controller managed network must be restarted on IP Address change

Description: If there is a change in assigned IP address on any of the vNICs that are connected to a Network Controller managed VM Network, you need to manually restart the associated vNIC(s).

Workaround: No workaround.

IPV6 configuration is not supported for Network Controller managed infrastructure

Description: IPV6 configurations are not supported with System Center 2016 - VMM.

Workaround: Use IPV4 configuration with VMM 2016.

User needs to disable "Register this connection's address in DNS" option for Frontend and Backend IPs Software Load Balancer MUX VMs

Description: For Front End and Back End IPs assigned to Software Load Balancer MUX Virtual Machines you need to uncheck the option for 'Register this connection's address in DNS'. Having this option checked may cause issues with the connectivity over these IP addresses.

Workaround: No workaround

SAN migration fails for Nano host

Description: If you attempt to do a SAN migration between two stand-alone Nano Server hosts, you will receive an error.

Workaround: Install Update Rollup 2.

Adding a host to VMM with Storage Spaces Direct enabled will result in a warning

Description:When hosts are added to a cluster with storage spaces direct enabled, a warning "Multipath I/O is not enabled for known storage arrays on host <\hostname>" is generated.

Workaround: Install Update Rollup 2.

VM deployment on Scale Out File Server using fast file copy completes with warning

Description: If you deploy a VM on a Scale Out File Server using fast file copy, the action completes successfully with the following warning: "VMM could not transfer the file to using fast file copy. The VMM agent on returned an error. The user name or password is incorrect (0x8007052E)

Workaround: None

When adding a node to a cluster or creating a hyperconverged cluster using VMM, cluster validation is always performed even when the skip cluster validation option is specified

Description: If you add a node to an existing hyperconverged cluster or create a new cluster using Storage Spaces Direct technology using VMM, cluster validation is always performed.

Workaround: Install Update Rollup 2.

Classification change on Cluster Shared Volume (CSV) in Hyperconverged cluster does not reflect on all the storage nodes in the cluster

Description: If you change the classification on the CSV, only the classification of the owner node gets updated. other nodes still has older classification, assigned

Workaround: Install Update Rollup 2.

Creating tiered file share on SOFS completes with error Error (26668): Error code: 43020 [SM_RC_DEDUP_NOT_AVAILABLE] even if dedup option is not selected

Description: if you create a tiered fileshare on SOFS, on the successful completion of VMM job, job throws an error 43020 [SM_RC_DEDUP_NOT_AVAILABLE] even if dedup option is not selected

Workaround: you can ignore this error.

VMM does not show storage provider and existing volume, physical disk & tiers, for an out-of-band Hyperconverged Cluster (HC) and Storage Spaces Direct (S2D) Scale Out File Server (SOFS).

Description: After you onboard an out-of-band HC or S2D SOFS into VMM, the Storage Provider is not added and SOFS properties like Volume, physical disk and tiers are not available in VMM.

Workaround: Install Update Rollup 2.

Total Capacity and Available capacity of NAS arrays is displayed as 0 GB.

Description: Virtual Machine Manager 2016 shows Total Capacity and Available capacity as 0 GB for existing file shares in the NAS arrays.

Workaround: None.

© 2017 Microsoft