Setting up the first user account

By default, the computer arrives with at least one of the following administrator accounts:
  • Administrator - enabled on server class computers
  • Emerson - enabled on workstation class computers
Important

The first user on a computer (before any DeltaV software is installed) must log into Windows using one of the above listed administrator accounts. The default password for both accounts is deltav (lowercase). You must change the default administrator account's password.

The Administrator account is disabled during DeltaV installation. You are prompted at that point to create a new account with administrator privileges. The Emerson account is not affected.

For added security when in a domain, consider making the local administrator account's password different than the same account name in the domain. That is, make the .\Emerson (the local computer administrator account) have a different password than the domain_name\Emerson account.

In a domain environment, include the domain name when you log on to Windows (for example, domain_name\Emerson). If you do not include the domain name and the user name exists on the workstation as well as on the domain, the software logs you in as the local administrator on the workstation rather than the domain administrator user.

Important

The first user who logs in to the system after DeltaV is installed must use the administrator account that was used when running Workstation Configuration. This account has administration privileges associated with the computer operating system as well as full access to all DeltaV functions such as configuring hardware, configuring the process system, making changes to the configuration, loading and assigning licenses, downloading all nodes, and so on.

There are other default interactive user accounts on your system, such as Operator, Supervisor, Maintainer, SIS_Configure, and Configure. We recommend creating unique passwords on these accounts as well.

Before any other users log in to the system, some thought should be given to the overall user access scheme. If more than just one or two users will be accessing the system, you may want to limit their ability to change the process configuration or perform downloads. To do this you need to set up user names and access privileges in the User Manager.