Especially the option to define the location for shared dictionaries and Word Templates / Letters / Notes, as the regular GP setup doesn't even ask about this.. which is IMHO something that should be possible out of the box.
Also, I noticed that the latest GP build 18.2 has a bug, as despite of specifying the initial program location for the deployment package, it defaults to a GP2018 folder, which is not good of course.
What would be nice is the option to be able to package several ISV or 3rd-party chunk files (.cnk) to be deployed withe the same client package. I know that the "Updates" folder can hold any GP service pack to be deployed at the same time, but not sure this is valid for .cnk files.
Comments
To work around this, I create a blank GP folder at the typical install location (C:\Program Files (x86)\Microsoft Dynamics\GP\). When I use the wizard to create the installation package, when I get to the select features window, I select Browse, and then browse to the GP folder I created at C:\Program Files (x86)\Microsoft Dynamics\GP. I then proceed through the rest of the creation of the installation package as I normally would.
When I go to run the installation package on a new client, it will automatically install GP at C:\Program Files (x86)\Microsoft Dynamics\GP\.
Category: Platform - Installation
Please also update the ODBC DSN to properly reflect the product name of Dynamics GP without the GP2018 year designation.
Category: Platform - Installation
Administrator
Thanks for the suggestion, we will not be re-doing the deployment package of GP at this time.
Terry Heley
Microsoft