Deployment, Administration and Performance

1. Deployment, Administration and Performance Jeff Soelberg Fastpath Sarah Purdy Microsoft

2. Agenda • Introductions • Jeff SoelbergFastpathsoelberg@gofastpath.com • Sarah Purdy Microsoft sarahcud@microsoft.com • Talking Points • Interactive Discussion • Terminal Server vs. Classic Client • Advantages of Virtualization • Service packs • Performance tips • Automate GP Install • Final Questions

3. Talking Points • Your Name • Your Company • Your Question or Topic of Interest

4. Terminal Server vs. Classic Client • Advantages of using Terminal Server • Fewer Client Installs • Performance Advantage • Remote Administration • Disadvantages • Users need to be off to update • Risk of downtime due to machine failure • Shared Dex.ini

5. Advantages of Virtualization • Lowers number of Physical Servers • Easily backup and restore environments • Isolate applications to one virtual server • Increase or Decrease resources for Debugging • Create multiple Test environments

6. Service Packs • By Rob Mitchell • Microsoft Dynamics GP offers a way to incorporate service packs into the Dynamics GP client installation package. To do this: • 1) Navigate out to your client installation package and find the Updates folder. This is the client install package that can be created during initial install to simply future client setup • 2) Delete any msp file in the Updates folder and copy the latest service pack in. • 3) The next time you install the client it will include the service pack. It’s that easy!! • Note that the service pack needs to have been applied to the server before adding clients with the same service pack level.

7. Service Packs • By Mark Polino • Before you start, the applicable update needs to be downloaded from CustomerSource and placed on a shared drive accessible to all the users. • We'll start with Tools-Setup-System-Client updates. • Give the update a name, like Service Pack 1. • Check the box to Update Clients at Next Use. This turns a particular update on or off. You can have multiple active updates like a hot fix and a service pack. However, you'll want to turn off an update if a new, comprehensive update is going to be used. (Turn off SP1, when SP2 is available) • Lookup and select the location where you stored the update. Again, this needs to be on a shared drive accessible to the users. • Now, when a user logs on, GP will check to see if the update is installed. If not, it informs the user and gives them the option to apply the update. When they say yes, the update installs. You'll still want to warn your users with an email, especially since some of these updates are quite large.

8. Performance tips • Store report dictionaries on local TS • Mariano Gomez • Minimum memory per queryIncreasing the value of this option can improve the performance of queries that use hashing or sorting operations, like those find in SmartList and SmartList Builder. Also, most table auto generated stored procedures — the stored procedures prefixed with zDP, see David Musgrave’s article, What do the zDP_ Auto Generated Stored Procedures do?, for more information– will benefit from this change if your SQL Server has a lot of memory available and there are many queries running concurrently on the server. • Default Index Fill FactorThe Default Index Fill Factor option specifies how full each index page will become. When there is no free space to insert new row on the index page, SQL Server will create new index page and transfer some rows from the previous page to the new one. This operation is called page splits. You can reduce the number of page splits by setting the appropriate fill factor option to reserve free space on each index page

9. Automate GP Install • Andy Nifong • Creating a GP 2010 installation package • Mohammad R. Daoud • Silent Installation for Dynamics GP

10. Questions? • Thank you • Jeff Soelberg • Fastpath • soelberg@gofastpath.com • Sarah Purdy • Microsoft • sarahcud@microsoft.com