David Musgrave on Automating the Distribution of Customizations

David has published two very detailed articles regarding the automatic deployment of customizations. Article I explores the different deployment scenarios for dictionaries and application files with pros and cons for each configuration, while Article II explores the automation of the deployment of customizations. However, the articles do not cover complex deployments in Citrix and Terminal Server environments and are not recommended for upgrades or deployment of new clients.

Drop a comment to David and let him know how (or how not) you can use his suggestions.

Until next post!

Mariano Gomez, MIS, MVP, MCP, PMP
Maximum Global Business, LLC.


David Musgrave said…
A couple of clarifications.

For a new install once you have installed the standard client from the CD, you can run the UpdateForce.bat batch file to bring all the third party products, customisations, service packs, hotfixes and settings from the Update Share down to the workstation. That would definately speed up the new client install process.

As for Citrix/Terminal Server, you can't use the Login.bat approach, but once you can confirm all users are logged out of the client, you can manually run Update.bat to bring all the updates down from the Update share to the shared client.

David Musgrave [MSFT]
Escalation Engineer - Microsoft Dynamics GP
Microsoft Dynamics Support - Asia Pacific

Microsoft Dynamics (formerly Microsoft Business Solutions)


Any views contained within are my personal views and not necessarily Microsoft policy.
This posting is provided "AS IS" with no warranties, and confers no rights.

Popular posts from this blog

Power Apps - Application Monitoring with Azure Application Insights

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

eConnect Integration Service for Microsoft Dynamics GP 2010