You’re offline. This is a read only version of the page.
115
Back in 2009 I had to move our Dynamics install from one domain to another.
I had the luxury of having the AOS and database servers on both domains so it was a simple add users with the new domain and cutover.
Now I have to move the AOS and database to a new domain and I DO NOT have the luxury of being able to join the domains.
I've been trying to find out how I can add a new domain user to the database tables to allow that user to log in and add all the other new domain users.
Does anyone know all the tables I need to touch in the database to add this user?
I do have the domain user SID in the new domain. I tried adding them to sysuserinfo, userinfo, and usergrouplist tables with the same made up recid.
Any help out there??
*This post is locked for comments
So updating the userinfo table with the SID, Name, domain and nickname fields worked.
I can start the Dynamics Ax client. I have a new problem and will post it separately if I can't find an answer
I wish I could set up the trust between the two domains. However it violates several policies and firewall rules.
I used the trust method back in 2009 - it works.
I'll try the userinfo update later this week and see if that works
If you can do so in a copy/testing environment, yes I believe you should try that. It should give you the one foothold account you need on the new domain to add the rest of the users before completing the switch.
So I should try shoving the SID, domain user, and domain in the Admin account record?
(userinfo table?)
On a side note, I have moved an AOS between domains. If you can manage to make the domain user names the same where only the domain name itself is different, then this change can be very fast. First, use SQL to update the NetworkDomain field for all of the appropriate UserInfo records that are moving. Then, log in as Admin, and for each user un-check the Enabled box, and then re-check the Enabled box. This fetches the new SID for the user in the new domain, after which that user can logon normally. This can also be accomplished in a small code loop on a job.
At the very least you must keep your Admin account functional in order to start the AOS properly. Thus, you will have to replace the SID on the UserInfo record for the Admin account, typically pointing this to a domain administrator account or whatever makes sense to you. You may have to SQL this change, along with the NetworkDomain and NetworkAlias fields, in order to align Admin with your new domain.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,151
Super User 2024 Season 2
#2
Martin Dráb
229,993
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (