Recommended: System Errors? Click here to Fix your PC »
In this small article we give you highlights on how to move Microsoft Great Plainsserver to new more powerful hardware with minimal problems. Here we do not provideyou information on GP version update, just how to redeploy. Our approach will be togive you architecture understanding, so you could make your decision knowing theoptions and technical reasons. You should be familiar with such concepts asMicrosoft SQL Server and its versions: 7.0, 2000, 2005, ODBC connection specifics,GP customization and its architecture (if you have one), GP ReportWriter andReports.DIC, Dynamics.set file (where you see all your GP products integrated intoyour GP installation), eConnect and Business Portal (if you deploy BP), CrystalReports and MS SQL Server Reporting Services (or SRS  again if you deploy CR orSRS) Risk minimization. Begin with philosophy, not with technical side of it,especially if you in the reasonable beginning of your career as DB Administrator, ITspecialist, GP programmer or consultant. If you move and redeploy GP over theweekend and then on Monday users will not be able to use it and in this casebusiness will stop its operations  then you will be forced to roll back to the oldserver and this will be a lesson for you  strategy and planning is required Windows Server Name and IP address. Please, make you homework first and getawareness if you do or donÂ't have customizations: Microsoft Dexterity custommodules, SQL stored procedures (integrations, extensions to dex modifications,etc.), custom reporting  all these are candidates that original software developershardcoded server names, IP address or placed these as parameters into setting files. If you are not really supporting and not in contact with original programmers orreports designers  the safest approach would be keep the same server name and IPaddress for the new server box (yes, this is what you just read  rename the oldserver and mount the new Goliath hardware box on its place with the same name andIP) GP DB migration. There are special scripts for transferring user logins andpasswords on GP customer source. This step is required and you have to follow theinstructions (or you might be the one who is MS SQL Server DTS maestro  then youmay feel comfortable to transfer security this way  in this article we assume youare normal IP person). These scripts should capture logins on the old server andsave them to the file. Then on the new server you create the logins from the fileand then grant access (via special scripts, not generically) for the users to the GPcompanies/databases Server Side Software. Sometimes you have such annoying things as softwareinstalled on the old server, utilized by users in their daily operations: eConnectis good example. eConnect might be used by Microsoft Great Plains modified logic,GP customization or such add-ons as Microsoft Great Plains Business Portal  checkif you use Requisition Management, Order Management, Employee Self Service and BP HRmodules, Electronic Document Delivery  to name a few modules of BP family. If thisis the case  you should be comfortable to face Business Portal redeployment, withpossible BP customizations, integrations, custom logo, etc. FRx. This is financial reporting software, typically in use by your top financialpeople: controllers, VP finance, etc., so treat it with respect. FRx has sysdatafolder, where all FRx settings should be stored. However, this is not the end ofthe concerns  FRx publishes its reports either to FRx viewer or to the files (likeinto Excel worksheets), and in the case of printing to the file  output directorymight be hardcoded  unpleasant result might be FRx bombing out Report Writer custom reports. Chances are high that your GP users workstationsdeploy centralized reports  review your user-side dynamics.set and find where youhave REPORTS.DIC placed. If you have them on mapped drive or through UNC path  youhave to build up the same shared folders on the new server Switching to new Windows domain. If you are changing such nice things as activedirectory and windows domain, then think about user profiles, where user mappeddrives might be initialized, plus printers (printers might be superseded in GP andwhen you switch to new domain with new printers management  you may need printersetting re-haul, not a big problem  if you do not deploy such business criticalprinters as barcode labels printing, dot-matrix invoices. Etc.)
Even if you think that it is too complex, you have the option to invite professionalGP consultant to help you and plus we believe that GP redeployment is a way easierthat something like mainframe or Oracle Financial redeployment on the new UNIXserver.
Alba Spectrum Group, http://www.albaspectrum.com help@albaspectrum.com1-866-52 8-0577, 1-630-961-5918, serving Microsoft Dynamics GP locally in Houston,Dallas and Chicago metros as well as USA / Canada nationwide via remote support:California, New York, Florida, Arizona, Colorado, Wisconsin, Indiana, Georgia,Louisiana, Quebec, Ontario, Washington, Nevada, Virginia, Pennsylvania, Ohio, Iowa,Nebraska, North and South Dakota, Wyoming. Local service is available in Houstonand Dallas areas: Rosenberg, Katy, Richmond, Galveston, Sugar Land, Aurora,Naperville, Wheaton, Plainfield, Romeoville, Joliet, Bolingbrook, Lombard, DownersGrove, Warrenville, Lisle, Montgomery, Oswego, DeKalb, Morris, Addison, Seneca,Ottawa. With reasonable travel we serve Springfield, Bloomington, Normal, Peoria,Sterling, Dixon, St. Luis, Peoria, Vandalia, Gary, Michigan City, Milwaukee.
