New-AXuser doesn't give the desirable output

(0) Share

Report

Posted on by Community Member

Hi,

I've created a script to automate the creation of new user Active Directory users combine with a profile in AX. With the use of the commandlet New-AXuser.

Everything works fine. Expect for the following populating of some user attributes:

The name in AX is populated with full domain name \ windows account name example "contoso.local\jdoe" instead of John Doe.

The "language" and "Alternate help language" is EN-US instead of EN-GB. EN-GB is the systemlanguage configured in "My systemparameters". I already changed every language setting from the OS (server 2012R2) to EN-GB.

When I use the Active Directory import Wizard to import from AD. I get the correct settings name and language settings.

Please assist,

Mike

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Suggested answer

Martin Dráb 239,381 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

What you get in the name corresponds to examples in documentation, therefore the problem seems to be in your expectations. It doesn't work as you thought.

I think that things like language are copied from the admin user. The kernel surely doesn't know anything about "My systemparameters" and if you added code to use them, it clearly doesn't work (but we can't comment on it without more information). It doesn't depend on your OS language either.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Thanks for your reply. We can live with the name population :)

The language settings are still a problem. Unfortunately the language settings are not copied from the admin user. I tested this.

What information do need?

Was this reply helpful? Yes No
Suggested answer

Vilmos Kintera 46,149 on at

Like (0)

Report
Copy link

Link copied!

One solution could be to write a batch job that goes through the user list, fetches the Active Directory data, and if the name and language does not match what it should be, then simply update it. You could run it like daily, or ad-hoc as part of your onboarding process once a user account is provisioned within the AD.

Another idea is that because we are talking about a PowerShell cmdlet for adding the user, why don't you just make it into a script where the user is created first, then you could use Business Connector within PowerShell to talk to AX and then update that record?

https://blogs.msdn.microsoft.com/axinthefield/harness-the-power-of-powershell-and-the-business-connector-too/

You could build it on top of Martin's already existing script:

http://dev.goshoom.net/en/2014/04/creating-ax-users-in-powershell/

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Thank you! I'll take a look at your suggestions.

Was this reply helpful? Yes No
Suggested answer

Martin Dráb 239,381 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

After looking into the library implementing the Powershell cmdlet, it seems to me that it calls SysUserManagement::registerUser() in AX. If it's so, you can both evaluate how the method exactly works and make some changes there.

Was this reply helpful? Yes No
Vilmos Kintera 46,149 on at

Like (0)

Report
Copy link

Link copied!

Please take your time to verify answers by ticking the checkbox next to each helpful answers in order to close the topic and assist other users with similar problems.

Was this reply helpful? Yes No