Custom Active Directory Groups and User Names Setup
Overview:
Velocity by default uses specific Windows Groups and User names for application and SQL authentication. The two Active Directory Group names it uses are: “Velocity Users” and “Velocity Services”. There is also one Active Directory User: “VelocityServices”. Depending on the installation, these groups and user will either be in Active Directory, or they will be local to the Velocity server. Where the groups and user reside depends on whether:
Velocity and SQL are installed on the same computer, or
Velocity and SQL are installed on separate computers
When Velocity and SQL are installed on the same computer, the only group that is created on the domain controller is the Velocity Users group. The Velocity Services group and the VelocityServices user are local to the Velocity server.
When Velocity and SQL are installed on separate computers, both groups and the user are all located on the Active Directory Domain Controller.
There are instances when you will not want to use the default Velocity Users group, Velocity Services group, or VelocityServices user names. Government or other large organizations in particular often require the assignment of unique naming conventions for every unit or department within the organization.
To do this, you need to choose the Advanced Authentication option on the Application Network and Security screen while performing a Server installation.
The purpose of custom user and groups is to replace the defaults. Making sure the new names work before deleting the defaults is strongly recommended. Because every installation is different, make sure you review your existing default accounts to guarantee that the new accounts have equivalent rights and permissions.
This procedure should be performed by an IT professional thoroughly familiar with the intricacies of SQL Server database management and Windows Active Directory.
Based on your requirement follow the steps mentioned in either of the sections
Configuration Details: