System Center Service Manager 的新增功能What's New in System Center Service Manager

本文详细介绍了 System Center 2019-Service Manager (SM)中支持的新增功能。This article details the new features supported in System Center 2019 - Service Manager (SM).

SM 2019 中的新增功能New features in SM 2019

请参阅以下部分,了解有关 SM 2019 中更新的新功能/功能的信息。See the following sections for information about the new features/features updated in SM 2019.

支持 SQL 2017Support to SQL 2017

SM 2019 支持 SQL Server 2017 的全新安装。SM 2019 supports new installation of SQL Server 2017. 了解详细信息Learn more.

Active Directory 连接器改进Improvement in Active Directory Connector

已标识 Active Directory (AD)连接器与特定域控制器进行同步。The Active Directory (AD) connector has been improvised to synchronize with a specific domain controller. 你现在可以在 Active Directory 连接器的 LDAP 查询中指定域控制器。You may now, specify the domain controller in the LDAP query of the Active Directory connector.

提高 UI 响应能力Improved UI Responsiveness

用户界面通过解决内存泄漏问题进行了响应。The user interface is made responsive by addressing memory leak problems.

启用服务登录Enable Service Logon

在以前的版本中,在 Service Manager 管理服务器和 Service Manager 数据仓库管理服务器的安装过程中,将要求为 SM 帐户提供各种凭据。In earlier releases, during the setup of Service Manager Management Server and Service Manager Data Warehouse Management Server, various credentials are asked for SM accounts. 这些帐户已是交互式的(具有 "允许在本地登录" (SetInteractiveLogonRight)权限的帐户)。These accounts had been interactive (accounts having Allow log on locally (SetInteractiveLogonRight) permission).

使用 SM 2019,我们已启用服务登录类型使 Service Manager 更安全,默认登录类型设置为 "服务登录"。With SM 2019, we have enabled Service Logon type to make Service Manager more secure, and the default logon type is set to Service Logon. 有关如何向运行方式帐户授予服务登录权限的信息,请参阅启用服务登录功能。For information on how to grant service logon permissions to the Run As accounts, see enable service logon feature.

Bug 修复情况Bug fixes

此版本的 System Center Service Manager 包含在SCSM 2016 的更新汇总 5之前发运的所有 bug 修复。This release of System Center Service Manager contains all the bug fixes shipped until the Update Rollup 5 of SCSM 2016.

备注

Service Manager 1807 中引入了以下功能,在2019中进行了增强。The following feature was introduced in Service Manager 1807, enhanced in 2019.

支持 SQL 2017 功能包Support to SQL 2017 feature pack

可以将 SQL Server 2016 升级到 SQL 2017。You can upgrade SQL server 2016 to SQL 2017. 了解详细信息Learn more.

备注

Service Manager 1801 中引入了以下功能,其中包括2019。The following feature was introduced in Service Manager 1801, included in 2019.

支持增强的评估体验Support to enhanced evaluation experience

SM 支持评估 Service Manager 和激活产品以供零售使用的增强体验。SM supports an enhanced experience for evaluating Service Manager and activating the product for retail use.

Service Manager 的评估版可以安装并使用 180 天。The evaluation version of Service Manager can be installed and used for 180 days. 在 SM 2016 中,安装评估版之后,没有选项可以查看评估期的剩余天数。in SM 2016, after an evaluation version is installed, there was no option to view the remaining days for the evaluation period. 在 Service Manager 1801 及更高版本中,你可以查看评估期的相关信息,并相应地激活 SM。With Service Manager 1801 and later, you can view the information about the evaluation period, and accordingly activate your SM. 了解详细信息Learn more.

本文详细介绍 System Center 1807 - Service Manager (SM) 中支持的新功能。This article details the new features supported in System Center 1807 - Service Manager (SM).

System Center 1807 - Service Manager 的新增功能What's new in System Center 1807 - Service Manager

SM 1807 中包含以下新功能。The following new feature is included in SM 1807.

备注

若要查看修复的 bug 和 SM 1807 的安装说明,请参阅知识库文章 4338239To view the bugs fixed and the installation instructions for SM 1807, see KB article 4338239.

支持 SQL 2017 功能包Support to SQL 2017 feature pack

SM 1807 支持 SQL 2017。SM 1807 supports SQL 2017. 可以将 SQL Server 2016 升级到 SQL 2017。You can upgrade SQL server 2016 to SQL 2017. 了解详细信息Learn more

备注

  • SM 1807 仅支持升级自 SQL 2016 的 SQL 2017。With SM 1807, SQL 2017 is supported only if it is upgraded from SQL 2016. 不支持使用 SM 1807 全新安装 SQL 2017。Fresh installation of SQL 2017 with SM 1807 is not supported. 部署了 1801 和 SQL 2016 的用户需应用 SM 1807,然后升级到 SQL 2017。Users with 1801 deployment and SQL 2016 needs to apply SM 1807 and then upgrade to SQL 2017.
  • 升级到 SQL 2017 的过程会卸载报表服务,请确保迁移所需的报表(例如备份报表数据库和加密密钥)。Upgrade process to SQL 2017 uninstalls the reporting services, ensure to migrate required reports such as backup reporting DB and encryption keys.

本文详细介绍 System Center 1801 - Service Manager (SM) 中支持的新功能。This article details the new features supported in System Center 1801 - Service Manager (SM).

本文详细介绍 System Center 2016 - Service Manager (SM) 中支持的新功能。This article details the new features supported in System Center 2016 - Service Manager (SM).

System Center 1801 - Service Manager 的新增功能What's new in System Center 1801 - Service Manager

以下部分汇总了 SM 1801 中的新功能。The following sections summarize the new features released in SM 1801.

支持增强的评估体验Support to enhanced evaluation experience

SM 1801 支持增强的评估 Service Manager 及激活产品以供零售使用的体验。SM 1801 supports an enhanced experience for evaluating Service Manager and activating the product for retail use.

Service Manager 的评估版可以安装并使用 180 天。The evaluation version of Service Manager can be installed and used for 180 days. 在 SM 2016 中,安装评估版之后,没有选项可以查看评估期的剩余天数。in SM 2016, after an evaluation version is installed, there was no option to view the remaining days for the evaluation period. 在 Service Manager 1801 中,可以查看有关评估期的信息,并相应地激活 SM。In Service Manager 1801, you can view the information about the evaluation period, and accordingly activate your SM. 了解详细信息Learn more

Bug 修复情况Bug fixes

此版本的 System Center Service Manager (SCSM) 包含在 SCSM 2016 的更新汇总 4 之前推出的所有 bug 修复,以及对 TLS 1.2 协议的更多支持。This release of System Center Service Manager (SCSM) contains all the bug fixes shipped until the Update Rollup 4 of SCSM 2016, along with added support for TLS 1.2 Protocol. 阅读本文,了解有关如何设置、配置和运行环境以使用 TLS 1.2 的详细信息。Read this article for more information about how to set up, configure and run your environment to use TLS 1.2.

此版本应该用于验证将 SCSM 与 1801 版本中包含的其他 System Center 组件进行集成的方案。This build should be used for validating the SCSM integration scenarios with other System Center components included in release 1801.

System Center 2016 - Service Manager 的新增功能What's new in System Center 2016 - Service Manager

以下部分汇总了 SM 2016 中的新功能。The following sections summarize the new features released in SM 2016.

支持 SQL Server 2014 SP2Support for SQL Server 2014 SP2

支持 SQL Server 2014 SP2 用于托管 Service Manager 数据库和数据仓库数据库。SQL Server 2014 SP2 is supported to host your Service Manager database and your data warehouse database.

Windows 7 支持的 Service Manager 控制台Service Manager console supported with Windows 7

Service Manager 控制台支持 Windows 7。Windows 7 is supported with the Service Manager console. 但是,需要 .NET 4.5.1 作为先决条件。However, you need .NET 4.5.1 as a prerequisite. 从 Microsoft 支持站点 https://support.microsoft.com/en-us/kb/2858728 下载带有语言包的脱机安装程序。Download the offline installer with language pack from the Microsoft Support site at https://support.microsoft.com/en-us/kb/2858728. Service Manager 2016 控制台中引入的新拼写检查功能对 Windows 7 安装的语言支持有限。The new spell check feature, which was introduced in the Service Manager 2016 console, has limited language support for Windows 7 installations. Windows 7 支持的语言包括英语、法语、德语和西班牙语。The supported languages on Windows 7 include English, French, German, and Spanish.

支持 System Center 2012 R2 组件Support for System Center 2012 R2 components

为了简化升级,可以将以下 Service Manager 2016 连接器与 System Center 2012 R2 组件一起使用。To help simplify upgrades, you can use the following Service Manager 2016 connectors with System Center 2012 R2 components.

  • System Center 2012 R2 Virtual Machine ManagerSystem Center 2012 R2 Virtual Machine manager
  • System Center 2012 R2 OrchestratorSystem Center 2012 R2 Orchestrator
  • System Center 2012 R2 Operations ManagerSystem Center 2012 R2 Operations Manager
  • System Center 2012 R2 Configuration Manager(包括 SCCM 1511、1602 和 1606)System Center 2012 R2 Configuration Manager (including SCCM 1511, 1602 and 1606)

性能改进Performance improvements

在 System Center 2016 - Service Manager 中,整个数据处理增加了四倍。In System Center 2016 - Service Manager, data processing throughout has been increased by four times. 通过这种改进,Service Manager 可以更好地利用 SQL Server。With this improvement, Service Manager better utilizes SQL Server. 这些结果来自 Microsoft 的测试,方法是大量使用标准推荐拓扑强调测试系统。These results are from testing at Microsoft by stressing test systems heavily using the standard recommended topology.

通过以下方式实现性能改进:Performance improvements are realized in the following ways:

工作项创建/更新提交性能提升Improved work-item creation and update commit performance

  • 使用此改进大大减少了创建和更新工作项的时间。Time to create and update work items was greatly reduced using this improvement.

工作流处理得到提升Improved workflow processing

  • Service Manager 中的工作流应该具有更少的延迟,并且在遇到延迟时应该更快地赶上。Workflows in Service Manager should have less latency and should catch up faster when you do experience latency.

工作量的每秒处理能力更高Higher work-item per second processing capacity

  • Service Manger 每分钟可更轻松地处理 45 个工作项的大流入量。Service Manger can more easily handle a large inflow of 45 work items per minute.

组和队列计算得到明显改进Group and queue calculations were improved significantly

  • 内部测试结果显示出 50% 的改进。The internal testing results have shown 50% improvement. 例如,在显示关联用户或工作流的工作项或配置项目上花费的时间减少了一半。For example, the time was reduced by half for a work item or configuration item to show up for associated users or workflows. 在 Service Manager 2012 R2 中,高负荷环境需要 30 分钟来刷新组和队列,而 Service Manager 2016 在 15 分钟内就可以刷新组/队列以获得相同的负载。In Service Manager 2012 R2 where a stressed environment would take 30 minutes to refresh the groups and queues, Service Manager 2016 can refresh the groups/queues within 15 minutes for the same load.

以下是性能改进指标的摘要:Here's a summary of the performance improvement metrics:

以下是我们用于测试的试验台的样子 -Here is how the test bed looks like which we have used for testing-

  • 400 个同步客户端连接400 simultaneous client connections
  • 每分钟 45 个工作项的流入量Inflow of 45 work-items per minute
  • 2 个辅助 Service Manager 管理服务器,每个服务器处理 200 个客户端连接2 secondary Service Manager management servers handling 200 client connections each
  • 216 个订阅工作流216 subscription workflows
  • 42 个队列42 queues
  • 注册的 Service Manager 数据仓库Service Manager Data Warehouse registered
  • AD 连接器正在运行同步 10 万个用户AD connector was running syncing 100K users
  • 所有计算机都有标准推荐的配置All computers had standard recommended configurations

工作项创建/更新提交性能提升Improved work-item creation and update commit performance

使用此改进大大减少了创建和更新工作项的时间。Time to create and update work items was greatly reduced using this improvement.

