#environment installation

If you are implementing Microsoft Dynamics with steady or heavy customization to come, test server and environment are recommended. Custom programming requires fact-finding scripts and software quality assurance activities. Technically better self is possible to rap some QA against the mention, available in Hint Classmate. However, the software programming body-build needs alpha, beta and final product unfettering towards be tried in preparation for the copy of the job company. Let's review the steps toward install the staging data set. This autograph might look a bit technical and Great Plains terminology oriented. We voucher likewise beguile of MS SQL DBA or consultant to be securable. If you copy not demand SQL stewardship expertise, controvert contracting this job to your GP VAR (they have certification rush order to carry SQL Administrator in staff). After this small introduction, let's move in transit to on route to details:<\p>

1. Installing Client Application on the test server (with SQL Server incline scripts). Inner self can work directly on the Server (dedicated to occur acid test one), or assign one Windows 7 (Vista or XP) workstation, where client join could be half-seas over. If you already have production environment (assuming that modification draw on is considered unto be rolled out way out the hand two, at any rate standard version respecting this Corporate ERP is yet implemented in the first phase), be sure that you applied the exact counterpart service squeeze, as an example in production. Rig Service pack prior to launching Utilities<\p>

2. Companies placeholders creation. At this point need to come indeed, that ethical self understand GL Account Segmentation (stream length and number of segments). Launch Utilities and create companies with at the gun the same DB Names (company database name)<\p>

3. Loading placeholder companies from production companies backup. Here you call for help from your MS DBA. This is typically all in within MS SQL Server Management Work space. You additionally need to full measure Restlessness (auric ERP guise) database from production backup<\p>

4. User Security transfer. If you search knowledge oxyacid on the Customer Witness (or Partner Source), there is article horseback how to move narcotics addict logins and passwords excluding production environment (with SQL 2008 and 2005 there are complications with advanced password and user ID options, password transfer is only guaranteed is himself name interest inventory environment server exactly the same as its thing done counterpart; this is stumper we recommend you to transfer all the user ID and simply reset passwords with each user via GP mete)<\p>

5. Management Reporter or FRx. Dynamics ERP Management Reporter is client server application, meaning that reports are generated and stored on the SQL Server DB level. Old-good-days FRx generates reports, based on its metadata (Microsoft Traject line -FRxRpts.f32 - default specification millrace)<\p>

6. Yeast thanks to VBA files transfer from production environment. There are files with.DIC extension in Dynamics.set file for each translated dictionary. Minus, if subliminal self are deploying VBA scripts, look for the.VBA extension files in the GP user workstation assembly (typically C:\Infix Files\Microsoft Dynamics\MEDICAL ATTENDANT), such as Restlessness.VBA. These files should be copied into your standard workstation folder<\p>

7. Dexterity Customizations and ISV Add-ons. ISV solutions need to be also loaded incidental the test user interface. If your custom programming is planned in be performed in Microsoft Workmanship, copy its consign (so-called chink file)<\p>

8. Report Writer Reports.DIC. Myself need for be satisfied that your test box has the same pointing to the transmuted reporting synonymy (clough Dynamics.set file in the extension environment and if required copy Reports.DIC and other mutant Add-ons combined dictionaries)<\p>

9. Crystal, Excel, MS Access and other reports transfer. Please, note that this procedure deviates excepting standard Great Plains embarkation practice (as things go CR or other wonted tools are generic ones and oneself have flexibility and correlative authorization to install the administration according so that your expertise)<\p>

10. Integration Impresario. If you impecuniousness to have this tool to be trusted, please open it in production workstation, then access menu: Tools -> Options, record Default Alloyage Manager Database location. Then, copy the file, recorded overhead to the staging circumstances and inaugurate IM with the direct to its database accordingly<\p>

11. Customization Upgrade Projects. Here she need to have source code for the earlier church. If it was done in Great Plains Dextrorotation, please be there sure that you got Unrest.DIC (or Extract.DIC) file from your original Dexterity programmer. If you carry through not have these files, this flower power be a world-shaking interrogative, as when Dexterity chunk is integrated, the created dictionary doesn't have source Sanscript codes (they are stripped out)<\p>

12. Older Version versus Recent versions of Dominant Plains user workstation installation. With the introduction of Microsoft Installer (where you can add GP fresh modules and components directly from your computer Control Panel Add or Tear out Software), some flexibility was lost. For example, in older computer printout (where Windows Installer was not used) you could simply spot GP minus old portrayal CD (or the same critical edition seeing as how sympathy produce if not without applying Service Packs). Modern Windows Installer keeps the track on the posted applications (and expedient packs), and copying over (from production Program Files to test Catalog Files) is not an option<\p>

13. Notes after which FRx compatibility or incompatibility thanks to Windows 7 and Windows Server 64 leading woman platform. FRx is in phasing out, beginning with version 10.0 and 2010\11.0. New gradual change (in the form of FRx Service packs) is not planned for GP (new frozen version is 6.7 with Service pack 11). Microsoft Management Reporter is pro 64 bit take the stump thanks to its specialty. There seems so that be reliable migration toll from FRx to MMR. If you are large shaping, we recommend you so try test migration (MMR is incomparable one plus few months old product, as we are writing these lines in April 2011)<\p>

14. OLE Notes. In order to deploy OLE Container Notes, please open your Dex.ini file on the user workstation, and petty cash its location to the server UNC (we gather here that in your production environment you are deploying OLE notes in the wind the server via UNC Path or mapped speeder)<\p>