web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Terminal server & ...
Microsoft Dynamics GP (Archived)

Terminal server & Windows Server 2008

(0) ShareShare
ReportReport
Posted on by John Weindorf 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

I have the same question (0)
  • Tom @ HNNCSB Profile Picture
    Tom @ HNNCSB 900 on at

    What were the steps you followed?

  • John Weindorf Profile Picture
    John Weindorf 250 on at

    Thanks for your reply, below are the steps that were followed. Thanks for your taking a look at these.

     

    Terminal Server\User Profile Setup Instructions  
    • Setup a local directory on the Terminal Server for each network User ID that will be logging in through the Terminal Server (see Terminal Server local user directory document.)
     
    • Second, in the specified users network account (Active Directory Users and Computers),

    under the tab entitled ‘Terminal Services Profile’, enter the path for the local directory

    defined for the user (see Terminal Services setup document.)   
    • After setting up the local directory and defining the path to it under the Terminal Services profile tab, the first time you attempt to log in to the Terminal Server as a user, the process will create the sub directories under that user’s directory, Windows/System. 
     
    • At first you won't be able to launch Microsoft Great Plains because the WINDOWS directory for that user was just created after the first login attempt, so the Dex.ini file could not be placed there in advance.
     
    • After the first attempt, verify that the WINDOWS directory was created and the copy the desired Dex.ini file into that user's newly created WINDOWS directory.
     
    • Now try to launch Microsoft Great Plains again and this time it should work, using the Dex.ini file in that user's local directory, WINDOWS subfolder.

     

  • Tom @ HNNCSB Profile Picture
    Tom @ HNNCSB 900 on at

    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

  • John Weindorf Profile Picture
    John Weindorf 250 on at

    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.  

  • Tom @ HNNCSB Profile Picture
    Tom @ HNNCSB 900 on at

    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.

  • John Weindorf Profile Picture
    John Weindorf 250 on at

    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?

     

     

     

  • Tom @ HNNCSB Profile Picture
    Tom @ HNNCSB 900 on at

    OU - Organizational unit (container within Active Directory)

     

    GPO - Group Policy Object

     

  • IceMan Profile Picture
    IceMan 1,115 on at

     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,

  • Fabian Perez-Parada Profile Picture
    Fabian Perez-Parada 55 on at

    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

  • IceMan Profile Picture
    IceMan 1,115 on at

     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. 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Community Member Profile Picture

Community Member 2

#2
mtabor Profile Picture

mtabor 1

#2
Victoria Yudin Profile Picture

Victoria Yudin 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans