Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Hi everyoneCurrently, I have two environments: one test and the production environment. Both run on their own hardware and use a dedicated AOS instance. Now I need a second test environment for things like patch testing and migration testing. The question is whether I can install a second, separate database under the same AOS server I use for test to achieve this goal. Or will I need to install a third AOS instance?If it is possible, is there a guide or instructions somewhere on how to do it? Thank you for your time!YoursAbaw
you should create new AOS, you may wana restore the production database to newly test instance. you also need to copy the AOD, ald files (ax2009 only) if you have customizations in productions systems.
that way you can create the replica of production system for all your testing.
When you run the setup and install a second AOS on the same server, this is allowed. It will use another port number for communication. So it will propose 2713 as 2712 already might is used.
Then if you have customizations you can copy the application folder like Amir mentioned.
Be aware that both AOS servers need to share the hardware resources and might respond slower.
So, in short. Running with one AOS to run multiple test environments on will not work for my purpose?
It do will work. you can setup multiple instances. The connection difference is in the port number then. I tought my previous reply was quit clear about that.
As you need a second test environment for things like patch testing and migration testing, it will good to use a new system/hardware, As suggested by André system might have performance issues and you might end up with installing the patch on both AOS by mistake.
You could use two databases with a single AOS, but the AOS can obviously point to just one database at time. You would have to stop the AOS, reconfigure it to use another database and start it again.
If you want to use the same database simultaneously, you need two AOS services.
Business Applications communities