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 AX (Archived) / AX 2012 on Terminal Se...
Microsoft Dynamics AX (Archived)

AX 2012 on Terminal Server how to run multiple configs on server?

(0) ShareShare
ReportReport
Posted on by Community Member

Hi, has anyone come across the following before and found a work around?

We have an AX 2012 environment running the clients across Terminal services and connecting to multiple AOS servers. The Terminal Services Apps are all configured to use separate AXC config files depending on which AOS they access. All work ok.

The issue:

We are trying to implement a system to generate a purchase order from a template, this works ok using the FULL locally installed AX client but not when using over Terminal Services.

We have tracked the issue down to, while a user may connect to one AOS over Terminal Services using an AXC file, when we use the generate from template option AX then looks for the Default installation config on the Terminal Server NOT the AXC or login the user is using.

IE. When AX was first installed on a Terminal Server it was set to point to AOS1, a user logs in to AX over Terminal Server and using an AXC config connects to AOS2, but when they run the generate from template it it looks at the Microsoft Dynamics AX Configuration  Utility Original Installation (AOS1) and fails.

Question: Is there a way around this for a multiple user/multiple AOS environment?

Thanks.

*This post is locked for comments

I have the same question (0)
  • Pfk Profile Picture
    Pfk 185 on at

    Hi, we have sort of the same situation. We have to AXC-files pointing to different environments, TEST and DEV. When clicking AXC-files directly, logged in as the user who installed, admin, one gets to different environments but when logged in as a normal user one always comes to the first, original environment. Would be nice to know if you find a reason. The terminal server is 2012. I wonder if that has something to do with it.

  • Community Member Profile Picture
    Community Member on at

    Hi PFK, for that issue you can use this:

    axwonders.blogspot.co.uk/.../deploy-ax-2009-from-terminal-services.html

    Rather than pointing directly to the AXC file we pull it in using a command line argument when starting AX.

    The problem we have is that when attaching files etc AX goes back to the original configuration when it was first installed on the server, not the one specified in the AXC.

  • Suggested answer
    Community Member Profile Picture
    Community Member on at

    Can you give us more detail about "Generate from template".  Because, the first question is "Why Generate from Template use the original config instead of the active config?".

    Workaround would be :

    When you installed the client first, did you store the config in the registry or you used an AXC file.

    If the original configuration is store in the registry, you can change it using regedit:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Dynamics\6.0\Configuration\Original (installed configuration)

    If the configuration is original config is store in an AXC file, well... just modify the AXC file :)

  • Community Member Profile Picture
    Community Member on at

    Hi, thanks for the replies everyone.

    We did get around the issue by editing the Original config in registry to point to an AOS that had all our users setup on.

    This will be ok when we go to our Production platform as there will be ONE environment (AOS) and this will be the original config.

    The problem was in our Testing and backup environments where users would log in to a Terminal server that had client setups to a number of environments:

    e.g: We have a terminal server with configs for environments 1/2/3/4/5 and environment 1 is setup as the original config. A user logs in to the server and accesses environment 3 (using the AXC for environment 3), all ok until they need to access a feature (one we found was where we call an invoice template within AX from sharepoint) at this point AX looks to the original config in registry rather than using the config the client is currently logged in on.

  • Pfk Profile Picture
    Pfk 185 on at

    Hi, we had serious problems with getting in to the "Original configured" environment as I wrote about earlier. Even if I clicked PROD I got into TEST. At last I found out that it was caused by File Association in Windows. AXC-files was recognized as AXC-file and opened with Dynamics AX Client. That is wrong. It should be recognized as a Dynamics AX Configuration. When that was fixed it all worked as expected. 

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 AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans