800xA 5.1 Workplace/Node connect Error -> Invalid Account in Configuration Wizard
I copied a workplace 5 times in vmware and while testing them i have found a problem on two clients:
When I start the Action "System software User settings" in the Configuration Wizard iv got an Error-Pop Up -> "Invalid Account"
When I view the log is there only one new entry each time:
"Configuring dom\800xaService as service account on local machine"
- the 2 nodes with this issue are shown in RnrpMon
- i disconnected die worplaces from the domain and reconnected them already - still the same error
1.Are you able to login in the workplace with the domain\800xaservice account?
yes on both workplaces with this problem
2. Disconnect the worplace two clients from the 800xA system and connect once again.
I already disconnected and reconnectet the workplaces from the domain... but the major problem is that they are not really connectet tot the 800xA system.
I cant even see a connect node or disconnect node "Action" in the Configuration wizard.
And I checked the health check procotolls and found nothing strange.
I try now to take a working VM, copy it and syspep it again for the 2 not working machines.
Are you using the same nodenames as your former clients? Maybe the disconnect of your old clients form 800XA had failed. Have a look at the nodes structure. Try to use different names. But the first step is to run all of the 800xA services under a valid account.
It is a good idea to recreate the machines from a running machine, maybe use a completly new name.
After making a copy, make it run without doing any changes, now disconnect from the 800xa system (as u said it is copy of running machine) later disconnect from the domain. Restart the machine. Now make the necessary changes like change machine name,ip etc.. and then connect it to domain And then try to connect it to 800xA system. This will work. As i have done this earlier.
Thanks for help
- the strange thing was that the cofig wizard on the conectivity Server wrote in the log "The server process could not be startet because the configured identity is incorrect. Check username and password"
But i never changed the password of 800xaService on the this VMs. And all 5 machines where from the same VM...
Now I took one of the working VMs and everything works (sysprep and IP settings changed)
I don't know what was wrong with this 2 VMs but now I'm glad that everything works fine now.
Cloning is not a documented procedure, but should work if made correct.
I prefer to clone clients/servers while OFF domain/xA system.
For each "new" clone made from "golden image":
a) change IP address (remember to check/purge the "hosts" file if manually edited previously)
b) change hostname + reboot
c) review/configure DNS client settings
d) join domain + reboot
e) make sure service account is administrator on new clone (I prefer using Domain Admin account in contradiction with Users Guides) and member of the IndustrialAdmin/User groups. Hint: study output of "whoami /all" - it will tell...
f) remove any lingering ..\IndustrialITData/Temp folders (might require "Take ownership")
g) verify firewall exclusions or rerun the wizard on CD-ROM
h) Run Config Wizard -> Software User settings
i) Verify RNRP "sees" client from aspect server or vice versa
j) Add as new client from arbitrary existing server node OR connect as existing (and free) old using "Connect node" from Node Admin Structure or Config Wizard in client.
h) Verify Data/Temp folders are created with content. Attempt to launch a workplace.
There could be more items...
"I copied a workplace 5 times in vmware "
This is your problem. When you clone the system like this, there is no guarantee that your clients can re-connect to the server again. They may not even connect to the domain properly. The messages you are getting indicate the identity of the cloned machines is unclear to the domain controllers. This is expected. You should .....
- Rename and remove the cloned client from the domain.
- Verify your computer name and IP adress settings. Configure RNRP etc.
- Add the client back to the domain with it's corrected unique client name.
- Ensure that you are logging onto a domain account and that all services are starting. Use the AfwConfigWizard on the local client to correct settings if required.
- Verify the DNS and Active Directory entries for the new client.
- Remove the client from the 800xA system and re-add it again.
---- Use the AfwConfigWizard on the local client to disconnect from the system. Do NOT update the server. ( there is a check box for this)
---- Check that the Cache Directories (OperateITData) have been deleted.
---- Use the AfwConfigWizard on the primary aspect server to connect the client to the system again.