Emerson Exchange 365

• Not Answered

How to convert Professional plus to operator station using PCInstall utility?

Hello, Emerson Exchange I need to configure operator station and I am facing these kind of situations :

DeltaV 14.3

PC 1 : “ATS”, win 10 enterprise, workgroup,

PC 2 : “ OPR”, win 10 professional, workgroup,

Communication : Straight ethernet cable 

A)Initially both the PC was configured as Professional plus and the PC  name & Pro+ name was the same. I created a operator station node named as "OPR" in PC1 and simultaneously changed the name of the PC 2 to "OPR" and rerun the workstation configuration as operator station from pro+ and loaded the workstation configuration file and it rerun successfully.Once rerun completed the system restarted and i was not able to login in the user account (account with DeltaV privilege “EMERSON”) & found that the account was locked out.  1. How can I login into operator station ? 2. In DeltaV user manager there are many users provided after installation but password to access the account ? 3. What’s the purpose of server password utility at the time of rerun & its relation with default DeltaV user accounts? 4. How to convert the proplus machine into an operator station using PCInstall utility in a workgroup setting ?

1. B) In a professional plus station what are the results of changing the DeltaVAdmin user account ?  I lost the privilege in the local user account “Emerson” ( an account as administrator, able to access dbadmin) How can this account be resolved or create a new account with full privilege as administrator ?

• configuration

Rishi

• 7 Mar 2020 5:39 AM
• Cancel

2 Replies

• Andre Dicaire

  

  • 9 Mar 2020 5:06 PM

  Rishi, Not sure if I've followed exactly what you've done, but if you are renaming the Pro Plus, you should do that first (too late?). I think you have to create a new Pro Plus using a new database. Then, when you import your configuration, it will skip the Pro Plus as one is already there. Once the Pro Plus is up and running you should then move onto aligning your other changes.
  
  As a cyber security precaution, default Administrator accounts are disabled by DeltaV Install. You should always create your own administrative accounts and not use default accounts that may have their default passwords compromised. DeltaV Used to provide the DeltaVAdmin account with a default password, which overtime, became known and was unsecure. Now, DeltaV Workstation Configuration requiers you to provide the password. no defaults are used.
  
  When you run Workstation configuration, you are prompted to set the DeltaVAdmin user password (or confirm it). This account is a local account on every DeltaV computer and is used by DeltaV services. It is used to connect engineering tools like Control Studio to the Pro Plus Database server. The Password must be the same on all machines, but also, all the services that use this account must be updated so they have the right password. Never change the DeltaVAdmin password via Windows user manager. You must use the password utility provided SERVPWD.EXE. This utility updates the account password and all the detlav services that makes use of it.
  
  In a workgroup environment, you have to create the Windows users on each workstation. Users logon locally, and if the windows account for the user name does not exist, you cannot logon. DeltaV User manager creates Windows users on the Pro Plus and you get to set the Password for this Windows User. (there is no DeltaV user password, only the windows user password). When you logon to the computer, you first logon to windows, which gives you windows user privileges (file access security and all that fun stuff). Then you logon to DeltaV. This logon defines the DeltaV write access privileges and span of control in DeltaV. It uses the windows user and password to validate, but does not change the Windows user.
  
  In DeltaV logon, you may see a long list of DeltaV Users defined in the database, but in order to logon as one of these, there must be a windows user/password defined for the user. In a workgroup, this must be a local Windows account.
  
  In answer to your specific question, The DeltaVAdmin account is strictly for services and not for interactive users. Always use SERVPWD utility to change this password. You must run this on every machine. If this account password does not match, you will not be able to connect to configuration database and such. You do not need to run Workstation configuration if you simply want to change the DeltaVAdmin password.
  
  For an administrator account, you can create this account using Windows User Manager prior to installing DeltaV. Make this user part of the Administrators Group. (same settings as the default Administrator account. This default account will be disabled by DeltaV so do not use this account to install DeltaV). During install running Workstation configuration, the install will add this account to the DeltaV user and DeltaV ADmin groups.
  
  After DeltaV is installed, you can go to Windows User manager and enable the default Administrator account. You need to know its password. If you have another administrator privilege account, you can set the password on Administrator so that you can now logon as ADMINISTRATOR. This account may allow you to logon to DeltaV as administrator, and from there you might be able to get the Pro Plus fully functional. Once you have your own Admin account set up again, disable the Administrator account. You don't need it anymore.
  
  On your new Operator stations, you need to create the Windows accounts, all with matching passwords to the Pro Plus versions. If you do not have a Windows User for a DeltaV account, that DeltaV logon will not work on that computer. Note that if you have Engineering users and you only want them to logon to the Pro Plus, by not creating their windows account on the Operator station, they cannot log on to that computer or logon to DeltaV logon on that computer.
  
  Hope this helps.
  , and I think this will require you to re-import your data base. When you do, it will skip the pro plus because there is already a Pro Plus

  Andre Dicaire

  • Cancel
• Rishi

  

  • 13 Mar 2020 7:16 PM

  In reply to Andre Dicaire:

  Andre Dicaire, Thakyou for your continuous support and answering the questions above. When I asked those questions I messed up the functionality of the operator station with Pro Plus function and there were some mismatch in configurations and I resolved some issues. After that my operator station functions like this. I converted the Pro Plus to operator station via the rerun function of PCInstall utility with operator operator station configure file( not any new DeltaV Installation). As I did that the rerun was successful and I logged in as operator in operator station and the comm integrity between Pro Plus and operator station was good and auto update service did its job but what failed was that the upload of displays at the time of download, but I was able to open the module faceplate in operator station. (The purpose of this offline configuration is to check the super cool features of DeltaV in aspect of granting operator access to control and monitor.) If this was the issue why does it require to re-import the database and skip the pro plus as you have mentioned above ?
  
  Regarding the DeltaVAdmin account , I found out that when the DeltaVAdmin password is manually changed from the windows user manager all the privileges to the local account i.e access to dbadmin is lost. After assigning a new password via SERVPWD utility, the access isn't granted to the local account and a new local account also cant be created with same administrator privilege. This requires reinstall.

  • Cancel