Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Active Administrator 8.6 - Installation Guide

Installation Considerations for Active Administrator Installing and configuring Active Administrator Appendix: Active Administrator Server Manager

Creating a passphrase

A passphrase is used to control access to Active Administrator data. A passphrase is similar to a password in usage, but is generally longer for added security. Active Administrator content will be secured using the passphrase and requires the passphrase for accessing the content or for changing the passphrase.

* 
CAUTION: You must know the current passphrase to change or restore the passphrase. It is very important to record the passphrase in a secure location where it can be retrieved when required.
CAUTION: If the passphrase is lost, it will be impossible to access Active Administrator data. You will have to uninstall Active Administrator, remove all associated files, and start a new installation of Active Administrator. For more information, see Recovering from a lost passphrase .
* 
NOTE: You can manage the passphrase from the Active Administrator Server Manager. From the Start menu, open AA Server Manager, and click Manage in the Security Manager section.
To create a passphrase
1
Type a passphrase of 25 to 32 characters and then type it again to confirm.
2
Record the passphrase in a secure location.
* 
CAUTION: You must know the current passphrase to change or restore the passphrase. It is very important to record the passphrase in a secure location where it can be retrieved when required.
3
Click Next. See Setting the Active Administrator database.

Setting the Active Administrator database

You can either create a new Active Administrator® database or use an existing database; however, you must ensure that an existing database has been upgraded to the latest version before proceeding.

* 
NOTE: If you are upgrading Active Administrator, you have the option to upgrade your existing live database and all archive databases.
* 
NOTE: In a TLS 1.2 only environment, SQL 2012 Native Client must be installed on the Active Administrator server and agent servers, and the database server must be configured to use TLS 1.2.
To create a new database
1
Select Create a new Active Administrator database.
2
Click Next.
3
Type the target SQL Server or Azure SQL Managed instance.
4
Type a name for the database or use the default.
5
By default, Secure Sockets Layer (SSL) encryption is used for all data sent from the named server to the Active Administrator archive database. To remove encryption, clear the Encrypt Connection check box.
6
By default, the server certificate is trusted. To remove the trust, clear the check box.
* 
NOTE: If the Trust Server Certificate check box is not selected, Active Administrator will walk the validation chain until it finds a valid authority.
7
If using an Azure SQL Managed instance, select SQL Server Authentication, enter a SQL user ID that has login privilege for the SQL Managed instance, and enter the password for the SQL account.
The characters in the password will be hidden. Each character will be represented by a displayed dot. Select Show Password to display the password.
8
Click Next.
9
If necessary, adjust the database size or file paths.
10
Select the security group type for the SQL groups. Using the default group types is recommended.
11
Click Next. See Setting the Active Administrator database.
To use an existing database
1
Ensure the existing database has been upgraded to the latest version before proceeding.
2
Select Use an existing Active Administrator database.
3
Type the target SQL Server or Azure SQL Managed instance.
4
Type the database name or browse to select the database.
5
By default, Secure Sockets Layer (SSL) encryption is used for all data sent from the named server to the Active Administrator archive database. To remove encryption, clear the Encrypt Connection check box.
6
By default, the server certificate is trusted. To remove the trust, clear the check box.
* 
NOTE: If the Trust Server Certificate check box is not selected, Active Administrator will walk the validation chain until it finds a valid authority.
7
If using an Azure SQL Managed instance, select SQL Server Authentication, enter a SQL user ID that has login privilege for the SQL Managed instance, and enter the password for the SQL account.
8
The characters in the password will be hidden. Each character will be represented by a displayed dot. Select Show Password to display the password.
9
Click Test Connection to validate the database.
10
Click Next. See Setting the Active Administrator archive database.

Setting the Active Administrator archive database

Next, set the Active Administrator® archive database, which is used to store events. By default, events older than 60 days are archived. You can either create a new archive database or use an existing archive database.

* 
NOTE: After you complete the configuration wizard, you can use the Active Administrator Console to manage archive databases by selecting Configuration | Archive Databases.
* 
NOTE: In a TLS 1.2 only environment, SQL 2012 Native Client must be installed on the Active Administrator server and agent servers, and the database server must be configured to use TLS 1.2.
To create a new archive database
1
Select Create a new Active Administrator Archive database.
2
Click Next.
3
Type the target SQL Server or Azure SQL Managed instance.
4
Type a name for the database or use the default.
5
By default, Secure Sockets Layer (SSL) encryption is used for all data sent from the named server to the Active Administrator archive database. To remove encryption, clear the Encrypt Connection check box.
6
By default, the server certificate is trusted. To remove the trust, clear the check box.
* 
NOTE: If the Trust Server Certificate check box is not selected, Active Administrator will walk the validation chain until it finds a valid authority.
7
If using an Azure SQL Managed instance, select SQL Server Authentication, enter a SQL user ID that has login privilege for the SQL Managed instance, and enter the password for the SQL account.
8
The characters in the password will be hidden. Each character will be represented by a displayed dot. Select Show Password to display the password.
9
Type a name for the archive or use the default.
10
Click Next.
11
If necessary, adjust the database size or file paths.
12
Select the security group type for the SQL groups.
13
Using the default group types is recommended.
14
Click Next. See Configuring purge and archive settings.
To use an existing archive database
1
Select Use an existing Active Administrator Archive database.
2
Type the target SQL Server or Azure SQL Managed instance.
3
Type the database name or browse to select the archive database.
4
By default, Secure Sockets Layer (SSL) encryption is used for all data sent from the named server to the Active Administrator archive database. To remove encryption, clear the Encrypt Connection check box.
5
By default, the server certificate is trusted. To remove the trust, clear the check box.
* 
NOTE: If the Trust Server Certificate check box is not selected, Active Administrator will walk the validation chain until it finds a valid authority.
6
If using an Azure SQL Managed instance, select SQL Server Authentication, enter a SQL user ID that has login privilege for the SQL Managed instance, and enter the password for the SQL account.
7
The characters in the password will be hidden. Each character will be represented by a displayed dot. Select Show Password to display the password.
8
Click Test Connection to validate the archive database.
9
Click Next. See Configuring purge and archive settings.

Configuring purge and archive settings

 
* 
NOTE: You can set more options to purge events, GPO history, and Active Directory® backups, and to archive events in the Active Administrator Console.
To configure purging and archiving
1
Select the purge and archive options to enable or disable.
 
Table 1. Purge and archive options
Option
Description

Event Archiving

By default, events older than 60 days are archived to the Active Directory archive database. To keep all events in the Active Administrator database, clear the check box.

Group Policy History Purging

By default, the GPO History backups are purged after 90 days. To keep all GPO History backups, clear the check box.

Active Directory Backup Purging

By default, Active Directory backups are purged after 90 days. To keep all Active Directory backups, clear the check box.

Inactive User and Computer History Purging

By default, inactive user accounts and computer history are purged after 30 days. To keep all inactive accounts and computer history, clear the check box.

2
Click Next. See Storing Active Administrator data.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation