Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K 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
Options
NAV RTC Client with multiple Terminal Servers
bbrown
Member Posts: 3,268
We have a client considering running the RTC client in a multiple Terminal Server environment. The server connections would be managed either by round-robin DNS or a NLB cluster arrangement. They have not decided yet. My thinking would lean toward NLB.
What are the issues with running the RTC in this environment? We have a client that runs the classic client in a NLB cluster. There we re-directed the user ZUP files to a shared network drive. Would using roaming user profiles be a valid approach for the RTC?
What are the issues with running the RTC in this environment? We have a client that runs the classic client in a NLB cluster. There we re-directed the user ZUP files to a shared network drive. Would using roaming user profiles be a valid approach for the RTC?
There are no bugs - only undocumented features.
0