Dynamics GP Partner Newsflash: Great Plains Upgrade notes

At this time, May 2009, Microsoft Dynamics GPAt this time, May 2009, Microsoft Dynamics GP
10.0 version has pretty reliable service packs10.0 version has pretty reliable service packs
under its belt, especially current SP3.  Earlierunder its belt, especially current SP3.  Earlier
Great Plains 10.0 upgrades were really surprisinglyGreat Plains 10.0 upgrades were really surprisingly
challenging, especially prior to the time of GP 10challenging, especially prior to the time of GP 10
SP1 was released.  In this small publication weSP1 was released.  In this small publication we
would like to share recent Dynamics GP upgradewould like to share recent Dynamics GP upgrade
from version 8.0 to 10.0 with migration to newfrom version 8.0 to 10.0 with migration to new
SQL Server machine: 1. GP version 8.0 ServiceSQL Server machine:
Pack 5 is required.  If you plan to move one step1. GP version 8.0 Service Pack 5 is required.  If
to 10.0, you will need to apply SP5 for Greatyou plan to move one step to 10.0, you will need
Plains 8.0.  Version 8.0 was pretty advanced withto apply SP5 for Great Plains 8.0.  Version 8.0
Service Pack applications, and virtually all you needwas pretty advanced with Service Pack
to know is to click install button and all the workapplications, and virtually all you need to know is
will be done automatically 2. Great Plains migrationto click install button and all the work will be done
to the new server.  For earlier versions of GPautomatically
you had pretty reliable scripts, where everything,2. Great Plains migration to the new server.  For
including user passwords was transferredearlier versions of GP you had pretty reliable
smoothly, with current procedure, available fromscripts, where everything, including user
Partner Source, passwords are not transferred,passwords was transferred smoothly, with
until the name of the SQL Server is exactly thecurrent procedure, available from Partner Source,
same as the old server name.  We recommendpasswords are not transferred, until the name of
you to move GP 8.0 SP5 databases to new SQLthe SQL Server is exactly the same as the old
Server.  Likely that you will migrate backupsserver name.  We recommend you to move GP
from SQL Server 2000 to 2005, or even SQL8.0 SP5 databases to new SQL Server.  Likely
2008.  In this case, please change DBthat you will migrate backups from SQL Server
compatibility level respectively 3. Please, prior to2000 to 2005, or even SQL 2008.  In this case,
launching Dynamics GP Utilities, be sure that youplease change DB compatibility level respectively
applied GP 10.0 Service Pack 3 (or newer).  DB3. Please, prior to launching Dynamics GP Utilities,
Tables upgrade process is very smooth and webe sure that you applied GP 10.0 Service Pack 3
saw no issues 4. Reports.Dic upgrade.  Here, you(or newer).  DB Tables upgrade process is very
should be aware that Dynamics GP 8.0 was moresmooth and we saw no issues
tolerant to Service Packs discrepancy, meaning4. Reports.Dic upgrade.  Here, you should be
that user workstations could be on differentaware that Dynamics GP 8.0 was more tolerant
service packs and patches level  This fact wasto Service Packs discrepancy, meaning that user
probably causing SQL red box error messagesworkstations could be on different service packs
from time to time (as you know GP Service Packand patches level  This fact was probably causing
upgrades SQL Stored Procedures for DynamicsSQL red box error messages from time to time
and Companies databases).  In our case, we got(as you know GP Service Pack upgrades SQL
Reports dictionary upgrade problem, getting errorStored Procedures for Dynamics and Companies
message that Dynamics.dic is not compatible withdatabases).  In our case, we got Reports
original Reports.dic version.  This problem wasdictionary upgrade problem, getting error message
fixed when we forced reports migration on thethat Dynamics.dic is not compatible with original
original GP 8.0 Service pack 5. Additional Notes. IfReports.dic version.  This problem was fixed
you are Great Plains Consultant, you probablywhen we forced reports migration on the original
aware that Microsoft Office 2007 as well as .NetGP 8.0 Service pack
components, released after Dynamics GP 10.0,5. Additional Notes. If you are Great Plains
lead to the fact, that you can no longer installConsultant, you probably aware that Microsoft
Great Plains form original CDs.  Now you have toOffice 2007 as well as .Net components, released
apply DexSkipDotNetCheck.mst andafter Dynamics GP 10.0, lead to the fact, that
SkipDotNetCheck.mst technologies, pleaseyou can no longer install Great Plains form original
download them from Partner Source 6. FRxCDs.  Now you have to apply
upgrade.  Assuming that you are installing FRxDexSkipDotNetCheck.mst and
fat client and not fighting with Citrix or TerminalSkipDotNetCheck.mst technologies, please
Server, FRx upgrade is smooth.  We upgradeddownload them from Partner Source
FRx 6.7 Service Pack 5 to SP 10 7. Office Web6. FRx upgrade.  Assuming that you are installing
Components.  If you will get Microsoft OfficeFRx fat client and not fighting with Citrix or
Metrics error message on Dynamics GP homeTerminal Server, FRx upgrade is smooth.  We
page, please download owc11.exe file fromupgraded FRx 6.7 Service Pack 5 to SP 10
Microsoft download center 8. Technically, you7. Office Web Components.  If you will get
could find these upgrade guidelines on GP PartnerMicrosoft Office Metrics error message on
Source or Customer Source, however we triedDynamics GP home page, please download
to popularize the concerns and pluses by publishingowc11.exe file from Microsoft download center
this Dynamics GP FAQ and Great Plains Guru stile8.
article