Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 317 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Available methods in Synchronize Login after password change
knm
Member Posts: 170
I'm currently running NAV 2009 R2 RTC, and have the following question with regards to Synchronizing Windows Login.
My current test environment is setup so that I have 2 tier configuration.
Terminal Server (TS):
- RTC
Database Server (DB):
- NAV Server
- SQL Server
*The servers are not part of any Domain
In the above environment, I took the following steps.
1. Create Local User named "Test1", in both TS and DB.
2. Add the user "Test1" in Administrator Group
3. Using Classic Client on DB, add the user "Test1" as one of the Windows Login
4. Process "Synchronize Login"
5. Login to NAV RTC using the account "Test1" (from TS), and confirm that I can login without any issue.
6. Change the User Login Password for "Test1" to different one.
7. Re-login to NAV RTC using the account "Test1" (from TS).
8. Now I cannot login to RTC.
I understand that if I change the user password on the DB and process the "Synchronize Login" from the Classic Client, but I wanted to know if there were any easier way around.
The only reason why I'm asking is because one of my customer wants to setup a Local Security Policy that the users are required to change the Password every 35 days, and whether NAV was capable of handling such setup, or not.
If the customer has to run the "Synchronize Login" every time the user's password changes, then it would be very inefficient.
Please let me know if you ever encountered this and how you solved this issue.
Thank you.
Kenji
My current test environment is setup so that I have 2 tier configuration.
Terminal Server (TS):
- RTC
Database Server (DB):
- NAV Server
- SQL Server
*The servers are not part of any Domain
In the above environment, I took the following steps.
1. Create Local User named "Test1", in both TS and DB.
2. Add the user "Test1" in Administrator Group
3. Using Classic Client on DB, add the user "Test1" as one of the Windows Login
4. Process "Synchronize Login"
5. Login to NAV RTC using the account "Test1" (from TS), and confirm that I can login without any issue.
6. Change the User Login Password for "Test1" to different one.
7. Re-login to NAV RTC using the account "Test1" (from TS).
8. Now I cannot login to RTC.
I understand that if I change the user password on the DB and process the "Synchronize Login" from the Classic Client, but I wanted to know if there were any easier way around.
The only reason why I'm asking is because one of my customer wants to setup a Local Security Policy that the users are required to change the Password every 35 days, and whether NAV was capable of handling such setup, or not.
If the customer has to run the "Synchronize Login" every time the user's password changes, then it would be very inefficient.
Please let me know if you ever encountered this and how you solved this issue.
Thank you.
Kenji
0
Answers
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
Thanks for your response.
So what would be the right way to configure the servers so that the I can avoid this issue? Should I be using the AD? or any other alternatives?
Thank you.
Kenji
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
I'll start testing using AD.
Kenji