Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Infor / Lawson Platforms
S3 Systems Administration
Migrating to New AD Domain
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jessica
Past 24 Hours:
2
Prev. 24 Hours:
0
Overall:
5164
People Online:
Visitors:
271
Members:
0
Total:
271
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1348
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
S3 Systems Administration
Migrating to New AD Domain
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Melissa Fowler
New Member
Posts: 2
9/13/2012 3:22 PM
Anyone ever try to Migrating LSF 9.0.1 Windows server to New AD Domain?
We are LSF 9.0.1.10 & WAS 7.0.0.21. We authenticate to AD/LDAP through ADAM.
Now we need to move to a New Windows Domain.
Our first attempt to migrate the test server using the "selected" migration tool, resulted in WAS not loading. I've been able to get finally get WAS to load and get some functionality to the system, but the question is once they "turn off" the old domain, will the system crash?
Lawson recommends a complete reinstall of WAS, ADAM, & LSF. Upper managements, wants us to just update all the pointers.
Has anyone successfully migrated to a new domain?
If so, any warnings or gotchas?
ekbelt
Basic Member
Posts: 8
9/13/2012 3:58 PM
I think the big thing is SSOConfig... have you tried to get an opinion from a licensed Lawson consulting firm? They might be able to give you some first hand experience. We just went through an upgrade to 9.0.1.10 and we have the small possibility of a domain change in the future. Our consultant said it was possible, and pretty much has everything to do with the ssoconfig. There are a few other things that need to be changed, but he thought it was possible. We went through the process of switching our PDC in the ssoconfig successfully, although we just tested it with a secondary so it was not a 100% domain change. Just a change in where we are authenticating.
Good luck! Post back your results if you are successful!
Kwane McNeal
Veteran Member
Posts: 479
9/13/2012 5:14 PM
Melissa,
This process is fairly simple, though a bit tedious, if you're unfamiliar.
Feel free to give me a call, and I'd be glad to help explain it.
Kwane
505-433-RSGI (7744)
Melissa Fowler
New Member
Posts: 2
9/21/2012 3:18 PM
The SSO config portion seems easy. Its changing all the server names in WAS to reflect the new domain instead of the old domain. Where do I go to tell Lawson to use the LawsonUsers group from the new domain instead of the old domain. How do I modify the Lawson account to point the new domain instead of the old domain - I can't just edit SSOP entry for the account, tried that.
And are there any other gotcha's that may show up when they turn off the old domain, that could interupt services on any of the Lawson servers. Just a search of the install.cfg file shows way to many references to the current domain.
Administration wants my assurance that the server is 100% covered and won't go down when the old domain is turned off. My response is then we need to have Lawson re-installed. Otherwise, I feel like I can only give a 90% guarantee that I have covered all touch points to the old domain.
You are not authorized to post a reply.