These two management options are frequently confused or misused. Both are often used when just starting to manage users with Senergy, or when recovering user storage after a disk failure. There are some differences which make using one or the other better based on circumstances.
Enforce Policy Paths
Use this option if user home directories exist and the home directory attribute is set correctly for users. You can also use this option if home folders do not exist for the users objects you want to manage. Even if you want the storage to be moved to a different location, as long as the current location and what is set in the home directory attribute match, this is the option to use. When you run this management action, the object will be managed using the home directory attribute. If the current location matches one of the paths in the policy, the storage will not be moved, but if the path does not match one in the policy, the storage will be moved to a location specified by the policy. If there is no home folder that matches an attribute set on an object, a new folder will be created according to the options set in the policy. Note: if the storage does not need to move, other steps will not be taken without separate management actions, including quota setting, template copy and default trustee rights settings. If the storage is moved or newly created, all policy settings will be applied at the new destination.
Assign Home Folder Attribute
Use this option for any of the following situations:
- Home folders exist, but the home directory path is not set on any user objects
- Home folders exist, but the home directory path attribute is set incorrectly
This option is most often used to match orphaned home directories with the appropriate user objects. It is also used if a share or volume has been lost and the data has been restored to a new location not matching the former path. This option can be used to directly set one path on one object, or it can be used to discover existing home directories that match the name of a user in a given parent path. It can be run multiple times if there are multiple parent locations. Nothing will be done on objects where a match is not found.