One Identity provides an interactive script, called oat, that walks you through the process of changing file ownerships to match Active Directory. This script calls oat_adlookup, oat_match, and oat_changeowner with appropriate arguments based on responses that you provide.
Note: You must have Safeguard Authentication Services installed and your system joined to an Active Directory domain to run the interactive script.
To change file ownership
-
At the command prompt enter:
/opt/quest/libexec/oat/oat
The interactive script requests information about:
-
Active Directory users and passwords
-
Attributes
-
Local users and passwords
-
Group names and path
-
Path where you want OAT to perform the Ownership Alignment process.
Note: No changes are made to your system until you have reviewed and approved the list of files and directories.
-
-
Enter the requested information or press Enter to accept the default values enclosed in square brackets.
-
At the end of the interview, it asks you to specify the directory for which you want to change file ownership.
Typically you would specify "/" for the root directory.
Note: If you choose "/", it changes the file ownership for every file in your file system. One Identity recommends that you run OAT against a test directory first to confirm your understanding of what OAT does.
The oat_changeowner script creates a list of files that will be modified.
-
Review the list of files that will be changed.
-
If the files in the list are what you want changed, respond with a yes or no.
oat saves rollback information in a directory called oatwork<date> (where <date> is today's date). For example, in the /var/opt/quest/oat/oatwork20100513/ you would see a list of files similar to this:
ad_groups ad_users filelist group_mapping log
The log file is especially useful because it lists all the commands or scripts that were run, the options that were passed to them, and any error messages that were produced.
For more information, see the OAT man page. For information about accessing the OAT man page, see Using manual pages (man pages).