You’re offline. This is a read only version of the page.
250
I have a customer installing Dynamics GP 10 on a Terminal Server, with Windows 2008 (64 bit.) They have gone through the steps to copy the dex.ini in to each of the user profiles, but the dex.ini files are not being recognized when trying to launch GP. Does anyone have any experience or suggestions on how to fix this problem? Thanks for your help!
*This post is locked for comments
John, one reason that a single dex.ini file is an issue is when trying to use GP with Terminal Server Remote App. With a single Dex.ini file, we have issues because some users have multiple monitors and some do not. If one of the dual monitor folks moves GP to their second screen, those coordinates are saved to the dex.ini file. Then one of the users with a single monitor opens it and it launches to some coordinates that they can't see. The icon is at the bottom, because GP is open, but to them it looks as though it's stuck in minimized mode, because it's not open anywhere that they can see it or interact with it. There are supposed to be some ways to mitigate this by using the Support Debugger, but as of yet, I've not been able to get it to work correctly.
Just my 2 cents on this; but, why use individual dex.ini files in the users profiles? We have been running Terminal Server for years (both 2003 and 2008) with a single Dex.ini in the normal folder "C:\Program Files (x86)\Microsoft Dynamics\GP\Data" (version 2010 R2, currently) with no problem. Yes, the Last Data Source and Last User are saved in the Dex.ini file but for all users the Data Source is always the same so with a little teaching (teach the users to change the name as well as enter their password) and everything runs great. It also makes maintenance and updates a lot easier, at least in my humble opion.
Just my 2 cents,
[If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
Has anyone seen updated Dynamics GP or other Microsoft KB that talks about this? I've looked all over and can't find supporting documentation. I agree with the approach and appreciate the response, but am surprised Microsoft has not provided additional guidenance in their documentation. For large GP role outs this is critical information to supporting the application in a thin client environment.
We have found that if you add the following change to the launch parameters for the Dynamics GP shortcut, it iwll use individual dex.ini files that are in the users profiles. Note that if there is no dex.ini file, it will give an error, and not allow the user to log in.
"C:\Program Files (x86)\Microsoft Dynamics\GP\Dynamics.exe" Dynamics.set c:\Users\%USERNAME%\dex.ini
Fabian
Has anyone had any luck with the Dex.ini in the users profile directory. I'm having no luck launching GP with the Dex.ini anywhere else but the standard location within the GP directory. This is a new Server 2008 TS implementation. We have this same TS architecture for 2003 with no problem and I've got the Dex.ini within C:\Users\%Username%\windows and no luck.
I know back in the day there were issues with Dex.ini timestamps and stuff like that but I think that was all corrected.
What am I missing.
Thanks,
OU - Organizational unit (container within Active Directory)
GPO - Group Policy Object
Thanks so much for your help and suggestions; I am going to forward these on to the customer.
A couple of final questions; I want to make sure that I know what the abbreviations that you used stand for -
OU - ?
GPO - Group Policy?
John:
Here is what I'd recommend:
1. Be sure all of your Terminal Servers are in a single OU, and create a GPO for that OU to apply against all Terminal Servers.
2. Set the profile size in the GPO under User Configuration | Policies | Administrative Templates | System | User Profles - set a maximum size here, otherwise profiles can get too large and will slow down logon/logoff. I set mine to 50,000 KB but you can adjust to suit your environment.
3. Set the profile path in the GPO under Computer Configuration | Policies | Administrative Templates | Windows Components | Terminal Sevices | Terminal Server | Profiles and the path should be a UNC share.
I set my share as a completely separate Windows volume (but these are virtual servers to be fair).
Permissions are important. You need to set, under this share:
User - Full Control, owner of folder
System-Full Control
Administrators - Full Control
If you have the Windows 2008 Terminal Server Resources Kit book (excellent and worth the money) this is covered in chapter four.
In the long run GPOs are much easier than per user setting. Please give this a try and let us know if this is successful.
Below are the answers to your questions -
1) This was a brand new install of Terminal Server and GP; the roaming profiles were not set up previously.
2) No errors are displayed; when GP is opened (using the Shortcut on the TS Desktop) a message is displayed that says GP Utilities needs to be run.
Okay, a few questions:
1. Where the roaming profiles already there and were staff using them successfully prior to you attempt to unique the dex.ini?
2. What do you see in terms of errors (or other signs) that the unique dex.ini file is not recognized?
Regards,
Tom
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,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (