Microsoft,Great,Plains,7.5,Per computer Microsoft Great Plains 7.5 on Pervasive SQL Migration to Win

Gone are those times when the companies and the organisations didn't need a hi-tech system to handle them. Owing to the considerable increase in the business sector and thus, an enormous increase in the complexity of the organisational struc ----------------------------------------------------------Permission is granted for the below article to forward,reprint, distribute, use for ezine, newsletter, website,offer as free bonus or part of a product for sale as longas no changes a

This opens good strata of possibilities for old versionsGreat Plains and Dynamics GP customers on Pervasive SQL 2000 to move fromWindows 2000 or Windows NT Server to Windows 2008 or Windows 2003 Server andredeploy Great Plains user workstations on Windows XP or Vista.  There is always a possibility to upgrade tonewest Dynamics GP version 10.0, which requires migration from Pervasive SQL toMicrosoft SQL Server 2000 for Great Plains 7.0, however we understand that ifyou decided to stay with old version, this decision probably was based on thelack of budget to pay Great Plains annual enhancement program 1.       MigrationScenario.  We had Pervasive SQL Server2000 SP2 running on Windows XP workstation (deployed as Great Plains Server).  Great Plains User workstations were onWindows 95 (this is in our opinion the same as if they would have poor hardwarewith Windows 97, Windows 2000, or even first releases of Windows XP).  Target was to move them to Windows 2008Server (please, do not expect too much miracles, it should be 32 bit edition,it is unlikely that you could install Pervasive SQL 2000 SP 3 maximum on 64 bitplatform, if you find out how to do this - let us know and we will ship yousmall pocket aquarium).  FRx was notdeployed in this environment, but we know that old FRx Sysdata folder is notsupported on Windows 64 bit platform 2.       GreatPlains Server Side Installation.  LoadPervasive SQL 2003 Service Pack 3 (we recommend this service pack, as you donot have to alter Pervasive Engine Settings, for older SPs you need to checkwith GP techknowledge on the Settings required changes).  Open Port 3351 on Windows 2008 Firewall - asyou may know Windows 2008 Server blocks all the ports, except the ones used byrequired services (Pervasive SQL 2000 is definitely not one of those).  Copy Great Plains Database Folder (typicallynamed Dynamics from old server to the new one) and share this folder.  In security for this shared folder add DomainUsers to have Full Control (this is required by Pervasive SQL 2000 data access,adding and modification model) 3.       GreatPlains Client Installation.  Please,insert Great Plains CD#1 (if you have additional modules such as Fixed Assets,Manufacturing, Human Resources, there is no need to install them as we willcopy their libraries from old Great Plains Workstation, see our notes below)and follow the steps to install Multiuser workstation.  Use the same path as you had it for legacyinstallation, usually C:\Dynamics.  Whenuser workstation installation is done, rename C:\Dynamics folder toC:\OldDynamics.  Then copy old DynamicsGP workstation to your new user workstation computer to the same folder, in ourcase C:\Dynamics.  If you have thirdparty add-ons, such as Wenn Soft  FieldService, please read Great Plains ISV add-on documentation.  In the case of Wenn Soft we were able toenable it by registering WS*.dll, simply copy them from your GP workstation toSystem32 folder on each user workstation and register them via REGSVR32command.  If you do not do this you willget error message on Great Plains login and Wenn Soft card login: DecryptService Failed to Start.  If your oldPervasive SQL based Great Plains system was on UNC Path, you will need locationtranslation service or help 4.       Intellisol.  This add-on was not present in our testedmigration, however we believe that Intellisol Advance Purchase Order Processingor Project Accounting would require similar approach 5.       GreatPlains Accounting For DOS and Windows 9.5, 9.2, 9.1 or earlier versions.  Yes, you got it - if you still have thislegacy Corporate ERP in production, we support it.  We support GPA for local customers inChicagoland, or if you are in USA and Canada we support it via web session andother remote support technologies.   Wetried and got success in GPA for DOS and Windows redeployment on Windows 2003Server Release 2, where GPA workstations were on Windows XP Professional 6.       OldDynamics version upgrade path.  In caseif you decide that it is now time to invest in Corporate ERP system re-haul andupgrade, what we need from you is to sign Dynamics GP Switch VAR form to AlbaSpectrum .  Then we will be your brokerfor Microsoft Business Solutions, and we should be able to add new company inthe case if you are on Great Plains Accounting for DOS or Windows and give youits registration key.  If you are onGreat Plains Dynamics 6.0, 5.5. 5.0, 4.0, 3.2 or earlier your upgrade pathshould be reviewed.  Simply call us andhave us to see via remote connection or web session you current Great PlainsWorkstation 7.       Wecertainly understand your concerns that Great Plains Dynamics and eEnterprisewere targeted to mid-market businesses, and their redeployment is notapparent.  If you feel that budget istight, try to make as much homework as you could and then feel free to call ouroffice for urgent help 8.       Howto get help?  Please, feel free to callus: 1-866-528-0577, outside of USA: 1-630-961-5918 or email [email protected]  We are verytechnical and real Dynamics GP Dexterity, SAP Business One SDK programminggurus.  We have Great Plains SoftwareDevelopment Factory and could support unlimited Dynamics GP Customization andProgramming needs.  Plus we speakEnglish, Chinese, Spanish, Portuguese, Russian, and not only as native speakingsales folks, but as real technical consultants. If you prefer skype: albaspectrum