cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

Best practice for maintaining 6.1 agents on 6.2 server upgrade?

jared_kemp
Organizer

We are looking to upgrade our main server and collector to 6.2 but have some agents that are on an IIS 6 server. I understand we should be able to turn off bootstrapping for those agents to prevent upgrade to 6.2 which does not support IIS6.

My questions are as follows:

1. Should we update all agents to the newest 6.1.0.XXXX fixpacks before doing the upgrade or is there a preferred version to be on?

2. Will there be future updates to older versions like 6.1? If yes, how do we keep track of those if our main server is 6.2?

3. Is it accurate to say this setup is not supported?

4. Are their plans to phase out connectivity with 6.1 agents entirely from 6.2?

1 REPLY 1

markus_baumgart
Dynatrace Advisor
Dynatrace Advisor

Generally, maintaining 6.1 agents on a 6.2 server is not a best practice.

1. Either latest fixpack or the version you have used successfully before.

2. There will be 6.1 fixpacks (to be installed on 6.1 servers), but you can't roll them out if you are on a 6.2 server already. You have to extract the updated 6.1 agent from the fixpack and replace the file manually. Should a fix related to the 6.1 agent be needed on the collector or server, it can't be done.

3. The 6.1 part of the setup will be unsupported. The decisive version for support is the version of the server. As you are upgrading the server to 6.2 and 6.2 does not support IIS6, it is unsupported. Among the reasons for that is that we don't test 6.2 with IIS6 anymore and that we can't apply fixes for 6.1 on a 6.2 server, as described above.

4. No. But it is still recommended to upgrade IIS ASAP. Even Microsoft doesn't support IIS6 (Windows Server 2003) anymore.