You’re offline. This is a read only version of the page.
1,110
Hi (me again!)
We are running GP 10 sp3 and want to update to sp5 (some of the major bug fixes come from us!) and we've got about 125 pcs with client installs of GP. When consulting the sp5 install guide they refer to the Manage Automated Client Updates window to create a package with automated response for an environment like ours.
The thing is we've also got Extender and at the bottom of the Dynamics sp download page, there is a reference to an extra procedure for users having Extender from eOne. This basically implicates opening Dynamics.set and removing a few lines before executing the update and after the update to simply paste them back in the Dynamics.set
So my question, if question there is, can I still use the Manage Automated Client Updates window to simplify the update process?
Thanks again,
Jason Chung
*This post is locked for comments
Hi Jason,
In that case I would script all the update process... this avenue might be the only choice, specially if you have 150 or more workstations to upgrade. Use the netlogon scripting capabilities to update your existing Dynamics GP installations. With some simple commands you can validate if the current user's workstation has an existing GP client and then take a backup of it (rename the folder), call up the installation package (which you would create from the newly SP5 installation DVD), add all the 3rd party modules and put a flag file containing the date & time (to validate it has been done, not to repeat it at the next user login) into the Microsoft Dynamics root folder (not the GP) or test in your batch process the existence of the backup folder....
Of course, there will be a manual step involved, which consist of launching the GP utilities at least once after the client installation, in order to sync the dictionnaries on the network and validate the module versions.
Another way to do it even more automated, is to take a complete package snapshot from a clean installed workstation and deploy this one accross your network, that way you even save the GP utilities step. I've done this in the past with GP 8 before the client update even exists in GP as an option to deploy upgrades. You can use SCCM if you manage your domain with it, but the netlogon scripting is no-cost approach :-). Be careful because the regular installation process of the GP client involves a lot of registry key entries
Unfortunately reality has caught up with me and we are using the eOne Enterprise edition of extender and so I do need to follow the Dynamics.set removal procedure...
Which is not a comforting thought!
Any ideas? On another blog site i've been suggested to do the server install and apply the changes to .set file and copy it and push it on the network. Then package the client install and once clients have been updated, push the newly modified .set file
The problem with that solution is that I don't know when all clients will be updated and if i push the newly .set file before a client has been updated, then that station will not be standard, compared to other stations. And what happens when a station who has the codeless .set file updated client and starts using GP? Will he be able to use GP's extender windows or will we have a major crysis in the morning?
I guess my other alternative is to manually update each station?... = (
Yours truly!
Hi Jason,
The note about the Extender version of eOne applies only to the full version (Enteprise I think it's called), not the one you buy from Microsoft with GP. If you have the dictionnary 3107 / Extender installed in your Dynamics.set, I don't think you have to remove it before applying SP5 (at least I didn't had to in the previous SP's and it was pointing to the same note).
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (