Veritas NetBackup™ Self Service Configuration Guide
- Configuring a Self Service solution
- Configuring a NetBackup master server
- Configuring Self Service
- Customizing Self Service
- User authentication methods
- Appendix A. NetBackup policy types
- Appendix B. Dashboard traffic light status and usage
- Appendix C. Synchronizing data from NetBackup
- Appendix D. NetBackup Self Service data caching process
- Appendix E. Integration settings
- Appendix F. REST API
- Appendix G. Glossary
Active Directory Import
You can synchronize Self Service with Active Directory for easier maintenance. Import is managed from a scheduled import task. This process lets you specify a time or frequency for the process. The schedule should reflect the full user set as any user that is not included is deactivated in Self Service.
You can create multiple import profiles with a different source for each profile. For each profile a Self Service access profile, cost center, and user account status must be specified. The users may be automatically assigned to zero or more user groups. The user group, however, must already exist in Self Service. You can source the Self Service user name from either Full Name (default) or Display Name. You can select a language, otherwise the system base language is used. You can specify an import profile by group or organizational unit, and with or without children included.
Import profiles are processed from the top of the list so you can modify the order to fit your requirements. If the same user is present in multiple profiles, only the Imported User Fields from the latest profile that is processed apply. User group membership is updated from all profiles.
The user that is specified within the Active Directory Import requires the List Contents and Read All Properties rights at the root level of the domain. These rights are required so that the user can search all organizational units and organizational groups and import all users.
A system configuration setting lets you control of whether the Domain Name is pre-pended to the user ID when you import it. Find the system configuration setting in. Verify the appropriate setting value before you create the first user accounts. Subsequent change causes new user accounts to be created and existing accounts are disabled, along with the attendant effect on accessing historical requests. A change of SAM account name causes the creation of a new Self Service user account.
You can create locally maintained Self Service users for the records that are not maintained in Active Directory. Active Directory update ignores these users.
If you use Windows Authentication, ensure that at least one user is associated to the Supervisor access profile on initial import. Otherwise access to the Administration area is compromised.
These instructions only apply to configuration on initial implementation of the system. They are not appropriate for later changes to the logon protocol due to effect on the user-maintained method