Open Forum

Expand all | Collapse all

Script GP 2016 R2 Client Install with 3rd Party

  • 1.  Script GP 2016 R2 Client Install with 3rd Party

    SILVER CONTRIBUTOR
    Posted Jan 02, 2019 03:01 PM
    ​​Hi,

    I am preparing to upgrade to GP 2016 R2 and would like to know if anyone has experience or knows of any product solutions that will help to script the GP client and 3rd party install.

    We will need to install the GP client on 80 to 90 workstations and as I am sure you are all aware can be quite cumbersome and time consuming.

    I am aware of the GP Client Installation script created by the Installation CD and this could certainly be done to help with creation of the ODBC's and installation directory location however, installing of 3rd parties is not as easy.

    We will be installing the below third party software for GP:
       -  eOne's SmartConnect
       -  Binary Stream's MEM
       -  Mekorma MICR
       -  Nolan Advanced Bank Rec
       -  SmartView
       -  PaperSave

    Is there a product that can help script the above to be able to quickly install GP and all 3rd parties on the 90 client workstations?

    Please help,





    ------------------------------
    Curtis Cruz
    Database Administrator
    Apex Healthcare Partners LLC
    Montebello NY
    ------------------------------
    GPUG Summit - Post


  • 2.  RE: Script GP 2016 R2 Client Install with 3rd Party

    GPUG ALL STAR
    Posted Jan 03, 2019 01:22 AM

    @Curtis Cruz

    Have a look at my articles on distributing customisations, we used this method to disrtibute the files. However it does not replicate registry entries that the installers might make.

    https://blogs.msdn.microsoft.com/developingfordynamicsgp/2008/08/20/automating-distribution-of-customizations-part-1/

    https://blogs.msdn.microsoft.com/developingfordynamicsgp/2008/08/26/automating-distribution-of-customizations-part-2/

    FYI: All Winthrop Development Consultants products support a scripted silent install. You should check with the other ISVs if they can do the same.

    https://winthropdc.wordpress.com/2015/08/24/gppt-installing-gp-power-tools-upgrading-from-sdt-silent-installs-and-more/

    Happy New Year

    David



    ------------------------------
    David Musgrave MVP, GPUG All-Star

    Managing Director
    Winthrop Development Consultants

    Perth, Western Australia

    http://www.winthropdc.com
    ------------------------------

    GPUG Summit - Post


  • 3.  RE: Script GP 2016 R2 Client Install with 3rd Party

    GOLD CONTRIBUTOR
    Posted Jan 03, 2019 06:30 AM
    Curtis, while there are ways to automate several of the 3rd-party products you mention, there are several in your list which must be run separately since, as David also mentioned, they need to create their own program files and registry entries.  The creation of a GP install template is a must and will reduce install time.  You will want to contact your GP partner to see if your ISV products offer silent install switches.  In the event some or all are able, it would be possible to write a batch file or PowerShell script to automate the installs.
    It is also possible to re-think your GP distribution mechanics; for instance:
    1. Use the Web Client for those users who only need GP without the need for supporting stand-alone applications such as Smart Connect, Jet Reports, Integration Manager, Management Reporter, etc.
    2. Use Remote Desktop Servers (with or without Citrix) to offer a full desktop or published applications to users.  You can configure one virtual RDS 'master', and restore a snapshot to production servers.  With 90 clients, you will need to be mindful of server loading to determine the number of RDS servers needed for your organization.
    Note that you will need to install Microsoft Office on each RDS as well to support interoperability.  Web Clients access the user's local Office install.
    In either of the two scenarios above, consider the use of the under-used Process Server GP offers to offload long-running processes and reports.  If you own GP, you own the Process Server.
    The cost of RDS deployment will likely be offset by the support required for 90 individual client installs.
    The above may not be the answer you're looking for, but it may be the answer you need.

    ------------------------------
    Charles Ray
    Senior Systems Specialist
    CAL Business Solutions, Inc.
    Harwinton CT
    ------------------------------

    GPUG Summit - Post


  • 4.  RE: Script GP 2016 R2 Client Install with 3rd Party

    Posted Jan 03, 2019 08:44 AM
    ​Our company uses a product called Altiris.  We were able to push out approximately 30 workstation installations using this.  You still have to go in and log on for the first time to run utilities, but all of the other installation work is done.  I don't have the details on it but I could find out more about this product from our Desktop Support team.

    ------------------------------
    Jeff Stowe
    IT Application Analyst
    Multiplan, Inc
    Sarasota FL
    ------------------------------

    GPUG Summit - Post


  • 5.  RE: Script GP 2016 R2 Client Install with 3rd Party

    Posted Jan 03, 2019 09:20 AM
    Curtis,

    Personally I have primarily used the batch file installation method briefly touched on by Charles. Generally split out into 3-4 different files:

    1. Install GP- which includes renaming the existing installations folder (personal preference), then creating the new GP folder and adding any required permissions, before launching the previously made Template to run a full GP installation including prerequisites.
    2. Install Service Pack- A very simple script that references the latest GP service pack and runs an msiexec on it. This is separated from script one as the service pack is more likely to change before you change major versions and so the script can be reused by only changing the msi name.
    3. Install third parties- This is very specific to each company, but a single batch file that runs the executable for each product you use. Regrettably not all products are as well documented in what their parameter lists are compared to what David has graciously done for Power Tools, but a throw away VM can be a useful tool to play around with launching the installer with different parameters to replicate the decisions you make when using the GUI installer and allows the installation to run in the same way, on every workstation, every time. The end of this file can also copy modified forms and reports dictionaries from a shared location to the local and finish by launching DynUtils.exe to synchronize the dictionaries then get SQL Messages and consume the cnks when you follow through into GP.

    Once you have created all the required batch files and tested them to make sure nothing is missing it's just a matter of placing the files and scripts on a share and launching them from each of the workstations (in numbered order) and completing a single log on before moving on to the next.

    While this method is time consuming to run on each individual machine, once the batch file is solid you will have the same footprint created every time with all the required files, and the registry will have also been updated accordingly for each product.

    ------------------------------
    Scott Davis
    Trudell Medical Limited
    London ON
    ------------------------------

    GPUG Summit - Post


  • 6.  RE: Script GP 2016 R2 Client Install with 3rd Party

    TOP CONTRIBUTOR
    Posted Jan 07, 2019 12:40 PM
    I agree with the others on scripting these out individually.I have been building new servers for our GP 2018 R2 upgrade and am too lazy to do it all by GUI, RBAR. Plus we have multiple variations of the GP Client, so a typical install for me has 9 GP Clients (for now).  I have a GP silent install batch file, and 8 other batch files for various 3rd party products). Run each in turn, and done! Or make a master batch file that calls each and run one?

    I have silent install scripts (batch files) for GP and most of our 3rd party add-ins. Some ISVs, like David Musgrave and GP Power Tools were responsive and easy, others didn't want to admit to the possibility. I can see and trigger AvaTax command windows, but they will not admit they exit <grin>.

    GP allows for much of the modules to be scripted into the call, like this
    msiexec /i "E:\GP2013 Software Installs\MDGP2013_R2_DVD_ENUS\Bin\GreatPlains.msi" /qb+ SQL_SERVER_NAME="SQLservername" INSTALLDIR="C:\Program Files\Microsoft Dynamics\GP2013" SELECTED_COUNTRY="United States" TRANSFORMS=:Inst01 INSTANCE_NAME="CORP" MSINEWINSTANCE=1 ADDLOCAL=EREC,FAM,MFG,PSTL,SP
    I have 9 lines in my GP Silent install batch to create each of our 9 GP Clients, and one additional line to patch all 9 to the latest KB.
    (Reference Link) One gotcha? Some of the newer GP (2015+) modules may not be listed in this reference. Hunt around for newer ones.

    I have batch scripts for GPPT, MICR, Collections Management, Extender, etc. One vendor showed my a trick to use Process Monitor(sysinsternals) to trace the calls made by an ISV's installer GUI, and expose the command options needed to build a command line script.

    Luck!

    ------------------------------
    David Morinello
    Senior Dynamics GP Systems Architect
    Ascend Learning, LLC
    Leawood KS
    ------------------------------

    GPUG Summit - Post


  • 7.  RE: Script GP 2016 R2 Client Install with 3rd Party

    SILVER CONTRIBUTOR
    Posted Jan 07, 2019 05:41 PM
    ​Hi David,

    Thanks so much for your reply to this thread.

    Using the Process Monitor to capture the command line used when installing the 3rd party applications sounds like the best idea to capture and script.

    I've gone ahead and downloaded the Process Monitor but there looks to be so many options to choose from. Which options would you suggest turning on in Process Monitor in order to capture the 3rd party command line installs?



    ------------------------------
    Curtis Cruz
    Database Administrator
    Apex Healthcare Partners LLC
    Montebello NY
    ------------------------------

    GPUG Summit - Post


  • 8.  RE: Script GP 2016 R2 Client Install with 3rd Party

    GOLD CONTRIBUTOR
    Posted Jan 07, 2019 07:57 PM

    Curtis, I'd capture everything, filter for 'setup.exe' or whatever the name of the installer is, then save the filtered results to a file for review.

     

    Charles Ray

    Senior Systems Specialist
    C A L Business Solutions Inc.
    Phone: 860.485.0910 x110

    logo_web_gif

     

     

     




    GPUG Summit - Post


  • 9.  RE: Script GP 2016 R2 Client Install with 3rd Party

    TOP CONTRIBUTOR
    Posted Jan 08, 2019 10:54 AM
    Here is one example in a discussion with eOne Support. This guy went above and beyond.

    I ran a procmon trace installing the GP addin for GP2015 on my machine and from the trace is shows:

    Command line: "D:\temp\gp addin\SmartConnect GP Addin 20.17.0.11.exe" /i "C:\Users\Pat\AppData\Roaming\eOne Solutions\SmartConnect GP Addin 20.17.0.11/install/SmartConnect GP Addin.msi" CLIENTPROCESSID="8576" SECONDSEQUENCE="1" CHAINERUIPROCESSID="8576Chainer" ACTION="INSTALL" EXECUTEACTION="INSTALL" CLIENTUILEVEL="0" ADDLOCAL="Gp2015F" ERROR_FOUND="False" APPDIR="C:\Program Files (x86)\microsoft dynamics\" AGREE_CHECKBOX="Yes" PRIMARYFOLDER="APPDIR" ROOTDRIVE="D:\" AI_SETUPEXEPATH="D:\temp\gp addin\SmartConnect GP Addin 20.17.0.11.exe" SETUPEXEDIR="D:\temp\gp addin\" EXE_CMD_LINE="/exenoupdates  /exelang 0 /noprereqs   " TARGETDIR="D:\" AI_SETUPEXEPATH_ORIGINAL="D:\temp\gp addin\SmartConnect GP Addin 20.17.0.11.exe" AI_INSTALL="1"

    The values that you need would appear to be there. also this is an advanced installer package not windows installer (well, it calls windows installer eventually) so you might have do something special with that.



    ------------------------------
    David Morinello
    Senior Dynamics GP Systems Architect
    Ascend Learning, LLC
    Leawood KS
    ------------------------------

    GPUG Summit - Post


If you've found this thread useful, dive deeper into User Group community content by role