Hi, we have implemented GP 2010 R2 on a 64 bit machine that has Win 2003 R2. We are planning to upgrade to Win 2008R2.
IM ver 11, RMT, Webservices, econnect and CRM adapter is all installed in that machine. Also I have SQL Srv 2008 R2 runtime component installed.
What do we need to consider before upgrade? off-course we will backup the server. Questions:
Do we need to reinstall GP and /or components?
Any known issues/fix related to this? Its used by 5 users.
Thanks for the question; we have a KB article that details how to move GP from one server to another:
If you follow these steps you should be able to move over your existing GP databases to the new server. As for eConnect that should be OK after the transfer. For some of the other products that you use such as CRM you may want to further advice if these steps will move them across also.
Please let me know if you would like any additional information on this issue.
Hi Rob, thanks for your feedback. Does it work, if I am not moving to a new server. Rather, I am upgrading the exciting server (that has GP, SQL running in a same box with OS being Win 2003 R2)?. Now I am upgrading the OS on this box to WIn 2008 R2
The directions in the KB are workign equally if you move to another server or upgrade insite. However I would strongly suggest that you do chose the path of moving to a new server, because then you get fresh new environement for your GP client... Upgrading an existing configuration may sometimes carry over old stuff that is not required anymore. I'm thinking in particular about old patches (backups) that keep your GP program directory growing for nothing. I would restore and migrate your SQL databases and then install the GP newly from scratch. Use the latest DVD that was just released by MS on Customer Source and that contains the SP3. If you are not confident and don't want to go with the SP3, just use the previous DVD from GP2010R2 and apply the latest mid-year tax updates.
I've never tried to upgrade a Win2003 to a Win2008R2, but to me it's equally dangerous than going from XP to Win7... you carry over a lot of old DLL's and apps that are not necessarly good to keep.
-- Enjoy the Life+-+-+-+-+-+-+-+ Beat BUCHER Dynamics GP 2010R2 Business Analystwww.fti-ibis.com +-+-+-+-+-+-+-+
Please let us know if you have any further questions.
Beat covered most of the information that I'd have added.
I usually recommend installing a new version of Dynamics GP to a new directory instead of upgrading over a existing version or install, as we just see more success and less opportunity for dictionary files to get damaged.
Other than this, there isn't much during an upgrade of the Windows operating system that affects Dynamics GP.
If we make a fresh install of Dynamics GP on the new server, and restore copies of the existing databases, which files other than Reports.dic and Forms.dic would need to be copied from the existing Dynamics GP installation?
You would want to copy over any dictionary's for any modules where you are using modified forms or reports; the Reports and Forms.dic only have those used by the core GP application such as general ledger, receivables etc.
As an example, if you have modified fixed assets reports you would want to copy over the R309.dic. If you have any customizations for GP it generally would be easier to reinstall them than try to copy them over.
Your best starting point is the Customization Maintenance window in GP, that will help you to identify all the modified forms and reports. Unfortunately, there is no report to print from this window, so your only choice is either to write them down (if not too many) or take screen captures of the list (we have over 120 customized forms or reports).
The best option is to export them all, grouping them by product (use the column sort feature), thus you’ll end up with a bunch of files that you can re-import in your new GP instance. Often this is much more successful than trying to upgrade insight with the GP Utilities, which may stop you from upgrading the dictionaries until you fixed the errors from the customization. Especially when you’re upgrading a major version of GP, there are often changes in the some forms or reports that may prevent you to upgrade.
Your next important files are the VBA customization that might be attached to some forms or reports in the GP folder, and also have a look about any recent changes in the Data sub-folder. You may want to keep a copy of the DEX.ini file, just in case something doesn’t behave as expected on the new instance (some printer settings are stored there).
Also take a backup of all the startup files for your GP client (the ones ending with .SET). We use different variants of startup files because of the various reports dictionaries for our different companies…
Check also if there are any upgrades to 3rd party products that you may have bought for your GP and if they are compatible with the new version you’re going to use (important when you do a major version upgrade).
Last but not least, if you don’t have it yet, ask your MBS partner to get the latest version of the Support Debugging Tools (SDT) from David Musgrave (MS Australia), because this is going to be of invaluable help if you run into troubles… It is also very helpful for the day-to-day administration of your GP system, when trying to track down end-user issues (with security for example), or trying to identify resources in GP.
Hope this helps and you’ll be able to enjoy your new GP instance without too much troubles.
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13