• Forums
    • Public Forums
      • Community Connect
      • Dynatrace
        • Dynatrace Open Q&A
      • Application Monitoring & UEM
        • AppMon & UEM Open Q&A
      • Network Application Monitoring
        • NAM Open Q&A
  • Home /
  • Public Forums /
  • Application Monitoring & UEM /
  • AppMon & UEM Open Q&A /
avatar image
Question by Jared K. · Sep 17, 2015 at 06:51 PM · agent server collector migration iis

Best practice for maintaining 6.1 agents on 6.2 server upgrade?

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?

Comment

People who like this

0 Show 0
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

1 Reply

  • Sort: 
  • Most voted
  • Newest
  • Oldest
avatar image
Best Answer

Answer by Markus B. · Sep 18, 2015 at 02:08 PM

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.

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

How to get started

First steps in the forum
Read Community User Guide
Best practices of using forum

NAM 2019 SP5 is available


Check the RHEL support added in the latest NAM service pack.

Learn more

LIVE WEBINAR

"Performance Clinic - Monitoring as a Self Service with Dynatrace"


JANUARY 15, 3:00 PM GMT / 10:00 AM ET

Register here

Follow this Question

Answers Answers and Comments

10 People are following this question.

avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image

Related Questions

Roadmap to Azure App Service monitoring for AppMon 6.5 and classic .net Windows Data Center Edition agent owners

Instrumentation Issue: Why Application Servers are not configuring, while the webservers for the same machines are configuring?

Sensor information found on unexpected Agent Group class cache

Training Guidance, Tips ( Words of Wisdom), or Documentation

Dynatrace AppMon Components Migration

Forum Tags

dotnet mobile monitoring load iis 6.5 kubernetes mainframe rest api dashboard framework 7.0 appmon 7 health monitoring adk log monitoring services auto-detection uem webserver test automation license web performance monitoring ios nam probe collector migration mq web services knowledge sharing reports window java hybris javascript appmon sensors good to know extensions search 6.3+ server documentation easytravel web dashboard kibana system profile purelytics docker splunk 6.1 process groups account 7.2 rest dynatrace saas spa guardian appmon administration production user actions postgresql upgrade oneagent measures security Dynatrace Managed transactionflow technologies diagnostics user session monitoring unique users continuous delivery sharing configuration alerting NGINX splitting business transaction client 6.3 installation database scheduler apache mobileapp RUM php dashlet azure purepath agent 7.1 appmonsaas messagebroker nodejs 6.2 android sensor performance warehouse
  • Forums
  • Public Forums
    • Community Connect
    • Dynatrace
      • Dynatrace Open Q&A
    • Application Monitoring & UEM
      • AppMon & UEM Open Q&A
    • Network Application Monitoring
      • NAM Open Q&A