Log in as the directory facing account Unity is running under and run DAD - select one of the users that's failing and check the import on it - it should run through all the properties that we need to be able to update and report which one(s) fail.
Since this Unity is converted from demo, I am now doing setup again to upgrade it. I am seeing it keel copying the stuff it actually copied in the first setup. Will this process is exactly same as install?
Another question: is there a way to rerun the conmfiguring service wizard and message store wizard? I recall in unity3.x we can run the second configuration step to configure message store.
I had a problem that could be what you are describing. By any chance, are the accounts who error out Domain Admins? That was my issue - I had to make the "UnityDirSvc" account a Domain Admin as well and only then did the error go away and I was able to import them.
I had this problem recently with an MCS 7835 and Unity 4.03. It was a fresh install and I had just moved the DB and transaction log files to the D drive. In order to do that I stopped all the unity services and once moved restarted, but they hadn't completely restarted gracefully. I just rebooted the server and all was good after that.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.