操作action Service Manager 2012 R2Service Manager 2012 R2 Service Manager 2016Service Manager 2016 改进improvement
事件创建时间incident creation time 2 - 6 秒2 - 6 seconds 0.5 秒0.5 seconds 4 次4 times
连接器同步期间的事件创建时间incident creation time during connector sync 8 - 10 秒8 - 10 seconds 小于 1 秒less than 1 second 8 次8 times

工作流处理得到提升Improved workflow processing

Service Manager 中的工作流应该具有更少的延迟,并且在遇到延迟时应该更快地赶上。Workflows in Service Manager should have less latency and should catch up faster when you do experience latency.

以下是工作流在延迟 2 小时后以每分钟 45 个工作项的速率赶上的时间:Here are the times for workflows to catch up after 2 hours of latency at a 45 work item per minute rate:

操作action Service Manager 2012 R2Service Manager 2012 R2 Service Manager 2016Service Manager 2016 改进improvement
工作流追赶时间workflow catch-up time 2 小时 50 分钟2 hours 50 mins 1 小时 46 分钟1 hour 46 mins 1.5 次1.5 times

工作量的每秒处理能力更高Higher work-item per second processing capacity

Service Manger 每分钟可更轻松地处理 45 个工作项的大流入量。Service Manger can more easily handle a large inflow of 45 work items per minute.

操作action Service Manager 2012 R2Service Manager 2012 R2 Service Manager 2016Service Manager 2016 改进improvement
事件平均创建时间average incident creation time 2.2 秒2.2 seconds 0.5 秒0.5 seconds 4 次4 times

更快的 SCCM 和 Active Directory 连接器同步Faster SCCM and Active Directory connector sync

Service Manager 中的 Active Directory 和 SCCM 连接器可将大量数据导入 Service Manager 数据库。The Active Directory and SCCM connectors in Service Manager can import large amounts of data into the Service Manager database. 这样不仅可增加数据表(连接器的数据的存储位置)的大小,还能大幅增加 EntityChangeLog (ECL) 表和历史记录表的大小。In doing so, they not only increase the size of the data table, which is where the data from the connectors are stored, but they also increase the size of the EntityChangeLog (ECL) table and history tables considerably. ECL 表的大小较大可能会造成问题 - 某些情况下,这会显著降低系统速度。A large ECL table size can be a problem - in some cases, it can slow down the system significantly.

这种情况中,ECL 表和历史记录表将存储有关将数据引入 Service Manager 的时间的详细信息,以及为每个数据项添加或更新的数据。The ECL table, and the history tables in this case, store details about when the data was brought into Service Manager and the properties that were added or updated for each data item. 禁用 ECL 日志记录不会影响从连接器导入数据。Disabling ECL logging, doesn't affect importing data from connectors. 相反,大多数日志数据不会写入到 ECL 和历史记录表中,从而可以明显提升性能。Instead, most logging data doesn't get written to the ECL and history tables, which can result is significant performance improvement. 默认情况下,禁用的 ECL 日志记录不可用。Disabled ECL logging is not available by default. 换言之,ECL 日志记录默认为启用状态。In other words, by default, ECL logging is enabled. 但是通过使用简单的 PowerShell cmdlet,可轻松打开禁用的 ECL 日志记录。However, you can easily turn on Disabled ECL logging by using a simple PowerShell cmdlet. 有关详细信息,请参阅可选择性地禁用 ECL 日志记录以加快连接器同步For more information, see Optionally Disable ECL Logging for Faster Connector Synchronization.

ECL 日志清理得到改善Grooming improvements for ECL logs

在 ECL 日志清理期间,Service Manager 不会清理实体的最新更改,即使此实体的保留历史时间已到期也是如此。During ECL log grooming, Service Manager does not groom the latest change to an entity, even if the retention history period of that entity has elapsed.

