| ### The serverentry and serverprincipal Attributes During the initial configuration of DCE and DTS, one DTS entry name is created for use with CDS, and one DTS name is created for use with the registry service. If you subsequently wish to change the name of a server, you can do this by changing two of the server's attributes: the serverentry attribute and serverprincipal attribute. The default settings for these dcecp program attributes are the same as the default settings for the names that are created during the initial DCE configuration; they are the recommended settings. This topic describes additional considerations for the settings of these attributes. If you decide to change the settings of the serverentry and serverprincipal attribute values, be sure that the new values are appropriate. If not, you will experience trouble with DTS. The serverentry attribute specifies the CDS entry name where bindings for the server are exported. If you change the setting of this attribute, the entry is also modified in the namespace. The following is an example command that sets the serverentry attribute value: dcecp> dts modify - change {serverentry /.:/hosts/cyclops/dts_ref_node} dcecp> The serverprincipal attribute specifies the principal name of the server which is used for authentication. If you change the name using the dcecp program, you must create a matching principal name and account in the security service registry. When you do this, you must add the new principal name to the existing DTS server group (dts-servers). The machine principal must be a member of this authorization group. See Creating and Maintaining Accounts of this guide for further information on creating a new principal account and Creating and Maintaining Principals, Groups, and Organizations on adding a principal name to an existing server group. The following example command sets the serverprincipal attribute: dcecp> dts modify -change {serverprincipal /.:/hosts/ajax/dts_machine} dcecp> ##