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
- 262 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
Technical upgrade to SP3
ta5
Member Posts: 1,164
Hi
I plan a techn. upgrade to SP3 to quite a few client machines. Since we do not have the option with automated software distribution I had the idea of just to copy a few files over the existing SP2 installation.
Is this a reasonable option? If yes, which files should be replaced?
Thanks
Thomas
I plan a techn. upgrade to SP3 to quite a few client machines. Since we do not have the option with automated software distribution I had the idea of just to copy a few files over the existing SP2 installation.
Is this a reasonable option? If yes, which files should be replaced?
Thanks
Thomas
0
Answers
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
I would say - no problem - I do it all the time...And have never had problems?
But if you are working with Citrix or Terminal Server - do a "normal" installation/upgrade...
Of course if you need certain integrations to work relying on other Navision components than the actual client-directory you should also update that...
Else - just copy the client-directory including ENU and other language directories...
Henrik Frederiksen, Denmark
Hi Frede,
sorry to disagree with you, but I don't think this is good as a "general comment"
yes I agree, in some circumstances this will work fine, and for some clinets there will not be a problem, and some registry entries are not needed. But just hat one member out there that tries this themselves and messes up is enough to say that it is not a general solution.
What if there are OCXs and DLLs that need to be registered in the new version, the list goes on.
I know a person that drives his car without wearing seatbelts, and he is not dead, from that you can not say the reverse i.e. that it is safe to drive without seatbelts. He is just lucky ... so far ...
Thank you for your thoughts on this topic.
Thomas