cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Not a customer? Start a free trial

Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.

AppDynamics customers and established members should click the sign in button to authenticate.

NET (Agent, Installation)

Upgrade .Net Agents

Riyaz.Shaik
Creator

Upgrade .Net Agents

We have 100+ .net agents (version 4.3.2.1) in our PROD environment.

What is the best practice to upgrade them all in one shot to latest version (4.5.12.0)?

By replying you agree to the Terms and Conditions of the AppDynamics Community.
Upgrade .Net Agents
3 REPLIES 3
Gunnar.Svanberg
Architect

We'll " it depends" (-:

 

I assume you are talking about the msi package and not .NET core.

We are using native tools like SCCM (Windows) and RedHat Satelite (Linux), to provision a new version twice a year. Sadly though it requires an IIS restart/reset which will mean downtime. So would have to make sure that the package you deploy also does that. Apart from that our windows SME's seems happy abbout the way the msi is packaged. An upgrade *should* not mess with the XML config file.

 

Unlike other vendors AppD does not have a solid auto upgrade feature built in.

Sure you want to go 4.5.12 and not 4.5.16?

 

/Gus

 

 

 

Riyaz.Shaik
Creator

Thank you Gunnar.

What is the difference between msi package & .NET core?

What are new/fixes in 4.5.16 than 4.5.12?

May I know the upgrade path from
a) 4.5.12 to 4.5.16?
b) 4.3.2.1 to 4.5.16?

Gunnar.Svanberg
Architect

For .NET core (I mean without framework) you have to include the agent in the build process of your application. Ther's no "real" installation task.

 

As for the upgrade process it's pretty straight forward. Just chose upgrade. all of AppD's agents can be installed as upgrades on pretty most any previous version. If you have really really old agents there might be issues since I remember that they changed the config from web.config to it's own xml config file but that was a long time ago.