Microsoft Great Plains

Version: 2010
Views: 2.4k  |  Created: 04/18/2013 by: grayson. mott

Average Rating: 0
Great Plains has 0 inventory records, 0 Questions, 0 Blogs and 0 links. Please help add to this by sharing more!

Deployment Tips (1)

Most Common Setup Type
Legacy Setup with no known command line support
Average Package Difficulty Rating
Rated 4 / 5 (Somewhat Difficult) based on 1 ratings
Most Commonly Reported Deployment Method
Repackaged (to a proprietary Format)

Before reading:  This specifically is for a Win 7 x 64 machine.  It IS possible to use on x32 however the files will need to be adjusted (as many of the msi's are for x64)


I have conducted a proper way to deploy Microsoft Great Plains 2010 from either the K2000 or K1000.  I decided to open this deployment tip as I was unable to find much help myself.  First step was to create a custom installation package for GP, which should differ from every company.  This can be done by launching "setup.exe" from the GP2010 DVD on a computer and letting it install all pre-components.  After this you can choose to create a packaged install from the main menu, then point to a place to store the packaged install and files (I used a blank USB drive as a storage directory).  At that point you will walk through the install, configuring as you would for your company (server information and installation specifics).  When complete, the storage location you originally selected (USB drive in my case) will have a msi for GP and many folders pertaining to it (during the silent install the GP msi will call upon these directories for data).  Keeping all directories intact The next step was making a batch file at the root of the GP packages (same level as the GP msi).  This is a copy of my batch file, which you can look and get an idea of what is needed to complete the install.

start /wait C:\WINDOWS\system32\msiexec.exe /qb /i DexteritySharedComponents\Microsoft_Dexterity11_SharedComponents_x64_en-us.msi


start /wait C:\WINDOWS\system32\msiexec.exe /qn /p DexteritySharedComponents\MicrosoftDexterity11_SharedComponents-KB2408958-ENU.msp REINSTALL=ALL REINSTALLMODE=omus


start /wait C:\WINDOWS\system32\msiexec.exe /i Watson\dw20sharedamd64.msi AppGUID={F5459EB2-A662-4EB3-AD94-E771DC2F542A} /Qb


start /wait C:\WINDOWS\system32\msiexec.exe /i Watson\dw20shared.msi APPGUID={74C84D32-0BFE-4DF1-A59A-49EEECE4043B} /Qb 


start /wait C:\WINDOWS\system32\msiexec.exe  /i OpenXmlFormatSDK\OpenXMLSDKv2.msi /qn


start /wait C:\WINDOWS\system32\msiexec.exe /i SqlNativeClient\sqlncli_x64.msi /qn




start /wait C:\WINDOWS\system32\msiexec.exe /qb /i GreatPlains.msi 




start /wait C:\WINDOWS\system32\msiexec.exe /qb /i IntegrationManager.msi




start /wait Updates\MicrosoftDynamicsGP11-KB2769066-ENU.msp /qn




cacls "C:\Program Files\Microsoft Dynamics" /t /e /g Everyone:f


start /wait C:\WINDOWS\system32\msiexec.exe /qb /i "Tools\SDK\VS Tools\Microsoft_DynamicsGP11_VSToolsSDK_x86_en-us.msi"


start /wait C:\WINDOWS\system32\msiexec.exe /qn /p MicrosoftDynamicsGP11-BITemplateMapping-KB2407.msp REINSTALL=ALL REINSTALLMODE=omus




@echo off

echo Verifying Installation...


choice /d y /t 5 > nul

Installation Complete...



All in bold is what is in the batch file.  The first 6 lines are pre-components which are required to install GP (note that lines 3 and 4 are attempts to install error reporting and need the specific appGUIDs to work).  

 Line 8 is where the GP msi installs; If it fails to start the gp install this is due to one or more of the pre-components (the first 6 lines) not installing.  After the GP msi begins installing, it will display a progress bar. (during this time if it fails this is due to the msi looking for a file and being unable to find it.  If this is the case than double check that all packaged files were NOT modified from when the setup.exe created them).

  After it completes, line 10 is used to install Integration Manager (is needed for our company however not needed for everyone).  I placed a msi for it in the root directory.

Line 12 applies the latest and greatest GP updates via MSP file.  (msp file moved to updates folder)

Line 14 gives proper permissions to the GP directory to all users on the computer 

Line 15 is used to install VSTools which is needed for GP to work properly in our environment (Not needed)

Line 16 is used to install a pre-defined word template for our environment (Not needed)


Finally just save the batch file and zip up the entire directory (all folders, the GP msi and the batch are in the root directory).  Add new post installation task for the K2000/1000 and just call the batch file

install.bat     (or whatever_name.bat)

That's it!  Most likely, every enviornment will need to modify these lines according to them.  As long as you look at the file structure that was created by the packaging and compare to the code above, you can see what is happening when/where and pin point any issues.  Please ask any questions regarding this, even if its basic help and I will do my best.  The goal with this post is to help others to be able to deploy a silent installation of GP that is already pre-configured and operational.  Please post any errors.


Thank you for reading!!

Setup Information:
Setup Type: Legacy Setup with no known command line support
Deployment Method Used: Repackaged (to a proprietary Format)
Deployment Difficulty: Somewhat Difficult
Platform(s): Windows
  • Thanks a ton... The company I started for was installing this program manually each time it needed installing and... to say the least, it was a pain. I haven't finished yet but this is going to help make my life so much easier.
Please log in to comment

Inventory Records (0)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.


Questions & Answers (0)

Questions & Answers related to Microsoft Great Plains

Blogs (0)

Blog posts related to Microsoft Great Plains

Reviews (0)

Reviews related to Microsoft Great Plains