When creating creating a new user, it always creates it as a domain user.
How can we create a user as a local user instead of a domain user?
When performing the same action on my local DMA, it creates the user as a local user.
Is there a difference between creating a user on a local DMA vs a remote DMA?
Is a user created as a local user on your local DMA, but from the moment you create a user on a remote DMA as a domain user?
If so, how can we create a local user on a remote DMA?
Hi Brecht, can you please verify the DataMiner Server name?
Due to technical limitation, agents name shouldn’t be longer than 15 characters, otherwise this is causing problems to create local users from within Cube.
Hi Brecht,
It is never possible to create a domain user via DataMiner. DataMiner only reads information from the domain and you can only reference to an existing user on a domain.
Creating a user in DataMiner will always be a local user on the OS of the DataMiner Agents.
Now, your screenshot seems to indicate this demo user you created is a domain user, but either there is an issue somewhere in the visualization, or the DMA you connected to has the DC role, and this is not a supported setup. DataMiner should not run on a domain controller. Is the prefix ‘SERVER-DATAMINE’ effectively a domain or is it a hostname?
Bert
We’ve verified that the server isn’t a domain controller as it has a domain role of 2 (standalone server).
The server name however exceeds the 15 character limitation.
Most likely we’re facing the same case as indicated by Karel.
My guess is that the DataMiner system you’re working on is the Domain Controller itself, in which case any user created on there is automatically a domain user.
If so, I would say this is not a recommended configuration.
I’d even argue it’s quite dangerous to run DataMiner on the domain controller since DataMiner users can for example run code on the DC through automation scripts.