清理最终会在 ECL 表中为每个对象保留一个条目,此条目是针对 Service Manager 部署生命期而创建的。Grooming eventually leaves one entry for every object ever created in the ECL table for the lifetime of your Service Manager deployment. 为了保留 ECL 表中的最后一个条目,执行存储过程 (p_GroomChangeLog) 可能很耗时。In order to keep the last entry in the ECL table, the execution of the stored procedure (p_GroomChangeLog) can take a time. 在某些情况下,ECL 条目非常大,可能要花 30 分钟以上的时间。In some cases, longer than 30 minutes when the ECL entry is very large. 在优化期间,Service Manager 不会保留此条目,从而提升了清理存储过程方面的性能。As part of the optimization, Service Manager does not keep the entry, which results in a performance improvement for the grooming stored procedure. 清理存储过程的速度通常会提升 3 到 4 倍。Typically, the grooming stored procedure runs 3 to 4 times faster.

因此,与先前的显示一个条目相反,如果某条目的历史记录保留期已过,则历史记录选项卡不会显示此条目的任何输入。As a result, the history tab would not show any entry for an entity if its history retention period has elapsed, as opposed to seeing one entry earlier.

减少事件工作流的滞后情况Reduction in incident workflow lag

以下 Service Manager 中随附的事件相关工作流已经过优化,可减少更新事件的时间量,尤其是同时创建多个工作项的时间。The following incident-related workflows included in Service Manager have been optimized to reduce the amount of time to update incidents, especially when many work items are created simultaneously.

  • WorkItem_SetFirstAssingedTo_RelationhsipAdd_RuleWorkItem_SetFirstAssingedTo_RelationhsipAdd_Rule

  • Incident_Adjust_PriorityAndResolutionTime_Custom_Rule.UpdateIncident_Adjust_PriorityAndResolutionTime_Custom_Rule.Update

  • Incident_Adjust_PriorityAndResolutionTime_Custom_Rule.AddIncident_Adjust_PriorityAndResolutionTime_Custom_Rule.Add

  • ServiceManager.IncidentManagement.ParentIncidentActivated.UpdateRuleServiceManager.IncidentManagement.ParentIncidentActivated.UpdateRule

增加了每个工作流的批处理大小,从而优化了性能,并允许更多数量的事件同时更新。The batch sizes were increased for each workflow, which results in better performance and allows an increased number of incidents to update simultaneously.

将 ADGroupExpansion 工作流集成到 ADConnector 中Integrated ADGroupExpansion Workflow into ADConnector

AD GroupExpansion 功能现包含在 ADConnector 内,而在先前版本中它是单独的工作流。The AD GroupExpansion functionality is now part of the ADConnector, as opposed to a separate workflow in the previous release.

  • GroupExpansion 功能和 ADConnector 一样按相同的计划运行。GroupExpansion functionality runs in the same schedule as ADConnector.

  • 减少了同步组成员身份更改所需的时间。The time required to sync group membership changes has been reduced.

数据仓库多维数据集中的新日期维度New Date dimensions in Data Warehouse cubes

使用 System Center 2016 - Service Manager,Service Manager 数据仓库多维数据集包含新的日期维度,可帮助你创建丰富的报表并根据年份、季度、月份、日期等进行数据切分。With System Center 2016 - Service Manager, the Service Manager Data Warehouse cubes contain new date dimensions which help you to create rich reports and slice data based on Year, Quarter, Month, Day etc.

日期维度

已向 Service Manager 数据仓库多维数据集添加了以下新维度:The following new dimensions have been added to Service Manager data warehouse cubes:

多维数据集名称:Service Manager 工作项多维数据集Cube Name: Service Manager Work Items Cube

  • 内容:事件、问题管理Content: Incident, Problem management
  • 新日期维度:New date dimensions:
    • 事件 ClosedDateIncident ClosedDate
      • 事件 CreatedDateIncident CreatedDate
    • 事件 ResolvedDateIncident ResolvedDate
    • 问题 ClosedDateProblem ClosedDate
    • 问题 CreatedDateProblem CreatedDate
    • 问题 ResolvedDateProblem ResolvedDate

