Notifications
Announcements
No record found.
Hello All,
We have AX 2012 R1 in Production and currently testing R3. Is there a way to have both clients running locally on testers machines?
thank you
*This post is locked for comments
if you want to install two clients on same machine, NOT Possible. R3 or R2 both are AX2012.
yes if you want user to access sometimes R3 and sometimes R1, from same machine, this is POSSIBLE.
keep client kernel version as of R3 and save two configurations/shortcuts at desktop. one shortcut will refer to R3 AOS. while other shortcut will refer to R1 shortcut.
Note: there may be any inconsistencies while using R3 Client to R1 AOS. Not sure what it could be but possibility is there as kernel has been update many times since arrival of R1 to R8 CU9
I've not tried this with AX 2012 but in the past I've had systems with AX 3, AX4 and AX 2009 clients all on the same machine. Here's how we did that...
Hi Sohaib,
can you please confirm, that you successfully connected an 2k12R3 client against an 2k12R1 AOS.
I don't think that it is possible.
regards
Douglas
Not really. you are right in this context.
as 'having different kernel version' is something else than a 'client version'. Client version is installed with setup which is different for each version.
Hi Malcolm,
having done this exactly as you described. But you should keep in mind for 2012:
We normally use this workaround to simply test some things using good old 2009 RPC Ax32.Exe functionality (within the same release (R01/2/3) of 2012) . But you will run in trouble, if you want to cross over the 'R -Line' of 2012.
Only some input:
You can use Virtual Apps (seamless running Ax32.Exe) on different RDP Servers for that.
At least one for R1, one for R2, and one for R3 (it's better to have two for R3, due to the heavy changes in R3CU8(VStudio, ReportViewer) - should in my opionion be named R4 )
We can use this to connect to a lot of different "Test"/Development AOS Servers.
On Each of the 4 VirtualApp Servers
R1, R2, R3<CU8, R3>=CU8 we use your specified 'ClientCopy ' for holding some different Ax32.Exe client kernel versions (related to this Release R123(4) ) only. The kernel versions are as high as possible, and before updating them, we copy the old client to a new directory.
So we use always a higher or equal client binary versions as the connected AOSses. (Multiple configurartions)
Holding each of the old clients in a separate directory available, give us the chance and possibility to test RPC based issues (related to different binary versions of the AOSses) with some of the copied "old" Client.
Hi guys,
something (maybe important) forgotten in my descrption:
Before installing the new client kernel on the RDP server, beside copying the whole client directory we additionally back up the all AX assemblies from GAC, to this kernel dependant 'old'-folder. So we have access, if we really need this, to even these things.
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.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Martin Dráb 4 Most Valuable Professional
Priya_K 4
MyDynamicsNAV 2
