A symbolic link is a pointer to another file or directory. This policy manages symbolic links (symlinks) on Unix. Administrators can configure a set of symlinks that are created when policy is applied. Symbolic link entries are append only and cannot be overridden. However, if there is more than one of the exact same entry, the link will be created only once.
Symbolic links can be used to simplify other policies where file locations may differ from system to system. You can use the Symbolic Link policy to create a more uniform file system environment for running commands or modifying files. Be sure that the Unix Settings Extension is processed before any other CSEs that might need symlink functionality. You can control this with the Client-Side Extensions policy.
To set a new symbolic link
- Start Group Policy Editor.
- Select Unix Settings | Authentication Services | Client Configuration in the scope view.
- Double click Symbolic Links.
The Symbolic Links Properties dialog opens.
- Click Add.
The Symbolic Link dialog opens.
- In the Existing File field, type the full Unix path to the file or directory to link to.
- In the Symbolic Link field, type the full Unix path where you want to create the link.
Note: If the link target does not exist on the Unix host, it does not create the symbolic link.
- Click OK.
The Custom Service Configuration policy lets you define services, that will be set up by Group Policy agents.
The Custom Service Configuration policy lets the administrator define services with a list of files that will be uploaded to the SYSVOL, then downloaded on the client side. You can specify the target path, ownership, and permissions for each file. You can also specify two special scripts. The verification script is used for verifying that a configuration will work properly with the given service. The restart script restarts the service if the verification script was successful.
To configure a service, complete the following steps:
- Create the files you want to distribute through Safeguard Authentication Services. Ensure that the file is accessible from your Windows computer.
-
Start the Group Policy Editor and navigate to Unix Settings > Authentication Services > Client Configuration.
-
Select Custom Service Configuration.
-
To create the new service, enter the service name into the dropdown field, then click Add.
-
Next to Files, click Add.
-
In Target File Path, enter the full path for the target file in Unix path format. The path must start with a /, for example /etc/hosts.
-
In User Name, enter the name of the user that will own this file. If the user does not exist on the Unix host, the default user will be root.
-
In Group Name, enter the name of the group that will own this file. If the group does not exist on the Unix host, the default group will be root (or system on AIX).
-
Click Set User Rights to indicate that you want to explicitly specify the permissions for the user that owns the file.
-
Click Set Group Rights option to indicate that you would like to explicitly specify the permissions for the group that owns the file.
-
Click Set Other Rights option to indicate that you want to explicitly specify the permissions for everyone.
-
Click Browse and select the file you created in Step 1.
-
Select Copy File Permanently to permanently copy the file. By default, Safeguard Authentication Services removes copied files when the policy no longer applies. If the policy overwrote an existing file, it will be restored when the policy is no longer applied.
-
Click OK.
-
Repeat the previous steps to add all the files for the service.
-
Click Verification to select the verification script file.
-
Click Restart to select the restart script file.
-
Click OK to save the service configuration.
After configuring the services, the Group Policy agent will download every file for each service. Then, for each service, it will run the verification script. If it returns with success, the files that are copied and kept, and the restart script is run. If the verification script fails, every file in that specific service is restored to their original version and the restart script will not run.
You can configure which entries go into the Unix syslog configuration file. Syslog entries are appended to the log and cannot be overridden. However, if there is a duplicate entry, it is only added once to /etc/syslog.conf.