多维数据集名称:更改和活动管理多维数据集Cube Name: Change and Activity Management Cube

  • 内容:更改和活动管理Content: Change and Activity management
  • 新日期维度:New Date Dimensions:
    • 活动 ActualEndDateActivity ActualEndDate
      • 活动 ActualStartDateActivity ActualStartDate
      • 活动 CreatedDateActivity CreatedDate
      • 活动 ScheduledEndDateActivity ScheduledEndDate
      • 活动 ScheduledStartDateActivity ScheduledStartDate
      • ChangeRequest ActualEndDateChangeRequest ActualEndDate
      • ChangeRequest ActualStartDateChangeRequest ActualStartDate
      • ChangeRequest CreatedDateChangeRequest CreatedDate
      • ChangeRequest ScheduledEndDateChangeRequest ScheduledEndDate
      • ChangeRequest ScheduledStartDateChangeRequest ScheduledStartDate

多维数据集名称:Service Manager 服务目录库多维数据集Cube Name: Service Manager Service Catalog library cube

  • 内容:服务目录Content: Service Catalog
  • 新日期维度:New Date Dimensions:
    • 活动 ActualEndDateActivity ActualEndDate
    • 活动 ActualStartDateActivity ActualStartDate
    • 活动 CreatedDateActivity CreatedDate
    • 活动 ScheduledEndDateActivity ScheduledEndDate
    • 活动 ScheduledStartDateActivity ScheduledStartDate
    • ReviewActivity ActualEndDateReviewActivity ActualEndDate
    • ReviewActivity ActualStartDateReviewActivity ActualStartDate
    • ReviewActivity CreatedDateReviewActivity CreatedDate
    • ReviewActivity ScheduledEndDateReviewActivity ScheduledEndDate
    • ReviewActivity ScheduledStartDateReviewActivity ScheduledStartDate
    • ServiceRequest ActualEndDateServiceRequest ActualEndDate
    • ServiceRequest ActualStartDateServiceRequest ActualStartDate
    • ServiceRequest CreatedDateServiceRequest CreatedDate
    • ServiceRequest CompletedDateServiceRequest CompletedDate
    • ServiceRequest ClosedDateServiceRequest ClosedDate
    • ServiceRequest ScheduledEndDateServiceRequest ScheduledEndDate
    • ServiceRequest ScheduledStartDateServiceRequest ScheduledStartDate

所有上述维度均具有以下属性,可用于进行数据切分:All these dimensions have the following attributes, which you can use for slicing your data:

维度列表

若要在自定义多维数据集中为其他日期字段添加日期维度To add date dimensions for other date fields in custom cubes

  1. 在定义多维数据集定义的管理包中,为所需字段添加命名计算,如下所述:In the management pack defining the cube definition, add the named Calculations for the required field like mentioned below:

    <NamedCalculation ID="Incident_CreatedDate__DateKey" Target="IncidentDW!IncidentDim" ColumnType="Int">
            <Calculation>isNull(CONVERT(nvarchar(8), CreatedDate, 112),'20000101')</Calculation>
          </NamedCalculation>
    

    NamedCalculation ID 最后应该包含字符串 __DateKey,并且数据仓库中的此字段不应为 NULL 或 0。The NamedCalculation ID should have string __DateKey in the end, and this field in the data warehouse should not be NULL or 0.

  2. 密封管理包并将其导入 Service Manager。Seal the management pack and import it into Service Manager.

  3. 在数据仓库上运行 MPSyncJob 并等待管理包被标记为“已完成”。Run the MPSyncJob on the data warehouse and wait until the management pack is marked Completed.

  4. 处理所有多维数据集,或等待其一夜之间自动处理。Process all the cubes, or wait for automatic processing overnight.

  5. 如上所述,多维数据集使用新的日期维度进行更新。Cubes are updated with new date dimensions, as defined above.

基于 HTML 的全新自助服务门户New HTML based Self Service portal

此版本包含基于 HTML 的新自助服务门户,它提供以下增强功能:This release contains a new HTML based Self Service Portal, which offers the following enhancements:

  • 具有易用导航的更新后的现代 UIUpdated modern UI with easy-to-use navigation
  • 多浏览器支持Multiple browsers support
  • 门户中现在支持公告Announcements are now supported in the portal
  • 新的服务目录New Service Catalog
  • 指向帮助文章的丰富浏览器Rich browser for help articles
  • “我的活动”和“我的请求”管理My Activities and My Request management
  • 服务器缓存,可减少数据库调用时间并提高门户性能Server caching to reduce database calls and improve portal performance
  • 支持自助服务门户页面的直接 URLSupport of direct URLs for Self Service Portal pages
  • 丰富的自定义选项Rich customization options

