Connecting Dynamics GP, thru windows 2003 terminal server

Can anyone give some tips to get the optimimum performance while using Microsoft Dynamics GP with terminal server in the remote locations.

backer-mAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

arunragCommented:
Hi. What exactly are you looking for. Terminal Services is already optimized for performance unless windows performance acts up. For Dynamics GP on terminal services, there isn't much that you need to do on Windows. If you are sharing the modified forms and dictionaries over mapped network, then only thing you need to take care is make sure that all windows users have access to the mapped network. Give us some info and i will try to give you more info on it
0
Steve EndowMicrosoft MVP - Dynamics GPCommented:
Hi,

The peformance of Terminal Services, and Dynamics GP over TS, is quite good.  So as long as the Internet connection is reliable and at least 512k, performance should not be an issue.

However, when you run GP over TS, you will need to think about the following considerations:

1) Printing.  When printing from GP on TS, you will have to deal with mapping the remote printers to the TS session.  This is supported by TS, and does work, but you will likely experience some hassles in both setup and support.  For instance, a printer will occasionally just stop working at the remote site, and you'll have to figure out the cause, reboot the workstation, restart the print spooler on the server, or possibly reboot the server.  This is more of a TS issue than a GP issue.  It is not a big deal, but just be ready for it.

2) Idle user sessions.  Users will definitely forgot to close GP, forget to logout of their TS session, or simply disconnect their TS active sessions, leaving GP running.  With GP, this has the side effect of consuming a concurrent user license.  If you are maxed out on GP licenses, this can be a hassle, as you will have to track down and clear the idle TS sessions.  One approach is to set your TS to shut down disconnected sessions, and possibly also idle sessions, but this may leave records in the Activity table, thus still consuming a GP license.  Another approach is to purchase OmniTools from Rockton Software, which has a feature that will automatically (and properly) log a user out of GP if they have been idle for XX minutes.  If you have alot of GP users, this OmniTools feature is very valuable, and will save you from having to buy extra (expensive) GP licenses that you may not need.

3) When performing maintenance on GP on the terminal server, you will occasionally need have all users log out of GP and the terminal server, as the GP sessions will lock files (such as dictionaries, vba files, AddIn DLLs, etc.).  You can use the tsadmin.exe utility and Task Manager -> Processes -> Show Process from all users to check to see who is logged in and who is running the Dynamics.exe process to know who to call to ask them to log out.  Also learn how to use TSAdmin to connect to the user's session if you can't get a hold of them so that you can properly shut down GP and then log them out.

Other than those concerns, TS works great for GP.

Thanks,

Steve Endow
Dynamics GP Certified Trainer
Dynamics GP Certified Professional


0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Steve EndowMicrosoft MVP - Dynamics GPCommented:
Hi,

One last tip that I forgot.  There is a common issue where some users will experience VERY long delays (several minutes) when trying to launch GP on the Terminal Server.  This is likely not a GP issue, but more likely an issue with their Active Directory profile.

If you observe this issue, go into the user's Active Directory profile and remove any Network Drive Mappings from the Profile tab of AD User Object.

If that doesn't resolve it, you can try creating a new AD account for the user so that they have a clean profile.

Another cause of this issue is Roaming Profiles.

Thanks,

Steve Endow
Dynamics GP Certified Trainer
Dynamics GP Certified Professional


0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Tax / Financial Software

From novice to tech pro — start learning today.