Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Does anyone use "Build restriction"?
Phenno
Member Posts: 630
Hi, all!
Does anyone use "Build restriction" function on service tier setup? By default it is set to WarnClient which should produce warning message if client with different build connects to a server, but I always receive error message that my build is different. I've tried this on number of different clients, NAV versions etc. and always get error instead of warning.
Does anyone use "Build restriction" function on service tier setup? By default it is set to WarnClient which should produce warning message if client with different build connects to a server, but I always receive error message that my build is different. I've tried this on number of different clients, NAV versions etc. and always get error instead of warning.
0