Dynamics,Partner,Newsflash,Aut computer Dynamics GP Partner Newsflash: Automatic Great Plains Instal
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
In Dynamics GP 10.0 and 9.0 you have Installation Packagefunctionality, which allows you to exercise this control. In this small publication we would like togive you guidelines and ideas on where to get more info:\ 1. To create installation package, please insertMicrosoft Dynamics GP 10.0 CD1 (or GP 9.0 CD1, if you are on version 9.0respectively). Click on Create InstallationPackage. You will be prompted to selectPackage folder we recommend you to use UNC path, which is open to each GreatPlains user in your organization, then follow simple decision making steps, wewould like to dedicate special paragraph to the decisions 2. Reports file location. On the Dictionary Location screen you caneither choose local path for Reports.Dic or switch to network folder. Let us stop here for the few seconds. If you have only couple of Dynamics GP users,then it is not a big deal to copy Reports.dic version, when reports have beenmodified (normally SOP Blank Invoice form, where you place your company logo,payment remittance information, etc). Inlarge company, where you have maybe hundred Great Plains users, there is goodidea to have all the users to share the same Reports.dic with approved modifiedreports 3. Forms. Ifyou are familiar with Modifier with VBA, you know that you can modify existingGP forms in Modifier by taking off some fields, placing new fields andattaching VBA script to them. Modifierwith VBA allows you to create very simple customization without appealing toyour Great Plains reseller to program it for you 4. OLE Notes. As you probably already know, OLE notes allow you to attach OLEcompliant objects (Excel, Word documents, Pictures, for example). In order for all the users to be able to openOLE notes, attached by one of the users, you should place OLE notes to thenetwork folder 5. Letters. Typical example would be collection letters. The same idea, consider placing them on thenetwork to share for all the users 6. Distributing GP Installation. After you are done with the InstallationPackage creation, in the installation folder you should see two files:Setup.exe and GreatPlains.msi. The linkto Setup.exe could be emailed to your users, who is chosen for Great Plainsinstallation, and MSI file could be placed into user profile policy or grouppolicy for automatic deployment 7. AutomaticUpdates. Installation Package is createdoff the original manufactured Great Plains CD1 and 2. In reality, you have to apply GP ServicePacks on the regular base, plus if you are using GP add-ons you distributethem in the form of Chink files with CNK extension. Service packs typically include all theearlier SPs and patches. To publishupdate for you GP users, you have to first install it on your GP server and thenenable for the users in Tools->Setup->System->Manage Automatic ClientUpdates window. Update is placed inSyupdate table. Control is pretty tight if user doesnt agree to the update Great Plains closes and doesnt allow theuser to keep working
Dynamics,Partner,Newsflash,Aut