立即与支持人员聊天
与支持团队交流

Active Roles 8.1.2 - Feature Guide

Introduction Administrative rules and roles Using Active Roles Configuring and administering Active Roles FIPS compliance LSA protection support

Safe mode

Active Roles provides a troubleshooting mode called "Safe mode" that starts Administration Service in a limited state.

When you enable Safe mode, Administration Service:

  • Disregards all custom policies, workflows, scripts, scheduled tasks and other custom-made assets that may prevent Active Roles from starting and operating normally.

  • Rejects connections from any users that do not have Active Roles Admin privileges.

While Safe mode is active, only Active Roles Admins can connect to Administration Service, so that they can troubleshoot problems by changing the existing Active Roles configuration or removing any customizations that could cause issues. Once troubleshooting is finished, Active Roles Admins can also turn off Safe mode and resume normal Active Roles operation.

Getting started

You can enable Safe mode from the Active Roles Management Shell.

To enable or disable Safe mode

  1. On the computer running the Active Roles Administration Service, log in with a user account that has administrator rights on the computer.

    NOTE: You can enable or disable Safe mode only with a user account that has local administrator rights on the computer running Administration Service.

  2. Start the Active Roles Management Shell from the Windows Start menu or the Apps page of the operating system.

  3. To enable safe mode, enter the following commands in the Management Shell command-line interface:

    Set-ARService -SafeModeEnabled $true

    Restart-ARService

  4. To enable safe mode, enter the following commands in the Management Shell command-line interface:

    Set-ARService -SafeModeEnabled $false

    Restart-ARService

FIPS compliance

Active Roles 8.1.2 supports cryptography libraries and algorithms compliant with Federal Information Processing Standards (FIPS) 140-2. For more information on FIPS-compliant libraries and algorithms, see FIPS 140-2: Security Requirements for Cryptographic Modules.

NOTE: Consider the following when planning to use FIPS-compliant cryptography libraries or algorithms:

  • Although Active Roles continues to support non-FIPS compliant cryptography libraries and algorithms, it will not work properly if it is configured to use non-FIPS compliant solutions in a FIPS-compliant environment.

  • If you already use FIPS-compliant security algorithms in your environment (such as the TripleDES security algorithm, or the SHA256 hash algorithm), you must export your existing configuration, and import it in a new Active Roles installation.

LSA protection support

The Active Roles Synchronization Service Capture Agent supports Local Security Authority (LSA). For more information, see Configuring Additional LSA Protection in the Microsoft Windows Server documentation.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级