Add another AOS after VM clone

(0) Share

Report

Posted on by Community Member

Hello Everyone,

I am looking into adding another AOS into our setup. We have the licenses available to add another AOS in our setup, but I am looking for what I would need to change in AX to make it a second or Third AOS? Just the name, and whatever characteristics like batch, WAX, or customization specific? I checked out the Installation guide, but that doesn't really apply since I'm trying to match versions and hotfixes by cloning the VM to somewhat bypass all that trouble. Thanks for any help.

Pat Kwelty

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (2)

Verified answer

BorisD 2,826 Moderator on at

Like (0)

Report

Hello Kwelty,

go to System administrator > Setup > System > Cluster configuration. Add the new AOS to the cluster for load balancing.

Go to System administrator > Setup > System > Server configuration here you can select which one you would like to be your batch server.

In the Batch server group, select groups you want the server to handle.

Additional details are available at link below.

https://technet.microsoft.com/en-us/library/hh397322.aspx

https://technet.microsoft.com/en-us/library/dd362041.aspx

Was this reply helpful? Yes No
M P 285 on at

Like (0)

Report

We are looking for this option to make additional AOS much faster. Can you share experience if you have already done this?

Was this reply helpful? Yes No
M P 285 on at

Like (0)

Report

Hi Boris,

Can you share steps?

1. Stop Source AOS Server services

2. Clone Source AOS Server

3. Start New AOS Server services

4. Configure Cluster config and Batch server group

Using this steps, the system can sense this new AOS server?

Was this reply helpful? Yes No
BorisD 2,826 Moderator on at

Like (0)

Report

Hello M P,

This is correct, once you see it show up in Server Config and Cluster Config, that means the system is recognizing it as an additional AOS.

Last step would be to add it as a additional AOS on the AX Client Config and save the new config so that you can point users to it.

Was this reply helpful? Yes No
M P 285 on at

Like (0)

Report

Hi Boris,

We initially plan to remove the AX Component after the clone, which will give us more time to do it.

So from your point, we can just tweak AX settings + client AXC and that was it =)

Not sure if there are other fellow AX guys already done this, but its worth to test.

Was this reply helpful? Yes No
BorisD 2,826 Moderator on at

Like (0)

Report

Hello M P,

That is correct, It should work. As you said it would be nice to hear from someone who actually done this before. On paper this should work. You might want to post it as a new question to get more feed back from others.

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (1)

Report
This did work. With some research you have to arguably run sysprep after you clone the VM to get a unique SID. It's apparently not a big deal/requirement unless you're using the server as a DNS Server in addition to an AOS. Why you would do that I have no idea, but I just wanted to put that out there. The SID is a unique identifier that AX uses for users, but may use for other AOSes. I am not sure how impactful this is if you don't run Sysprep.

Ideally the steps would be:

Ensure your licensing is valid and can handle another AOS in the environment.

Clone Server

Remove Network cable so it doesn't connect to network and conflict with the original.

Turn on VM

Set AOS Service to manual if it isn't already and turn it off.

Run Sysprep

Rename Server

Change IP Address

Configure DNS with new name

Create new configuration file

If you cloned a Batch server, ensure that didn't come over as well. It shouldn't, but CYA.

And as Boris stated above, Check Server and Cluster Configurations to ensure everything is good.

Was this reply helpful? Yes No