有关详细信息以及门户的安装和自定义,请参阅部署 Service Manager 的自助服务门户For more information and installing and customizing the portal, see Deploy the Self-Service Portal for Service Manager.

备注

较早版本的 Silverlight 和基于 SharePoint 的自助服务门户已删除。The older Silverlight and SharePoint-based Self-Service portal has been removed.

Service Manager 控制台中的拼写检查Spell check in Service Manager console

现已对工作项窗体启用拼写检查。Spell check is now enabled for work item forms. 它支持 Service Manager 支持的 21 种语言中的 17 种[目前不支持中文(简体)、中文(繁体)、日语和韩语]。It is enabled for 17 out of the 21 Service Manager supported languages [Chinese (Simplified), Chinese (Traditional), Japanese and Korean are currently not supported]. 要使用此功能,请安装所需的语言包并将键盘 IME 设置为所需的语言。To use this feature, install your desired language pack and set the keyboard IME for your desired language. 默认情况下启用此功能,但可以通过导航至“查看” > “拼写检查”进行切换。This feature is enabled by default, but can be switched by navigating to View > spell check.

打开正在进行的活动Open activity in progress

为服务请求和更改请求添加了新的控制台任务“打开正在进行的活动”。A new console task Open Activity in Progress, was added for service requests and change requests. 当工作项移动到“正在进行”状态时,将启用此控制台任务的链接。This console task’s link is enabled when a work item moves to the in progress state. 单击此任务的链接将打开当前正在进行的活动。Clicking this task’s link opens the current in-progress activity. 对于没有任何正在进行的活动的工作项,将显示本地化消息“没有为工作项找到具有‘正在进行’状态的活动。”For work items that don’t have any in-progress activity, the localized message No Activity with In Progress state is found for the work item. is displayed. 在早期版本的 Service Manager 中,需要打开工作项,导航到“活动”选项卡,然后单击“正在进行”的活动。In previous versions of Service Manager, it required to open the work item, navigate to the Activities tab, and then clicking the In progress activity. 现在可以通过单击访问“正在进行”的活动。Now In progress activity can be accessed with a single click.

支持 Lync 2013 和 Skype for BusinessSupport for Lync 2013 and Skype for Business

System Center 2016 - Service Manager 包括支持在 Microsoft Office 套件 2013 和 2016 中与 Lync 2013 和 Skype for Business 集成的更新。System Center 2016 - Service Manager includes the updates that support integration with Lync 2013 and Skype for Business in Microsoft Office suite 2013 and 2016. 有关使用 Lync 或 Skype for Business 联系用户的信息,请参阅从事件表单联系用户For information about contacting a user using Lync or Skype for Business, see Contact a User from an Incident Form.

备注

不支持 2013 年之前的 Lync 版本。Lync versions earlier to 2013 are not supported.

安装程序更改以支持 SQL AlwaysOn 安装Setup changes to support SQL AlwaysOn installation

安装向导可使你在复杂配置中轻松安装 Service Manager,例如具有不同命名实例的 SQL AlwaysOn 配置。The Setup wizard allows you to easily install Service Manager in complex configurations such as a SQL AlwaysOn configuration with different named instances.

现在,你可以一起配置 SQL 管理服务器、实例名称和端口号。Now you can configure the SQL management server, instance name and port number together.

配置 SQL 管理服务器和端口configure SQL management server and port

支持 .NET Framework 4.5.1Support for .NET Framework 4.5.1

Service Manager 2016 现在支持 .Net framework 4.5.1Service Manager 2016 now supports the .Net framework 4.5.1

后续步骤Next steps

  • 在公司或组织中部署 Service Manager 之前,请查看规划 Service Manager 以了解准备 Service Manager 所需要的硬件和软件要求以及软件角色。Review Planning for Service Manager to understand hardware and software requirements and software roles you need to prepare for Service Manager before you deploy it in your company or organization.
  • 请参阅已解决的问题See the fixed issues.