Emerson Exchange 365

• Not Answered

DeltaV Workstation Configuration Receiving Domain Error Prompt...CNTSecurity::IsDomainAdministrator::Failed!A Domain Controller Could not be Contacted

Hello,

I want to put a workstation on my control Network after restoring the image.I restored the image. Created a Node in DeltaV Explorer "Control Network".Assigned Professional Station license to that Node,Assigned Areas.Created Computer Name in my Active Directory of Domain Controller under DeltaV Workstation.Exported Configuration File.I joined the system on Domain.After this I ran workstation Config utility and imported Config file.While Config Utility I prompted a error which is attached. A domain Controller could not contacted in mid of Utility processing During "Creating User accounts.I was logged in as domain Administrator on workstation during this activity and System was on Domain Network.

If i press OK the prompt Utility Starts further process and Finish the Installation.For Operator Station It works.

DeltaV Version:12.3

Domain: Server2008

But for Professional Station ,DeltaV Explorer Opens for 2 Hrs Only and after that I received Database Access Denied.Though DeltaVAdmin password is same on P PLUS and Workstation.But after some time DeltaV Explorer again opens but I am not able to download any thing from Workstation."Professional Station. Unfortunately I am at site and dnt have telephonic access.Your prompt response will be Highly appreciated

Best Regards,

AK

.

AK

• 13 May 2016 12:50 PM
• Cancel

6 Replies

• Steve Linehan

  

  • 13 May 2016 1:13 PM

  It looks like you have an AD problem and not related to DeltaV. If I restore from an image I will always delete any records associated with the machine from AD and then join the PC to the network using the new machine itself rather than creating a record on AD on the proplus. This has proved to be a better approach for me over the years. In the restore I keep the PC offline and make sure it is in a workgroup and then connect it to the network and rejoin it to the domain.

  • Cancel
• AK

  

  • 13 May 2016 1:29 PM

  In reply to Steve Linehan:

  Thanks Steve, for your reply.I did same steps which you mentioned,First I Put the system on WORKGROUP, then Network and after that joined the domain.How can I clear Previous AD logs after restoring the image on domain Client.My second problem still exists.Database access denied for some time on same station.But after few Hours Access available for few Hrs,But not able to download from workstation.

  • Cancel
• Steve Linehan

  

  • 13 May 2016 1:47 PM

  In reply to AK:

  I would put the PC in a workgroup and keep off the network. Then go onto the domain controller and delete any record associated with the new machine in AD. I would then connect the cables one by one doing a ping check on each to ensure each cable can see the DC on all networks. One I have established that all cables are connected correctly on the right network i.e. Cables are not swapped then I would join the PC to the domain. For clearing of the AD records you use AD Users and machines on the Domain Controller. One caveat here is if you have used the PC for manufacturing purposes then you have a data integrity issue. If you are in a non GMP environment or commissioning stage then proceed. Also make sure the DeltaVadmin password on the local machine matches the domain account when you are in workgroup mode.

  • Cancel
• AK

  

  • 14 May 2016 2:40 PM

  In reply to Steve Linehan:

  Hi steve,
  
  Thanks for your help.your solution helped some how.I can open DeltaV Explorer now on my workstation.But i am still not able to download any thing from my workstation.DeltaVAdmin password is same on P+ n on my workstation.I have chekd my node name in AD untr Dv user n workstation.also in DNS.I will be greatful if u can give any wayaround.
  
  Best Regards,
  AK

  • Cancel
• bilal761

  

  • 27 Jul 2016 7:13 PM

  In reply to AK:

  Hi,
  We have recently found this problem as well when we were merging a workstation to a domain. It was of course previously configured for a default workgroup and then converted. When you log in as administrator, we noticed after some frustration and troubleshooting that the login would change from the Domain to the local machine. When logging in as Administrator, the machine would always log in to the local machine and not the domain. The fix for us was to login as with this username: DomainName\Administrator and this error you posted a picture of disappeared and workstation configuration works just fine.

  • Cancel
• Lun.Raznik

  

  • 27 Jul 2016 9:00 PM

  In reply to bilal761:

  Additional note. When cleaning up your AD, also remove entries in the DNS. It seems like you are making progress. Are getting the same error message?

  • Cancel