Notifications
Announcements
No record found.
Dear All,
Hope all are doing great. I have upgraded system GP8 to GP2010. Now, I have to install client on 60 client user machines remotely. I am using SCCM (System Center Configuration Manager) for other widnows updates. But I am not sure whether I can use SCCM for GP remote client installation. Any thougths about this is highly appreciable. Many thanks in advance.
Regards,
Vijay
*This post is locked for comments
I would suggest that you create installation package file that you can run on each machine. This information is in your Installation PDF file location in the Documentation folder where you installed GP.
Run Setup from the DVD, and create an installation package. Set the target folder to be somewhere that your SCCM server can access - I used a folder in a share where I store all my SCCM packages.
Then you need to create a package based on that folder. The package will need to contain several programs which will install the prerequisite software (including updates) and then GP, then any GP updates.
The install of Dexterity/DrWatson/SQL components is different for x64/x86 so I'll deal with x64, and note the differences for x86.
I set all the programs to run hidden, and whether or not a user is logged in and assign to targeted machines (and in the Accounts PC build task sequence)
Dexterity for x64 clients:msiexec /i DexteritySharedComponents\Microsoft_Dexterity11_SharedComponents_x64_en-us.msi /qnNOTE - there's a different MSI for x86.
Latest Dexterity Update: (you may have a different update of course)msiexec /update DexteritySharedComponents\Microsoft_Dexterity11_SharedComponents-KB2435568-ENU.msp /qn
Dr. Watson for Dexterity x64msiexec /i Watson\dw20sharedamd64.msi APPGUID={F5459EB2-A662-4EB3-AD94-E771DC2F542A} /qn /norestartNOTE - the APPGUID for x86 is {74C84D32-0BFE-4DF1-A59A-49EEECE4043B}, and the msi is dw20shared.msi
SQL Native Client x64msiexec.exe /i SqlNativeClient\sqlncli_x64.msi /qnNOTE - the msi is different for x86
Open XML SDK 2.0msiexec.exe /i OpenXmlFormatSDK\OpenXMLSDKv2.msi /qn
Lync 2010 SDKMSIExec.exe /i LyncSdkRedist\LyncSdkRedist.msi /qn
Dynamics GP 2010 - finally!!!! :)msiexec /i GreatPlains.msi /qn
Dynamics GP 2010 Update (whichever MSP you're up to)msiexec.exe /update Updates\MicrosoftDynamicsGP11-KB2682502-ENU.msp /qn
Then create a task sequence (I have one for x64, one for x86) that does the install in the order above.
Hope this helps and isn't too late for you!
Neil
This is great information and certainly could be a potential time saver for companies with more than a few workstations running GP. The big $1,000,000 question is ... What about 3rd parties such as Mekorma, Smartlist Builder, etc? And what about Integration Manager, Management Reporter, and all the other aspects of the client install? Seems like all those are missed, but at least this is a good first step.
Also, my other question lies around ongoing maintenance. Say, in 3 months, the client decides they want to deploy SafePay. In Add/remove programs - when you click change on Dynamics GP, you have to go and select the module, SafePay to install. I'm assuming to make this work with SCCM you would have to go back and create a new deployment package and re-deploy to the workstations, or is there a way to tell SCCM to change the installed options on the existing install?
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
mtabor 1
