Emerson Exchange 365

Do not change the password using anything except the DeltaV Workstation config or the setpass utility. This will ensure that all services are running and with the correct credentials after the change. The only other thing to worry about is any third party applications that access data from DeltaV (OPC, PI and Others) If you have installed these they may be configured with the DeltaVAdmin account and then would have to be updated also.

This was discussed here also. 

To clarify, are you talking about DeltaVAdmin or Administrator? As Steve Linehan noted, there may be dependencies, specific to your system, that require that account. Checking the Services console and your DCOM configuration are a good start.

If you're referring to Administrator, this account is disabled in DeltaV 13.x and above. If you are targeting these versions, it would be a good idea to transition any services using Administrator to a dedicated, non-managed service account.

In reply to DXSANCH:

DXSANCH, the Windows built-in Administrator account should be disabled completely and replaced by another username as already mentioned by other DeltaV users on this thread - and yes, since you are in a workgroup environment you will need to do that on every station of your system - domains would not only make this process easier, but also improve the overall cybersecurity of your system.

As also said, since v13+ systems already force users to define the username of an administrative account, and we also have the DeltaV Security Administration tool in v13.3+ that makes it simple to go through the process after an upgrade to v13. Instead of managing this account, you should really disable it altogether and then manage its replacement accordingly.

Worth noting that an upgrade to a newer DeltaV version will improve the cybersecurity of your system from various angles.