Active Administrator 8.7 - User Guide

Migrating data to another database

Migrating data to another database

The Active Administrator® Database Migration Tool helps you migrate data quickly and efficiently from a source database to a target database. For example, you created a new Active Administrator database and want to copy custom reports and alerts from an existing database. Use the Database Migration Tool to copy the existing data to your new database.

NOTE: The source and target databases must exist within the same version of Active Administrator. It is recommended that you back up the target database before you begin the migration.

To use the Database Migration Tool

1	Stop the Active Administrator Foundation and Active Administrator Notification services.

2	Select Start | Quest | AA Database Migration Tool.

3	On the Welcome page, click Next.

4	Type the names or browse to locate the source server and database that contains the data to migrate to the target database.

5	Type the names or browse to locate the target server and database to receive the data from the source database.

6	Click Next.

7	Select the data that you want to migrate from the source to the target database.

▪	To select all the options, click Select all.

▪	To clear all the selections, click Clear all.

8	Click Next.

9	Review the selections you made.

10	Click Finish.

11	After the data migration is finished, you can view details about the migration.

12	Click Finish.

13	Start the Active Administrator Foundation and Active Administrator Notification services.

Setting a preferred domain controller

Setting a preferred domain controller

Preferred domain controllers are used when requesting resources from Active Directory®. Normally, Active Directory assigns you the closest domain controller. You can use this feature to specify a domain controller to be used when a domain controller has not already been specified.

NOTE: Preferred domain controllers retrieve objects from Active Directory, such as a list of domain controller or a list of users. If all domain controllers in the domain are required to be scanned, such as the Inactive Accounts feature, the preferred domain controllers are not used.

You can select to verify if a preferred domain controller is offline before use. If the preferred domain controller is offline, you can choose to use the primary domain controller (PDC) of the domain or allow Active Directory to select a domain controller. The offline preferred domain controller is recorded in the server log.

To add preferred domain controllers

1	Select Configuration | Preferred Domain Controllers.

2	Click Add.

3	Type the name of the domain controller.

-OR-

Browse for and select a domain. Select a domain controller.

4

Click OK.

To delete preferred domain controllers

1	Select Configuration | Preferred Domain Controllers.

2	Click Delete All to delete all domain controllers in the list.

-OR-

Select specific domain controllers, and click Delete.

Setting up workstation logon auditing

Setting up workstation logon auditing

With workstation logon auditing, you can audit user logon and logoff events including lock and unlock. See Monitoring user logon activity.

Deploying the workstation logon audit agent adds these workstation events to the event definitions:

•	User Locked Workstation

•	User Logoff

•	User Logon (interactive)

•	User Logon (Remote Desktop)

•	User Unlocked Workstation

Topics 

•	Deploying the workstation logon audit agent

•	Enabling the default port for the workstation logon auditing agent

Deploying the workstation logon audit agent

Deploying the workstation logon audit agent

To audit user logon events, you must enable workstation logon auditing and deploy the workstation logon audit agent to workstations and member servers. Once enabled, the workstation logon auditing service will send messages to the Active Administrator® server.

NOTE: The workstation logon auditing service must run under context of the local system account.

Topics 

•	Enabling workstation auditing

•	Deploying the workstation logon agent from a GPO